%CAPWAP-3-ERRORLOG in MESH setup WLC7.6
Hello everyone,
I configured a MESH setup consisting of 3 AP's (1 root and 2 remote),
however one AP (remote) cannot join the WLC anymore since I made the changes to static IP and bridge mode.
I can't even reset the AP to factory settings to get it back to WLC appliance...
This is the error logs from the AP - can anyone help?
*Apr 10 16:15:59.187: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Apr 10 16:15:59.231: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Apr 10 16:15:59.235: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 10 16:16:00.235: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Apr 10 16:16:00.263: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 10 16:16:01.263: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Apr 10 16:16:09.187: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Apr 10 16:16:09.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.88.53 peer_port: 5246
*Apr 10 16:16:09.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Apr 10 16:16:09.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 10 16:16:09.411: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.88.53 peer_port: 5246
*Apr 10 16:16:09.411: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.88.53
*Apr 10 16:16:09.415: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Apr 10 16:16:09.415: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Apr 10 16:16:09.415: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Apr 10 16:16:09.415: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 192.168.88.53
*Apr 10 16:16:10.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Apr 10 16:16:10.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 10 16:16:10.047: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Apr 10 16:16:11.083: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 10 16:16:12.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Apr 10 16:16:14.411: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.88.53
*Apr 10 16:16:14.415: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Apr 10 16:16:14.423: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 10 16:16:15.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Apr 10 16:16:15.451: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 10 16:16:16.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Apr 10 16:17:08.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.88.53:5246
*Apr 10 16:17:09.039: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Apr 10 16:17:09.055: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Apr 10 16:17:09.091: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 10 16:17:10.059: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Apr 10 16:17:10.095: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Apr 10 16:17:10.103: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Apr 10 16:17:11.131: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Apr 10 16:17:12.131: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
info0000246:
Are you sure you allowed the AP on the mac filter in your WLC? I was having the same issue today because I had forgotten to add the mac into the mac filtering, as soon as I did that the AP was able to join the controller.
Similar Messages
-
Information about %CAPWAP-3- ERRORLOG messages
Hello,
Does anyone know where to find information about CAPWAP-3 messages like these ?
%CAPWAP-3-ERRORLOG: Failed to send data transfer request.
%CAPWAP-3-ERRORLOG: Queue already full.
Thanks in advance.I'm with Scott.
Post the entire bootup process. This contains vital information than you can surmiss.
Also post the output to the following commands:
1. WLC: sh sysinfo;
2. WLC: sh time;
3. AP: sh version;
4. AP: sh ip interface brief; and
5. AP: sh inventory -
I am trying to get an AP to associate with a wireless Controller but keep getting this error message (%CAPWAP-3-ERRORLOG:Could not resovle CISCO-CAPWAP-CONTRPLLER)
I can ping through to the WLC and the AP.Thanks a lot Loe for the Feedback. The issue was not my configuration but rather the type of Wireless LAN controller I have, the WLC does not support my AP's. I have a Cisco 520 series WLC and got to know they only work with the 500 series AP's. my AP's are 1130 series meaning i have to get another controller or change the APs.
thanks once again.. -
AIR-CAP3702I booting up in mesh mode and not joining our 5508 WLC
I have a batch of 30+ AIR-CAP3702I-A-K9 APs that I need to setup but none of them are joining to the 5508 WLC and when I connect a console cable and view the output from the AP it shows that it is trying to initiate in mesh mode. I have read other forums that are showing that I need to put in the APs MAC address to a filter list on the WLC for it to show up and then I will be able to change it from mesh mode to local mode. The only issue I'm having with that solution is not knowing how it will affect my current production environment off of that 5508 WLC. I have 69 active production APs with clients working off them and there are no MAC filters currently in place on the WLC. By adding a MAC filter entry for the new APs would the WLC create an implicit deny for all other clients that don't have their MAC addresses entered?? If so is there another work around? Can the mode be changed via the CLI on the AP itself to make it local instead of mesh?
sh capwap client rcb
AdminState : ADMIN_ENABLED
SwVer : 7.6.1.118
NumFilledSlots : 2
Name : AP88f0.4290.7184
Location : default location
MwarName : xxxxx
MwarApMgrIp : x.x.x.x !<it has the correct name and IP of the WLC>
MwarHwVer : 0.0.0.0
ApMode : Bridge
ApSubMode : Not Configured
OperationState : JOIN
CAPWAP Path MTU : 576
LinkAuditing : disabled
ApRole : MeshAP
ApBackhaul : 802.11a
ApBackhaulChannel : 0
ApBackhaulSlot : 2
ApBackhaul11gEnabled : 0
ApBackhaulTxRate : 24000
Ethernet Bridging State : 0
Public Safety State : disabled
AP Rogue Detection Mode : Enabled
AP Tcp Mss Adjust : Disabled
AP IPv6 TCP MSS Adjust : Disabled
Predownload Status : None
Auto Immune Status : Disabled
RA Guard Status : Disabled
Efficient Upgrade State : Disabled
Efficient Upgrade Role : None
TFTP Server : Disabled
Antenna Band Mode : Unknown
802.11bg(0) Radio
ADMIN State = ENABLE [1]
OPER State = DOWN [1]
CONFIG State = UP [2]
HW State = UP [4]
Radio Mode : Bridge
GPR Period : 0
Beacon Period : 0
DTIM Period : 0
World Mode : 1
VoceraFix : 0
Dfs peakdetect : 1
Fragmentation Threshold : 2346
Current Tx Power Level : 0
Current Channel : 11
Current Bandwidth : 20
802.11a(1) Radio
ADMIN State = ENABLE [1]
OPER State = DOWN [1]
CONFIG State = UP [2]
HW State = UP [4]
Radio Mode : Bridge
GPR Period : 0
Beacon Period : 0
DTIM Period : 0
World Mode : 1
VoceraFix : 0
Dfs peakdetect : 1
Fragmentation Threshold : 2346
Current Tx Power Level : 1
Current Channel : 165
Current Bandwidth : 20
It is showing the following error on our WLC in the log file:
Tue Jul 15 14:01:26 2014
AAA Authentication Failure for UserName:88f042907184 User Type: WLAN USER
And here are some of the errors it's showing on the AP after bootup:
*Jul 15 17:47:30.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Jul 15 17:47:31.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 15 17:47:31.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:31.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 15 17:47:31.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 15 17:47:32.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:33.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 15 17:47:35.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
*Jul 15 17:47:35.471: %DTLS-5-ALERT: Received WARNING : Close notify alert from x.x.x.x
*Jul 15 17:47:35.475: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 15 17:47:35.483: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 15 17:47:36.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 15 17:47:36.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 15 17:47:37.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Jul 15 17:48:15.007: %MESH-6-LINK_UPDOWN: Mesh station 88f0.4290.7184 link Down
*Jul 15 17:48:17.007: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Jul 15 17:48:22.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: Invalid event 31 & state 4 combination
*Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 31, state 4 -
CAPWAP: Retransmission count for packet exceeded
We are noticing that WLAN-APs with HREAP-setup are jumping between different remotely located WLCs.
The APs are LAP1131 and LAP1242 with IOS 12.4(21a)JHC and WLC 4402-50-K9 with 6.0.202-image
All starts with the following Log-entries in the WLAN-APs:
*Jan 24 08:22:50.036: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max (CAPWAP_ECHO_REQUEST., 1)
*Jan 24 08:22:50.036: %LWAPP-3-CLIENTEVENTLOG: Switching to Standalone mode
*Jan 24 08:22:50.040: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Jan 24 08:22:50.040: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 163.157.1.101:5246
*Jan 24 08:22:50.088: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
*Jan 24 08:22:50.090: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jan 24 08:23:00.093: %CAPWAP-3-ERRORLOG: Selected MWAR 'SGOTWLC03'(index 1).
Who can tell me the reason for this behaviour ?
Is it possible to tune the CAPWAP-parameter retransmission count ?
Thanks in advance
WiniGoing to try to answer this a different way for anyone Googling this who needs an answer.
"Is it possible to tune the CAPWAP-parameter retransmission count?"
Yes. See here:
http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED_chapter_01110110.html
Browse to your WLC.
Choose "Wireless" from the top bar.
Under "Access Points" on the left, choose "Global Configuration."
In the main panel off to the right you will see "AP Retransmit Config Parameters" with 2 options: "AP Retransmit Count" and "AP Retransmit Interval."
AP Retransmit Count is how many times it will try to contact a WLC before failing. Maximum is 8.
AP Retransmit Interval is how long between each try. Maximum is 5.
(AP Retransmit Count) * (AP Retransmit Interval) = How long the AP can go without talking to a WLC, in seconds.
If you are using FlexConnect Local Switching and FlexConnect Local Auth, the AP SHOULD still be able to handle clients during this timeframe.
When an AP cannot contact a WLC...
Step 1.) When the retransmit count (max 8, with a max 5 second interval, so 40 seconds max) is exceeded, the AP goes into Standalone mode (similar to Autonomous) and tries to contact a WLC via its static IP for apprx 5 minutes.
Step 2.) If unsuccessful, the AP switches to DHCP, renews the DHCP lease (to get a new IP address) and tries again to contact a WLC for apprx 3 minutes. This repeats 3 times, for a total of apprx 9-10 minutes.
Step 3.) If after step 2 the AP could still not find a controller, the AP reboots itself and starts at Step 1 all over again. Reboot takes apprx 2-3 minutes.
Note if using DHCP addresses, the process may start at Step 2.
Yes, the maximum time an AP can be out of contact with its WLC then is 40 seconds. If you're just using CAPWAP to configure and reconfigure APs which are otherwise nearly autonomous, this can be quite the annoying level of neediness.
"Who can tell me the reason for this behaviour?"
I believe this behaviour is to ensure management capability, and also to support some of the more "interesting" (for lack of a better term) reasons for CAPWAP... maybe wireless client mobility, remote switching, remote authentication, etc. In those scenarios you DO want your APs to be "needy."
Message was edited by: Mark Withers - not mesh... - -
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 helpNajaf,
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 -
AIR-CAP1532I in a non-mesh environment
Hi.
I'm trying to get a CAP1532I working as a "normal access point" and not in a mesh environment.
Is that possible?
If I try to get the AP joining our controller ( 5508 with 7.6.120.0 ), I get these errors:
*Mar 1 00:02:27.495: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Aug 20 10:22:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: XX peer_port: 5246
*Aug 20 10:22:44.515: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: XX peer_port: 5246
*Aug 20 10:22:44.515: %CAPWAP-5-SENDJOIN: sending Join Request to XX
*Aug 20 10:22:44.519: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Aug 20 10:22:44.519: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Aug 20 10:22:44.519: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Aug 20 10:22:44.519: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from XX
*Aug 20 10:22:49.515: %CAPWAP-5-SENDJOIN: sending Join Request to XX
*Aug 20 10:23:43.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to XX:5246
*Aug 20 10:23:44.031: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Aug 20 10:23:44.083: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Aug 20 10:23:44.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Aug 20 10:23:45.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Aug 20 10:23:45.139: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Aug 20 10:23:46.139: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
IP of the controller is correct through DHCP.
We don't have any mesh access points in our network and I don't think that would be possible because we have more than one country code registred.
No information in the controller log, so I don't know what to do now.
Does anyone has an idea?
Regards,
SvenHello Sandeep.
I already added the MAC address to the filter.
I did everything that was in the configuration guide.
Here is the further information:
sh version
Cisco IOS Software, C1530 Software (ap1g3-K9W8-M), Version 15.2(4)JB3b, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Thu 23-Jan-14 21:52 by prod_rel_team
ROM: Bootstrap program is C1530 boot loader
BOOTLDR: C1530 Boot Loader (ap1g3-BOOT-M) Version 15.2(4)JB3b, RELEASE SOFTWARE (fc1)
AP78da.6e60.8a72 uptime is 3 minutes
System returned to ROM by power-on
System image file is "flash:/ap1g3-k9w8-mx.152-4.JB3b/ap1g3-k9w8-mx.152-4.JB3b"
Last reload reason: Reload
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-CAP1532I-E-K9 (MIPS74k) processor (revision 28) with 204800K/57344K bytes of memory.
Processor board ID FCZ1825H059
MIPS74k CPU at 700Mhz, revision number 0x0000
Last reset from power-on
LWAPP image version 7.6.95.12
2 Gigabit Ethernet interfaces
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 78:DA:6E:60:8A:72
Part Number : 74-11942-01
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC182280HQ
Top Assembly Part Number : 000-00000-00
Top Assembly Serial Number : FCZ1825H059
Top Revision Number : 23
Product/Model Number : AIR-CAP1532I-E-K9
Configuration register is 0xF
sh sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.120.0
Bootloader Version............................... 1.0.16
Field Recovery Image Version..................... 7.0.112.21
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... XX
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. SSO (Both AP and Client SSO)
IP Address....................................... XX
Last Reset....................................... Software reset
System Up Time................................... 10 days 1 hrs 7 mins 54 secs
System Timezone Location......................... (GMT +1:00) Amsterdam, Berlin, Rome, Vienna
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... Multiple Countries:AT,BG,BR,CH,CN,CZ,DE,DK,FI,FR,GB,HK,IT,JP,KR,NL,NO,PL,SE,SK
--More-- or (q)uit
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +27 C
External Temperature............................. +22 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 15
Number of Active Clients......................... 563
Burned-in MAC Address............................ 2C:54:2D:72:60:C0
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 500
Regards,
Sven -
Error Cisco 892f-w Wireless driver lwapp and capwap controller
Hello, greetings to cisco support community, I write to ask for help for my router, I have trouble lifting the wireless network, I hope you can help me thanks.
Upon entering cli ap: I have this error:
*Jul 3 22:33:04.951: %CAPWAP-3-STATIC_TO_DHCP_IP: Could not discover WLC using
static IP. Forcing AP to use DHCP.
*Jul 3 22:33:14.959: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination
*Jul 3 22:33:15.083: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigne
d DHCP address 10.10.10.4, mask 255.255.255.248, hostname AP6400.f1cf.6738
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (8.8.8.8)
Translating "CISCO-LWAPP-CONTROLLER"...domain server (8.8.8.8)
*Jul 3 22:33:18.959: %CAPWAP-3-ERRORLOG: Did not get log server settings from D
HCP.
*Jul 3 22:33:19.083: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROL
LER
*Jul 3 22:33:19.207: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLL
ER
Here is my configuration
Natural#SHOW RUNNing-config
Building configuration...
Current configuration : 5681 bytes
! Last configuration change at 19:56:22 UTC Wed Oct 16 2013 by juanrifle
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Natural
boot-start-marker
boot-end-marker
logging buffered 51200 warnings
no aaa new-model
memory-size iomem 10
service-module wlan-ap 0 bootimage autonomous
crypto pki trustpoint TP-self-signed-634714217
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-634714217
revocation-check none
rsakeypair TP-self-signed-634714217
crypto pki certificate chain TP-self-signed-634714217
certificate self-signed 01
30820229 30820192 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
30312E30 2C060355 04031325 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 36333437 31343231 37301E17 0D313331 30313131 38343833
395A170D 32303031 30313030 30303030 5A303031 2E302C06 03550403 1325494F
532D5365 6C662D53 69676E65 642D4365 72746966 69636174 652D3633 34373134
32313730 819F300D 06092A86 4886F70D 01010105 0003818D 00308189 02818100
E814BC99 A2374C6C C52A0828 7D8D2215 5220B891 63F3CB16 C03D6F00 F3ECF2E9
BE71FB32 9D1388FA 608C3267 3105F7E9 4A0FADDB C3031255 2054BF5D 971D4B0F
AD5914F8 8D7E9CF3 FBDDD586 63C8D981 3C32F53F E43CE93F 20930CFA 9F6055E7
810AF11D D8CBF7EA D6D5B680 B9AA465C EA9D533B A8E39059 6401101F D81939C9
02030100 01A35330 51300F06 03551D13 0101FF04 05300301 01FF301F 0603551D
23041830 168014A1 4A274F69 1972E173 6F458E3E 67212F22 A21F3F30 1D060355
1D0E0416 0414A14A 274F6919 72E1736F 458E3E67 212F22A2 1F3F300D 06092A86
4886F70D 01010505 00038181 006B165B E1CABC78 F125A399 A8DB860B 7A134E69
A342D73A A5215D08 E675406C 318E1877 EFCBB5E8 747291F3 6D39D0CD DD38FE96
E4829127 A2BB4F47 CF1BA9A1 43631C0B BE5932A7 BDE1EAEB 98F832AC 83EAB223
141BB6A0 3ECD607B 8E126FDC 5AC8AD12 28F8DB6A 9742994B 063610C6 D5144944
8A129632 AC689172 1B108332 44
quit
ip cef
ip dhcp excluded-address 10.10.10.1
ip dhcp excluded-address 10.10.10.145
ip dhcp excluded-address 10.10.10.153
ip dhcp excluded-address 10.10.10.1 10.10.10.2
ip dhcp pool ccp-pool
import all
network 10.10.10.0 255.255.255.248
default-router 10.10.10.1
dns-server 8.8.8.8 200.87.100.10
lease 0 2
ip dhcp pool ccp
dns-server 8.8.8.8 200.87.100.10
ip dhcp pool Oficina wireless pool
import all
network 10.10.10.144 255.255.255.248
default-router 10.10.10.145
dns-server 8.8.8.8 200.87.100.10
ip dhcp pool guest pool
import all
network 10.10.10.152 255.255.255.248
default-router 10.10.10.153
dns-server 8.8.8.8 200.87.100.10
no ip domain lookup
ip domain name yourdomain.com
no ipv6 cef
multilink bundle-name authenticated
license udi pid CISCO892FW-A-K9 sn FTX172783RH
username ******** privilege 15 password 0 ******
username ******** privilege 15 secret 4 df2cx1EOReyOFTzHQGHyju0MCCMPPDggzToRobK46
vI
redundancy
interface BRI0
no ip address
encapsulation hdlc
shutdown
isdn termination multidrop
interface FastEthernet0
no ip address
spanning-tree portfast
interface FastEthernet1
no ip address
interface FastEthernet2
no ip address
interface FastEthernet3
no ip address
interface FastEthernet4
no ip address
interface FastEthernet5
no ip address
interface FastEthernet6
no ip address
interface FastEthernet7
no ip address
interface FastEthernet8
description modem adsl
ip address dhcp
ip flow ingress
ip flow egress
ip nat outside
ip virtual-reassembly in
duplex auto
speed auto
interface GigabitEthernet0
no ip address
shutdown
duplex auto
speed auto
interface wlan-ap0
description Service module interface to manage the embedded AP
ip unnumbered Vlan1
arp timeout 0
interface Wlan-GigabitEthernet0
description Internal switch interface connecting to the embedded AP
switchport trunk allowed vlan 1-3,1002-1005
switchport mode trunk
no ip address
interface Vlan1
description $ETH-SW-LAUNCH$$INTF-INFO-HWIC 4ESW$
ip address 10.10.10.1 255.255.255.248
ip nat inside
ip virtual-reassembly in
ip tcp adjust-mss 1452
interface Vlan2
description wireless oficina
ip address 10.10.10.145 255.255.255.248
ip nat inside
ip virtual-reassembly in
interface Vlan3
description wireless guest
ip address 10.10.10.153 255.255.255.248
ip nat inside
ip virtual-reassembly in
ip forward-protocol nd
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip flow-export destination 10.10.10.5 2055
ip nat inside source list 110 interface FastEthernet8 overload
ip sla auto discovery
access-list 10 permit 10.10.10.0 0.0.0.7
access-list 23 permit 10.10.10.0 0.0.0.7
access-list 110 permit ip 10.10.10.0 0.0.0.255 any
access-list 120 remark wireless guest Restriction
access-list 120 permit udp host 0.0.0.0 eq bootpc host 255.255.255.255 eq bootps
access-list 120 permit ip 10.10.10.152 0.0.0.7 any
access-list 120 deny ip 10.10.10.152 0.0.0.7 0.0.0.0 255.255.255.0
access-list 120 deny ip 10.10.10.152 0.0.0.7 172.16.0.0 0.15.255.255
access-list 120 deny ip 10.10.10.152 0.0.0.7 192.168.0.0 0.0.255.255
no cdp run
control-plane
mgcp profile default
line con 0
login local
line 2
no activation-character
no exec
transport preferred none
transport input all
transport output pad telnet rlogin udptn ssh
line aux 0
line vty 0 4
access-class 23 in
privilege level 15
login local
transport input telnet ssh
line vty 5 15
access-class 23 in
privilege level 15
login local
transport input telnet ssh
end
Natural#Hi Andrew,
LAP always download the image run on a WLC (in this case 3850). So no point upgrade LAP independantly as it will always sync with image run on the controller it joins.
In this case you can upgrade 3850 to 3.3.2 (which is the latest image as of today) if you are not already running that code
HTH
Rasika
**** Pls rate all useful resposnes **** -
WLC 5508 - LAP1242: Failed to handle capwap control message from controller
Hello everyone,
after finally successfully upgrading my WLCs from 6.0.199.4 to 7.6.100.0 there is another problem showing up...
If I want to change any configuration regarding the APs on the WLCs (which doesn't work) I get the following error-messages from the APs:
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.169: %CAPWAP-3-ERRORLOG: Validate Msg: msg type 12 does not supported payload 215
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.169: %CAPWAP-3-ERRORLOG: Validate Msg: error in Unknown Payload(215) payload (received length = 9, payload type = 215)
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.170: %CAPWAP-3-ERRORLOG: Failed to validate vendor specific message element type 215 len 9.
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.170: %CAPWAP-3-ERRORLOG: Failed to decode Configuration update request.
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.170: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 7 state 11.
*spamApTask7: Feb 27 14:34:00.558: 00:3a:9a:d6:5d:30 Test-AP-09-03: *Feb 27 13:34:00.171: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
Find attached some informations regarding the AP and the 5508.
Any suggestions are, as always, highly appriciated.
Regards
ManuelGood morning,
if I need free space at the flash: How much is "enough" to handle config changes?
Here you can see the filesystem of one of my accesspoints (all are affected):
AP#dir all-filesystems
Directory of arch:/
2 -rwx 91288 Feb 22 2014 18:16:42 +00:00 event.log
8 drwx 448 Feb 22 2014 18:16:38 +00:00 c1240-k9w8-mx.124-25e.JAO3
4 drwx 0 Nov 2 2011 23:32:18 +00:00 configs
5 -rwx 397 Feb 22 2014 18:19:03 +00:00 env_vars
6 -rwx 6168 Feb 27 2014 18:14:24 +00:00 private-multiple-fs
No space information available
Directory of flash:/
2 -rwx 91288 Feb 22 2014 18:16:42 +00:00 event.log
8 drwx 448 Feb 22 2014 18:16:38 +00:00 c1240-k9w8-mx.124-25e.JAO3
4 drwx 0 Nov 2 2011 23:32:18 +00:00 configs
5 -rwx 397 Feb 22 2014 18:19:03 +00:00 env_vars
6 -rwx 6168 Feb 27 2014 18:14:24 +00:00 private-multiple-fs
15740928 bytes total (10614784 bytes free)
Directory of zflash:/
2 -rwx 91288 Feb 22 2014 18:16:42 +00:00 event.log
8 drwx 448 Feb 22 2014 18:16:38 +00:00 c1240-k9w8-mx.124-25e.JAO3
4 drwx 0 Nov 2 2011 23:32:18 +00:00 configs
5 -rwx 397 Feb 22 2014 18:19:03 +00:00 env_vars
6 -rwx 6168 Feb 27 2014 18:14:24 +00:00 private-multiple-fs
15740928 bytes total (10614784 bytes free)
Directory of archive:/
No files in directory
No space information available
Directory of system:/
2 dr-x 0 memory
1 -rw- 17631 running-config
No space information available
Directory of nvram:/
30 -rw- 0 startup-config
31 ---- 0 private-config
1 ---- 4100 lwapp_ap.cfg
6 ---- 528 lwapp_ap_tlv.cfg
32768 bytes total (26572 bytes free)
Regards, Manuel -
Autonomous 1252 converted to CAPWAP will not join 5508 WLC
WLC 5508 firmware is v6.0.188.0
I've tried updating the autonomous 1252 via both the upgrade tool 3.4 and 'archive download-sw' from the CLI
I've tried multiple recovery images
c1250-rcvk9w8-tar.124-21a.JA2.tar
c1250-rcvk9w8-tar.124-10b.JDA.tar
After AP reboots with recovery image it joins WLC and downloads new CAPWAP image then reboots again
AP will not rejoin WLC with updated CAPWAP firmware
Any help with this is greatly appreciated!
Thanks in advance and happy holidays,
Scott
Error Msg from 1252 console
*Dec 18 15:52:50.691: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.100.2 peer_port: 5246
*Dec 18 15:52:50.695: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.2
*Dec 18 15:52:50.695: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message from 192.168.100.2
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.100.2
Additional info
WLC Debugs Enabled:
MAC address ................................ c4:7d:4f:39:31:e2
Debug Flags Enabled:
aaa detail enabled.
capwap error enabled.
capwap critical enabled.
capwap events enabled.
capwap state enabled.
dtls event enabled.
lwapp events enabled.
lwapp errors enabled.
pm pki enabled.
WLC Debug Output:
*Dec 18 10:51:51.575: dtls_conn_hash_search: Connection not found in hash table - Table empty.
*Dec 18 10:51:51.575: sshpmGetCID: called to evaluate <cscoDefaultIdCert>
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: called to get cert for CID 154c7072
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultCaCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultRootCaCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 2, certname >bsnDefaultCaCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 3, certname >bsnDefaultBuildCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 4, certname >cscoDefaultNewRootCaCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 5, certname >cscoDefaultMfgCaCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCertFromCID: comparing to row 2, certname >cscoDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCID: called to evaluate <cscoDefaultIdCert>
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*Dec 18 10:51:51.575: sshpmGetSshPrivateKeyFromCID: called to get key for CID 154c7072
*Dec 18 10:51:51.575: sshpmGetSshPrivateKeyFromCID: comparing to row 0, certname >bsnOldDefaultIdCert<
*Dec 18 10:51:51.576: sshpmGetSshPrivateKeyFromCID: comparing to row 1, certname >bsnDefaultIdCert<
*Dec 18 10:51:51.576: sshpmGetSshPrivateKeyFromCID: comparing to row 2, certname >cscoDefaultIdCert<
*Dec 18 10:51:51.576: sshpmGetSshPrivateKeyFromCID: match in row 2
*Dec 18 10:51:51.692: acDtlsCallback: Certificate installed for PKI based authentication.
*Dec 18 10:51:51.693: local_openssl_dtls_record_inspect: record=Handshake epoch=0 seq=0
*Dec 18 10:51:51.693: local_openssl_dtls_record_inspect: msg=ClientHello len=44 seq=0 frag_off=0 frag_len=44
*Dec 18 10:51:51.693: openssl_dtls_process_packet: Handshake in progress...
*Dec 18 10:51:51.693: local_openssl_dtls_send: Sending 60 bytes
*Dec 18 10:51:51.694: dtls_conn_hash_search: Searching hash for Local 192.168.100.2:5246 Peer 192.168.100.54:62227
*Dec 18 10:51:51.694: local_openssl_dtls_record_inspect: record=Handshake epoch=0 seq=1
*Dec 18 10:51:51.694: local_openssl_dtls_record_inspect: msg=ClientHello len=76 seq=1 frag_off=0 frag_len=76
*Dec 18 10:51:51.695: openssl_dtls_process_packet: Handshake in progress...
*Dec 18 10:51:51.695: local_openssl_dtls_send: Sending 544 bytes
*Dec 18 10:51:51.695: local_openssl_dtls_send: Sending 544 bytes
*Dec 18 10:51:51.696: local_openssl_dtls_send: Sending 314 bytes
*Dec 18 10:51:51.712: dtls_conn_hash_search: Searching hash for Local 192.168.100.2:5246 Peer 192.168.100.54:62227
*Dec 18 10:51:51.712: local_openssl_dtls_record_inspect: record=Handshake epoch=0 seq=2
*Dec 18 10:51:51.712: local_openssl_dtls_record_inspect: msg=Certificate len=1146 seq=2 frag_off=0 frag_len=519
*Dec 18 10:51:51.712: openssl_dtls_process_packet: Handshake in progress...
*Dec 18 10:51:51.712: dtls_conn_hash_search: Searching hash for Local 192.168.100.2:5246 Peer 192.168.100.54:62227
*Dec 18 10:51:51.712: local_openssl_dtls_record_inspect: record=Handshake epoch=0 seq=3
*Dec 18 10:51:51.712: local_openssl_dtls_record_inspect: msg=Certificate len=1146 seq=2 frag_off=519 frag_len=519
*Dec 18 10:51:51.713: openssl_dtls_process_packet: Handshake in progress...
*Dec 18 10:51:51.713: dtls_conn_hash_search: Searching hash for Local 192.168.100.2:5246 Peer 192.168.100.54:62227
*Dec 18 10:51:51.713: local_openssl_dtls_record_inspect: record=Handshake epoch=0 seq=4
*Dec 18 10:51:51.713: local_openssl_dtls_record_inspect: msg=Certificate len=1146 seq=2 frag_off=1038 frag_len=108
*Dec 18 10:51:51.714: sshpmGetIssuerHandles: locking ca cert table
*Dec 18 10:51:51.714: sshpmGetIssuerHandles: calling x509_alloc() for user cert
*Dec 18 10:51:51.714: sshpmGetIssuerHandles: calling x509_decode()
*Dec 18 10:51:51.719: sshpmGetIssuerHandles: <subject> C=US, ST=California, L=San Jose, O=Cisco Systems, CN=C1250-c47d4f3931e2, [email protected]
*Dec 18 10:51:51.719: sshpmGetIssuerHandles: <issuer> O=Cisco Systems, CN=Cisco Manufacturing CA
*Dec 18 10:51:51.719: sshpmGetIssuerHandles: Mac Address in subject is c4:7d:4f:39:31:e2
*Dec 18 10:51:51.719: sshpmGetIssuerHandles: Cert Name in subject is C1250-c47d4f3931e2
*Dec 18 10:51:51.719: sshpmGetIssuerHandles: Cert is issued by Cisco Systems.
*Dec 18 10:51:51.719: sshpmGetCID: called to evaluate <cscoDefaultMfgCaCert>
*Dec 18 10:51:51.719: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*Dec 18 10:51:51.719: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*Dec 18 10:51:51.719: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*Dec 18 10:51:51.719: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*Dec 18 10:51:51.719: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*Dec 18 10:51:51.719: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*Dec 18 10:51:51.719: sshpmGetCertFromCID: called to get cert for CID 2ab15c0a
*Dec 18 10:51:51.719: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultCaCert<
*Dec 18 10:51:51.719: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultRootCaCert<
*Dec 18 10:51:51.719: sshpmGetCertFromCID: comparing to row 2, certname >bsnDefaultCaCert<
*Dec 18 10:51:51.719: sshpmGetCertFromCID: comparing to row 3, certname >bsnDefaultBuildCert<
*Dec 18 10:51:51.719: sshpmGetCertFromCID: comparing to row 4, certname >cscoDefaultNewRootCaCert<
*Dec 18 10:51:51.719: sshpmGetCertFromCID: comparing to row 5, certname >cscoDefaultMfgCaCert<
*Dec 18 10:51:51.719: ssphmUserCertVerify: calling x509_decode()
*Dec 18 10:51:51.730: ssphmUserCertVerify: user cert verfied using >cscoDefaultMfgCaCert<
*Dec 18 10:51:51.730: sshpmGetIssuerHandles: ValidityString (current): 2009/12/18/15:51:51
*Dec 18 10:51:51.730: sshpmGetIssuerHandles: ValidityString (NotBefore): 2009/11/03/00:47:36
*Dec 18 10:51:51.730: sshpmGetIssuerHandles: ValidityString (NotAfter): 2019/11/03/00:57:36
*Dec 18 10:51:51.730: sshpmGetIssuerHandles: getting cisco ID cert handle...
*Dec 18 10:51:51.730: sshpmGetCID: called to evaluate <cscoDefaultIdCert>
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*Dec 18 10:51:51.730: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*Dec 18 10:51:51.731: sshpmFreePublicKeyHandle: called with 0x1f1f3b8c
*Dec 18 10:51:51.731: sshpmFreePublicKeyHandle: freeing public key
*Dec 18 10:51:51.731: openssl_shim_cert_verify_callback: Certificate verification - passed!
*Dec 18 10:51:51.732: openssl_dtls_process_packet: Handshake in progress...
*Dec 18 10:51:52.155: dtls_conn_hash_search: Searching hash for Local 192.168.100.2:5246 Peer 192.168.100.54:62227
*Dec 18 10:51:52.155: local_openssl_dtls_record_inspect: record=Handshake epoch=0 seq=5
*Dec 18 10:51:52.155: local_openssl_dtls_record_inspect: msg=ClientKeyExchange len=258 seq=3 frag_off=0 frag_len=258
*Dec 18 10:51:52.269: openssl_dtls_process_packet: Handshake in progress...
*Dec 18 10:51:52.269: dtls_conn_hash_search: Searching hash for Local 192.168.100.2:5246 Peer 192.168.100.54:62227
*Dec 18 10:51:52.269: local_openssl_dtls_record_inspect: record=Handshake epoch=0 seq=6
*Dec 18 10:51:52.269: local_openssl_dtls_record_inspect: msg=CertificateVerify len=258 seq=4 frag_off=0 frag_len=258
*Dec 18 10:51:52.269: local_openssl_dtls_record_inspect: record=ChangeCipherSpec epoch=0 seq=7
*Dec 18 10:51:52.269: local_openssl_dtls_record_inspect: record=Handshake epoch=1 seq=0
*Dec 18 10:51:52.269: local_openssl_dtls_record_inspect: msg=Unknown or Encrypted
*Dec 18 10:51:52.273: openssl_dtls_process_packet: Connection established!
*Dec 18 10:51:52.273: acDtlsCallback: DTLS Connection 0x167c5c00 established
*Dec 18 10:51:52.273: openssl_dtls_mtu_update: Setting DTLS MTU for link to peer 192.168.100.54:62227
*Dec 18 10:51:52.273: local_openssl_dtls_send: Sending 91 bytes
*Dec 18 10:53:06.183: sshpmLscTask: LSC Task received a message 4
Aironet 1252 Console Debug:
*Dec 16 11:07:12.055: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 18 15:51:40.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.100.2 peer_port: 5246
*Dec 18 15:51:40.999: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Dec 18 15:51:41.695: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.100.2 peer_port: 5246
*Dec 18 15:51:41.699: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.2
*Dec 18 15:51:41.699: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Dec 18 15:51:41.699: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message from 192.168.100.2
*Dec 18 15:51:41.699: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
*Dec 18 15:51:41.699: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Dec 18 15:51:41.699: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.100.2
*Dec 18 15:51:46.695: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.2
*Dec 18 15:51:46.695: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message from 192.168.100.2
*Dec 18 15:51:46.695: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
*Dec 18 15:51:46.695: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Dec 18 15:51:46.695: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.100.2
*Dec 18 15:52:39.999: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 192.168.100.2:5246
*Dec 18 15:52:40.039: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Dec 18 15:52:40.039: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Dec 18 15:52:40.051: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Dec 18 15:52:40.051: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Dec 18 15:52:40.059: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 18 15:52:40.063: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up
*Dec 18 15:52:40.079: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 18 15:52:40.079: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Dec 18 15:52:50.059: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 18 15:52:50.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.100.2 peer_port: 5246
*Dec 18 15:52:50.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Dec 18 15:52:50.691: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.100.2 peer_port: 5246
*Dec 18 15:52:50.695: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.2
*Dec 18 15:52:50.695: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message from 192.168.100.2
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Dec 18 15:52:50.695: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.100.2
*Dec 18 15:52:55.691: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.100.2
*Dec 18 15:52:55.691: %CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message from 192.168.100.2
*Dec 18 15:52:55.691: %CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
*Dec 18 15:52:55.691: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Dec 18 15:52:55.691: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 192.168.1Nathan and Leo are alluding to CSCte01087. Basically the caveat is that DTLS fails on a non-00:xx:xx:xx:xx:xx L2 first hop. e.g. if the APs are on the same VLAN as the management interface, they must have 00 MACs; if they are on a different VLAN, the WLC/AP gateway must have a 00 MAC. If the workaround below does not suit your environment, open a TAC case for an image with the fix.
Symptom:
An access point running 6.0.188.0 code may be unable to join a WLC5508.
Messages similar to the following will be seen on the AP.
%CAPWAP-3-ERRORLOG: Invalid AC Message Type 4.
%CAPWAP-3-ERRORLOG: Unencrypted non-discovery CAPWAP Control Message
Conditions:
At least one of the following conditions pertains:
- The high order byte of the AP's MAC address is nonzero, and the AP is in
the same subnet as the WLC5508's management (or AP manager) interface
- The WLC's management (or AP manager) interface's default gateway's
MAC address' high order byte is nonzero.
Workaround:
If the MAC address of the WLC's default gateway does not begin with 00,
and if all of the APs' MAC addresses begin with 00, then: you can put
the APs into the same subnet as the WLC's management (or AP manager)
interface.
In the general case, for the situation where the WLC's default gateway's
MAC does not begin with 00, you can address this by changing it to begin
with 00. Some methods for doing this include:
-- use the "mac-address" command on the gateway, to set a MAC address
that begins with 00
-- then enable HSRP on the gateway (standby ip ww.xx.yy.zz) and use this
IP as the WLC's gateway.
For the case where the APs' MAC addresses do not begin with 00, then make
sure that they are *not* in the same subnet as the WLC's management
(AP manager) interface, but are behind a router.
Another workaround is to downgrade to 6.0.182.0. However, after
downgrading the WLC to 6.0.182.0, any APs that have 6.0.188.0 IOS
(i.e. 12.4(21a)JA2) still installed on them will be unable to join.
Therefore, after downgrading the WLC, the APs will need to have a
pre-12.4(21a)JA2 rcvk9w8 or k9w8 image installed on them. -
High CAPWAP traffic when locally switched
Hello all,
We're seeing an ongoing issue where several APs accross multiple sites log the error, "%CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST., 12)", then disassociates from the controller, and reassociates almost immediately. The issue is the users get disassociated from the AP and call the helpdesk.
A counter measure at one site was to add the CAPWAP traffic (udp ports 5246 & 5247) to the controller in our QOS Platinum policy (setting the DSCP bit to 'ef'), but that doesn't seem to help.
We're using Flexconnect with central authentication, local switching.
A couple of questions:
1) The Platinum queue on the QOS is showing over 500 kbps when the only thing put in that queue is the CAPWAP traffic - there aren't any phones. Why so much bandwidth for authentication and control traffic?
2) What is happening with the APs that they can't talk to the controller that causes the issue in the first place? Bandwidth doesn't seem to be an issue.
Below are some config and outputs:
AP-1242#show capwap reap status
AP Mode: REAP, Connected
Radar detected on:
AP-1242#show capwap reap association
REAP Data Switching: Local
2960#show int fa0/22
Hardware is Fast Ethernet
Full-duplex, 100Mb/s, media type is 10/100BaseTX
Last input 00:00:22, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 23000 bits/sec, 13 packets/sec
5 minute output rate 208000 bits/sec, 48 packets/sec
37478173 packets input, 13839718021 bytes, 0 no buffer
Received 2818773 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 502342 multicast, 0 pause input
0 input packets with dribble condition detected
118634332 packets output, 36491262361 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
2811#show policy-map interface multilink 1
Service-policy output: MPLS-QOS
queue stats for all priority classes:
queue limit 64 packets
(queue depth/total drops/no-buffer drops) 0/0/0
(pkts output/bytes output) 300637/46124112
Class-map: PLATINUM (match-any)
300637 packets, 46124112 bytes
30 second offered rate 28000 bps, drop rate 0 bps
Match: ip dscp ef (46)
300637 packets, 46124112 bytes
30 second rate 28000 bps
Priority: 18% (552 kbps), burst bytes 13800, b/w exceed drops: -16
Any help is appreciated.Hi Jeff,
I think you are hitting a bug (CSCse92856) specific to 1242 AP. Solution given is "Enable Proxy ARP on the default-gateway device of your AP". You can try that & see.
Even I cannot view detail of this bug as of insufficient access permission.Therefore I do not know more details about this bug fix & which software version affected,etc. Better you contact Cisco TAC & get more information.
I found this infomration here
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008081103d.shtml
One other reason that H-REAP APs do not join WLCs is if the Proxy ARP is disabled on the gateway for the H-REAP APs. From the AP console, this message is logged:
*Jul 29 14:04:10.897: LWAPP_CLIENT_ERROR_DEBUG:
Retransmission count for packet exceeded more than max(CHANGE_STATE_EVENT , 1)
This can be caused by Cisco bug ID CSCse92856. This problem applies only to AP1130 and AP1240. This problem does not apply to AP1000s, AP1100, or AP1200.
This problem occurs when these conditions are met:
HREAP mode is used in the WLAN. Local mode is not affected by this issue. Native VLAN mapping is required.
The APs have to be on a different IP subnet than the AP Manager of the WLCs.
Proxy ARP is disabled on the default gateway for the AP.
The H-REAP AP gets the default gateway from a DHCP server.
In order to resolve this issue, enable Proxy ARP on the default gateway router of the AP
HTH
Rasika
*** Pls rate all useful responses **** -
CAPWAP APs drop off the 7500 controller
I have a multiple 7500 flex controller deployed with over 2000 APs each on them and I notice that APs occasionally drop off. When I find these APs I am able to telnet to them and I have found a fix for getting them back on the controller, but I want to know why this happens and if there is a way to avoid the problem.
Observed:
The APs have telnet enabled so I can get to the CLI. Once in I do a dir command and see that there is little to no memory available (512 bytes to 0 bytes) in the flash memory. I see that there are 5 large log files, file names are in the commands below. When I do a show logging command I see the following over and over again
*Oct 3 20:31:44.102: %CAPWAP-3-ERRORLOG: Certificate verification failed!
*Oct 3 20:31:44.102: DTLS_CLIENT_ERROR: ../capwap/base_capwap/capwap/base_capwap_wtp_dtls.c:447 Certificate verified failed!
*Oct 3 20:31:44.102: %DTLS-5-SEND_ALERT: Send FATAL : Bad certificate Alert to 10.128.5.5:5246
*Oct 3 20:31:44.102: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.128.5.5:5246
*Oct 3 20:31:44.103: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 3 combination.
*Oct 3 20:32:48.999: %CAPWAP-3-ERRORLOG: Selected MWAR 'tc-cl-wlc01'(index 0).
*Oct 3 20:32:48.999: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Oct 3 20:31:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.128.5.5 peer_port: 5246
*Oct 3 20:31:44.125: CRYPTO_PKI: New CRL Not Valid - expired (router time not synched to CA?)
*Oct 3 20:31:44.125: CRL expires: 05:29:39 UTC Mar 3 2012
*Oct 3 20:31:44.125: Router time: 20:31:44 UTC Oct 3 2013
*Oct 3 20:31:44.125: %PKI-4-CRLINSERTFAIL: Trustpoint "Trustpool2" unknown (error 1804:E_VALIDITY : validity period start later than end)Peer certificate verification failed 0059
To resolve:
The working theory is that the flash gets filled up with log files and is unable to download the certificate from the controller during the join process. I delete the logs with the commands below and then do a wr mem and a copy run start and then reload. This will fix the problem every time.
delete /force flash:ap_log_r0_0.log
delete /force flash:ap_log_r1_0.log
delete /force flash:ap_log_r0_1.log
delete /force flash:ap_log_r0_2.log
delete /force flash:ap_log_r1_1.log
delete /force flash:ap_log_r1_2.log
Other info
- currently running an engineering code of 7.3.113.12 on one 7500 and 7.4.110 on another, both seem to be having this issue. I do not have this issue on a 5508 running 7.5 code. Currently getting 7.4 vetted for deployment.
Good luck with this oneI have seen this issue, but only with older model access points and it doesn't have to be flexconnect and it doesn't matter what WLC code version your running. Problamatic access points, I always check the flash to verify if there are logs or not, and do delete them in order to get the AP back up. Again, I have only seen this with older non-802.11n access points.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered" -
Hi.
I have a question about a CAPWAP messages in my trap logs after upgrading my WISM2 to 7.5.102.
AP "xxxxxx", MAC: 34...... disassoiated previously due to Link Failure Uptime 4 days , 10 h... Reason: Capwap WTP Event request
My AP environment is 1142N attached thru WS-2960S switches. This message was not in my traplogs before upgarding to 7.5.102.
The switch and WAN environment is the same as before upgarding.
Thanks for any tips.
Regards
Johan LindstrandHi,
Thanks for you reply. I´m not sure if my radio stuck, what looks for me that AP lose conectivity for a brief moment with WLC and then recovery connectivity (flapping).
I have APs(same model) at same site without issues, and APs (same model) in others site with same behavior.
AP model LAP1141N
Below logs are from AP reboot process... however joining erros occurs several times during the day... and association time with controller keeps reseting (example: AP up time 1d / association time 15 min).
That instability to AP association creates WLAN instability, because my authentication is central.
*Mar 1 00:12:38.693: %CAPWAP-3-ERRORLOG: Selected MWAR 'WLC01'(index 0).
*Mar 1 00:12:38.693: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 20 14:16:42.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.1 peer_port: 5246
*Dec 20 14:16:42.776: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.1 peer_port: 5246
*Dec 20 14:16:42.777: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.1
*Dec 20 14:16:42.786: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Dec 20 14:16:42.786: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Dec 20 14:16:42.787: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Dec 20 14:16:42.787: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 192.168.1.1
*Dec 20 14:16:42.897: Starting Ethernet promiscuous mode
*Dec 20 14:16:43.202: %LWAPP-4-CLIENTEVENTLOG: OfficeExtend Localssid saved in AP flash
*Dec 20 14:16:43.294: ac_first_hop_mac - IP:10.8.2.136 Hop IP:10.8.2.136 IDB:BVI1
*Dec 20 14:16:44.555: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WLC01 -
Failed to handle capwap control message from controller
Hello,
I am struggling in associating a 1242 AP's with WLC's.
Show version of the AP:
Cisco IOS Software, C1240 Software (C1240-K9W8-M), Version 12.4(25e)JAM2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Mon 29-Jul-13 11:32 by prod_rel_team
ROM: Bootstrap program is C1240 boot loader
BOOTLDR: C1240 Boot Loader (C1240-BOOT-M) Version 12.3(7)JA1, RELEASE SOFTWARE (fc1)
AP0019.56b0.855e uptime is 9 minutes
System returned to ROM by power-on
System image file is "flash:/c1240-k9w8-mx.124-25e.JAM2/c1240-k9w8-mx.124-25e.JAM2"
Show inventory of the AP:
AME: "AP1240", DESCR: "Cisco Aironet 1240 Series (IEEE 802.11a/g) Access Point"
PID: AIR-LAP1242AG-E-K9, VID: V01, SN: FCZ10408384
When trying to attach it to a WLC 5508 running 6.0.199.4, the AP keeps on downloading image and power cycling.
When trying to attach it to a WLC 5508 running 7.4.110.0, the AP shows the following message :
Jan 30 08:24:56.372: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Jan 30 08:24:56.373: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.71.142.7:5246
*Jan 30 08:24:56.427: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jan 30 08:24:56.445: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jan 30 08:24:56.445: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jan 30 08:24:56.447: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan 30 08:24:56.484: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jan 30 08:24:57.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jan 30 08:24:57.473: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jan 30 08:24:57.478: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jan 30 08:24:58.466: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jan 30 08:24:58.473: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jan 30 08:24:58.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan 30 08:24:58.508: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jan 30 08:24:58.513: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jan 30 08:24:59.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jan 30 08:24:59.508: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jan 30 08:24:59.532: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jan 30 08:25:00.532: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jan 30 08:25:06.483: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 30 08:25:07.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.71.142.7 peer_port: 5246
*Jan 30 08:25:08.565: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.71.142.7 peer_port: 5246
*Jan 30 08:25:08.567: %CAPWAP-5-SENDJOIN: sending Join Request to 10.71.142.7
*Jan 30 08:25:08.598: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jan 30 08:25:08.599: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jan 30 08:25:08.599: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jan 30 08:25:08.599: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.71.142.7 Jan 30 08:24:56.372: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Jan 30 08:24:56.373: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.71.142.7:5246
*Jan 30 08:24:56.427: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jan 30 08:24:56.445: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jan 30 08:24:56.445: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jan 30 08:24:56.447: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan 30 08:24:56.484: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jan 30 08:24:57.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jan 30 08:24:57.473: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jan 30 08:24:57.478: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jan 30 08:24:58.466: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jan 30 08:24:58.473: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jan 30 08:24:58.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jan 30 08:24:58.508: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jan 30 08:24:58.513: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jan 30 08:24:59.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jan 30 08:24:59.508: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jan 30 08:24:59.532: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jan 30 08:25:00.532: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jan 30 08:25:06.483: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 30 08:25:07.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.71.142.7 peer_port: 5246
*Jan 30 08:25:08.565: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.71.142.7 peer_port: 5246
*Jan 30 08:25:08.567: %CAPWAP-5-SENDJOIN: sending Join Request to 10.71.142.7
*Jan 30 08:25:08.598: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jan 30 08:25:08.599: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jan 30 08:25:08.599: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jan 30 08:25:08.599: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.71.142.7
Any idea ?
Many thanks !here is the debug output:
login as: groupwls
(Cisco Controller)
User: groupwls
Password:************
Your password does not meet the strong password requirements.For added security, set a new password that meets these requirements. To prevent this message from showing again, disable the strong password feature.
(Cisco Controller) >debug pm pki enable
(Cisco Controller) >debug capwap events enable
(Cisco Controller) >*spamApTask2: Jan 30 09:46:38.639: 00:19:07:c6:39:60 DTLS connection not found, creating new connection for 10:64:94:52 (2134) 10:71:142:8 (5246)
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: called to evaluate
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCertFromCID: called to get cert for CID 155224fa
*spamApTask2: Jan 30 09:46:38.640: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultRootCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 2, certname >bsnDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 3, certname >bsnDefaultBuildCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 4, certname >cscoDefaultNewRootCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 5, certname >cscoDefaultMfgCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCertFromCID: comparing to row 2, certname >cscoDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: called to evaluate
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetSshPrivateKeyFromCID: called to get key for CID 155224fa
*spamApTask2: Jan 30 09:46:38.641: sshpmGetSshPrivateKeyFromCID: comparing to row 0, certname >bsnOldDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetSshPrivateKeyFromCID: comparing to row 1, certname >bsnDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetSshPrivateKeyFromCID: comparing to row 2, certname >cscoDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.641: sshpmGetSshPrivateKeyFromCID: match in row 2
*spamApTask2: Jan 30 09:46:38.883: sshpmGetIssuerHandles: locking ca cert table
*spamApTask2: Jan 30 09:46:38.883: sshpmGetIssuerHandles: calling x509_alloc() for user cert
*spamApTask2: Jan 30 09:46:38.883: sshpmGetIssuerHandles: calling x509_decode()
*spamApTask2: Jan 30 09:46:38.887: sshpmGetIssuerHandles: C=US, ST=California, L=San Jose, O=Cisco Systems, CN=C1240-001956b0855e, [email protected]
*spamApTask2: Jan 30 09:46:38.887: sshpmGetIssuerHandles: O=Cisco Systems, CN=Cisco Manufacturing CA
*spamApTask2: Jan 30 09:46:38.887: sshpmGetIssuerHandles: Mac Address in subject is 00:19:56:b0:85:5e
*spamApTask2: Jan 30 09:46:38.887: sshpmGetIssuerHandles: Cert Name in subject is C1240-001956b0855e
*spamApTask2: Jan 30 09:46:38.887: sshpmGetIssuerHandles: Cert is issued by Cisco Systems.
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCID: called to evaluate
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCertFromCID: called to get cert for CID 2f6d981f
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCertFromCID: comparing to row 0, certname >bsnOldDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCertFromCID: comparing to row 1, certname >bsnDefaultRootCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCertFromCID: comparing to row 2, certname >bsnDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCertFromCID: comparing to row 3, certname >bsnDefaultBuildCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCertFromCID: comparing to row 4, certname >cscoDefaultNewRootCaCert<
*spamApTask2: Jan 30 09:46:38.887: sshpmGetCertFromCID: comparing to row 5, certname >cscoDefaultMfgCaCert<
*spamApTask2: Jan 30 09:46:38.887: ssphmUserCertVerify: calling x509_decode()
*spamApTask2: Jan 30 09:46:38.898: ssphmUserCertVerify: user cert verfied using >cscoDefaultMfgCaCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetIssuerHandles: ValidityString (current): 2014/01/30/09:46:38
*spamApTask2: Jan 30 09:46:38.898: sshpmGetIssuerHandles: ValidityString (NotBefore): 2006/10/05/13:05:43
*spamApTask2: Jan 30 09:46:38.898: sshpmGetIssuerHandles: ValidityString (NotAfter): 2016/10/05/13:15:43
*spamApTask2: Jan 30 09:46:38.898: sshpmGetIssuerHandles: getting cisco ID cert handle...
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: called to evaluate
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 0, CA cert >bsnOldDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 1, CA cert >bsnDefaultRootCaCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 2, CA cert >bsnDefaultCaCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 3, CA cert >bsnDefaultBuildCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 4, CA cert >cscoDefaultNewRootCaCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 5, CA cert >cscoDefaultMfgCaCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 0, ID cert >bsnOldDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 1, ID cert >bsnDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.898: sshpmGetCID: comparing to row 2, ID cert >cscoDefaultIdCert<
*spamApTask2: Jan 30 09:46:38.906: sshpmFreePublicKeyHandle: called with 0x2c058e50
*spamApTask2: Jan 30 09:46:38.906: sshpmFreePublicKeyHandle: freeing public key
*spamApTask2: Jan 30 09:46:40.169: 00:19:07:c6:39:60 Allocated index from main list, Index: 312
*spamApTask2: Jan 30 09:46:40.169: 00:19:07:c6:39:60 DTLS keys for Control Plane are plumbed successfully for AP 10.64.94.52. Index 313
*spamApTask2: Jan 30 09:46:40.169: 00:19:07:c6:39:60 DTLS Session established server (10.71.142.8:5246), client (10.64.94.52:2134)
*spamApTask2: Jan 30 09:46:40.169: 00:19:07:c6:39:60 Starting wait join timer for AP: 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:40.199: 00:19:07:c6:39:60 Join Request from 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:40.200: 00:19:07:c6:39:60 Deleting AP entry 10.64.94.52:2134 from temporary database.
*spamApTask2: Jan 30 09:46:40.201: 00:19:07:c6:39:60 Join Version: = 117730816
*spamApTask2: Jan 30 09:46:40.201: 00:19:07:c6:39:60 Join resp: CAPWAP Maximum Msg element len = 87
*spamApTask2: Jan 30 09:46:40.201: 00:19:07:c6:39:60 Join Response sent to 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:40.201: 00:19:07:c6:39:60 CAPWAP State: Join
*spamApTask2: Jan 30 09:46:40.201: 00:19:07:c6:39:60 capwap_ac_platform.c:1225 - Operation State 0 ===> 4
*apfReceiveTask: Jan 30 09:46:40.201: 00:19:07:c6:39:60 Register LWAPP event for AP 00:19:07:c6:39:60 slot 0
*apfReceiveTask: Jan 30 09:46:40.201: WARP IEs: (12)
*apfReceiveTask: Jan 30 09:46:40.202: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Jan 30 09:46:40.202: WARP IEs: (12)
*apfReceiveTask: Jan 30 09:46:40.202: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Jan 30 09:46:40.202: WARP IEs: (12)
*apfReceiveTask: Jan 30 09:46:40.202: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Jan 30 09:46:40.203: 00:19:07:c6:39:60 Register LWAPP event for AP 00:19:07:c6:39:60 slot 1
*apfReceiveTask: Jan 30 09:46:40.203: WARP IEs: (12)
*apfReceiveTask: Jan 30 09:46:40.203: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Jan 30 09:46:40.203: WARP IEs: (12)
*apfReceiveTask: Jan 30 09:46:40.203: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Jan 30 09:46:40.203: WARP IEs: (12)
*apfReceiveTask: Jan 30 09:46:40.203: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*spamApTask2: Jan 30 09:46:41.021: 00:19:07:c6:39:60 Configuration Status from 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:41.022: 00:19:07:c6:39:60 CAPWAP State: Configure
*spamApTask2: Jan 30 09:46:41.022: 00:19:07:c6:39:60 Updating IP info for AP 00:19:07:c6:39:60 -- static 0, 10.64.94.52/255.255.255.0, gtw 10.64.94.254
*spamApTask2: Jan 30 09:46:41.022: 00:19:07:c6:39:60 Updating IP 10.64.94.52 ===> 10.64.94.52 for AP 00:19:07:c6:39:60
*spamApTask2: Jan 30 09:46:41.023: 00:19:07:c6:39:60 Setting MTU to 1485
*spamApTask2: Jan 30 09:46:44.028: 00:19:07:c6:39:60 Configuration Status from 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:44.028: 00:19:07:c6:39:60 CAPWAP State: Configure
*spamApTask2: Jan 30 09:46:44.028: 00:19:07:c6:39:60 Updating IP info for AP 00:19:07:c6:39:60 -- static 0, 10.64.94.52/255.255.255.0, gtw 10.64.94.254
*spamApTask2: Jan 30 09:46:44.028: 00:19:07:c6:39:60 Updating IP 10.64.94.52 ===> 10.64.94.52 for AP 00:19:07:c6:39:60
*spamApTask2: Jan 30 09:46:44.029: 00:19:07:c6:39:60 Setting MTU to 1485
*spamApTask2: Jan 30 09:46:47.021: 00:19:07:c6:39:60 Configuration Status from 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:47.021: 00:19:07:c6:39:60 CAPWAP State: Configure
*spamApTask2: Jan 30 09:46:47.021: 00:19:07:c6:39:60 Updating IP info for AP 00:19:07:c6:39:60 -- static 0, 10.64.94.52/255.255.255.0, gtw 10.64.94.254
*spamApTask2: Jan 30 09:46:47.021: 00:19:07:c6:39:60 Updating IP 10.64.94.52 ===> 10.64.94.52 for AP 00:19:07:c6:39:60
*spamApTask2: Jan 30 09:46:47.022: 00:19:07:c6:39:60 Setting MTU to 1485
*spamApTask2: Jan 30 09:46:50.021: 00:19:07:c6:39:60 Configuration Status from 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:50.021: 00:19:07:c6:39:60 CAPWAP State: Configure
*spamApTask2: Jan 30 09:46:50.021: 00:19:07:c6:39:60 Updating IP info for AP 00:19:07:c6:39:60 -- static 0, 10.64.94.52/255.255.255.0, gtw 10.64.94.254
*spamApTask2: Jan 30 09:46:50.021: 00:19:07:c6:39:60 Updating IP 10.64.94.52 ===> 10.64.94.52 for AP 00:19:07:c6:39:60
*spamApTask2: Jan 30 09:46:50.022: 00:19:07:c6:39:60 Setting MTU to 1485
*spamApTask2: Jan 30 09:46:53.021: 00:19:07:c6:39:60 Configuration Status from 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:53.021: 00:19:07:c6:39:60 CAPWAP State: Configure
*spamApTask2: Jan 30 09:46:53.021: 00:19:07:c6:39:60 Updating IP info for AP 00:19:07:c6:39:60 -- static 0, 10.64.94.52/255.255.255.0, gtw 10.64.94.254
*spamApTask2: Jan 30 09:46:53.021: 00:19:07:c6:39:60 Updating IP 10.64.94.52 ===> 10.64.94.52 for AP 00:19:07:c6:39:60
*spamApTask2: Jan 30 09:46:53.022: 00:19:07:c6:39:60 Setting MTU to 1485
*spamApTask2: Jan 30 09:46:56.021: 00:19:07:c6:39:60 Configuration Status from 10.64.94.52:2134
*spamApTask2: Jan 30 09:46:56.021: 00:19:07:c6:39:60 CAPWAP State: Configure
*spamApTask2: Jan 30 09:46:56.021: 00:19:07:c6:39:60 Updating IP info for AP 00:19:07:c6:39:60 -- static 0, 10.64.94.52/255.255.255.0, gtw 10.64.94.254
*spamApTask2: Jan 30 09:46:56.021: 00:19:07:c6:39:60 Updating IP 10.64.94.52 ===> 10.64.94.52 for AP 00:19:07:c6:39:60
*spamApTask2: Jan 30 09:46:56.022: 00:19:07:c6:39:60 Setting MTU to 1485
*spamApTask2: Jan 30 09:46:59.019: 00:19:07:c6:39:60 DTLS keys for Control Plane deleted successfully for AP 10.64.94.52
*spamApTask2: Jan 30 09:46:59.026: 00:19:07:c6:39:60 DTLS connection closed event receivedserver (10:71:142:8/5246) client (10:64:94:52/2134)
*spamApTask2: Jan 30 09:46:59.026: 00:19:07:c6:39:60 Entry exists for AP (10:64:94:52/2134)
*spamApTask2: Jan 30 09:46:59.026: 00:19:07:c6:39:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:19:07:c6:39:60 slot 0
*apfReceiveTask: Jan 30 09:46:59.026: 00:19:07:c6:39:60 Deregister LWAPP event for AP 00:19:07:c6:39:60 slot 0
*spamApTask2: Jan 30 09:46:59.027: 00:19:07:c6:39:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:19:07:c6:39:60 slot 1
*apfReceiveTask: Jan 30 09:46:59.027: 00:19:07:c6:39:60 Deregister LWAPP event for AP 00:19:07:c6:39:60 slot 1
*spamApTask2: Jan 30 09:46:59.028: 00:19:07:c6:39:60 No AP entry exist in temporary database for 10.64.94.52:2134
*spamApTask0: Jan 30 09:46:59.127: 00:19:07:c6:39:60 Received LWAPP DISCOVERY REQUEST to 44:2b:03:b4:39:cf on port '13'
*spamApTask3: Jan 30 09:46:59.128: 00:19:07:c6:39:60 Discovery Request from 10.64.94.52:2135
*spamApTask3: Jan 30 09:46:59.128: 00:19:07:c6:39:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 50, joined Aps =0
*spamApTask3: Jan 30 09:46:59.128: 00:19:07:c6:39:60 Discovery Response sent to 10.64.94.52:2135
*spamApTask3: Jan 30 09:46:59.129: 00:19:07:c6:39:60 Discovery Response sent to 10.64.94.52:2135
*spamApTask0: Jan 30 09:46:59.129: 00:19:07:c6:39:60 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask0: Jan 30 09:47:28.995: 00:19:07:c6:39:60 Received LWAPP DISCOVERY REQUEST to 44:2b:03:b4:39:cf on port '13'
*spamApTask2: Jan 30 09:47:28.996: 00:19:07:c6:39:60 Discovery Request from 10.64.94.52:2134
*spamApTask2: Jan 30 09:47:28.996: 00:19:07:c6:39:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 50, joined Aps =0
*spamApTask2: Jan 30 09:47:28.996: 00:19:07:c6:39:60 Discovery Response sent to 10.64.94.52:2134
*spamApTask2: Jan 30 09:47:28.996: 00:19:07:c6:39:60 Discovery Response sent to 10.64.94.52:2134
*spamApTask0: Jan 30 09:47:28.996: 00:19:07:c6:39:60 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask0: Jan 30 09:47:58.856: 00:19:07:c6:39:60 Received LWAPP DISCOVERY REQUEST to 44:2b:03:b4:39:cf on port '13'
*spamApTask3: Jan 30 09:47:58.857: 00:19:07:c6:39:60 Discovery Request from 10.64.94.52:2135
*spamApTask3: Jan 30 09:47:58.857: 00:19:07:c6:39:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 50, joined Aps =0
*spamApTask3: Jan 30 09:47:58.857: 00:19:07:c6:39:60 Discovery Response sent to 10.64.94.52:2135
*spamApTask3: Jan 30 09:47:58.857: 00:19:07:c6:39:60 Discovery Response sent to 10.64.94.52:2135
*spamApTask0: Jan 30 09:47:58.857: 00:19:07:c6:39:60 Discarding discovery request in LWAPP from AP supporting CAPWAP
*sshpmLscTask: Jan 30 09:48:10.688: sshpmLscTask: LSC Task received a message 4 -
New Cisco 1552AP Mesh with 5508 controller version 7.0.116.0
New to working with Wireless and the Cisco Meshing concept so have a few questions to ask.
I currently have the majority of the mesh setup and configured. I have a setup with two RAPs with 9 MAPS connecting to each RAP.
First question is how many MAPS can connect to a RAP generally?
Secondly how can I block other cisco AP's that are not in my mesh network from trying to connect to my AP's
The below is constantly hammering the logs for 6 devices that are Cisco close to my mesh that are not mine.
8
Sat Nov 12 23:31:53 2011
Mesh child node '58:35:d9:aa:db:4f' has changed its parent to mesh node '88:f0:77:b7:c6:e0' from mesh node '88:f0:77:b7:c6:c0'.
Mesh Node '58:35:d9:aa:db:4f' failed to join controller, MAC address not in MAC filter list.
I have only added the MAC addresses of my AP's in to my AP Policy under security. Would these other AP's affect the mesh in any way?
What I am seeing is the AP's constantly changing the child to parent relationship. I have inherited this network and they have about 20 AP's all within a square mile which is absolutely overkill. Would this close proximity of AP's together be the cause for the constant child parent changes?
How close should I have RAP's together. The network was setup so two raps are about 20 metres apart and the AP's on one side connect to RAP1 and the other to RAP2?
How do you deal with Radar? The install is pretty much next to an airfield with radar running and a few times I have seen all the AP's disconnect and change channels.
These are a few questions to start. As I go through my logs I will continue to ask additional questions. Cheers.Out of order answers here.
Don't use the UNI-II band, this should help with the radar, for the most part. Generally I only recommend 4-6 MAP to a RAP. Othewise you can over saturate the backhaul, and of course the further out you go, the smaller the backhaul.
You could set a bridge-group name (BGN), for the RAP-MAP sectors. This can help you limit the number of MAP to RAP, it also will help keep MAPs that aren't your off your network as they do look at the BGN. However, this is not an end all method. a MAP can still try to join a MESH using 'default' as it's BGN.
If the mac address isn't in your filter, the MAP won't be able to join, and the message it sends to try, is low bandwidth.
HTH,
Steve
Please remember to rate helpful posts or to mark the question as answered so that it can be found later.
Maybe you are looking for
-
Hi experts, I have a Java project that includes a third party tool for formatting and printing a report (JasperReports and iReport). The project was originally done back in Feb.2004 and I needed to update the tools and jars. When I made my applicatio
-
Controlling instances in dynamic forms with a strange twist.
Hello,<br /><br />Is there a way to program a numeric text field that controls the number of instances of a subform? For example, I would like to have a nested subform appear twice in the form if the user enters 2 in the numeric field. But more impor
-
All of a sudden today my battery life just started dropping off on my iphone 4s. I charge it every night. I double clicked the circle button on the bottom to see what was running and there was minimal running but i turned them off anyway. I checked b
-
BDC Session processing in SM35
Hi, Please let me if a session in SM35 has lot of data to process, will it be timed out?? Thanks & Regards, Soumya.
-
Black rectangles in Gallery on Lumia 930
Can't see some pictures on Lumia 930, but the files appear to be there. Also they upload to a MacBook Pro, but appear as black rectangles. What is going on?