Re: AP switched to Standalone mode and re-joined to WLC

yeekhiang.ching · ‎07-25-2019

Hi,

I realized the AP was disassociated from WLC and then re-joined to WLC again after 1 minute. Then from the logs, I could not find any unusual symptoms. The AP just happened to be like this on 10 July then happened again on 22 July. Can anyone please have a look at the logs and advise what had happen to the AP or WLC.

Sandeep Choudhary · ‎07-25-2019

As you are using AP in flexconnect mode....

There was a WAN Interruption for few seconds that is the reason AP lost connection to WLC and acted as standalone.

when the WAN connection was normal it joined back to WLC. Means you should check the packet loss on WAN connectivity.

__________

Jul 10 07:54:54 kernel: [*07/10/2019 07:54:54.5048] Lost connection to the controller, going to restart CAPWAP...
Jul 10 07:54:54 kernel: [*07/10/2019 07:54:54.5048] 
Jul 10 07:54:54 kernel: [*07/10/2019 07:54:54.5048] Restarting CAPWAP State Machine.
Jul 10 07:54:54 kernel: [*07/10/2019 07:54:54.5048] CAPWAP State: DTLS Teardown
Jul 10 07:54:55 kernel: [*07/10/2019 07:54:55.3346] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2733] CAPWAP State: Discovery
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2733] Discovery Request sent to xx.xx.254.21, discovery type STATIC_CONFIG(1)
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2733] Discovery Request sent to xx.xx.0.29, discovery type STATIC_CONFIG(1)
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2833] Discovery Request sent to xx.xx.0.29, discovery type STATIC_CONFIG(1)
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2833] Discovery Request sent to xx.xx.254.21, discovery type STATIC_CONFIG(1)
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2933] Discovery Request sent to xx.xx.0.29, discovery type STATIC_CONFIG(1)
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2933] Discovery Request sent to xx.xx.0.29, discovery type STATIC_CONFIG(1)
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2933] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.2933] Discovery Response from xx.xx.254.21
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.0000] Discovery Response from xx.xx.254.21
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.0199] Discovery Response from xx.xx.0.29
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.0000] Discovery Response from xx.xx.0.29
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.0000] Discovery Response from xx.xx.0.29
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.0000] Discovery Response from xx.xx.0.29
Jul 10 07:55:04 kernel: [*07/10/2019 07:55:04.0084] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.0075] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
Jul 10 07:55:08 kernel: [*07/10/2019 07:55:07.9772] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.0000] CAPWAP State: DTLS Setup
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.1799] CAPWAP State: Join
Jul 10 07:54:59 kernel: [*07/10/2019 07:54:59.1899] Sending Join request to xx.xx.0.29 through port 5256
Jul 10 07:55:03 kernel: [*07/10/2019 07:55:03.9684] Join Response from xx.xx.0.29 
Jul 10 07:55:03 kernel: [*07/10/2019 07:55:03.9684] CAPWAP State: Image Data
Jul 10 07:55:03 kernel: [*07/10/2019 07:55:03.9684] CAPWAP State: Configure
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.0975] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.0975] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.0975] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.0975] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Configure(8).
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.3374] CAPWAP State: Run
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.4773] AP has joined controller TestWLC
Jul 10 07:55:07 kernel: [*07/10/2019 07:55:07.4973] Flexconnect Switching to Connected Mode!
Jul 10 07:55:20 syslog: Password for 'admin' changed
Jul 10 07:55:20 kernel: [*07/10/2019 07:55:20.8132] Password for 'admin' changed
Jul 10 07:55:21 kernel: [*07/10/2019 07:55:21.1131] TLV-DEC-PROC: Info missing for 320
Jul 10 07:55:21 kernel: [*07/10/2019 07:55:21.2530] TLV-DEC-ERR: cannot process TLV for TLV_FLEX_VLAN_NAME_ID_MAPPING_PAYLOAD(591/0)
Jul 10 07:55:21 kernel: [*07/10/2019 07:55:21.2530] TLV-DEC-ERR: No CB for TLV_FLEX_VLAN_NAME_ID_MAPPING_PAYLOAD(591)
Jul 10 07:55:39 hostapd: apr1v2:RADIUS: No authentication server configured
Jul 10 08:06:05 kernel: [*07/10/2019 08:06:05.0100] Re-Tx Count=11, Max Re-Tx Value=10, NumofPendingMsgs=8
Jul 10 08:06:05 kernel: [*07/10/2019 08:06:05.0100] 
Jul 10 08:06:07 kernel: [*07/10/2019 08:06:07.8791] Re-Tx Count=12, Max Re-Tx Value=10, NumofPendingMsgs=9
Jul 10 08:06:07 kernel: [*07/10/2019 08:06:07.8791] 
Jul 10 08:06:10 kernel: [*07/10/2019 08:06:10.7082] Re-Tx Count=13, Max Re-Tx Value=10, NumofPendingMsgs=10
Jul 10 08:06:10 kernel: [*07/10/2019 08:06:10.7082] 
Jul 10 08:06:13 kernel: [*07/10/2019 08:06:13.5573] Re-Tx Count=14, Max Re-Tx Value=10, NumofPendingMsgs=12
Jul 10 08:06:13 kernel: [*07/10/2019 08:06:13.5573] 
Jul 10 08:06:19 kernel: [*07/10/2019 08:06:19.2655] Re-Tx Count=15, Max Re-Tx Value=10, NumofPendingMsgs=13
Jul 10 08:06:19 kernel: [*07/10/2019 08:06:19.2655] 
Jul 10 08:06:22 kernel: [*07/10/2019 08:06:22.1146] Re-Tx Count=16, Max Re-Tx Value=10, NumofPendingMsgs=14
Jul 10 08:06:22 kernel: [*07/10/2019 08:06:22.1146] 
Jul 10 08:06:22 kernel: [*07/10/2019 08:06:22.1146] Max retransmission count exceeded, going back to DISCOVER mode.
Jul 10 08:06:22 kernel: [*07/10/2019 08:06:22.1146] Flexconnect Switching to Standalone Mode!
Jul 10 08:06:22 kernel: [*07/10/2019 08:06:22.1246] CAPWAP State: DTLS Teardown
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:26.8932] Discovery Response from xx.xx.0.29
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.0000] Discovery Response from xx.xx.0.29
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.0000] Discovery Response from xx.xx.254.21
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.0000] Discovery Response from xx.xx.0.29
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.0000] Discovery Response from xx.xx.0.29
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.0000] Discovery Response from xx.xx.254.21
Jul 10 08:06:27 hostapd: apr1v2:RADIUS: No authentication server configured
Jul 10 08:06:30 hostapd: apr1v2:RADIUS: No authentication server configured
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.0000] CAPWAP State: DTLS Setup
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.1399] CAPWAP State: Join
Jul 10 08:06:27 kernel: [*07/10/2019 08:06:27.1499] Sending Join request to xx.xx.0.29 through port 5256
Jul 10 08:06:29 hostapd: apr1v2:RADIUS: No authentication server configured
Jul 10 08:06:29 hostapd: apr1v2:RADIUS: No authentication server configured
Jul 10 08:06:58 hostapd: apr1v2:RADIUS: No authentication server configured
Jul 10 08:06:59 kernel: [*07/10/2019 08:06:59.7698] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
Jul 10 08:07:03 hostapd: apr1v4:RADIUS: No authentication server configured
Jul 10 08:07:08 hostapd: apr1v2:RADIUS: No authentication server configured
Jul 10 08:07:10 kernel: [*07/10/2019 08:07:10.6763] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
Jul 10 08:07:10 kernel: [*07/10/2019 08:07:10.6763] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
Jul 10 08:07:13 kernel: [*07/10/2019 08:07:13.8454] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
Jul 10 08:07:13 kernel: [*07/10/2019 08:07:13.8454] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
Jul 10 08:07:24 kernel: [*07/10/2019 08:07:24.0422] CAPWAP State: DTLS Teardown
Jul 10 08:07:38 kernel: [*07/10/2019 08:07:28.8207] Discovery Response from xx.xx.0.29
Jul 10 08:07:38 kernel: [*07/10/2019 08:07:38.0000] Discovery Response from xx.xx.254.21
Jul 10 08:07:38 kernel: [*07/10/2019 08:07:38.0000] Discovery Response from xx.xx.0.29
Jul 10 08:07:38 kernel: [*07/10/2019 08:07:38.0000] Discovery Response from xx.xx.254.21
Jul 10 08:07:38 kernel: [*07/10/2019 08:07:38.0000] Discovery Response from xx.xx.0.29
Jul 10 08:07:38 kernel: [*07/10/2019 08:07:38.0000] Discovery Response from xx.xx.0.29
Jul 10 08:07:38 kernel: [*07/10/2019 08:07:38.0000] CAPWAP State: DTLS Setup
Jul 10 08:07:40 kernel: [*07/10/2019 08:07:40.0294] CAPWAP State: Join
Jul 10 08:07:40 kernel: [*07/10/2019 08:07:40.0394] Sending Join request to xx.xx.0.29 through port 5256
Jul 10 08:07:44 kernel: [*07/10/2019 08:07:44.6779] Join Response from xx.xx.0.29 
Jul 10 08:07:44 kernel: [*07/10/2019 08:07:44.6779] CAPWAP State: Image Data
Jul 10 08:07:44 kernel: [*07/10/2019 08:07:44.6779] CAPWAP State: Configure
Jul 10 08:07:45 kernel: [*07/10/2019 08:07:45.3177] CAPWAP State: Run
Jul 10 08:07:45 kernel: [*07/10/2019 08:07:45.4477] AP has joined controller TestWLC
Jul 10 08:07:45 kernel: [*07/10/2019 08:07:45.4677] Flexconnect Switching to Connected Mode!
Jul 10 08:07:57 syslog: Password for 'admin' changed
Jul 10 08:07:58 kernel: [*07/10/2019 08:07:57.9937] Password for 'admin' changed

__________

Regards

Dont forget to rate helpful posts

gaurav mahajan1 · ‎03-03-2023

This happens to one of my site where all we have 4 9120 aps which randomly disconnect from cisco 9800L wlc and join back after 10-20 mins
still couldnt find the root cause

Scott Fella · ‎03-03-2023

You should open a new thread with information on your environment, code and model type. If you have logs and also tell use any additional details, we can possible help.

-Scott
*** Please rate helpful posts ***