Re: All WLAN APs stuck in Channel 1*

derobbacher · ‎10-31-2019

Hello Cisco WLAN experts,

recently I have noticed that on one of our Wism2-WLCs running 8.3.141 all WLAN APs

are configured by RRM to use Channel 1* in 802.11b-WLAN:

What might be worng ?

How can I easily start RRM all over to calculate a new deployment to use channel 1 and 6 and 11 finally ?

I have tried to start all-over using:

config 802.11b channel global restart

But it seems to me that RRM seems to remain in Startup somehow even after several hours.

(WiSM-slot22-1) >show advanced 802.11b channel

Leader Automatic Channel Assignment
Channel Assignment Mode........................ AUTO
Channel Update Interval........................ 600 seconds [startup]
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 Contributio.... Disabled
Channel Assignment Leader...................... WISM2_193_3_KNE (10.241.230.103) (::)
Last Run....................................... 582 seconds ago
Last Run Time.................................. 0 seconds

DCA Sensitivity Level: ...................... STARTUP (5 dB)
DCA Aggressive Remaining Cycle................. 5 (50 minutes)
DCA Minimum Energy Limit....................... -95 dBm
Channel Energy Levels
Minimum...................................... -86 dBm

    Average...................................... -72 dBm
    Maximum...................................... 13 dBm
Channel Dwell Times
    Minimum...................................... 0 days, 01 h 07 m 14 s
    Average...................................... 21 days, 01 h 58 m 47 s
    Maximum...................................... 293 days, 20 h 39 m 35 s
802.11b Auto-RF Allowed Channel List........... 1,6,11
Auto-RF Unused Channel List.................... 2,3,4,5,7,8,9,10,12,13

The WLC is the RRM-Leader for 802.11b but does not show any Current AP number:

(WiSM-slot22-1) >show advanced 802.11b group

802.11b Radio RF Grouping
RF Group Name.................................. ukw1
RF Protocol Version(MIN)....................... 101(30)
RF Packet Header Version....................... 2
Group Role(Mode)............................... LEADER(AUTO)
Group State.................................... Idle
Group Update Interval.......................... 600 seconds
Group Leader................................... WISM2_193_3_KNE (10.241.230.103) (::)
Group Member
................................. WISM2_193_3_KNE (10.241.230.103)
Maximum/Current number of Group Member......... 20/1
Maximum/Current number of AP................... 2000/0
Last Run....................................... 108 seconds ago

(WiSM-slot22-1) >show advanced 802.11b monitor

Default 802.11b AP monitoring
802.11b Monitor Mode........................... enable
802.11b Monitor Channels....................... DCA channels
802.11b RRM Neighbor Discovery Type............ Transparent
802.11b RRM Neighbor RSSI Normalization........ Enabled
802.11b AP Coverage Interval................... 90 seconds
802.11b AP Load Interval....................... 60 seconds
802.11b AP Monitor Measurement Interval........ 180 seconds
802.11b AP Neighbor Timeout Factor............. 20
802.11b AP Report Measurement Interval......... 180 seconds

(WiSM-slot22-1) >show advanced 802.11b summary
Leader RRM Information
----------------------

Member RRM Information
AP Name                          MAC Address       Admin    Oper        Channel    TxPower
-------------------------------- ----------------- -------- ----------- ---------- -------------
ZIM-AP418                        00:25:84:24:57:70 ENABLED UP          1*         *1/7 (17 dBm)
KFR-AP34                         1c:6a:7a:b5:9c:d0 ENABLED UP          1*         *1/6 (16 dBm)
ZIM-AP228                        00:25:84:24:eb:e0 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP324                        00:25:84:24:bb:80 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP256                        00:25:84:24:bf:20 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP368                        00:25:84:24:53:c0 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP410                        00:25:84:24:55:80 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP260                        a4:56:30:8e:f5:b0 ENABLED UP          1*         *2/7 (14 dBm)
ZIM-AP289                        cc:d5:39:64:f2:20 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP404                        00:25:84:24:53:f0 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP315                        cc:d5:39:65:79:80 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP443                        00:25:84:24:e9:70 ENABLED UP          1*         *1/7 (17 dBm)
ZIM-AP304                        00:25:84:24:b8:90 ENABLED UP          1*         *1/7 (17 dBm

What is wrong here ?

Thank You for any help in advance

Greetings from Frankonia

Wini

Sandeep Choudhary · ‎10-31-2019

if you see star on channel number means its a global assignment.

Now come to your quetsion reagrding having the same channel:

1. DCA must be set to automatic.

2. If APs coverage area are not overlaping then it will not be an issue if they are on same channel.

Regards

Dont forget to arte helpful posts

Leo Laohoo · ‎10-31-2019

8.3.141.0 is a very, very old release.
I'd recommend upgrading to something more recent.
The above behaviour looks like a bug.

derobbacher · ‎11-07-2019

Hello,

I can tell that the Situation has been improved now.

We found out that the Wism2-High-Availability was broken between the two modules in a VSS.

One of the modules was found in factory-default, while the secondary WisM2 had taken over all APs

and calculated them all in channel 1.

On this unit, also a Memory Problem was visible, which disappeared after a reload and new Setup

after recovery of the broken WiSM2 and reactivating of the SSO-Setup.

Sorry about all this old Hardware and Software. But we still are running on 1142 WLAN APs partly.

New 9800 are already in place, but I have no clue how to configure all this new DNA-stuff.

I think it is time for retirement before diving into this new intention-based world of Cisco.

Kind regards

Wini