Mesh AP joins learns controller IP via DHCP and joins different controller
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-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
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: 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: 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: 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: 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: 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: spamResolveStaticGateway - gateway NOT found
*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-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-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: 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: 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: 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: 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: 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: spamResolveStaticGateway - gateway NOT found
*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-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-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#
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: 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: 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: 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: 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: 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: spamResolveStaticGateway - gateway NOT found
*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-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-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 discover
Similar Messages
-
No IP Address via DHCP connecting to Cisco WiFi via WPA - after update
Good Evening,
We use Cisco Aeronet WiFi devices at work and use WPA security. I was able to successfully connect via my MacBook Pro until an OS update a few weeks ago. Now I can connect and it appears that I authenticate - however I cannot get a valid IP address (just a 169.x.x.x address).
I can successfully connect to open and WEP networks - but WPA is an issue.
Is this a known issue?
I have applied the latest Airport update I believe.This is an old issue, I have yet to see a fix. I have the same problem; my MBP assigns its own IP address, and no matter what I do, it will connect to the network but not the internet. Interestingly, when I boot my iBook, which I first did to check settings (the iBook always connected easily) the MBP connected. It does this every time. As soon as the iBook boots, or wakes, the MBP does its thing, gets a valid IP address via DHCP, and connects. Even entering a manual address, will not connect the MBP to the internet. Deleting ports, and locations doesn't help.The MBP has connected on its own about three times out of (say) a hundred. Apple engineers here in Australia, said they'd never heard of the problem. Maybe they are asleep. Bah.
-
Anyone know how I can acquire an IP via DHCP and have a hostname in my /etc/hosts file?
currently i get
192.168.100.101 unknown #added by DHCP
would like to have
192.168.100.101 pfw01 loghost
Before I switched to DHCP I had pfw01 in my hostname.le0 file but now it just doesnt see it anymorecheck out this website...it should give you what you needhttp://sunblade100.wells.org.uk/cache/30.html
-
my icloud account keeps telling me that my user name or password for icloud is incorrect but it works for downloading apps etc and joining this forum
Accessing the itunes store and joining this forum are different accounts than an icloud account, so it's not necessarily true that your ID for icloud is the same as for itunes.
Did you set up an icloud account?
To create a new icloud account, go to
http://www.apple.com/icloud/setup/ -
Using one controller as primary DHCP server for 2 or more controllers
Here's my setup
2 - 5508 controllers (40 APs per controller) running 6.0.196.0 (100 user license per controller)
about 80 mixed - 1142 and 1252 APs, trying to put 40 APs on each controller
One subnet connects two controllers together on the management interface on port 1 on both controllers. 10.x.x.x addresses.
Port 2 on each controller (LAG not used) connects to a DMZ via dynamic interfaces for user traffic, 172.x.x.x addresses.
I want to use one controller for all clients to get their DHCP addresses from (no matter what controller their AP is on)
as a primary DHCP server (controller A as primary), then i'd like to point the clients to the other controller (controller B) to be used as a backup DHCP server in case Controller A fails. Also, the APs are setup to have the correct primary and secondary controllers under their high availability setting as well as the mobility group information.
I want to avoid splitting my DHCP scopes between controllers, and I don't have a DHCP server dedicated to this project, so the 5508s should be able to do the job. Or at least I thought.
When configuring the controllers with the proper DHCP scopes, this only seems to work for clients connecting to controller A. Clients on controller B don't get an address from controller A when pointing to that controller, in fact, the wierd thing is that debugging shows DHCP requests going out of port 2 (DMZ traffic) instead of port 1 (management) on controller B. Shouldn't they be going out of the interface that is specified with the DHCP configuration in the dynamic interface? And I don't have "override" turned on in the WLAN configuration so the DHCP server should be taken from the dynamic interface that the user resides on.
Mobility groups are configured correctly between the two controllers and both the control and data paths are up between the two controllers. Another wierd thing, both controllers management interfaces are on the same subnet, no acls or filters, when the mobility groups are configured, controller A can ping controller B, but controller B cannot ping A. The status still shows as UP/UP in the mobility members windows, but they use mPing which seems to work fine. Remove the mobility group configuration and ping works just fine between the boxes. I don't know if this is related to my DHCP issues, but it would seem that if I put the controller A's management address in the dynamic interface configuration for DHCP on controller B, my clients on B should get an address from A's DHCP pool. Controller A's dynamic interfaces all point to controller A's management interface and they work just fine.
I'm trying to load ballance my AP distribution between two boxes, and I'm also trying to have some controller redundancy.
Controller A works just fine, it's in production. Trying to add another controller B to talk A for DHCP is the issue.
Anyone have any clues?
-BlairI guess i was under the impression that when mobility groups were cofigured, the lease time, along with other client information (mac address, IP address and such), would replicated from one controller to the other controller over the EoIP tunnel. If that's not the case, then obviously I'll have to look elsewhere.
Also, does this mean that it will not work, or just that it's not recommended. If it does work and I have to fix something, at least I can move on with my testing, all while pursuing a DHCP server. It doesn't sound like using an AP as a DHCP server is any better than using the controllers for that same purpose.
Thank you for the quick response. -
Clients can not obtain an ip-address via DHCP.
HI all, I would like to share one problem with WLC 5508 .
we added a new virtual interface on the WLC. One new SSID is associated with this interface.
We created a ACL for this interface to restrict the access via WIFI to certian services.
The following services are allowed on this ACL:
TCP-Traffic for HTTPS
UDP-Traffic for DNS
UDP-Traffic for DHCP
TCP-Traffic for HTTP
ICMP-Traffic
TCP-Traffic for CITRIX
The Problem is, as soon as we add a new service to this ACL, we need to reboot the Controller because the Clients which are working over WIFI do not get a IP-Address assigned via DHCP.
It´s not correct that everything works fine because the change were not applied.
The changes of the ACL are applied on the fly, but for reason we don´t know, the clients don´t get a DHCP IP-Address (after changing the ACL) until the Controller is rebooted.
I am attaching configruation from affected wlc
thank youIf shop is coming from a server on the LAN you need to add DHCP as a port they can reach.
Steve
Sent from Cisco Technical Support iPhone App -
Ten 1142N APs and one 2112 Controller MESH Design. Is it possible?
Hi all.
I've came with this question when started wireless design, so will appreciate any help. I want to implement MESH Wireless Design.
There are 3 floor building. One controller connected to one RAP configured AP on each floor by Cat5 cable, so 3 RAPs. Other APs on the floor are configured as MAPs and connected to RAP wirelessly.
The simple diagram:
AP5 AP4 AP3 AP2 RAP1-----Cat5-------Controller 2112 ---Cat5----- DSL Router---Cat5-----Internet
I can't use Cat5 cable to all APs, as there are 3 floor building, with max distances over 300 metres.
The question is:
Can these devices be configured for MESH topology?
I followed that article from cisco website.
Cisco Mesh Access Points, Design and Deployment Guide, Release 7.0.116.0
Is there any other solutions, wirelessly connect controller and 10 APs?
As I thought it can be connected wirelessly, that's a purpose of the controller. But some sellers and technicians say that every AP should be Cat5 connected.
Thanks in advance.I have a similar situation. I have to setup a temporary WLAN solution to handle appx. 400 clients for a 1 day event. I have extremely little time to get this together, such as a couple days, as I said, very impromptu project. I have a WLC 5508 as well as several 1142n LAPs at my disposal. I believe the 1142n can operate as a mesh AP correct? Problem is, where the WLAN and internet is needed, there is no existing infrastructure, I'm aiming to extend our infrastructure there wirelessly. I plan on deploying the 5508 at our location where we do have some infrastructure, setup 2 LAPs as mesh APs, with the root being at same site as WLC. Then extend the network via the mesh APs to the new site. I'll be using a Catalyst 3560-24 PoE at the new site to both power up the APs as well as provide local switching. Then create a new WLAN/SSID for the new site and enable that for necessary access, intent etc.
Does this sound as if it would be a feasible solution for a "quick and dirty" temporary wireless solution? Also, how many LAPs would you recommend to handle appx 400 400 clients? I believe each of those LAPs can handle appx. 25 clients with a max of 50? I don't expect 400 clients to be actively using the system, but in attendance. I just have to ensure that if they opt to connect, they can. Obviously I want adequate performance, but max performance as far as bandwidth is not necessary here, instead maximum connections.
If anyone has any suggestions, I certainly welcome them. Once again, thanks in advance. If I can help by supplying additional information I'll be happy to. Thanks again. -
I moved from 10.6.8 (Snow Leopard) to 10.9 (Mavericks). Apple support won't help because it's not their hardware. It's not a playstation controller, it's Spartan brand, and it never connected via bluetooth (it continues to not connect via bluetooth in Mavericks which is fine). I always just plugged it in and it ran because apparently Apple included drivers for it from Snow Leopard onward. However, in Mavericks that's not the case, as when I plug it in nothing picks it up, and when I tried to connect it via bluetooth I would enter the pairing code and then it wouldn't pair. Anyone got any thoughts/ideas?
Thanks for no help. Such a supportive community. I figured it out on my own. I can only connect it via usb cable (which I'm happy with) and in order to do that I had to go through the bluetooth connection steps for some reason. It doesn't show up as paired but I did the steps outlined in this video - http://www.youtube.com/watch?v=Efk77f6d98Y -, plugged the controller in via usb cable and then it worked.
-
WRT54G: Static mode set on WAN side, but still sometimes pulls address via DHCP!
We've had (6) WRT54G (v5) installed in a building, for about (2) years now, with no previous problems. Now, ALL of them are doing something weird. They are all set for Static mode on the WAN side (we have static ip addresses for these), yet every now and then they will spontaneously pull an address via DHCP on their own. When they do this, the setting itself doesn't change. It will still show "STATIC" in the pull down list. But, the address will no longer be the address we assigned to the unit, and will instead appear to be an address that it pulled via DHCP.
Thanks, in advance, for any help and insight into this strange problem.
DavidAh. In that case, we're not going to put our client through the frustration of chasing a ghost in the machine. We'll just replace them with new ones. But, I'll try this on them in my spare time and let you know how it goes.
Thanks for your assistance,
David
Message Edited by ld-systems on 09-19-2007 08:01 AM -
An attempt to resolve the DNS name of a domain controller in the domain being joined has failed.
"An attempt to resolve the DNS name of a domain controller in the domain being joined has failed."
This is the error message I get whenever I try to connect to my servers domain which I just set up earlier today. I have read through a bunch of other threads on the same error message
but each of them has had different solutions and none of them have helped me.
The one thing that I suspect is related to my problem is that I can't ping my domain on the W7 computer I'm trying to connect. I can ping the server, but not the domain. the domain
i'm using is set up like "domain.local" .
Other things that might be relevant.
I'v already set up user accounts and a computer under the Server 2012 active domain administrator settings.
I'v port forwarded ports 80 and 443 on the server.
The server has a static IPv4 IP adress. I haven't done anything with IPv6
The W7 computer has a dynamic IP adress, but I don't think it changes. I believe my router is set up to keep it constant, not 100% sure though.
Thanks for any help with this, I'm pretty much out of ideas on this.Hi ZachPrinz,
Firstly, would you please let us know the outputs of ipconfig /all both of the clients and the DC.
Also, if you run nslookup FQDN of your DC from your clients, what will you receive?
Meanwhile, regarding the issue, we can refer to
the similar thread and see how it works.
More information:
Troubleshooting Domain Join Error Messages (en-US)
Hope this helps.
Jeremy Wu
TechNet Community Support -
SPA112 not picking up DHCP and cant set via IVR
Firmware 1.2.1.004
I have 2 spa112's that came back from the field
Neither of them will pick up an ip address via DHCP, I tried on multiple routers. The ivr 110# says 0.0.0.0
I also tried setting the ip to static via IVR
101# 1# (this sets to static ip)
111# it says is invalid (It should let me set the ip based on page 7 of the manual)
121# it says is invalid (It should let me set the netmask based on page 7 of the manual)
Are these defective? One was working for 2 weeks the other failed at install time however it did work when we provisioned it.All I can say is - it works for me. May be you missed the response as it's hard to recognize it.
Enter IVR menu. Press 100. Wait until the IVR says one-zero-zero. Press #. IVR will shout "zero". But it will not help you as code 100 return DHCP settings od WAN interface - and SPA112 has no one.
On SPA122, there are two interfaces - WAN and LAN, IVR codes 1xx are dedicated to WAN interface. IVR codes 2xx are dedicated to LAN interface. There are no WAN interface on SPA112, so 1xx codes are meaningless here. As there are no 2xx codes for network settings, the LAN interface can't be configured by IVR. Just use IVR code 210 to obtain LAN IP address, then use browser to configure the device.
I don't know if it is intentional behavior or not. I don't know if it follow the user's manual or not. But the devices seems to work this way.
I got it for business use and my business is without a phone
Do not overdo, please. Even if you are unable to use DHCP to assign IP address, even if you are unable to set static IP via IVR, the phone still can be configured via WWW according your wishes.
Yes, the SPA1xx is buggy device, there are so many issues with it, but this one is not critical issue that make them impossible to use. -
Wireless on 1811W not getting IP via DHCP
What am I doing wrong? The wireless client authenticates to the router, but doesn't get an IP via DHCP? Help??
Hi Jeff,
Just now got the chnace to apply your suggestions and test. Still no go.
Here's the updated config.
Just want the wireless to be an extension of the wired network - no "guest" access required - so no additional DHCP pool/rules to apply. -
Motor Controller communication via PDO CANopen
I am using a Mattkeg Servo position Controller (MDR2300) to control a PMSM via Speed and Position control. The motor controller uses the CANopen protocol to receive commands from the NI Realtime Controller. In order to send the speed, position, velocity, etc commands, I am currently using the SDO method of communication. But I want to use the PDO method in order to do the same.
I am using the 'NI-Industrial Communications for CANopen 1.0.3' library. The examples given by NI regarding PDO, transmit/receive 64bit word. But the way I understand it, the Objects can be mapped to the 4 transmit and 4 receive PDO's so that I can send, for example object values for target_position, profile_velocity, profile_acceleration, and polarity in one PDO msg. I managed to do the PDO mapping using the LabVIEW Batch SDO process. But I don't know how to use it further in my Program. I have attached the current program I have that uses SDO. I wish to accomplish the same using PDO. Has anyone managed to do this?
Thanks a lot for your help..
Attachments:
Position_Control.png 115 KB
Speed_Control.png 103 KBthe more appropriate NI forum http://forums.ni.com/t5/Automotive-and-Embedded-Networks/bd-p/30
-
Code 12 on [VIA PCI to PCI Bridge Controller]
Hi,
I am having an issue while setting up a new pc with the following setup:
MotherBoard: MSI P4M900M3
CPU: Pentium Dual Core e2180
Memory: 2 * 1Gb Kingston DDR2 667
Harddisk: Hitachi SATA 320Gb Harddisk
OS: Windows Professional (upgrade to SP3)
Using the build-in video and audio card provided in the motherboard.
After I installed the OS, i find a yellow exclamation mark in [Device Manager] -> [System Devices] -> [VIA PCI to PCI Bridge Controller] (there are 2 of these entries with the same problem) indicating the problem is :
This device cannot find enough free resources that it can use (code 12).
If you want to use this device, you will need to disable one of the other devices on this system.
I have tried removing the 2 entries and let windows detect it automatically but the same problem still show up.
I have only 1 harddisk, 1 dvd drive and 1 floppy drive connected to the motherboard so i wasn't expecting such conflicts to show up.
Please help.Have you tried to delete them, and let's windows to re-detect them?
Have you done >>Clear CMOS Guide<<?
What mainboard you have? {P4M900M3-F or P4M900M3-L} -
TS1398 ipad setup - can't join my wifi, entered wrong password and now wants DHCP and other info
just got an iPad and set it up, synched with my computer. Then I turned on WiFi (to connect to my home FiOS router) and when it asked for password I entered the wrong one. So, I tried again and now, instead of prompting me for password, it's asking for DHCP and lots of other detailed info that I don't know.I tried turning wifi off and then back on ... same result when I tried to join (the DHCP et. al. prompts). I tried turning the iPad off and back on ... same result.
What to do??? I'm so anxious to try out my new iPad
(P.S. I have an iPhone and have no problem accessing WiFi. This issue with the iPad was obviously triggered by my entering the wrong password)Go to Settings>WiFi>Your Network Name - tap on the blue arrow to the right of the name and then tap - Forget this Network in the next window at the top.
Restart your iPad for good measure and then go back to Settings>WiFi>Your home network name and start over again.
Maybe you are looking for
-
Why is it a shared folder in the music app and why do i need internet to listen to it?
why is it a shared folder in the music app and why do i need internet to listen to it?
-
hi i have a scenatio where the table need scroll bar , so ihave used scroll container for the table and i am able to view both horizontal and vertical scroll var , but i need only verticle scro
-
I upgraded to Photoshop CS6 from CS5.X and I can not open RAW files in Camera RAW for my Nikon D800. It functioned properly in CS5 with the latest RAW release but won't work in CS6.
-
I'm playing bakery story on my ipod.. and it's not working i have plenty of food
i have food and tables but the people wont come in they just wait at the door and they wait there and there clock finishes and then i get brocken hearts HELP !
-
Satellite A200-2BH PSAE6E: Cannot install Flash Cards Support Utility - serial number is invalid
Hi first sorry for my bad English. Second I have a Toshiba notebook Satellite A200-2BH PSAE6E I changeg my OS to Vista and I have a problem with "Flash Cards Support Utility". I can't install it. I have this message error "the serial number is invali