CAP1532 cannot join to WLC

[xuzhengyi1995]

Hi,

Have a problem of join a CAP1532 to a WLC2504, the two devices could ping each other and on 2504 I could see the AP in the ap join statistics, but it seems like the AP does not receive the response from WLC.

I configured both DHCP and DNS, tried use DHCP and static ip, but seems got the same problem.

I have some 2702 and they work well.

Ap bundle is also installed in the WLC.

Hope could get some help, thanks!

WLC 2504:

Software Version

8.5.171.0

1532:

Cisco IOS Software, C1530 Software (ap1g3-K9W8-M), Version 15.3(3)JF9, RELEASE SOFTWARE (fc1)

LWAPP image version 8.5.140.0

*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*Mar 1 00:50:01.419: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*Mar 1 00:50:11.423: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:50:15.099: %CAPWAP-3-EVENTLOG: No changes in lwapp configs
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

[xuzhengyi1995]

Logs on WLC:

*spamApTask3: Oct 09 09:06:02.641: 00:b6:70:40:de:90 Discovery Request from 192.168.0.101:62899

*spamApTask3: Oct 09 09:06:02.641: 00:b6:70:40:de:90 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 75, MaxLicense=75 joined Aps =5
*spamApTask3: Oct 09 09:06:02.641: 00:b6:70:40:de:90 apType = 34 apModel: AIR-CAP1532I-H-K9

*spamApTask3: Oct 09 09:06:02.641: 00:b6:70:40:de:90 apType: Ox22 bundleApImageVer: 8.5.171.0
*spamApTask3: Oct 09 09:06:02.641: 00:b6:70:40:de:90 version:8 release:5 maint:171 build:0
*spamApTask3: Oct 09 09:06:02.641: 00:b6:70:40:de:90 Discovery Response sent to 192.168.0.101 port 62899

*spamApTask3: Oct 09 09:06:02.641: 00:b6:70:40:de:90 Discovery Response sent to 192.168.0.101:62899

Repeat...

[xuzhengyi1995]

Logs on 1532:

*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1
*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: Discovery Request sent to 192.168.0.33 with discovery type set to 2
*Mar 1 00:51:19.811: %CAPWAP-3-EVENTLOG: Discovery Request sent to 192.168.0.33 with discovery type set to 3
*Mar 1 00:51:29.811: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.
*Mar 1 00:51:29.811: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.
*Mar 1 00:51:29.811: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.
*Mar 1 00:51:29.811: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - Adding default route for gateway 192.168.0.1
*Mar 1 00:51:29.811: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 192.168.0.1% Nameserver entry 192.168.0.100 does not exist

Not in Bound state.
*Mar 1 00:51:35.191: %CAPWAP-3-EVENTLOG: No changes in lwapp configs
*Mar 1 00:51:35.331: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 00:51:35.331: %CAPWAP-3-EVENTLOG: Discovery failed 5 times. Release/Renew DHCP

Repeat...

[Rich R]

What is the WLC IP address?
What discovery method are you using?
I'm going to guess they're sitting on the same LAN/VLAN and you're relying on local subnet discovery.
So have you added the AP MAC address to AP policy on WLC? https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/98848-lap-auth-uwn-config.html#anc7
Have you checked to make sure you're not affected by https://www.cisco.com/c/en/us/support/docs/field-notices/639/fn63942.html