AIR-CAP 3702i Not Joining 9800 wlc

2D-Technology Services · ‎04-03-2024

Hi Community Members.,

I got a refurbished 9800 wlc which I have configured and booted to GUI.

My challenge is that the AP is not joining the WLC

How do i go about this? Possibly am missing out a config that would allow the AP associate with the Controller.

MHM Cisco World · ‎04-03-2024

Show wireless ap history

Show wireless ap join

Show wireless ap discovery

Share above

MHM

2D-Technology Services · ‎04-03-2024

WLC#sh wireless stats ap join summary
Number of APs: 0

Base MAC Ethernet MAC AP Name IP Address Stat us Last Failure Phase Last Disconnect Reason
---------------------------------------------------------------------------------------------------------------- ------------------------------------------------------

WLC#sh wireless stats ap discovery

Discovery requests received from total number of APs : 0

AP Radio MAC AP Ethernet MAC IP Address Last S uccess time Last failure type Last failure time
-------------------------------------------------------------------------------- --------------------------------------------------------------------

marce1000 · ‎04-03-2024

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

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! '

Haydn Andrews · ‎04-03-2024

What version the WLC running

Potentially hit:
https://www.cisco.com/c/en/us/support/docs/field-notices/639/fn63942.html

Post console of the AP during boot cycle

*****Help out other by using the rating system and marking answered questions as "Answered"*****
*** Please rate helpful posts ***

2D-Technology Services · ‎04-05-2024

Attached is the console at boot up

2D-Technology Services · ‎04-05-2024

David Ritter · ‎04-04-2024

Your 3702 ap's begin as AIROS devices. They are supported in the 9800 in 17.3.x and older. they were removed in 17.4 and returned in 17.9.3. All wave1 AP's are then removed in all newer code trains.

x702 aps also have expired certs Dec2021. causing one to need to reset the 9800 date to a date earlier than Dec21 (or was it 22). a current code image resolves that problem. If they are being rejected for certs, they most likely will not get recorded in the join log as a device knocking on the door.

2D-Technology Services · ‎04-05-2024

Below is my AP details:

AP Running Image : 8.5.161.0
Primary Boot Image : 8.5.161.0
Backup Boot Image : 8.2.151.0
2 Gigabit Ethernet interfaces
2 802.11 Radios
Radio FW version : 64035bf3490c0cb9e24ce9b09a56fe6c
NSS FW version : NSS.AK.C.CS-3-fix3

Base ethernet MAC Address : 4C:BC:48:32:55:40

Top Revision Number : A0
Product/Model Number : AIR-AP1852I-E-K9

ERROR MESSAGE FROM AP CONSOLE:

[*09/29/2021 14:53:25.8092] ethernet_port wired0, ip 172.20.0.248, netmask 255.255.255.0, gw 172.20.0.1, mtu 1500, bcast 172.20.0.255, dns1 10.10.10.125, dns2 8.8.8.8, vid 0, static_ip_failover false, dhcp_vlan_failover false
[*09/29/2021 14:53:36.0860] AP IPv4 Address updated from 0.0.0.0 to 172.20.0.248
[*09/29/2021 14:53:36.1659] DOT11_CFG[0] Radio Mode is changed from Local to Local
[*09/29/2021 14:53:36.1659] DOT11_CFG[1] Radio Mode is changed from Local to Local
[*09/29/2021 14:53:36.2359] dtls_init: Use MIC certificate
[*09/29/2021 14:53:36.2359]
[*09/29/2021 14:53:36.2359] CAPWAP State: Init
[*09/29/2021 14:53:36.2359]
[*09/29/2021 14:53:36.2359] Config not found, PNP is required, Starting PNP
[*09/29/2021 14:53:36.2359]
[*09/29/2021 14:53:43.1238] PNP:Server not reachable, Start CAPWAP Discovery
[*09/29/2021 14:53:43.1238]
[*09/29/2021 14:53:43.1238] CAPWAP State: Discovery
[*09/29/2021 14:53:43.1238] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:53:43.1238]
[*09/29/2021 14:53:43.1238] CAPWAP State: Discovery
[*09/29/2021 14:53:52.5908]
[*09/29/2021 14:53:52.5908] CAPWAP State: Discovery
[*09/29/2021 14:53:52.6008] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:54:02.1078]
[*09/29/2021 14:54:02.1078] CAPWAP State: Discovery
[*09/29/2021 14:54:02.1078] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:54:03.4574]
[*09/29/2021 14:54:03.4574] phy_value=0: org="0x1800" phy_reg="0x1800"
[*09/29/2021 14:54:11.6049]
[*09/29/2021 14:54:11.6049] CAPWAP State: Discovery
[*09/29/2021 14:54:11.6149] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:54:21.1119]
[*09/29/2021 14:54:21.1119] CAPWAP State: Discovery
[*09/29/2021 14:54:21.1119] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:55:20.1634] PNP:Server not reachable, Start CAPWAP Discovery
[*09/29/2021 14:55:20.1634]
[*09/29/2021 14:55:20.1634] Lost connection to the controller, going to restart CAPWAP (reason : Post startCapwapDiscovery)...
[*09/29/2021 14:55:20.1634]
[*09/29/2021 14:55:20.1634] Restarting CAPWAP State Machine.
[*09/29/2021 14:55:20.2734] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*09/29/2021 14:55:20.2734]
[*09/29/2021 14:55:20.2734] CAPWAP State: DTLS Teardown
[*09/29/2021 14:55:24.9819]
[*09/29/2021 14:55:24.9819] CAPWAP State: Discovery
[*09/29/2021 14:55:24.9819] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:55:34.4890]
[*09/29/2021 14:55:34.4890] CAPWAP State: Discovery
[*09/29/2021 14:55:34.4890] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:55:43.9860]
[*09/29/2021 14:55:43.9860] CAPWAP State: Discovery
[*09/29/2021 14:55:43.9960] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:55:53.4930]
[*09/29/2021 14:55:53.4930] CAPWAP State: Discovery
[*09/29/2021 14:55:53.5030] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:56:02.9900]
[*09/29/2021 14:56:02.9900] CAPWAP State: Discovery
[*09/29/2021 14:56:02.9900] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:57:03.0713] PNP:Server not reachable, Start CAPWAP Discovery
[*09/29/2021 14:57:03.0713]
[*09/29/2021 14:57:03.0713] Lost connection to the controller, going to restart CAPWAP (reason : Post startCapwapDiscovery)...
[*09/29/2021 14:57:03.0713]
[*09/29/2021 14:57:03.0713] Restarting CAPWAP State Machine.
[*09/29/2021 14:57:03.1812] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*09/29/2021 14:57:03.1812]
[*09/29/2021 14:57:03.1812] CAPWAP State: DTLS Teardown
[*09/29/2021 14:57:08.0097]
[*09/29/2021 14:57:08.0097] CAPWAP State: Discovery
[*09/29/2021 14:57:08.0097] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:57:17.5268]
[*09/29/2021 14:57:17.5268] CAPWAP State: Discovery
[*09/29/2021 14:57:17.5268] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:57:27.0238]
[*09/29/2021 14:57:27.0238] CAPWAP State: Discovery
[*09/29/2021 14:57:27.0238] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:57:36.5208]
[*09/29/2021 14:57:36.5208] CAPWAP State: Discovery
[*09/29/2021 14:57:36.5308] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:57:46.0378]
[*09/29/2021 14:57:46.0378] CAPWAP State: Discovery
[*09/29/2021 14:57:46.0378] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:58:45.9791] PNP:Server not reachable, Start CAPWAP Discovery
[*09/29/2021 14:58:45.9791]
[*09/29/2021 14:58:45.9791] Lost connection to the controller, going to restart CAPWAP (reason : Post startCapwapDiscovery)...
[*09/29/2021 14:58:45.9791]
[*09/29/2021 14:58:45.9791] Restarting CAPWAP State Machine.
[*09/29/2021 14:58:46.0891] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*09/29/2021 14:58:46.0891]
[*09/29/2021 14:58:46.0891] CAPWAP State: DTLS Teardown
[*09/29/2021 14:58:50.8576]
[*09/29/2021 14:58:50.8576] CAPWAP State: Discovery
[*09/29/2021 14:58:50.8576] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:59:00.3546]
[*09/29/2021 14:59:00.3546] CAPWAP State: Discovery
[*09/29/2021 14:59:00.3546] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:59:09.8517]
[*09/29/2021 14:59:09.8517] CAPWAP State: Discovery
[*09/29/2021 14:59:09.8616] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:59:19.3687]
[*09/29/2021 14:59:19.3687] CAPWAP State: Discovery
[*09/29/2021 14:59:19.3687] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 14:59:28.8657]
[*09/29/2021 14:59:28.8657] CAPWAP State: Discovery
[*09/29/2021 14:59:28.8757] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 15:00:28.9769] PNP:Server not reachable, Start CAPWAP Discovery
[*09/29/2021 15:00:28.9769]
[*09/29/2021 15:00:28.9769] Lost connection to the controller, going to restart CAPWAP (reason : Post startCapwapDiscovery)...
[*09/29/2021 15:00:28.9769]
[*09/29/2021 15:00:28.9769] Restarting CAPWAP State Machine.
[*09/29/2021 15:00:29.0869] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Discovery(2).
[*09/29/2021 15:00:29.0869]
[*09/29/2021 15:00:29.0869] CAPWAP State: DTLS Teardown
[*09/29/2021 15:00:33.8754]
[*09/29/2021 15:00:33.8754] CAPWAP State: Discovery
[*09/29/2021 15:00:33.8754] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 15:00:43.3724]
[*09/29/2021 15:00:43.3724] CAPWAP State: Discovery
[*09/29/2021 15:00:43.3824] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 15:00:52.8795]
[*09/29/2021 15:00:52.8795] CAPWAP State: Discovery
[*09/29/2021 15:00:52.8795] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*09/29/2021 15:01:02.3865]
[*09/29/2021 15:01:02.3865] CAPWAP State: Discovery
[*09/29/2021 15:01:02.3965] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

marce1000 · ‎04-05-2024

- Check controller logs too, just after AP join attempt ,

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! '

2D-Technology Services · ‎04-05-2024

login as: Towers
Keyboard-interactive authentication prompts from server:
| Password:
End of keyboard-interactive prompts from server

WLC#
WLC#
WLC#
WLC#sh log
Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.

No Inactive Message Discriminator.

Console logging: level debugging, 138 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 138 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 133 message lines logged
Logging Source-Interface: VRF Name:
TLS Profiles:

Log Buffer (4096 bytes):
ES128-GCM-SHA256'
*Apr 5 09:32:06.982: %WEBSERVER-5-SESS_LOGOUT: Chassis 1 R0/0: : Successfully logged out from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
*Apr 5 09:42:46.209: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: Towers] [Source: 172.20.0.254] [localport: 22] at 09:42:46 UTC Fri Apr 5 2024
*Apr 5 09:58:03.190: %SYS-6-TTY_EXPIRE_TIMER: (exec timer expired, tty 2 (172.20.0.254)), user Towers
*Apr 5 09:58:03.190: %SYS-6-LOGOUT: User Towers has exited tty session 2(172.20.0.254)
*Apr 5 10:47:05.593: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: Towers] [Source: 172.20.0.254] [localport: 22] at 10:47:05 UTC Fri Apr 5 2024
*Apr 5 10:52:54.567: %SEC_LOGIN-5-WEBLOGIN_SUCCESS: Login Success [user: Towers] [Source: ] at 10:52:54 UTC Fri Apr 5 2024
*Apr 5 10:52:54.568: %WEBSERVER-5-LOGIN_PASSED: Chassis 1 R0/0: : Login Successful from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
*Apr 5 11:01:11.648: %SYS-6-TTY_EXPIRE_TIMER: (exec timer expired, tty 2 (172.20.0.254)), user Towers
*Apr 5 11:01:11.648: %SYS-6-LOGOUT: User Towers has exited tty session 2(172.20.0.254)
*Apr 5 11:03:21.610: %WEBSERVER-5-SESS_LOGOUT: Chassis 1 R0/0: : Successfully logged out from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
*Apr 5 11:20:13.631: %SEC_LOGIN-5-WEBLOGIN_SUCCESS: Login Success [user: Towers] [Source: ] at 11:20:13 UTC Fri Apr 5 2024
*Apr 5 11:20:13.632: %WEBSERVER-5-LOGIN_PASSED: Chassis 1 R0/0: : Login Successful from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
*Apr 5 11:42:13.722: %WEBSERVER-5-SESS_LOGOUT: Chassis 1 R0/0: : Successfully logged out from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
*Apr 5 13:06:49.620: %SEC_LOGIN-5-WEBLOGIN_SUCCESS: Login Success [user: Towers] [Source: ] at 13:06:49 UTC Fri Apr 5 2024
*Apr 5 13:06:49.620: %WEBSERVER-5-LOGIN_PASSED: Chassis 1 R0/0: : Login Successful from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
*Apr 5 13:27:02.087: %SYS-6-CLOCKUPDATE: System clock has been updated from 13:27:02 UTC Fri Apr 5 2024 to 13:27:02 GMT Fri Apr 5 2024, configured from console by Towers on vty0.
*Apr 5 02:30:00.000: %SYS-6-CLOCKUPDATE: System clock has been updated from 13:27:02 GMT Fri Apr 5 2024 to 02:30:00 GMT Fri Apr 5 2024, configured from console by Towers on vty0.
Apr 5 02:30:00.000: %PKI-6-AUTHORITATIVE_CLOCK: The system clock has been set.
Apr 5 02:30:00.012: %SYS-5-CONFIG_P: Configured programmatically by process SEP_webui_wsma_http from console as Towers on vty0
Apr 5 02:30:10.208: %WEBSERVER-5-SESS_LOGOUT: Chassis 1 R0/0: : Successfully logged out from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
Apr 5 02:30:43.926: %SEC_LOGIN-5-WEBLOGIN_SUCCESS: Login Success [user: Towers] [Source: ] at 02:30:43 GMT Fri Apr 5 2024
Apr 5 02:30:43.926: %WEBSERVER-5-LOGIN_PASSED: Chassis 1 R0/0: : Login Successful from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
Apr 5 02:37:55.841: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: Towers] [Source: 172.20.0.254] [localport: 22] at 02:37:55 GMT Fri Apr 5 2024
Apr 5 02:39:21.442: %SYS-5-CONFIG_I: Configured from console by Towers on vty0 (172.20.0.254)
Apr 5 02:53:25.050: %WEBSERVER-5-SESS_LOGOUT: Chassis 1 R0/0: : Successfully logged out from host 172.20.0.254 by user 'Towers' using crypto cipher 'ECDHE-RSA-AES128-GCM-SHA256'
Apr 5 02:54:56.761: %SYS-6-TTY_EXPIRE_TIMER: (exec timer expired, tty 2 (172.20.0.254)), user Towers
Apr 5 02:54:56.761: %SYS-6-LOGOUT: User Towers has exited tty session 2(172.20.0.254)
Apr 5 04:45:33.153: %SMART_LIC-3-COMM_FAILED: Communications failure with the Cisco Smart License Utility (CSLU) : Unable to resolve server hostname/domain name
Apr 5 05:01:59.019: %SEC_LOGIN-5-LOGIN_SUCCESS: Login Success [user: Towers] [Source: 172.20.0.254] [localport: 22] at 05:01:59 GMT Fri Apr 5 2024
WLC#
WLC#
WLC#

marce1000 · ‎04-05-2024

- What mechanism is the AP using to discover a(the) controller ?

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! '

David Ritter · ‎04-05-2024

It did not even attempt the Default DNS search for Cisco-lwapp-controller/Cisco-capwap-controller.

2D-Technology Services · ‎04-09-2024

Yes I can see that....what can I do to the Controller

David Ritter · ‎04-09-2024

CAPWAP State: Init
CAPWAP State: Discovery
Discovery Request sent to 172.xx.xx.4, discovery type STATIC_CONFIG(1)
IP DNS query for CISCO-CAPWAP-CONTROLLER.tc.tularecounty.tcweb
Discovery Request sent to 172.xx.xx.4, discovery type STATIC_CONFIG(1)
Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
CAPWAP State: Discovery
Discovery Response from 172.xx.xx.4
Start: RPC thread 1105509520 created.
Discovery Response from 172.xx.xx.4
Discovery Response from 172.xx.xx.4
Discovery Response from 172.xx.xx.4
CAPWAP State: DTLS Setup