Auto-tune fails and channel plan for BG does not generate when there is different hardware/MSS platform in a mobility-domain.
Auto-tune calculation fails and WLC shows the following errors:
APM_RF Jul 26 12:53:47.600395 ERROR AUTORF_ERROR: AutoRF process failed on BG band: reason 1
APM_RF Jul 26 10:44:47.508970 ERROR AUTORF_ERROR: AutoRF process failed on BG band: reason 1
APM_RF Jul 26 08:35:47.422971 ERROR AUTORF_ERROR: AutoRF process failed on BG band: reason 1
APM_RF Jul 26 06:26:47.324192 ERROR AUTORF_ERROR: AutoRF process failed on BG band: reason 1
This issue is due to the difference in WLC-8 and WLC-2 hardware. It is not recommended to configure both of them in a mobility-domain. The max cohort limitation set for FUGU(WLC8) and MISO(WLC2) is 4. While for other platforms, it is 16. Upon exceeding this limit, the AutoRF process fails and the above error messages are generated.
All auto-tune calculations such as the following are based on max_cohort value:
Generate the channel plan by disabling the mobility-domain and perform the AutoRF calculation individually on both the controllers.
Example: The following example shows that there is no channel plan created for 11BG
Test-WLC1# sh auto-tune channel verbose
Band: 11A
Last deployment: (channel plan applied at boot time)
Channel plan: ach_2016_07_16_174913_A.xml
Latest channel plan: ach_2016_07_17_1858_A.xml (2 hrs 1 min ago)
Details: run 7
Convergence Stage: Completed on Sun Jul 17 2016, 18:01 (duration 1 min)
Calculation Stage: Completed on Sun Jul 17 2016, 18:58 (duration 56 min 22 sec)
Band: 11BG
Last deployment: (no channel plan available at deployment time)
Latest channel plan: (none)
Details: run 0
The
file:ach_2016_07_16_174913_A.xml is seen in the autorf directory for 11A but not for 11BG band:
Test-WLC1# dir autorf/
=================================================================
file:
Filename Size Created
file:ach_2016_07_16_085127_A.xml 2740 bytes Jul 16 2016, 08:51:26
file:ach_2016_07_16_103226_A.xml 2740 bytes Jul 16 2016, 10:32:26
file:ach_2016_07_16_113326_A.xml 2740 bytes Jul 16 2016, 11:33:26
file:ach_2016_07_16_131426_A.xml 2740 bytes Jul 16 2016, 13:14:26
file:ach_2016_07_16_145423_A.xml 2740 bytes Jul 16 2016, 14:54:22
file:ach_2016_07_16_174913_A.xml 4036 bytes Jul 16 2016, 17:49:12
file:ach_2016_07_17_1445_A.xml 4612 bytes Jul 17 2016, 14:45:13
file:ach_2016_07_17_1858_A.xml 4468 bytes Jul 17 2016, 18:58:17
file:ach_2016_07_17_2101_A.xml 582 bytes Jul 17 2016, 21:01:15
Total: 27 KBytes used, 51 MBytes free
Ran the auto-tune to calculate and deploy, but still no progress:
Test-WLC1# run auto-tune calculate-deploy band 11bg
success: Calculation started...
Check "show auto-tune channel" for progress.
Test-WLC1# show auto-tune channel a band 11bg verbose
Band: 11BG
Last deployment: (no channel plan available at deployment time)
Latest channel plan: (none)
Details: run 0
Disabling the mobility-domain and performing AutoRF on both the controllers allowed to generate
'channel plan' on 11BG. If the mobility-domain is re-enabled, the channel plan for 11BG may have miscalculations. To avoid these issues, Juniper does not recommend to have different hardware/MSS platform in a mobility-domain.