Re: 2702I-B won't join 9800-80 WLC

AlexZmann · ‎06-25-2022

We have a single 2702I-B series AP that is unable to join our 9800-80 WLC. The other 100+ APs at the same site, same IP space, and same model were able to join no problem. For the AP with the issue, we do see a Join attempt, but the 9800 simply states there is an "Internal Error." Below is a snippet of a "debug capwap client event" on the AP itself. Any guidance would be appreciated in getting this issue resolved. We have a contingency plan in place to replace the AP if this issue cannot be reasonably resolved.

The target WLC is "TSS-9800-WLC" at address 10.196.253.43.

ITDSPGDWI-FL1-AP-6#

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery Request sent to 10.196.253.39

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery Request sent to 10.196.253.43

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery Request sent to 10.255.6.7

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery Request sent to 10.255.6.2

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery Response from 10.255.6.2

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery response from MWAR 'TSS-SPG-ELL-WC1'running version 8.5.176.2.

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery Response from 10.255.6.7

*Jun 24 12:36:46.223: %CAPWAP-3-EVENTLOG: Primary Discovery response from MWAR 'SDC-9800-WLC'running version 17.3.4.40.

*Jun 24 12:36:46.227: %CAPWAP-3-EVENTLOG: Primary Discovery Response from 10.196.253.39

*Jun 24 12:36:46.227: %CAPWAP-3-EVENTLOG: Primary Discovery response from MWAR 'ITDCHLARL-WSA-1'running version 8.5.176.2.

*Jun 24 12:36:46.227: %CAPWAP-3-EVENTLOG: Primary Discovery Response from 10.196.253.43

*Jun 24 12:36:46.227: %CAPWAP-3-EVENTLOG: Primary Discovery response from MWAR 'TSS-9800-WLC'running version 17.3.4.40.

*Jun 24 12:36:46.227: %CAPWAP-3-EVENTLOG: FOUND CONFIGURED MWAR(Primary) REDISCOVER TO CONNECT WITH THAT.

*Jun 24 12:36:46.231: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.196.253.39:5246

*Jun 24 12:36:46.231: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Jun 24 12:36:46.231: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.set_radio_pwr_mode: bad radio unit# 0

*Jun 24 12:36:46.231: %CAPWAP-3-EVENTLOG: Discarding msg type 9 in CAPWAP state: 4.

*Jun 24 12:36:46.231: %CAPWAP-3-EVENTLOG: Configuration update for Power Mode sent to10.196.253.39

*Jun 24 12:36:46.231: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 27

*Jun 24 12:36:46.231: %WIDS-6-DISABLED: IDS Signature is removed and disabled.

*Jun 24 12:36:46.231: bsnInitRcbSlot: slot 0 has NO radio

*Jun 24 12:36:46.231: %CAPWAP-3-EVENTLOG: Configs changed - Writing into flash and nvram

*Jun 24 12:36:46.359: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - EASY_ADMIN is not set, turn off easy admin service!

*Jun 24 12:36:46.359: %CAPWAP-5-AP_EASYADMIN_INFO: AP Easy Admin information - Easy Admin is not enabled, turn it off!

*Jun 24 12:36:46.379: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 39

*Jun 24 12:36:46.379: %CAPWAP-5-PRIMEDTIMERSTARTED: Primed Timer Started.AP will only try to join Primary/Secondary/Tertiary for next 120 seconds

*Jun 24 12:36:46.387: %CLEANAIR-6-STATE: Slot 1 down

*Jun 24 12:36:46.387: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Jun 24 12:36:46.991: %CAPWAP-3-EVENTLOG: LRAD state down. Skip sending PHY_TX_POWER_LEVEL_PAYLOADset_radio_pwr_mode: bad radio unit# 0

*Jun 24 12:36:46.991: %CAPWAP-3-EVENTLOG: Discarding msg type 9 in CAPWAP state: 4.

*Jun 24 12:36:46.991: %CAPWAP-3-EVENTLOG: Configuration update for Power Mode sent to10.196.253.39

*Jun 24 12:36:46.991: %DOT11-5-EXPECTED_RADIO_RESET: Restarting Radio interface Dot11Radio1 due to the reason code 10

*Jun 24 12:36:47.003: %CAPWAP-5-PRIMEDTIMERSTARTED: Primed Timer Started.AP will only try to join Primary/Secondary/Tertiary for next 120 seconds

*Jun 24 12:36:47.007: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Jun 24 12:36:47.007: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Jun 24 12:36:47.007: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 10.199.203.1

*Jun 24 12:36:47.007: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 10.199.203.1

*Jun 24 12:36:47.007: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 10.199.203.1

*Jun 24 12:36:47.007: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 10.199.203.1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.196.253.39 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.196.253.43 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.255.6.7 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.255.6.2 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.196.253.39 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.196.253.43 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.255.6.7 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.255.6.2 with discovery type set to 1

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Send broadcast discovery request

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Failed to send packet to destination FF01::18C

*Jun 24 12:36:47.011: %CAPWAP-3-EVENTLOG: Discovery Request sent to FF01::18C with discovery type set to 0

*Jun 24 12:36:47.011: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Discovery Response from 10.255.6.2

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 0

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.255.6.2(147E) into discoveryResp

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.255.6.2 to discoveryResponseList

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_NAME TSS-SPG-ELL-WC1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Discovery Response from 10.255.6.2

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.255.6.2(147E) into discoveryResp

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.255.6.2 to discoveryResponseList

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_NAME TSS-SPG-ELL-WC1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Discovery Response from 10.255.6.7

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 2

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.255.6.7(147E) into discoveryResp

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.255.6.7 to discoveryResponseList

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_NAME SDC-9800-WLC

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Discovery Response from 10.255.6.7

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 3

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.255.6.7(147E) into discoveryResp

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.255.6.7 to discoveryResponseList

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_NAME SDC-9800-WLC

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Discovery Response from 10.196.253.43

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 4

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.196.253.43(147E) into discoveryResp

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.196.253.43 to discoveryResponseList

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: AC_NAME TSS-9800-WLC

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Discovery Response from 10.196.253.43

*Jun 24 12:36:47.015: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 5

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.196.253.43(147E) into discoveryResp

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.196.253.43 to discoveryResponseList

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: AC_NAME TSS-9800-WLC

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: Discovery Response from 10.196.253.39

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 6

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.196.253.39(147E) into discoveryResp

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.196.253.39 to discoveryResponseList

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: AC_NAME ITDCHLARL-WSA-1

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: Discovery Response from 10.196.253.39

*Jun 24 12:36:47.019: %CAPWAP-3-EVENTLOG: Entered wtpDecodeDiscoveryResponse: numOfCapwapDiscoveryResp 7

*Jun 24 12:36:47.023: %CAPWAP-3-EVENTLOG: Copied ipAddr 10.196.253.39(147E) into discoveryResp

*Jun 24 12:36:47.023: %CAPWAP-3-EVENTLOG: CapwapDiscoveryResponse: added mwar 10.196.253.39 to discoveryResponseList

*Jun 24 12:36:47.023: %CAPWAP-3-EVENTLOG: AC_DESCRIPTOR

*Jun 24 12:36:47.023: %CAPWAP-3-EVENTLOG: AC_NAME ITDCHLARL-WSA-1

*Jun 24 12:36:47.023: %CAPWAP-3-EVENTLOG: IPV4 MGR 1

*Jun 24 12:36:47.023: %CAPWAP-3-EVENTLOG: return from wtpDecodeDiscoveryResponse

*Jun 24 12:36:47.023: %CAPWAP-3-EVENTLOG: returning from wtpProcessDiscoveryResponse

*Jun 24 12:36:47.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Jun 24 12:36:47.415: %CAPWAP-3-EVENTLOG: LRAD state down. Skip sending PHY_TX_POWER_LEVEL_PAYLOAD

*Jun 24 12:36:47.427: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Jun 24 12:36:47.435: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Jun 24 12:36:48.467: %CAPWAP-3-EVENTLOG: LRAD state down. Skip sending PHY_TX_POWER_LEVEL_PAYLOAD

*Jun 24 12:36:48.471: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Jun 24 12:36:49.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: Calling wtpGetAcToJoin from timer expiry.

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: Selected MWAR 'TSS-9800-WLC' (index 4).

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: Controller: TSS-9800-WLC. ApMgr count is 1 ipTransportTried 0 prefer-mode 1

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: Adding Ipv4 AP manager 10.196.253.43 to least load

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: IPv4 Pref mode. Choosing AP Mgr with index 0, IP = 10.196.253.43, load = 4149 ap ip: (10.199.203.24)

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: capwapSetTransportAddr returning: index=4, apMgrCount = 0

*Jun 24 12:36:57.011: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Jun 24 18:36:56.000: %CAPWAP-3-EVENTLOG: Setting time to 18:36:56 UTC Jun 24 2022

*Jun 24 18:36:56.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.196.253.43 peer_port: 5246

*Jun 24 18:36:56.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Jun 24 18:36:56.000: %CAPWAP-3-EVENTLOG: Setting default MTU: MTU discovery can start with 576

*Jun 24 18:36:56.219: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.196.253.43 peer_port: 5246

*Jun 24 18:36:56.219: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 10.196.253.43,port= 5246

*Jun 24 18:36:56.219: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Jun 24 18:36:56.219: %CAPWAP-3-EVENTLOG: Join request: version=285410344

*Jun 24 18:36:56.219: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Jun 24 18:36:56.219: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload, Length 1376

*Jun 24 18:36:56.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.196.253.43

*Jun 24 18:36:56.227: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.196.253.43

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Ignoring callback message Close alert received..

*Jun 24 18:36:56.227: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.196.253.43:5246

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Previous CAPWAP state was DTLS Setup,numOfCapwapDiscoveryResp = 8.

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Attempting to join next controller

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Go Join the next controller

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Calling wtpGetAcToJoin from timer expiry.

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Selected MWAR 'TSS-9800-WLC' (index 4).

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Ap mgr count=0

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Go Join the next controller

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Remove discovery response at index 4

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Calling wtpGetAcToJoin from timer expiry.

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Selected MWAR 'TSS-9800-WLC' (index 4).

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Controller: TSS-9800-WLC. ApMgr count is 1 ipTransportTried 0 prefer-mode 1

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Adding Ipv4 AP manager 10.196.253.43 to least load

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: IPv4 Pref mode. Choosing AP Mgr with index 0, IP = 10.196.253.43, load = 4149 ap ip: (10.199.203.24)

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: capwapSetTransportAddr returning: index=4, apMgrCount = 0

*Jun 24 18:36:56.227: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Jun 24 18:36:56.000: %CAPWAP-3-EVENTLOG: Setting time to 18:36:56 UTC Jun 24 2022

*Jun 24 18:36:56.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.196.253.43 peer_port: 5246

*Jun 24 18:36:56.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Jun 24 18:36:56.000: %CAPWAP-3-EVENTLOG: Setting default MTU: MTU discovery can start with 576

*Jun 24 18:36:56.223: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.196.253.43 peer_port: 5246

*Jun 24 18:36:56.223: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 10.196.253.43,port= 5246

*Jun 24 18:36:56.223: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Jun 24 18:36:56.223: %CAPWAP-3-EVENTLOG: Join request: version=285410344

*Jun 24 18:36:56.223: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Jun 24 18:36:56.223: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload, Length 1376

*Jun 24 18:36:56.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.196.253.43

*Jun 24 18:36:56.227: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.196.253.43

*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Ignoring callback message Close alert received..

*Jun 24 18:36:56.231: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.196.253.43:5246

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Previous CAPWAP state was DTLS Setup,numOfCapwapDiscoveryResp = 7.

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Attempting to join next controller

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Go Join the next controller

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Calling wtpGetAcToJoin from timer expiry.

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Selected MWAR 'TSS-9800-WLC' (index 4).

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Ap mgr count=0

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Go Join the next controller

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Remove discovery response at index 4

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Calling wtpGetAcToJoin from timer expiry.

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Selected MWAR 'ITDCHLARL-WSA-1' (index 4).

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Controller: ITDCHLARL-WSA-1. ApMgr count is 1 ipTransportTried 0 prefer-mode 1

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Adding Ipv4 AP manager 10.196.253.39 to least load

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: IPv4 Pref mode. Choosing AP Mgr with index 0, IP = 10.196.253.39, load = 13 ap ip: (10.199.203.24)

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: capwapSetTransportAddr returning: index=4, apMgrCount = 0

*Jun 24 18:36:56.231: AP has SHA2 MIC certificate - Using SHA2 MIC certificate for DTLS.

*Jun 24 18:36:56.231: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Jun 24 11:47:29.000: %CAPWAP-3-EVENTLOG: Setting time to 11:47:29 UTC Jun 24 2022

*Jun 24 11:47:29.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.196.253.39 peer_port: 5246

*Jun 24 11:47:29.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Jun 24 11:47:29.000: %CAPWAP-3-EVENTLOG: Setting default MTU: MTU discovery can start with 576

*Jun 24 11:47:29.219: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.196.253.39 peer_port: 5246

*Jun 24 11:47:29.219: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 10.196.253.39,port= 5246

*Jun 24 11:47:29.219: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

*Jun 24 11:47:29.219: %CAPWAP-3-EVENTLOG: Join request: version=134590466

*Jun 24 11:47:29.219: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Jun 24 11:47:29.219: %CAPWAP-3-EVENTLOG: Sending Join Request Path MTU payload, Length 1376

*Jun 24 11:47:29.219: %CAPWAP-5-SENDJOIN: sending Join Request to 10.196.253.39

*Jun 24 11:47:34.219: %CAPWAP-3-EVENTLOG: Join request: version=134590466

*Jun 24 11:47:34.219: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Jun 24 11:47:34.219: %CAPWAP-5-SENDJOIN: sending Join Request to 10.196.253.39

*Jun 24 11:47:34.223: %CAPWAP-3-EVENTLOG: Join Response from 10.196.253.39

*Jun 24 11:47:34.223: %CAPWAP-3-EVENTLOG: New Mwar DTLS capability 1 Old Mwar DTLS capability 1

*Jun 24 11:47:34.223: %CAPWAP-3-EVENTLOG: New Mwar DTLS capability 1 is same from the prev Mwar

*Jun 24 11:47:34.223: %CAPWAP-3-EVENTLOG: Starting Post Join timer

*Jun 24 11:47:34.223: %CAPWAP-3-EVENTLOG: CAPWAP State: Image Data.

*Jun 24 11:47:34.239: %CAPWAP-3-EVENTLOG: CAPWAP State: Configure.

*Jun 24 11:47:34.295: %CAPWAP-3-EVENTLOG: AP Dissociated due to LinkFailure, while sending message type 13

*Jun 24 11:47:34.295: %CAPWAP-3-EVENTLOG: ap sw version 15.3(20210318:134220)$

*Jun 24 11:47:34.295: %CAPWAP-3-EVENTLOG: lwapp_encode_ap_reset_button_payload: reset button state on

*Jun 24 11:47:34.299: %CAPWAP-3-EVENTLOG: Sending packet to AC

Flavio Miranda · ‎06-25-2022

HI

Did you try clear the capwap? factory reset?

AlexZmann · ‎06-25-2022

Yes, we tried clearing the CAPWAP config on the AP and still encountered the same issues.

balaji.bandi · ‎06-25-2022

is this a new setup or after the upgrade failed?

check the matrix :

https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

check this thread :

https://community.cisco.com/t5/wireless/1702-failing-to-join-9800-cl/td-p/4101566

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

AlexZmann · ‎06-25-2022

This is a new setup, the 9800 is running 17.3.4c; which is compatible with the 2700 series AP. All the other APs of the same model were able to join with the exception of this single AP. All APs were previously running on a 8510 WLC, to migrate we simply update the HA settings for the APs.

balaji.bandi · ‎06-25-2022

All the other APs of the same model were able to join with the exception of this single AP.

what model other AP's ? same model ?

if this issue only single AP, then I will reset the AP to factory and start testing ?

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

AlexZmann · ‎06-25-2022

Thanks for the response, all APs are 2702I-B series. Yes, we did a factory reset and still had the same issues.

marce1000 · ‎06-27-2022

Always useful and or could provide (additional) hints

- Review the 9800-80 configuration with the CLI command : show tech wireless , have the output analyzed by https://cway.cisco.com/tools/WirelessAnalyzer/ , please note do not use classical show tech-support (short version) , use the command denoted in green for Wireless Analyzer

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

ammahend · ‎06-25-2022

*Jun 24 11:47:29.219: %CAPWAP-3-EVENTLOG: Dtls Session Established with the AC 10.196.253.39,port= 5246

*Jun 24 11:47:29.219: %CAPWAP-3-EVENTLOG: CAPWAP State: Join.

whats .39 IP ?

-hope this helps-

AlexZmann · ‎06-27-2022

.39 is the 8510 WLC the AP falls back to. .43 is the target 9800 WLC.

Leo Laohoo · ‎06-25-2022

@AlexZmann wrote:

*Jun 24 12:36:57.011: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.
*Jun 24 18:36:56.000: %CAPWAP-3-EVENTLOG: Setting time to 18:36:56 UTC Jun 24 2022

The WLC has seen the AP.

@AlexZmann wrote:

*Jun 24 18:36:56.223: %CAPWAP-5-SENDJOIN: sending Join Request to 10.196.253.43

AP is sending join request to the WLC.

@AlexZmann wrote:

*Jun 24 18:36:56.227: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.196.253.43
*Jun 24 18:36:56.227: %CAPWAP-3-EVENTLOG: Ignoring callback message Close alert received..
*Jun 24 18:36:56.227: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.196.253.43:5246

Almost immediately, the WLC replies back a "go away" message.

On the AP, post the complete output to the following commands:

dir
show version
sh capwap client rcb

AlexZmann · ‎06-28-2022

ITDSPGDWI-FL1-AP-6#dir

Directory of flash:/

2 -rwx 282 Jan 1 1970 00:14:42 +00:00 info

3 -rwx 965 Jun 28 2022 08:27:43 +00:00 lwapp_mm_mwar_hash.cfg

4 -rwx 70297 Jun 24 2022 12:00:33 +00:00 event.log

5 -rwx 0 Mar 1 1993 00:00:34 +00:00 config.txt

38 drwx 576 Jan 1 1970 00:14:37 +00:00 ap3g2-rcvk9w8-mx

6 -rwx 64 Dec 13 2019 21:43:02 +00:00 sensord_CSPRNG0

86 drwx 2368 Apr 16 2022 00:09:13 +00:00 ap3g2-k9w8-mx.ap_85mr7_ircm.202103180326

80 drwx 0 Mar 1 1993 00:01:08 +00:00 configs

7 -rwx 368 Jun 28 2022 08:27:43 +00:00 capwap-saved-config

8 -rwx 368 Jun 24 2022 12:08:47 +00:00 capwap-saved-config-bak

10 -rwx 12312 Jun 28 2022 08:27:43 +00:00 private-multiple-fs

84 -rwx 64 Jun 24 2022 12:00:26 +00:00 sensord_CSPRNG1

12 -rwx 345 Jun 28 2022 08:27:43 +00:00 env_vars

88 -rwx 120394 Dec 13 2019 21:46:14 +00:00 event.r0

90 -rwx 123567 Dec 6 2019 01:23:51 +00:00 event.r1

40900608 bytes total (18638336 bytes free)

ITDSPGDWI-FL1-AP-6#

ITDSPGDWI-FL1-AP-6#sho version

Cisco IOS Software, C2700 Software (AP3G2-K9W8-M), Experimental Version 15.3(20210318:134220) [aut 239]

Compiled Thu 18-Mar-21 06:46 by aut

ROM: Bootstrap program is C2700 boot loader

BOOTLDR: C2700 Boot Loader (AP3G2-BOOT-M) LoaderVersion 15.2(4)JB5m, RELEASE SOFTWARE (fc2)

ITDSPGDWI-FL1-AP-6 uptime is 3 days, 19 hours, 36 minutes

System returned to ROM by power-on

System image file is "flash:/ap3g2-k9w8-mx.ap_85mr7_ircm.202103180326/ap3g2-k9w8-xx.a"

Last reload reason: Invalid image opcode.

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to

export@cisco.com.

cisco AIR-CAP2702I-B-K9 (PowerPC) processor (revision A0) with 376814K/134656K bytes of memory.

Processor board ID FCW2031NUMG

PowerPC CPU at 800Mhz, revision number 0x2151

Last reset from power-on

LWAPP image version 8.5.176.2

1 Gigabit Ethernet interface

1 802.11 Radio

32K bytes of flash-simulated non-volatile configuration memory.

Base ethernet MAC Address: 84:3D:C6:2B:CE:08

Part Number : 73-15824-03

PCB Serial Number : FOC20304KSG

Top Assembly Part Number : 068-100895-01

Top Assembly Serial Number : FCW2031NUMG

Top Revision Number : A0

Product/Model Number : AIR-CAP2702I-B-K9

Configuration register is 0xF

ITDSPGDWI-FL1-AP-6#sh capwap client rcb

AdminState : ADMIN_ENABLED

SwVer : 8.5.176.2

NumFilledSlots : 1

Name : ITDSPGDWI-FL1-AP-6

Location : default location

MwarName : ITDCHLARL-WSA-1

MwarApMgrIp : 10.196.253.39

MwarHwVer : 0.0.0.0

ApMode : Local

ApSubMode : Not Configured

OperationState : UP

CAPWAP Path MTU : 576

Link-Encryption (AP) : Disabled

Link-Encryption (MWAR) : Enabled

Prefer-mode : IPv4

LinkAuditing : disabled

AP Rogue Detection Mode : Enabled

AP Tcp MSS Adjust : Disabled

Predownload Status : None

Auto Immune Status : Disabled

RA Guard Status : Enabled

Efficient Upgrade State : Disabled

Efficient Upgrade Role : None

TFTP Server : Disabled

Antenna Band Mode : Unknown

Universal AP Priming mode : Unprimed

802.11a(1) Radio

ADMIN State = ENABLE [1]

OPER State = UP [2]

CONFIG State = UP [2]

HW State = UP [4]

Radio Mode : Local

GPR Period : 10

Beacon Period : 100

DTIM Period : 0

World Mode : 1

VoceraFix : 0

Dfs peakdetect : 1

Fragmentation Threshold : 2346

Current Tx Power Level : 1

Current Channel : 36

Current Bandwidth : 40

Nexthop MAC Address : cc98.9124.32e5

HYPERLOCATION ADMIN STATE : 0

WLC GATEWAY MAC : 00:00:00:00:00:00

WLC HYPERLOCATION SRC PORT : 0

Remote Machine's IP : 0.0.0.0

Cisco Trustsec Config

CTS Override state : Disabled

AP InlineTagging : Disabled

SGACL Enforcement : Disabled

ITDSPGDWI-FL1-AP-6#

Leo Laohoo · ‎06-28-2022

Alright, try the following:

debug capwap console cli
delete /f /r flash:sen*
delete /f /r flash:eve*
conf t
 no boot system flash
end

Reboot the AP by pulling the power (do not use "reload" command).