Wifi users always get disconnected - how to start troubleshooting

[s.lachica]

Hi Everyone,

Need support, i'm originally an RnS support, anyone who can suggest how to nail down which is the problem on a wifi issue. Customer reports that wifi users always get disconnected. Any suggestion to start the troubleshooting is much appreciated.

Thanks,

Sonny

[Sandeep Choudhary · Accepted solution]

Provide the WLAN info. From WLC:

sh WLAN <I'd >

debug capwap <MAC address >

Regards

[s.lachica]

Hi Sandeep,

Thanks for this useful info.

I have not got my hands yet on the equipment, but the logs sent by the admins include these logs:

*spamApTask2: Nov 17 13:32:56.592: #LWAPP-3-REPLAY_ERR: spam_lrad.c:37704 The system has received replay error on slot 0, WLAN ID 1, count 1 from AP 58:97:bd:83:7c:20

*spamApTask3: Nov 17 13:31:47.040: #LWAPP-3-REPLAY_ERR: spam_lrad.c:37704 The system has received replay error on slot 0, WLAN ID 1, count 61 from AP e4:aa:5d:19:c8:70

*spamApTask2: Nov 17 13:30:56.606: #LWAPP-3-REPLAY_ERR: spam_lrad.c:37704 The system has received replay error on slot 0, WLAN ID 1, count 2 from AP 58:97:bd:83:7c:20

*spamApTask3: Nov 17 13:29:47.053: #LWAPP-3-REPLAY_ERR: spam_lrad.c:37704 The system has received replay error on slot 0, WLAN ID 1, count 4 from AP e4:aa:5d:19:c8:70

*RRM-CLNT-5_0: Nov 17 13:29:15.093: #RRM-3-RRM_LOGMSG: rrmClientProc.c:691 RRM LOG: Airewave Director: Unable to set channel 0[20] on the on AP  E4:AA:5D:19:C8:70(1)

*RRM-CLNT-5_0: Nov 17 13:29:15.093: #RRM-3-RRM_LOGMSG: rrmChanUtils.c:617 RRM LOG: Attempt to set invalid channel 0 on AP  E4:AA:5D:19:C8:70(1)

*spamApTask6: Nov 17 13:26:57.122: #LWAPP-3-REPLAY_ERR: spam_lrad.c:37704 The system has received replay error on slot 0, WLAN ID 1, count 5 from AP 58:97:bd:44:ef:70

*spamApTask4: Nov 17 13:26:36.777: #LWAPP-3-REPLAY_ERR: spam_lrad.c:37704 The system has received replay error on slot 0, WLAN ID 1, count 6 from AP 58:97:bd:80:5e:50

Any obvious information I can get from here?

Thanks,

Sonny

[Sandeep Choudhary]

Not so much info I got from these logs.

I can only say......

1. The first thing I would look at is the WLAN. Makes sure WPA2/AES is the only think checked, not WPA or TKIP. Use either WPA + TKIP or WAP2+ AES.

2. fast-ssid must be enabled...

3. Upgrading the driver on the client is another thing that might help

Regards

Dont forget to rate helpful posts

[s.lachica]

We found out the issue. This was because of a universal AP domain/region and settings. Priming required to change this settings. This case was already solved. Thanks everyone!

Please refer to this short documentation:

• Before any action taken, the two Cisco 2702I APs installed have LED light cycling through red, green and off.
• The status of the two APs can also be seen on the WLC they’re connected to 

Priming Requirements

A universal access point can get primed in two ways:

• Manual Priming, using the Cisco AirProvision mobile application
• Automatic Priming, through Cisco Neighbor Discovery Protocol (NDP) message propagation in the RF neighborhood.

Action taken

One of the Cisco 2702I universal access points will be primed. After the first AP has been successfully manually primed, then the other universal AP in the RF neighborhood can get primed via Automatic Priming.

Manual Priming

• A new WLAN on WLC was created. This WLAN was able to reach the management IP of the controller.
• A new custom AP group has been created to which only the SSID of the WLAN recently created is added.
• The newly created AP group was added on the universal access points.
• The Cisco AirProvision app is downloaded on the smartphone.
• The smartphone with AirProvision app is connected to the SSID created.

Cisco AirProvision uses the geographical location of the smartphone on which it is running, to decide on the regulatory domain for priming the AP.

• Upon successfully logging into the universal AP via Cisco AirProvision, the Configured button was tapped. Then the AP's status LED blinks Green for 15 seconds.
• After booting, the first AP primed had a stable blue light.

Automatic Priming

• When the first AP has been successfully primed, the second Cisco 2702I AP automatically primes. This is evident on its LED light which blinks with white light. This means that it is priming via Cisco NDP.
• After booting, the AP had a stable blue light.

 Final AP Status

If the AP is already configured correctly based on the location of the smartphone, it will be verified using the Cisco AirProvision on the smartphone. The Configure and Audit buttons will be disabled with the message 'Universal AP is configured correctly'.

The priming can also be verified with the observed LED light of the access points and their status viewed on the WLC they are connected to.