Clients suddenly cannot connect to 2602 connected to WLC 2504

[Cormac Champion]

Hi all,

I have updated my controllers (N+1) to 8.5.171.0 after hitting the certificate expiry bug recently, and set config ap cert-expiry-ignore.  I believe it was all working fine for a few days at least.  It appears that clients are connecting to the SSID but not getting an IP Address by DHCP.

What is my best debug commands to run to see as to what is going on (on both the WLC and on the Lightweight AP's) ?  Just now, the Network Summary shows one client - but when I click on the number 1, it says there are no clients connected.

I'm really at a loss to understand as to what is happening, so I would be very grateful for any assistance to solve my issues.

[marce1000]

 - Have a sanity check on the current controller configuration with : https://cway.cisco.com/tools/WirelessAnalyzer/  also have client-mac debugging session for the problematic devices which you can have analyzed with https://cway.cisco.com/tools/WirelessDebugAnalyzer/

 M.

[Cormac Champion]

Loaded but did nothing and just came back with the prompt to load it

[marce1000]

 - May depend on the output-format, either upload running-config with tftp , or output of show run with prompting disabled.

 M.

[xaxa]

This seem like a bug.After upgrade wlc from 8.3.150.0 to 8.5.171.0. I have same symptom with two 3802E AP. Clients traffic randomly disconnect to the APs without any significant log(client wireless signal keep associated with aps).I do some base actions:

1.Can't ping gateway

2.Can't browse web

3.reassociated to the aps,Client get address 169.254.x.x,don't receive dhcp offer message.

4.debug on wlc:debug dhcp message enable , debug dhcp client xx.no information available.

I do a downgrade to 8.2.166.0 yesterday,and hoping to get back to normal.I get some bug reports for you reference:CSCvt22353,CSCvc67005,CSCvv78719,There have some similar symptom in the reports.

[Hurricane Wheatbread]

Also experiencing this issue on 8.5.171.0, client traces I have run in my environment point to CSCvv78719.

I am currently waiting for TAC to verify that the recently released 8.5.182.0 has a permanent fix for the issue (the bug report describes a situation where the AP will detect that the error is occurring and reset it's radio causing 20 seconds of wireless outage).