Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Heartbeat timer expiring before AP completes code 5.2.193.0 upgrade

I have a few APs that will not complete the code upgrade process after the controller was taken to 5.2.193.0 When watching the debugs, the AP starts the image data process, reaches the data transfer done point and then the AP heartbeat expires. The DTLS session is torn down and eventually the whole process repeats itself. Does any one have idea of what's going on here? This has only occured with a small percentage of my APs....

2 REPLIES
Community Member

Re: Heartbeat timer expiring before AP completes code 5.2.193.0

Here's the Debug:

*Jul 27 16:03:49.070: 00:18:74:c7:fe:20 Image data Response from 192.168.245.226:43557

*Jul 27 16:03:49.070: 00:18:74:c7:fe:20 Image data transfer done

*Jul 27 16:04:17.581: 00:18:74:c7:fe:20 Heartbeat timer expired for AP 00:18:74:c7:fe:20

*Jul 27 16:04:17.581: 00:18:74:c7:fe:20 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 00:18:74:c7:fe:20 slot 0

*Jul 27 16:04:17.583: 00:18:74:c7:fe:20 apfSpamProcessStateChangeInSpamContext: Down LWAPP event for AP 00:18:74:c7:fe:20 slot 1

*Jul 27 16:04:17.585: 00:18:74:c7:fe:20 Echo Timer Expiry: Did not receive heartbeat reply from AP 00:18:74:c7:fe:20 (192:168:245:226/4355

*Jul 27 16:04:17.585: 00:18:74:c7:fe:20 Finding DTLS connection to delete for AP (192:168:245:226/43557)

*Jul 27 16:04:17.585: 00:18:74:c7:fe:20 Disconnecting DTLS session 0x1868936c for AP(192:168:245:226/43557)

*Jul 27 16:04:17.585: 00:18:74:c7:fe:20 CAPWAP State: Dtls tear down

*Jul 27 16:04:17.585: DTLS connection closed by controller

*Jul 27 16:04:17.586: DTLS connection closed event receivedserver (192:168:245:249/5246) client (192:168:245:226/43557)

*Jul 27 16:04:17.586: 00:18:74:c7:fe:20 Entry exists for AP (192:168:245:226/43557)

*Jul 27 16:04:17.586: 00:18:74:c7:fe:20 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:74:c7:fe:20 slot 0

*Jul 27 16:04:17.586: 00:18:74:c7:fe:20 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:74:c7:fe:20 slot 1

*Jul 27 16:04:17.587: 00:18:74:c7:fe:20 Received LWAPP Down event for AP 00:18:74:c7:fe:20 slot 0!

*Jul 27 16:04:17.587: 00:18:74:c7:fe:20 Received LWAPP Down event for AP 00:18:74:c7:fe:20 slot 1!

*Jul 27 16:04:17.587: 00:18:74:c7:fe:20 Deregister LWAPP event for AP 00:18:74:c7:fe:20 slot 0

Hall of Fame Super Gold

Re: Heartbeat timer expiring before AP completes code 5.2.193.0

Let the affected LAP boot to the RCV image and see if this re-occurs. If so, clear the private-config of the AP and try again.

908
Views
0
Helpful
2
Replies
CreatePlease to create content