Buy or Renew
Buy or Renew
Cisco Virtual Engineer generative AI bot now active in Wireless Discussion Forum. Learn more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
2467
Views
0
Helpful
2
Replies

Heartbeat timer expiring before AP completes code 5.2.193.0 upgrade

cchitwood1
Level 1
Level 1

‎07-27-2009 07:53 AM - edited ‎07-03-2021 05:52 PM

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....

1 person had this problem
Labels:
0 Helpful
2 Replies 2

cchitwood1
Level 1
Level 1

‎07-27-2009 08:05 AM

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

0 Helpful

Leo Laohoo
Hall of Fame
Hall of Fame

‎07-27-2009 02:45 PM

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.

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card