Mesh AP joins learns controller IP via DHCP and joins different

mohammed.buda · ‎09-24-2013

Hi ,

I am testing 1552e mesh AP.It gets its IP information from a lucent qip dhcp server.the problem is this AP gets an IP address and obtained controller IP via option 43 but when it tries to join it goes to another controller not the one on option 43. I have entered the MAC address of this AP in 10.107.133.40 under security - MAC filtering here is the log:

*Sep 24 12:59:58.959: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 13:00:00.015: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.107.133.40 obtained through DHCP

*Sep 24 13:00:00.015: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Sep 24 13:00:09.015: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

*Sep 24 13:00:19.015: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 24 13:00:19.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 13:00:19.595: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 13:00:19.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40

*Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Sep 24 13:00:19.603: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.124.133.40

*Sep 24 13:00:24.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40

any idea?

Thanks for any help

Scott Fella · ‎09-24-2013

Well are you sure that option 43 is configured right? If not, then create a DNS entry for the time being and resolve

CISCO-CAPWAP-CONTROLLER to your WLC management. If the AP already has joined, then it will continue to join that WLC, so you might need to add the mac address to let it join, then under the AP, change the high availability to point to the WLC you want it to be on.

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

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

mohammed.buda · ‎09-24-2013

Scott,

I have tested option 43 with different AP's and it is correct. DNS is not an option for me here. it is under management. under high avail. nothing is configured - empty fields - . MAC address has been added to the right controller 10.107.133.40.

Thanks for your response.

Scott Fella · ‎09-24-2013

If the AP has joined the other WLC, then its going to join that WLC and not the one you have used in option 43 unless the other WLC is down. So my suggestion is to allow the AP to join the other WLC by adding the mac address to that and when it is in the run state, you set the primary WLC to the WLC you want it to join, then reboot the AP.

Thanks,

Scott

Help out other by using the rating system and marking answered questions as "Answered"

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

mohammed.buda · ‎09-24-2013

One option is to do it as you suggested Scott.

Thanks,

kcnajaf · ‎09-24-2013

Hi Mohammed,

Which model of WLC you have got? And what is the IOS which you are using on the same? Do you have already any mesh AP which is registered to WLC? Have you tried to put the AP on the same subnet of WLC to which you want it to get regsistered and verfied if it is getting registered to the same?

Could you please share the output of debug lwapp events enable when AP try to join the WLC?

Regards

Najaf

mohammed.buda · ‎09-24-2013

Hi Najaf,

I am using 5508 with 7.4.110. it is a new controller. I will run debug command you mentioned and will post the results.

Thanks,

Stephen Rodriguez · ‎09-24-2013

Option 43 does not tell your AP which WLC to join, it informs the AP of one of the WLC in your mobility group so it can learn all the WLC.

http://wifijanitor.net/2013/08/02/cisco-ap-discovery-option-4360-and-you/

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

mohammed.buda · ‎09-24-2013

You are right Steve, I opened case with Cisco and a TAC has contacted me. He says option 43 does not guarantee AP joins the controller configured in option43.

mohammed.buda · ‎09-24-2013

Najaf,

I am attaching a debug results if you are interested.

Thanks,

*Sep 24 19:30:50.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40

*Sep 24 19:31:31.115: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Sep 24 19:31:31.115: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Sep 24 19:31:31.115: %MESH-6-LINK_UPDOWN: Mesh station dca5.f4b8.302f link Down

*Sep 24 19:31:31.115: %MESH-4-NO_POTENTIAL_PARENT: There are no potential parents

*Sep 24 19:31:31.315: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 going down

*Sep 24 19:31:31.319: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down

*Sep 24 19:31:32.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down

*Sep 24 19:31:36.131: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:36.139: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:38.155: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:38.163: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:40.179: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:40.187: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:42.203: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:42.211: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:44.227: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:44.235: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired

*Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: Did not get join response

*Sep 24 19:31:44.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:31:44.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:31:45.843: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:31:45.895: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:31:45.895: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:31:45.895: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:31:46.251: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:46.259: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:48.275: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:48.283: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:50.299: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:50.307: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:52.323: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:52.331: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:54.347: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:54.355: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:31:55.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:31:56.371: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:56.379: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:58.395: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:31:58.403: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:00.419: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:00.427: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:02.443: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:02.451: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:04.467: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:04.475: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:32:05.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:32:06.491: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:06.499: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:08.515: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:08.523: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:10.539: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:10.547: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:12.563: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:12.571: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:14.587: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:14.595: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:32:15.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:32:16.611: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:16.619: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:18.635: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:18.643: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:20.659: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:20.667: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:22.683: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:22.691: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:24.707: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:24.715: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:32:25.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:32:26.731: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:26.739: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:32:29.739: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 dot1x control

*Sep 24 19:32:29.743: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up

*Sep 24 19:32:30.743: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up

*Sep 24 19:32:35.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:32:35.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:32:35.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:32:38.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.

*Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.

*Sep 24 19:32:41.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2

*Sep 24 19:32:51.899: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:32:59.239: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:32:59.239: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.

*Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4

*Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Sep 24 19:33:01.899: %CAPWAP-3-ERRORLOG: Failed to process timer message.

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:33:04.239: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:33:04.299: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4

*Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:33:04.339: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup

*Sep 24 19:33:07.855: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod A, ip_dhcp_addr 1

*Sep 24 19:33:07.855: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:33:07.855: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Sep 24 19:33:07.927: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 42.117.53.12, mask 255.255.255.0, hostname APdca5.f4b8.5480

*Sep 24 19:33:07.927: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod A, ip_dhcp_addr 1

*Sep 24 19:33:07.927: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:33:07.927: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

% CDP is not supported on this interface, or for this encapsulation

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

*Sep 24 19:33:12.927: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:33:12.963: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:33:12.987: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:33:13.027: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:33:13.027: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:33:14.027: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:33:14.027: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP

*Sep 24 19:33:14.027: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Sep 24 19:33:23.027: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

*Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:33:23.027: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:33:23.031: %CAPWAP-3-EVENTLOG: Discovery Response from 10.124.133.40

*Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).

*Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Sep 24 19:33:33.027: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..

*Sep 24 19:33:33.027: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Sep 24 19:33:33.000: %CAPWAP-3-EVENTLOG: Setting time to 19:33:33 UTC Sep 24 2013

*Sep 24 19:33:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:33:33.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Sep 24 19:33:33.591: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:33:38.591: %CAPWAP-3-EVENTLOG: Join request: version=117728256

*Sep 24 19:33:38.591: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Sep 24 19:33:38.591: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired

*Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: Did not get join response

*Sep 24 19:34:32.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246

*Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:34:32.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:34:33.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:34:33.059: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:34:33.099: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:34:33.099: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).

*Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Sep 24 19:34:43.099: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..

*Sep 24 19:34:43.099: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Sep 24 19:34:43.000: %CAPWAP-3-EVENTLOG: Setting time to 19:34:43 UTC Sep 24 2013

*Sep 24 19:34:43.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:34:43.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Sep 24 19:34:43.591: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:34:48.591: %CAPWAP-3-EVENTLOG: Join request: version=117728256

*Sep 24 19:34:48.591: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Sep 24 19:34:48.591: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40

*Sep 24 19:35:29.111: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Sep 24 19:35:29.111: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Sep 24 19:35:29.111: %MESH-6-LINK_UPDOWN: Mesh station dca5.f4b8.302f link Down

*Sep 24 19:35:29.111: %MESH-4-NO_POTENTIAL_PARENT: There are no potential parents

*Sep 24 19:35:29.311: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 going down

*Sep 24 19:35:29.315: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down

*Sep 24 19:35:30.315: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down

*Sep 24 19:35:34.127: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:34.135: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:36.151: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:36.159: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:38.175: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:38.183: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:40.199: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:40.207: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:35:42.223: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:42.231: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired

*Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: Did not get join response

*Sep 24 19:35:42.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246

*Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:35:42.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:35:43.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:35:43.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:35:43.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:35:43.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:35:44.247: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:44.255: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:46.271: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:46.279: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:48.295: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:48.303: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:50.319: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:50.327: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:52.343: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:52.351: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:35:53.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:35:54.367: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:54.375: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:56.391: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:56.399: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:58.415: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:35:58.423: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:00.439: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:00.447: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:02.463: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:02.471: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:36:03.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:36:04.487: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:04.495: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:06.511: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:06.519: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:08.535: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:08.543: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:10.559: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:10.567: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:12.583: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:12.591: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:36:13.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:36:14.607: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:14.615: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:16.631: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:16.639: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:18.655: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:18.663: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:20.679: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:20.687: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:22.703: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:22.711: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:36:23.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:36:24.727: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:24.735: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:36:27.735: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 dot1x control

*Sep 24 19:36:27.739: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up

*Sep 24 19:36:28.739: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up

*Sep 24 19:36:33.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:36:33.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:36:33.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:36:36.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.

*Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.

*Sep 24 19:36:39.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2

*Sep 24 19:36:49.091: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:36:57.235: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:36:57.235: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.

*Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4

*Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Sep 24 19:36:59.091: %CAPWAP-3-ERRORLOG: Failed to process timer message.

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:37:02.235: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:37:02.295: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4

*Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:37:02.335: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup

*Sep 24 19:37:05.851: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod A, ip_dhcp_addr 1

*Sep 24 19:37:05.851: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:37:05.851: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Sep 24 19:37:05.923: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 42.117.53.12, mask 255.255.255.0, hostname APdca5.f4b8.5480

*Sep 24 19:37:05.923: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod A, ip_dhcp_addr 1

*Sep 24 19:37:05.923: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:37:05.923: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

% CDP is not supported on this interface, or for this encapsulation

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

*Sep 24 19:37:10.923: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:37:10.963: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:37:10.983: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:37:11.023: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:37:11.023: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:37:12.023: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:37:12.023: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP

*Sep 24 19:37:12.023: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Sep 24 19:37:20.875: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

*Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:37:20.875: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:37:20.879: %CAPWAP-3-EVENTLOG: Discovery Response from 10.124.133.40

*Sep 24 19:37:20.919: %CAPWAP-3-EVENTLOG: Discovery Response from 42.117.52.200

*Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).

*Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Sep 24 19:37:30.875: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..

*Sep 24 19:37:30.875: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Sep 24 19:37:31.000: %CAPWAP-3-EVENTLOG: Setting time to 19:37:31 UTC Sep 24 2013

*Sep 24 19:37:31.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:37:31.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Sep 24 19:37:31.591: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:37:36.595: %CAPWAP-3-EVENTLOG: Join request: version=117728256

*Sep 24 19:37:36.595: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Sep 24 19:37:36.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired

*Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: Did not get join response

*Sep 24 19:38:30.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246

*Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:38:30.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:38:31.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:38:31.059: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:38:31.099: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:38:31.099: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).

*Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Sep 24 19:38:41.099: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..

*Sep 24 19:38:41.099: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Sep 24 19:38:41.000: %CAPWAP-3-EVENTLOG: Setting time to 19:38:41 UTC Sep 24 2013

*Sep 24 19:38:41.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:38:41.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Sep 24 19:38:41.595: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:38:46.595: %CAPWAP-3-EVENTLOG: Join request: version=117728256

*Sep 24 19:38:46.595: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

*Sep 24 19:38:46.595: %CAPWAP-5-SENDJOIN: sending Join Request to 10.124.133.40

APdca5.f4b8.5480#

APdca5.f4b8.5480#sh cap

APdca5.f4b8.5480#sh capwap ?

client CAPWAP Client Information

ids CAPWAP IDS Information

ip CAPWAP IP configuration

location CAPWAP Location Information

mcast CAPWAP Mcast Information

reap CAPWAP FlexConnect Information

rm CAPWAP RM Information

APdca5.f4b8.5480#sh capwap cli

APdca5.f4b8.5480#sh capwap client ?

callinfo Lwapp client Call Info

config CAPWAP Client NV Config File

detailrcb Lwapp client rcb Info

ha CAPWAP Client HA parameters

mn CAPWAP Client 80211 MN

rcb CAPWAP Client RCB

timers CAPWAP Client Timers

traffic CAPWAP Client 80211 Traffic

APdca5.f4b8.5480#sh capwap ?

client CAPWAP Client Information

ids CAPWAP IDS Information

ip CAPWAP IP configuration

location CAPWAP Location Information

mcast CAPWAP Mcast Information

reap CAPWAP FlexConnect Information

rm CAPWAP RM Information

APdca5.f4b8.5480#sh capwap

*Sep 24 19:39:27.259: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired

*Sep 24 19:39:27.259: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired

*Sep 24 19:39:27.259: %MESH-6-LINK_UPDOWN: Mesh station dca5.f4b8.302f link Down

*Sep 24 19:39:27.259: %MESH-4-NO_POTENTIAL_PARENT: There are no potential parents

*Sep 24 19:39:27.459: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 going down

*Sep 24 19:39:27.463: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down

*Sep 24 19:39:28.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down

*Sep 24 19:39:32.275: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:32.283: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:34.299: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:34.307: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:36.323: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:36.331: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:38.347: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:38.355: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:39:40.371: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:40.379: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: Wait DTLS timer has expired

*Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: Did not get join response

*Sep 24 19:39:40.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.124.133.40:5246

*Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:39:40.999: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:39:41.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:39:41.091: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:39:41.091: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:39:41.091: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:39:42.395: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:42.403: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:44.419: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:44.427: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:46.443: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:46.451: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:48.467: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:48.475: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:50.491: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:50.499: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:39:51.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:39:52.515: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:52.523: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:54.539: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:54.547: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:56.563: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:56.571: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:58.587: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:39:58.595: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:00.611: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:00.619: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:40:02.635: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:02.643: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:04.659: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:04.667: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:06.683: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:06.691: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:08.707: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:08.715: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:10.731: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:10.739: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:40:11.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:40:12.755: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:12.763: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:14.779: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:14.787: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:16.803: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:16.811: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:18.827: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:18.835: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:20.851: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:20.859: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:40:21.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:40:22.875: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:22.883: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:40:25.883: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor dca5.f4b8.302f VIDB Virtual-Dot11Radio0 dot1x control

*Sep 24 19:40:25.887: %LINK-6-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up

*Sep 24 19:40:26.887: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up

*Sep 24 19:40:31.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:40:31.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:40:31.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:40:34.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.

*Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.

*Sep 24 19:40:37.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not discover any MWAR.

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.40, type 1.

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 10.124.133.41, type 1.

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Not sending discovery request to 42.117.52.200, type 2

*Sep 24 19:40:47.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:40:55.387: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:40:55.387: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.

*Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4

*Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: Failed to handle timer message.

*Sep 24 19:40:57.095: %CAPWAP-3-ERRORLOG: Failed to process timer message.

% CDP is not supported on this interface, or for this encapsulation

*Sep 24 19:41:00.387: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:41:00.447: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: Not waiting for DHCP options as resolve method on interface BVI1 is 4

*Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway NOT found

*Sep 24 19:41:00.487: %CAPWAP-3-EVENTLOG: Could not resolve gateway. Ignoring WLC name lookup

*Sep 24 19:41:04.003: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod A, ip_dhcp_addr 1

*Sep 24 19:41:04.003: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:41:04.003: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

*Sep 24 19:41:04.075: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 42.117.53.12, mask 255.255.255.0, hostname APdca5.f4b8.5480

*Sep 24 19:41:04.075: %CAPWAP-3-EVENTLOG: ADDING IP 42.117.53.12, 255.255.255.0 resolvemethod A, ip_dhcp_addr 1

*Sep 24 19:41:04.075: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Teardown.

*Sep 24 19:41:04.075: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started

% CDP is not supported on this interface, or for this encapsulation

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

*Sep 24 19:41:09.075: %CAPWAP-3-EVENTLOG: DTLS session cleanup completed. Restarting capwap state machine.

*Sep 24 19:41:09.111: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Sep 24 19:41:09.135: %CAPWAP-3-EVENTLOG: CAPWAP state not up. Abort sending channel and power levels info.10:124:133:40

*Sep 24 19:41:09.175: %CAPWAP-3-EVENTLOG: Starting Discovery. Initializing discovery latency in discovery responses.

*Sep 24 19:41:09.175: %CAPWAP-3-EVENTLOG: CAPWAP State: Discovery.

*Sep 24 19:41:10.175: %CAPWAP-3-EVENTLOG: spamResolveStaticGateway - gateway found 42.117.53.1

*Sep 24 19:41:10.175: %CAPWAP-5-DHCP_OPTION_43: Controller address 42.117.52.200 obtained through DHCP

*Sep 24 19:41:10.175: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Sep 24 19:41:19.175: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

*Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:41:19.175: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

*Sep 24 19:41:19.179: %CAPWAP-3-EVENTLOG: Discovery Response from 10.124.133.40

*Sep 24 19:41:19.219: %CAPWAP-3-EVENTLOG: Discovery Response from 42.117.52.200

*Sep 24 19:41:29.175: %CAPWAP-3-EVENTLOG: Selected MWAR 'AJB-C1-WLC5508-1' (index 0).

*Sep 24 19:41:29.175: %CAPWAP-3-EVENTLOG: Ap mgr count=1

*Sep 24 19:41:29.175: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Sep 24 19:41:29.175: %CAPWAP-3-EVENTLOG: Choosing AP Mgr with index 0, IP = 0xA7C8528 , load = 0..

*Sep 24 19:41:29.175: %CAPWAP-3-EVENTLOG: Synchronizing time with AC time.

*Sep 24 19:41:29.000: %CAPWAP-3-EVENTLOG: Setting time to 19:41:29 UTC Sep 24 2013

*Sep 24 19:41:29.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:41:29.000: %CAPWAP-3-EVENTLOG: CAPWAP State: DTLS Setup.

*Sep 24 19:41:29.599: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.124.133.40 peer_port: 5246

*Sep 24 19:41:34.599: %CAPWAP-3-EVENTLOG: Join request: version=117728256

*Sep 24 19:41:34.599: %CAPWAP-3-EVENTLOG: Join request: hasMaximum Message Payload

kcnajaf · ‎09-24-2013

Hi Mohammed,

From the logs you can see AP is sending

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.40 with discovery type set to 1

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 10.124.133.41 with discovery type set to 1

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 42.117.52.200 with discovery type set to 2

*Sep 24 19:40:01.095: %CAPWAP-3-EVENTLOG: Discovery Request sent to 255.255.255.255 with discovery type set to 0

If you dont have High Availability configured on AP like Scot mentioned you can enable Master Controller feature on the particular WLC where you want the AP to get registered to by clearing the private conffigurations on the AP.

Hope that helps.

Regards

Najaf

Please rate when applicable or helpful !!!

mohammed.buda · ‎09-25-2013

Thanks Najaf,

Controller in HA so Master is not an option

Also I have noticed that after 90 minutes or so , Mesh AP gave up joining wrong controller and it joined the right one "which is configured under option 43".

I would like to thank everyone who has commented on this

Mesh AP joins learns controller IP via DHCP and joins different controller