3702I not joint a 2504

[Scott O'Brien]

Hi Guys, please see below: 

AP ( 3702i) 

Mar  1 00:34:49.691: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
*Mar  1 00:34:54.703: %CAPWAP-3-ERRORLOG: Invalid event 40 & state 2 combination.
*Mar  1 00:34:54.811: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.65, mask 255.255.255.0, hostname APf44e.05b7.1e84

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (203.0.178.191)
*Mar  1 00:35:00.691: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained through DHCP
*Mar  1 00:35:00.691: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar  1 00:35:09.691: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
Not in Bound state.

The Controller management ip is 10.1.1.231 and the DHCP scope is working on the switch. I am running version 7.6.120.0 code on the 2504. 

it seems to get the IP of the WLC but not use it, any ideas? 

Thanks  

[Scott Fella]

Is the time set properly on the WLC?  You should also upgrade to v7.6.130.0 for stability.  Place the AP on the same subnet as the WLC just to get the ap to join after you heck the time/NTP on the wlc. 

-Scott

[Scott O'Brien]

Hi Scott, 

thanks for that, I fixed the time issue and placed the AP's into the same Vlan and they joined.

my switch config is below 

ip dhcp pool WAP_Pool

   network 10.1.20.0 255.255.255.0

   default-router 10.1.20.1 

   option 43 hex f104.0a01.01e7

and my controller config is attached.

The AP's are in Vlan 20 and management is vlan 10  

Thanks

[Scott Fella]

Well now since that so has joined, you can move it to any vlan. You don't need the option 43 because the ap already knows of the WLC ip.  You can leave it and test another new ap by placing it in vlan 20 and see if it joins now since the time was off.

-Scott

[Scott O'Brien]

Thanks Scott, I did test it in Vlan 20 before I made the jump to the same Vlan as the WLC. 

it just looks a little odd as it gets the IP of the WLC but then looks like it try's the CAPWAP route of the option 43 route?  

[Scott Fella]

The AP has a process of finding the WLC and grows through each step until the WLC sends a join accept. If the AP doesn't get a response, the process is to go to the next process of finding the WLC. If the time is wrong, the WLC and AP can't negotiate and the join will never happen.  Console into the AP and power it down then back up and look at the output now.  There are requirements for the join process to happen, time must be set, the country code matches and the WLC code supports the ap model.

-Scott

[Scott O'Brien]

Just looking at the logs on the AP and it looks as they it still had the wrong time up until it found the controller on the same VLAN, 

*Mar  1 00:01:09.431: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar  1 00:01:09.735: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.1.3, mask 255.255.255.0, hostname APf44e.05b7.1e84

*Mar  1 00:01:12.115: Logging LWAPP message to 255.255.255.255.

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

*Mar  1 00:01:23.119: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar  1 00:01:23.143: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar  1 00:01:33.143: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 20 06:06:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.1.231 peer_port: 5246
*Jan 20 06:06:59.411: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.1.231 peer_port: 5246
*Jan 20 06:06:59.411: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.1.231

so by the looks it should have still worked when it was on VLAN 20 and once it found the WLC it should have changed its time to match? 

The time on the WLC was correct it was the time on the Switch that I changed. 

sorry to keep bugging but it just looks to me like an odd error. I will reset one of my AP's tomorrow and do a little bit more playing around. ( the joys of a lab :) )

Thanks heaps for your help Scott!  

[Scott O'Brien]

Hi Scott, 

I Just moved one of the AP's back to Vlan 20, and left the config as it, and I am getting the same errors and the time has gone back to the 1 or march: 

Username:
Not in Bound state.cisco
Password:
*Mar  1 00:03:32.915: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
*Mar  1 00:03:38.015: %CAPWAP-3-ERRORLOG: Invalid event 40 & state 2 combination.
*Mar  1 00:03:38.035: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.122, mask 255.255.255.0, hostname APf44e.05b7.1e84

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar  1 00:03:43.915: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained throug

??? it looks like the AP's have reset them selfs? 

EDIT I also tryed to set the time manually on the AP and still no luck, time is fine on both switch and WLC. 

[Viten Patel]

try using version 8.0.110.0