wlc5508 update to 8.5.171 ap-3802 have bug

[willwillwang]

Since upgrading to 8.5.171, I have restarted two APS this week to solve the problem

When using 8.5.161, this problem does not exist at all

I'm considering whether to go back to 8.5.161.6 

log is the zip file

[patoberli]

I haven't checked your zip file and you also haven't written which bug you actually encounter. 

In any case, there is an update to 8.5.171.0 out: https://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn85mr8.html

[marce1000]

                   - FYI : https://cway.cisco.com/wireless-debug-analyzer/

  You can input your debug file in the tool mentioned above , not seen problems at first glance :

00:db:df:d4:35:a5

Connection 1 of 2

•  
•  
• 1
• 2
•  
•  

---

Show Time

Show Task

Show Translated

Show Original

Show Prior First Connection

Show All

---

TimeTaskTranslated

Nov 02 14:42:25.577	*apfMsConnTask_3	Client made new Association to AP/BSSID BSSID 80:e0:1d:4c:3a:0b AP AP-42-HQ-chanyan-inside
Nov 02 14:42:25.579	*apfMsConnTask_3	The WLC/AP has found from client association request Information Element that claims PMKID Caching support
Nov 02 14:42:25.579	*apfMsConnTask_3	The Reassociation Request from the client comes with 0 PMKID
Nov 02 14:42:25.579	*apfMsConnTask_3	The Reassociation Request from the client comes with 0 PMKID
Nov 02 14:42:25.580	*apfMsConnTask_3	Client is entering the 802.1x or PSK Authentication state
Nov 02 14:42:25.581	*apfMsConnTask_3	WLC/AP is sending an Association Response to the client with status code 0 = Successful association
Nov 02 14:42:25.584	*Dot1x_NW_MsgTask_5	Client will be required to Reauthenticate in 0 seconds
Nov 02 14:42:25.584	*Dot1x_NW_MsgTask_5	WLC/AP is sending EAP-Identity-Request to the client
Nov 02 14:42:25.616	*Dot1x_NW_MsgTask_5	WLC/AP is sending EAP-Identity-Request to the client
Nov 02 14:42:25.647	*Dot1x_NW_MsgTask_5	Client sent EAP-Identity-Response to WLC/AP
Nov 02 14:42:25.772	*Dot1x_NW_MsgTask_5	RADIUS Server permitted access
Nov 02 14:42:25.773	*Dot1x_NW_MsgTask_5	Client will be required to Reauthenticate in 0 seconds
Nov 02 14:42:25.774	*Dot1x_NW_MsgTask_5	4-Way PTK Handshake, Sending M1
Nov 02 14:42:25.783	*Dot1x_NW_MsgTask_5	4-Way PTK Handshake, Received M2
Nov 02 14:42:25.784	*Dot1x_NW_MsgTask_5	4-Way PTK Handshake, Sending M3
Nov 02 14:42:25.788	*Dot1x_NW_MsgTask_5	4-Way PTK Handshake, Received M4
Nov 02 14:42:25.788	*Dot1x_NW_MsgTask_5	Client has completed PSK Dot1x or WEP authentication phase
Nov 02 14:42:25.789	*Dot1x_NW_MsgTask_5	Client has entered DHCP Required state
Nov 02 14:42:25.826	*DHCP Socket Task	Received DHCP request from client
Nov 02 14:42:25.827	*DHCP Socket Task	Sending DHCP Discover to DHCP Server CP through gateway 10.2.0.10 on VLAN selected relay 2 - 192.168.13.85 (local address 10.2.0.10, gateway 10.2.0.1, VLAN 200, port 13)
Nov 02 14:42:25.827	*DHCP Socket Task	Sending DHCP Discover to DHCP Server CP through gateway 10.2.0.10 on VLAN setting server from OFFER (server 192.168.215.2, yiaddr 10.2.4.21)
Nov 02 14:42:25.828	*DHCP Socket Task	Received DHCP offer from server and transmitting to client
Nov 02 14:42:25.888	*DHCP Socket Task	Received DHCP request from client
Nov 02 14:42:25.888	*DHCP Socket Task	Sending DHCP Request to DHCP Server CP through gateway 10.2.0.10 requesting 10.2.4.21 on VLAN sending REQUEST to 10.2.0.1 (len 382, port 13, vlan 200)
Nov 02 14:42:25.888	*DHCP Socket Task	Sending DHCP Request to DHCP Server CP through gateway 10.2.0.10 requesting 10.2.4.21 on VLAN sending REQUEST to 10.2.0.1 (len 382, port 13, vlan 200)
Nov 02 14:42:25.892	*DHCP Socket Task	Client has entered RUN state
Nov 02 14:42:25.892	*DHCP Socket Task	Received DHCP ACK, assigning IP Address 10.2.4.21
Nov 02 14:42:25.893	*DHCP Socket Task	Received DHCP ACK from DHCP server