Mesh parent
I have few questions for mesh network:
what exactly is a parent, child and neigbor in mesh network
1.can a mesh access point act as parent or child to another mesh neighbor ?
2. an electronic temperature gauge connects to root access point eventhough another mesh access point
is near to it.Any reason why is it so and if we can forcibly make it connect to the nearer one
3. should the gain be set manually on each access point or should it be left to default as it is seen in controller
4. should the gain if set manually be set on both 802.11a & g
5. What is the ideal snr for optimal connectivity.
thanks in advance
1-
Parent: the root AP that other APs connect to as a child.
Child: the AP that reaches controller through another AP (through the parent AP).
Neighbor: an AP that the mesh AP can hear but it is not connected to it. So it can be heared but it is neighbor parent nor a child.
This link must be read so you understand this: http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob41dg/ch8_MESH.html#wp1016044
2- Root AP may have better signal. being closer does not necessarily mean you have better signal. The further AP may have higher power level than the closer one. Test power levels. also, try to make the guage disconnect and connect again and test.
3- Gain is put in order to maintain power levels set by authority. leaving it blank may make the ap exceed the power threshold specified by the authorities. You need to specify the accurate gain under the antenna (for external antennas only).
4- You need to set the gain under both b/g and a radios. each radio may have different transmit power and different antenna gains.
5- There is no ideal value for SNR. It all depends on your requirements and your site. I would say 20+ SNR value is OK. But it may vary slightly depending on your area that you want to cover and clients that connect.
HTH
Amjad
Similar Messages
-
AP mesh info in WCS not show bridge links.
Hi guys,
I would like to know if any of you following problem has occurred. I have implemented 3 wireless mesh with 1262 AP WLC 5508 v 7.0.116.0 and WCS 7.0.172.0 base lic, all has been running perfect, the problem arises when I want to see on the map graphically bridge links, I have enabled AP Messh info but it not shows the bridge links, in hierarchical Mesh Parent-Child View only shows the RAP. To load the maps we used Campus> Outdoor area> AP.
I will appreciate any comments.
Greetings.Are you loading 4.0? With WCS 4.x you need to generate a license with the PAK you should have received from Cisco. If you did not receive a PAK, read the following excerpt from the following url:
Existing Cisco WCS customers that have not received their PAK certificate from Cisco should contact their Cisco sales representative or send an e-mail to the [email protected] alias to notify Cisco that they need their PAK certificate. Cisco will attempt to respond to requests to this alias within 48 hours Monday-Friday 9AM-5PM Pacific Standard Time.
http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
I hope this helps.
-Eric -
Hi,
I am trying to avoid having to un-visible a node's children one by one. The code:
nod1 = c3d.scene.nodes.getByName( "lev-2" );
nod1.visible=false;
turns off the node lev-2 but not it's numerous children.
*- Is there any code that would turn off a node's children even if it contains no mesh of its own?
Thanks in AdvanceThanks. I can't make the parent.parent to work. I can cascade the loops and that works but it takes unacceptably long time to go throgh the loops. The code that I have that fails is:
for (var i = 0; i < c3d.scene.meshes.count; ++i)
mesh = c3d.scene.meshes.getByIndex(i);
if (mesh.parent.name.indexOf("cov-4") > -1)
mesh.visible = false;
if (mesh.parent.parent.name.indexOf("cov-4") > -1)
mesh.visible = false; -
Wireless Mesh topology parent child optimization. How do you force a reconfig?
Release 6 controller
9 Mesh APs. 1524 (2x 5G radios, 1x 2.4G) and 1522 (1x 5G radios, 1x 2.4G)
Designed for 3 linear hops and then a split to the rest.
AP1 = Root AP
linear to
AP2
Linear to
AP3
Linear to
AP4
equidistant to
AP5 and AP6
The rest are further away from AP4, but have visibility back to AP 4
The issue is after an event (say a power outage) at AP4.
AP5 uses AP3 as it's parent.
That's okay during the power failure, but when AP4 comes back up, I want to force AP5 to switch it's parent to AP4.
You may ask why, if AP5 can reach AP3 okay, it's okay to leave it that way.
Well, doing link tests...
test --------packet loss %-----
speed AP3toAP5 AP3toAP4 AP5-AP4
===== ======= ======= =======
54M 100 0 0
48M 100 0 0
36M 52.6 0 0
24M 1.44 0 0
18M 0.89 0 0
So you can see it's desireable now that AP5 uses AP4 as it's parent.
Over time, the system might figure it out, but our limited experience shows it seems to stick to the way it is.
To complicate matters, sometimes we've found that it doesn't seem to reconfigure when the channel number has changed so AP5 can reach AP3, but AP4 (1524) comes up with a different channel on it's downlink radio.
So, how can we force a mesh topology reevaluation/change for either 1 AP or the whole bridge group?
I thought changing the bridge speed from "auto" to 54M (on AP3 above, for example) might force the attached children to rethink it, but it didn't seem to work (maybe I needed to wait an hour?).
I also thought tweaks to "Radio Performance Profile" for radio might help. (not sure what to change, or how long to wait for a result)
suggestions on how to quickly reconverge?
reseting APs and hoping they come back in a better topology is painful and slow.
Thanks - GlenGlen, I know this is a very old topic but we are suffering from similar conditions on our end. Even using directional antennas we are having a difficult time having the Mesh network consistently optimize itself. Did you guys ever find a tweak that worked for you to have the system re-evaluate the connection by packet loss on speed?
Thanks! -
Forcing Mesh AP to join a particular parent
Hi there;
I have a setup of 10 1522 APs (4 RAPs and 6 MAPs). Two of them (One RAP and one MAP) are placed bit away from the remaining ones. The two remote APs function correctly as desired (the remote MAP selects nearest RAP as parent) but when the RAP looses its ethernet connection due to wired network failure; the MAP joins a remote RAP with very low SNR and stays at it even when the desired RAP comes up again.
Is there any way we can set a priority that the MAP joins intended RAP as soon as it comes alive again?
Thanks,The 1520's don't currently support background scanning. The result of this is the condition you described. Bug CSCsw28993 was filed to have background scanning added to the 1520's.
-
AP1522 changing parent node very frequent & 2 RAPs are creating a loop
Hi,
i have 2 issues..
i have 7 units of AP1522 installed, 2 units as RAP and 5 units as MAP. The system is up and running. i have the following problem.
1) The MESH AP changing the parents every now and than.
2) My 2 RAPs connection has been deteced as a loop at my CE500 Switch and on port will be blocked.
following msg from cotroller "(Cisco Controller) >Thu Dec 18 12:41:06 2008: spamMeshExcessiveParentChangeAlarm :: Mesh AP 00:23:05:2D:AC:00 changed a parent 3 times within 60 minutes.
Thu Dec 18 12:41:37 2008: spamMeshExcessiveParentChangeAlarm :: Mesh AP 00:23:05:2C:EB:00 changed a parent 3 times within 60 minutes."
has anyone came across this situation on 2 RAPs before.Hi Dennis, thanks for your brief info, i have tried all those thing and the spanning tree loop problem is now solve in the latest release XX.35M.
Now when i have 2 RAP connected to CE500, all AP and controller working fine but when i unplug 1 unit of the RAP from the CE500 switch i fond that both RAP link is down. in some tries 1 RAP come up again after about 15 to 20 min and some times my mesh link is fully out from the controller. Can i assume that when i unplug 1 RAP the other RAP works as the primary and make connections available.
Am i correct to say that when i have 2 RAP in the mesh network, both work at the same time 1 fails also another one works find.
Please advice me if anyone came across this situation. -
[JavaScript] access to vertices of a mesh node
Hi forum,<br /><br />is there a way to get access to the vertices of a mesh node, in particular to their x, y and z coordinates (with respect to the local coordinate system of the parent mesh node)?<br /><br />I mean something like:<br /><br /><font face=Courier><br />var meshes = scene.meshes;<br><br />for(i=0; i<meshes.count; i++){<br><br /> var mesh = meshes.getByIndex(i);<br><br /> for j=0; j<mesh.vertices.count; j++) {<br><br /> var vertex = mesh.vertices.getByIndex(j);<br><br /> x = vertex.x;<br><br /> ...<br><br /> }<br />}<br /></font><br /><br />Thanks,<br /><br />Alexander.
Alexander,
Sorry for the big delay. You're probably on to new things now...
The answer is that there is not yet access to vertices. You can of course get the 4x4Matrix of a mesh and transform the mesh in that manner, but specific control or deformation of vertices is not present. -
Wireless Mesh losing connectivity
My client has a Cisco 2504 controller running 7.5.102.0 code. They have 2602E APs as Mesh Root AP and Mesh APs. The distance between the antennas is approximately 30 feet. The client is complaining of constant drops. To date I have configured preferred partent on both mesh APs, and dropped min tx rates to lower multi-path issues in this manufacturing environment.
This is from the output from today's event log:
Mesh Root AP: US052TXPEA-ASL22 64:e9:50:6a:fd:70
Mesh AP: US052TXPEA-ASL33 64:e9:50:d0:f1:30
Mesh AP: US052TXPEA-ASL34 64:e9:50:67:ae:90
1 Mon May 5 12:52:31 2014 MFP Anomaly Detected - 1 Not encrypted event(s) found as violated by the radio 64:e9:50:67:ae:9f and detected by the dot11 interface at slot 1 of AP 64:e9:50:67:ae:90 in 300 seconds when observing . Client's last source mac 04:db:56:1e:43:55
185 Mon May 5 12:13:26 2014 AP US052TXPEA-ASL34[0] (64:e9:50:67:ae:90) Device ID: 0x5012, Type: Jammer[19], Severity: 64, Channels: 6, Cluster ID: 30:bf:e0:01:1a:ef, Previous Cluster ID: 30:bf:e0:01:1a:ef, Event: Clear
189 Mon May 5 12:12:30 2014 AP US052TXPEA-ASL34[0] (64:e9:50:67:ae:90) Device ID: 0x5012, Type: Jammer[19], Severity: 64, Channels: 6, Cluster ID: 30:bf:e0:01:1a:ef, Previous Cluster ID: 30:bf:e0:01:1a:ef, Event: Set
635 Mon May 5 10:57:28 2014 MFP Anomaly Detected - 1 Not encrypted event(s) found as violated by the radio 64:e9:50:67:ae:9f and detected by the dot11 interface at slot 1 of AP 64:e9:50:67:ae:90 in 300 seconds when observing . Client's last source mac 04:db:56:1e:43:55
1339 Mon May 5 08:57:03 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio interface reset. Status:NA
1340 Mon May 5 08:57:03 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio interface reset. Status:NA
1341 Mon May 5 08:57:03 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio reset due to configuration change. Status:NA
1342 Mon May 5 08:57:03 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio reset due to configuration change. Status:NA
1345 Mon May 5 08:57:00 2014 AP 'US052TXPEA-ASL34', MAC: 64:e9:50:67:ae:90 disassociated previously due to Link Failure. Uptime: 0 days, 23 h 59 m 03 s . Reason: Capwap WTP Event request.
1346 Mon May 5 08:56:59 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Unknown Reset Status:NA
1347 Mon May 5 08:56:59 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Unknown Reset Status:NA
1348 Mon May 5 08:56:58 2014 AP 'US052TXPEA-ASL33', MAC: 64:e9:50:d0:f1:30 disassociated previously due to Link Failure. Uptime: 0 days, 23 h 58 m 55 s . Reason: Capwap WTP Event request.
1400 Mon May 5 08:57:06 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio interface reset. Status:NA
1401 Mon May 5 08:57:06 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio interface reset. Status:NA
1402 Mon May 5 08:57:06 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio reset due to configuration change. Status:NA
1403 Mon May 5 08:57:06 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio reset due to configuration change. Status:NA
1408 Mon May 5 08:57:02 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Unknown Reset Status:NA
1409 Mon May 5 08:57:02 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Unknown Reset Status:NA
1410 Mon May 5 08:57:00 2014 AP 'US052TXPEA-ASL34', MAC: 64:e9:50:67:ae:90 disassociated previously due to Link Failure. Uptime: 0 days, 23 h 59 m 03 s . Reason: Capwap WTP Event request.
1415 Mon May 5 08:56:33 2014 Mesh child node '64:e9:50:d0:f1:3f' has changed its parent to mesh node '64:e9:50:6a:fd:70' from mesh node '64:e9:50:6a:fd:70'.
1672 Mon May 5 08:27:22 2014 Mesh child node '64:e9:50:d0:f1:3f' is no longer associated with mesh node '64:e9:50:6a:fd:70'.
1674 Mon May 5 08:26:46 2014 AP Disassociated. Base Radio MAC:64:e9:50:67:ae:90
1675 Mon May 5 08:26:46 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Heartbeat Timeout Status:NA
1676 Mon May 5 08:26:46 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Heartbeat Timeout Status:NA
1750 Mon May 5 08:09:19 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio interface reset. Status:NA
1751 Mon May 5 08:09:19 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio interface reset. Status:NA
1752 Mon May 5 08:09:19 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio reset due to configuration change. Status:NA
1753 Mon May 5 08:09:19 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio reset due to configuration change. Status:NA
1754 Mon May 5 08:09:16 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Unknown Reset Status:NA
1755 Mon May 5 08:09:16 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Unknown Reset Status:NA
1756 Mon May 5 08:09:16 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Unknown Reset Status:NA
1757 Mon May 5 08:09:16 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Unknown Reset Status:NA
1758 Mon May 5 08:09:14 2014 AP 'US052TXPEA-ASL34', MAC: 64:e9:50:67:ae:90 disassociated previously due to Link Failure. Uptime: 0 days, 23 h 11 m 19 s . Reason: Capwap WTP Event request.
1759 Mon May 5 08:09:13 2014 AP 'US052TXPEA-ASL33', MAC: 64:e9:50:d0:f1:30 disassociated previously due to Link Failure. Uptime: 0 days, 23 h 11 m 13 s . Reason: Capwap WTP Event request.
1811 Mon May 5 08:09:19 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio interface reset. Status:NA
1812 Mon May 5 08:09:19 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio interface reset. Status:NA
1813 Mon May 5 08:09:19 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio reset due to configuration change. Status:NA
1814 Mon May 5 08:09:19 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Radio reset due to configuration change. Status:NA
1819 Mon May 5 08:09:16 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Unknown Reset Status:NA
1820 Mon May 5 08:09:16 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:67:ae:90 Cause=Unknown Reset Status:NA
1823 Mon May 5 08:09:14 2014 AP 'US052TXPEA-ASL34', MAC: 64:e9:50:67:ae:90 disassociated previously due to Link Failure. Uptime: 0 days, 23 h 11 m 19 s . Reason: Capwap WTP Event request.
1826 Mon May 5 08:08:43 2014 Mesh child node '64:e9:50:d0:f1:3f' has changed its parent to mesh node '64:e9:50:6a:fd:70' from mesh node '64:e9:50:6a:fd:7f'.
1929 Mon May 5 07:38:58 2014 AP Disassociated. Base Radio MAC:64:e9:50:d0:f1:30
1930 Mon May 5 07:38:58 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Heartbeat Timeout Status:NA
1931 Mon May 5 07:38:58 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Heartbeat Timeout Status:NA
2000 Mon May 5 07:38:54 2014 AP Disassociated. Base Radio MAC:64:e9:50:67:ae:90
2001 Mon May 5 07:38:54 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Heartbeat Timeout Status:NA
2002 Mon May 5 07:38:54 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:67:ae:90 Cause=Heartbeat Timeout
2008 Mon May 5 07:30:33 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio interface reset. Status:NA
2009 Mon May 5 07:30:33 2014 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio interface reset. Status:NA
2010 Mon May 5 07:30:33 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio reset due to configuration change. Status:NA
2011 Mon May 5 07:30:33 2014 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Radio reset due to configuration change. Status:NA
2012 Mon May 5 07:30:30 2014 AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Unknown Reset Status:NA
2013 Mon May 5 07:30:30 2014 AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:64:e9:50:d0:f1:30 Cause=Unknown Reset Status:NA
2014 Mon May 5 07:30:27 2014 AP 'US052TXPEA-ASL33', MAC: 64:e9:50:d0:f1:30 disassociated previously due to Link Failure. Uptime: 0 days, 22 h 32 m 28 s . Reason: Capwap WTP Event request.Hi,
After performing the site survey, select low noise channel on the access-points, yes it seem due to the interference clients are dropping their connection. -
Mesh with WLC (7.0.220)
Dear Tech Gurus,
Can any one help me regarding channel assignament at root and mesh access points.
will the channel be same on all RAPS and MAPS (5Ghz).
With Regards,
Chaitanya.GYour RAP's should be on different channels. So it will depend on how far apart your RAP's will be apart from each other to get the channel separation you need. Your MAP's will be assigned the same channel as the parent RAP. Makes sense?
Thanks,
Scott Fella
Sent from my iPhone -
hy engineers
My question is this desire to deploy a wireless network through mesh, but the locationof the access point for this purpose is behind the walls, I want to know if a design formy mesh access point must be linear or serial, or must see each other, or there may be some interference, such as walls, ceilings or something else.
1. Must have line of sight between the access point for mesh or there may be interferencefrom walls or other materials?
2. The 1310 access point or work against a parent should be autonomous?
3. What percentage of overlap should be in the access point should make a mesh topology?
4. There are access points that handle ny protocol can be implemented for mesh?
thanks for your help.Daniel,
Take a loog at the document linked below:
http://www.cisco.com/en/US/customer/docs/wireless/technology/mesh/7.0/design/guide/MeshAP_70.html -
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. -
Prime Infrastructure with Mesh Networks
My customer has a Mesh network at a sea port. They have about 15 mesh access points at each location with two controllers each. Would Prime Infrastructure work with a mesh deployment? There is a lot of interference and sometimes the performance of the network is affected. I want to use the WCS portion of Prime, to manage the mesh coverage, parent/child relationship between the RAP's and MAP's.
Please let me know if Prime is something I can suggest to my customer to ease the management of the mesh network.
Thanks,
ScottHi Scott
Prime is the replacement for wcs. Wcs isn't supported past code 7.0.
Sent from Cisco Technical Support iPad App -
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 -
Hi,
I m using one 1522 AP as a RAP and one 1522 AP as a MAP.Also there are four 1242 RAP Aps.1522 AP could find its 1522 RAP earlier before connecting 1242 RAPs in network but after connecting 1242 RAP APs the mesh 1522 AP disappars after few menutes of joining to RAP 1522.
plase help.
output of 'debug mesh security events enable' is show below
(Cisco Controller) >debug mesh security events enable
(Cisco Controller) >Fri May 29 12:31:17 2009: 00:22:BE:43:4E:00 MESH_ASSOC_REQU
EST_PAYLOAD in Association Request for AP 00:22:BE:42:0B:00
Fri May 29 12:31:17 2009: 00:22:BE:43:4E:00 Mesh assoc request for known AP 00:
22:be:42:0b:00
Fri May 29 12:31:17 2009: 00:22:BE:43:4E:00 Mesh assoc request :child : 00:22:b
e:42:0b:00 NextHop : 00:22:be:43:4e:00 LradIp 10.7.51.74 vlanid: 0 mwarPort:
12223 lradPort: 13536
Fri May 29 12:31:17 2009: Sending PMK Delete request to other MDID members for A
P(mscb)00:22:be:42:0b:00
Fri May 29 12:31:17 2009: MAC Validation of Mesh Assoc Request for00:22:be:42:0b
:00 is 0, Mode is : 0
Fri May 29 12:31:17 2009: Starting dot1x authentication for : 00:22:be:42:0b:00
Fri May 29 12:31:18 2009: Got the following AAA key message for : 00:22:be:42:0b
:00
Fri May 29 12:31:18 2009: Control Msg Hex Dump:
93 BC A8 97 57 2C 6B 82
0B EC 4F A
9 61 62 70 A2
F7 0F 5B 4F A3 68 4D 11
46 C9 12 F0 49 6F E1 6F
Fri May 29 12:31:18 2009: Parent Nonce for : 00:22:be:42:0b:00
Fri May 29 12:31:18 2009: Key Hex Dump:
E2 D1 11 C6 79 FE 35 DD
F6 A6 0D 19 94 F7
C0 79
50 C3 80 AC B0 88 C7 62
2B 76 87 DF E0 F6 DF AA
Fri May 29 12:31:18 2009: PMK-R0 Key for : 00:22:be:42:0b:00
Fri May 29 12:31:18 2009: NASID WLC1-T MGID: 00:00:00:00:00:00:00:00
Fri May 29 12:31:18 2009: Key Hex Dump:
03 95 21 5D 5A C0 26 7B
E6 02 DD 0D 09 F2
06 95
EB 9D CE 57 B0 76 92 51
1C 68 D6 E2 52 29 A3 44
Fri May 29 12:31:18 2009: PMK-R0 Name for : 00:22:be:42:0b:00
Fri May 29 12:31:18 2009: Key Hex Dump:
B7 56 31 49 88 AC C2 5C
E7 85 98 56 E4 A6
A4 24
Fri May 29 12:31:18 2009: PMK-R1 Key for : 00:22:be:42:0b:00
Fri May 29 12:31:18 2009: Key Hex Dump:
18 34 4B A1 52 86 58 FA
5E 59 75 F7 BA 0B
37 34
96 C3 FE 6E 13 24 11 88
1C 56 B3 19 B3 34 AD 47
Fri May 29 12:31:18 2009: Sending the following key for : 00:22:be:42:0b:00
Fri May 29 12:31:18 2009: Control Msg Hex Dump:
18 34 4B A1 52 86 58 FA
5E 59 75 F
7 BA 0B 37 34
96 C3 FE 6E 13 24 11 88
1C 56 B3 19 B3 34 AD 47
Fri May 29 12:31:18 2009: Processing of Mesh key response success from AP00:22:b
e:43:4e:00
and i can't see any output from 'debug lwapp events enable' for 30 min.4.WLC configuration:
(Cisco Controller) >show running-config
802.11a cac voice tspec-inactivity-timeout ignore
802.11a cac voice stream-size 84000 max-streams 2
802.11a channel global off
802.11a rate supported 12
802.11a rate supported 24
802.11b cac voice tspec-inactivity-timeout ignore
802.11b cac voice stream-size 84000 max-streams 2
802.11b channel global off
advanced 802.11a channel add 165
advanced 802.11a profile coverage global 15
advanced 802.11a profile foreign global 60
advanced 802.11a profile level global 12
advanced 802.11b profile foreign global 60
advanced 802.11b profile clients global 15
advanced 802.11b profile level global 12
advanced 802.11b profile coverage global 15
advanced location expiry tags 1200
advanced location expiry client 150
advanced location expiry calibrating-client 30
advanced location expiry rogue-aps 1200
Cisco Public Safety is not allowed to set in this domain
auth-list ap-policy ssc enable
auth-list add mic 00:22:be:41:e3:00
auth-list add mic 00:22:be:42:0b:00
auth-list add mic 00:22:be:43:4e:00
auth-list add mic 00:23:5e:03:b2:14
auth-list add mic 00:23:5e:03:b2:c6
country IN
dhcp create-scope DHCP Scope
dhcp create-scope Electronic Shop
dhcp address-pool DHCP Scope 10.7.51.12 10.7.51.254
dhcp address-pool Electronic Shop 10.7.24.240 10.7.24.250
dhcp default-router DHCP Scope 10.7.51.1
dhcp default-router Electronic Shop 10.7.24.1
dhcp enable DHCP Scope
dhcp enable Electronic Shop
dhcp dns-servers DHCP Scope 10.7.24.2 172.16.7.86
dhcp dns-servers Electronic Shop 10.7.24.2 172.16.7.86
dhcp domain DHCP Scope lthed.com
dhcp domain Electronic Shop lthed.com
dhcp network DHCP Scope 10.7.51.0 255.255.255.0
dhcp network Electronic Shop 10.7.24.0 255.255.255.0
interface address ap-manager 10.7.51.11 255.255.255.0 10.7.51.1
interface address management 10.7.51.10 255.255.255.0 10.7.51.1
interface address service-port 192.168.1.1 255.255.255.0
interface address virtual 1.1.1.1
interface dhcp ap-manager primary 10.7.51.10
interface dhcp management primary 10.7.51.10
interface dhcp service-port disable
interface port ap-manager 1
interface port management 1
known ap add 00:30:5b:02:3b:9f
load-balancing window 5
wlan apgroup add EleShop Electronic Shop
logging buffered 2
macfilter add 00:0e:35:90:ee:85 0 management U1
macfilter add 00:17:23:06:54:54 0 management U2
macfilter add 00:17:23:06:59:4d 0 management U3
mesh client-access enable
mesh security rad-mac-filter disable
mesh security eap
mgmtuser add admin **** read-write
mobility group domain Mobility
mobility group member add 00:23:33:b2:c3:c0 172.16.5.1 Mobility
msglog level critical
network telnet enable
network broadcast enable
network mgmt-via-wireless enable
network fast-ssid-change enable
network rf-network-name none
radius auth add 1 172.16.7.12 1812 ascii ****
radius auth rfc3576 enable 1
radius auth retransmit-timeout 1 5
snmp version v2c enable
snmp version v3 enable
snmp trapreceiver create WCS 10.7.24.39
snmp trapreceiver mode enable WCS
syslog 172.16.7.12
sysname WLC1-T
trapflags 802.11-Security wepDecryptError disable
trapflags rrm-profile load disable
trapflags rrm-params tx-power disable
trapflags rogueap disable
wlan create 1 LTAIT LTAIT
wlan mac-filtering enable 1
wlan session-timeout 1 1800
wlan session-timeout 2 disable
wlan wmm allow 1
wlan wmm allow 2
wlan radius_server auth add 1 1
wlan radius_server acct disable 2
wlan security static-wep-key encryption 1 104 1
wlan security wpa disable 2
wlan security wpa wpa1 enable 1
wlan security wpa wpa1 ciphers tkip enable 1
wlan security wpa wpa2 disable 1
wlan dhcp_server 1 0.0.0.0 required required
wlan dhcp_server 2 0.0.0.0 required required
wlan enable 1
wlan enable 2 -
Hi all,
I'm running a 2106 with version 6.0.196.0. I'm running a couple indoor 1131s on it for regular client access successfully, but my problem is with trying to Ethernet Bridge Wireless Mesh two 1522s. I have placed the 1522 MAC addresses in the MAC Filter. I have Ethernet Bridging radio set on both the RAP and the MAP. I have the RAP and MAP connecting(They see each other as AWAPP neighbors, I can ping the MAP from the wired LAN, and it registers to the WLC, but I can't seem to bridge through these APs. I tried setting the Switchport attached to the RAP as an access port were the WLC and other APs sit as well as tried trunking it, making that same WLC vlan the native vlan. I also tried creating a separate AP group for the 1522s...no joy. Can anyone point me in the right direction on this?/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Indoor WLAN and outdoor mesh is not supported on the same WLC at the same time.
So you cannot mix 1131s and 1522s on the same controller.
Regards,
André
Maybe you are looking for
-
How do I Move video files from films to tv programmes and group the series together?
I've recently ripped a tv series from DVD and successfully converted to play on iPad and iPhone. However it's listed all the videos under the "films" tab as individual files. How do I move them into the TV programme tab and group them together? Thank
-
What version(s) of Acrobat are compatible w Windows8.1 ?
I'm wanting to purchase a version of Acrobat for my new computer. What is the oldest version that works with Windows 8.1 ( I recently bought Acrobat 7.0 and then found out it doesn't work on Windows 8.1)
-
How do I delete a game app I tap it it jiggles but no x appears I can't delete it
How do I delete a game app I touch it it jiggles but no x appears I can't delete it
-
In return sales order(va01) return amt value is not showing plz help
DEAR, Issue : When Sales Order, Delivary, Transfer Order, Billing is created by one user , and if the same user creates Sales Return Order(VA01) it is working fine. But if any other user creates this Sales Return then it is not showing Sales Return A
-
Organizer no longer available?
Just tonight I had (another) unpleasent surprise using Premiere Elements: I can no longer access the organizer. Only the limited organizer within Premiere is available, but I can no longer switch to the full organizer within Photoshop. The organizer