Solved: Re: WLC5520 8.5.140 - 2800 AP, Channel Width 40Mhz, but APS broadcasting 80Mhz

craiglebutt · ‎08-22-2019

Currently running new WLC 5520 on above code.

Channel Width is set to 40MHz and DCA using 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140

But for some reason APs are broadcasting on 80MHz and 160MHz

Can't see any thing obvious,

Local Automatic Channel Assignment
Channel Assignment Mode........................ AUTO
Channel Update Interval........................ 600 seconds
Anchor time (Hour of the day).................. 0
Update Contribution
    Noise........................................ Enable
    Interference................................. Enable
    Load......................................... Disable
    Device Aware................................. Enable
CleanAir Event-driven RRM option............... Enabled
CleanAir Event-driven RRM sensitivity.......... Medium
CleanAir Event-driven RRM Rogue Option......... Enabled
CleanAir Event-driven RRM Rogue Duty Cycle..... 80
Channel Assignment Leader...................... ************** **.**.**.**.
DCA Sensitivity Level.......................... HIGH (5 dB)
DCA 802.11n/ac Channel Width................... 40 MHz
DCA Minimum Energy Limit....................... -95 dBm
Channel Energy Levels
    Minimum...................................... -81 dBm
    Average...................................... -79 dBm
    Maximum...................................... -65 dBm

Channel Dwell Times
    Minimum...................................... 0 days, 04 h 13 m 22 s
    Average...................................... 10 days, 01 h 52 m 07 s
    Maximum...................................... 64 days, 09 h 05 m 42 s
802.11a 5 GHz Auto-RF Channel List
    Allowed Channel List......................... 36,40,44,48,52,56,60,64,100,
                                                  104,108,112,116,120,124,128,
                                                  132,136,140
    Unused Channel List..........................
DCA Outdoor AP option.......................... Enabled

Leader Automatic Channel Assignment
Channel Assignment Mode........................ AUTO
Channel Update Interval........................ 600 seconds
Update Contribution
    Noise........................................ Enable
    Interference................................. Enable
    Load......................................... Disable
    Device Aware................................. Disable
DCA Sensitivity Level.......................... HIGH
    Allowed Channel List......................... 36,40,44,48,52,56,60,64,100,
                                                  104,108,112,116,120,124,128,
                                                  132,136,140

craiglebutt · ‎10-03-2019

Just an update incase anyone else comes across this.

It is a bug CSCvp64704 causing the issue https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvp64704/?reffering_site=dumpcr

View solution in original post

Rasika Nayanajith · ‎08-22-2019

Pls post "show advanced 802.11a summary" to see

HTH

Rasika

craiglebutt · ‎08-22-2019

Hi

Copied and pasted a few,
Looked on prime, even though says global config, is set to 80mhz, resetting to custom and change it to 40Mhz, then go back in to change to global, seems to stay at 40Mhz, just need figure out why it is doing it and how to change globally.

AP Name MAC Address Slot Admin Oper Channel TxPower
-------------------------------- ----------------- ---- -------- ----------- ------------------ -------------
Name-LIBRARY-LVL0-AP02 6c:8b:d3:a1:fa:a0 1 ENABLED UP (36,40)* *1/6 (17 dBm)
Name-CARDIC_BRU-LVL0-AP02 6c:8b:d3:ac:79:a0 1 ENABLED UP (64,60)* *1/6 (17 dBm)
Name-CARDIC_BRU-LVL0-AP01 6c:8b:d3:a2:05:c0 1 ENABLED UP (132,136)* *2/8 (20 dBm)
Name-CARDIC_BRU-LVL1-AP02 6c:8b:d3:a2:1a:80 1 ENABLED UP (36,40)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-PHARMACY-AP03 6c:8b:d3:a1:f7:00 1 ENABLED UP (132,136)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-PHARMACY-AP04 6c:8b:d3:ac:71:e0 1 ENABLED UP (100,104,108,112)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-PHARMACY-AP05 6c:8b:d3:95:d1:00 1 ENABLED UP (52,56,60,64)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-PHARMACY-AP06 6c:8b:d3:a2:06:60 1 ENABLED UP (132,136)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-PHARMACY-AP02 6c:8b:d3:99:09:80 1 ENABLED UP (36,40,44,48)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-PHARMACY-AP01 6c:8b:d3:ac:7c:40 1 ENABLED UP (100,104)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-PATHOLOGY-AP01 6c:8b:d3:95:cf:a0 1 ENABLED UP (56,52)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-PATHOLOGY-AP02 6c:8b:d3:95:d0:a0 1 ENABLED UP (132,136)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-PATHOLOGY-AP03 6c:8b:d3:ac:76:80 1 ENABLED UP (36,40,44,48)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-PATHOLOGY-AP05 6c:8b:d3:99:0c:80 1 ENABLED UP (112,108)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-LIFT_LOBBY-AP01 6c:8b:d3:a2:5c:20 1 ENABLED UP (132,136)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-MORTUARY-AP01 6c:8b:d3:ac:8f:40 1 ENABLED UP (36,40,44,48)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-PATHOLOGY-AP04 6c:8b:d3:95:d1:c0 1 ENABLED UP (132,136)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-UOL-AP02 6c:8b:d3:b6:0c:60 1 ENABLED UP (36,40,44,48)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-UOL-AP03 6c:8b:d3:ac:8e:20 1 ENABLED UP (132,136)* *1/8 (23 dBm)
Name-MAIN_B-LVL0-UOL-AP05 6c:8b:d3:b5:fa:c0 1 ENABLED UP (64,60)* *1/6 (17 dBm)
Name-MAIN_B-LVL0-UOL-AP07 6c:8b:d3:95:ce:40 1 ENABLED UP (100,104)* *1/8 (23 dBm)

cheers

Rasika Nayanajith · ‎08-22-2019

Check under WLC DCA setting & make sure it is set to 40MHz. Also check what interval DCA channel changes are configured.

Once that DCA channel change interval reached, check it out again.

Still if you see weird behavior, reach TAC

HTH

Rasika

Leo Laohoo · ‎08-22-2019

Raise a TAC Case. That looks like a bug.

craiglebutt · ‎09-06-2019

Thanks for reply's.

I missed out the 5520 is in a RF Group with a 8510, the 8510 is on 8.0150 and is the RF Leader.

Just separated them and tested, took long than thought but when the 5520 was it's own leader, everything seem to go back to what it should be.

So issue seems to be between the issue of the 5520 on 8.5.140 and the 8510 on 8.0.150, but can't sperate at the minute as 2 massive sites and still require full roaming.

cheers

patoberli · ‎09-06-2019

You maybe can solve it with an AP group on the 5520. Create a group, put 1-2 APs for testing in it and set the channel width to 40 MHz. With some luck the calculation will be done separately for that group.

craiglebutt · ‎09-06-2019

cheers, I've split most of the APs in to AP Groups already but still affected.

TAC have come back saying need to upgrade 8510, but can't at the minute as couple hundred 1240 and 1140 still migrating, so APs on both new and old wlc in the middle of buildings, could separate the RF grouping then that will cause more issue.

cheers

Flavio Miranda · ‎09-06-2019

Hi

Do you have RF profile on the WLC and is it on the AP group? RF profile overwrite global config and that´s what it is used for, actually.

If RRM on the global config is 40 but on the RF profile is 80, AP will use 80.

-If I helped you somehow, please, rate it as useful.-

craiglebutt · ‎09-10-2019

Hi

Tried that, didn't work. Need to consult with customer and see what TAC comes back with, still got 3 moths to completely migrated APs

cheers

craiglebutt · ‎10-03-2019

Just an update incase anyone else comes across this.

It is a bug CSCvp64704 causing the issue https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvp64704/?reffering_site=dumpcr