APs not joining 5508 on dynamic ports created manualy
Hey all,
i have a problem with our new 5508 wireless controller (7.0.116.0).
Port 1 is the system default "management" (Port 2 is backup). Dynamic AP Management is disabled.
Port 3 is a new dynamic interface "ap-manager 2" with Dynamic AP Management enabled and has a ip in a seperated VLAN which is not routed.
When i am connecting the AP (1260 series) to the "ap-manager 2" interface, then it will not join and i get an error message on the WLC:
*spamApTask1: Mar 05 14:52:12.783: %CAPWAP-3-DISC_INTF_ERR1:
capwap_ac_sm.c:1453 Ignoring discovery request received on non-management
interface (3) from AP
When i am connecting the AP to the "management2 interface, then it is working fine. But i don't want the APs in the Management LAN. I want them in the separated no routed LAN explicit for the APs.
What do i miss here.
Thanks a lot.
Regards
Matthew
Hmmm...but i found follwoing in the documentation:
The AP-manager interface's IP address must be different from the management interface's IP address and may or may not be on the same subnet as the management interface. However, we recommend that both interfaces be on the same subnet for optimum access point association.
I want the APs in a separated non routed LAN because of security reasons. Why set APs into the management LAN when they only need to communicate with the controller?
But if there is no way to do that, then i need to redesign the plans for the WLAN structure.
Thanks
Matthew
Similar Messages
-
APs not joining controller errors
I keep getting errors on different APs not joining controllers:
Jan 5 15:54:40.097: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jan 5 15:54:40.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.x.x.x peer_port: 5246
*Jan 5 15:54:40.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jan 5 15:54:41.778: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.x.x.x peer_port: 5246
*Jan 5 15:54:41.780: %CAPWAP-5-SENDJOIN: sending Join Request to 10.x.x.x
*Jan 5 15:54:41.780: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Jan 5 15:54:41.787: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.x.x.x
*Jan 5 15:54:41.788: %DTLS-5-PEER_DISCONNECT: Peer 10.x.x.x has closed connection.
*Jan 5 15:54:41.788: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.x.x.x :5246.
Any ideas? I'm not sure why the peer is disconnecting the connection. The controller that is linked to It happens on 1242 and 1231 APs mostly. I've had it happen on a 1142 and 1252 once, but after a reboot it joined fine.
I'm running 6.0.188.0 on 6 WISMs. The ap-manager that these APs keep trying to join only has 5 APs on it.Can you get a sniffer trace of the port-channel to one of the WiSM, and if possible, the console of the AP? Also, check the MAC address of the AP(s) that are not joining to see if they start with something other than 00:, you may also want to check the MAC of the gw for those AP for the same thing.
The defect I'm thinking of is CSCte01087 -
Hi guys,
I am in the process of configuring a WLC and got stuck due to APs are not joining the WLC.
I have configure DHCP server on the Gateway router and the WLC management interface is pointing to the Gateway as DHCP Server.
I have multiple Dynamic interfaces configured on the WLC and Interface group has been configured and mapped to Management Interface.
For each WLAN, a separate DHCP pool has been created on the router.
LAG has been configured and working fine. Connectivity works fine in the network and I can ping all devices and vlans from WLC.
Now, the APs are not joining the WLC. The error I am getting
" 44:03:a7:f1:b4:40 Received a Discovery Request from 44:03:A7:F1:B4:40 via IP broadcast address but the source IP address (10.xx.xx.xx) is not in any of the configured subnets. Dropping it "
Some one help me troubleshooting this issue with DHCP IP Assignment.
Thanks,
CJIf you are using Broadcast method to discover WLC to AP then you need to ensure following is correctly configured.
1. Unders the switch SVI defined for AP-management (10.38.11.x) you have to configure "ip helper-address "
2. In switch global config "ip forward-protocol udp 5246"
Refer this for more detail
http://mrncciew.com/2013/05/04/wlc-discovery-via-broadcast/
There are other methods available as well (static, DNS, DHCP option 43) for the WLC discovery purpose. To verify there is no configuration issues at WLC end, you can simply configure the WLC details on AP statically & check wether AP get register to WLC. To do this you can enter following CLI commands on AP console priviledge mode.
debug capwap console cli
capwap ap ip address 10.38.11.x 255.255.255.x
capwap ap ip default-gateway 10.38.11.y
capwap ap controller ip address
In this way your AP should get registered to WLC (if no config issue at WLC end). Refer this for more detail
http://mrncciew.com/2013/03/17/ap-registration/
If you have so many APs, then as Steve pointed configuring DHCP-Option 43 would be a good option
Regards
Rasika
**** Pls rate all useful responses **** -
Hello community,
I hope you can help me with my problem.
I have a vWLC Firmware version: 7.4.121.0, I have also Aironet 1700Aps
I have successfully configured wlc with service and management interface. In the management network I can ping the vWLC managenemt interface as well the APs in this network. The firewall is also the DHCP Server for the management network. (It is working because APs get an IP address) The problem is the APs are not joining the vWLC. This is my first time I use WLC and APs. So they are completely new and not used before.
Here is the debug output of vWLC:
ApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 Finding DTLS connection to delete for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 Disconnecting DTLS Capwap-Ctrl session 0x8faa580 for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.997: 84:80:2d:bd:fa:10 CAPWAP State: Dtls tear down
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 DTLS connection closed event receivedserver (192:168:200:3/5246) client (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 Entry exists for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:07.998: 84:80:2d:bd:fa:10 No AP entry exist in temporary database for 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.004: 84:80:2d:bd:fa:1e DTLS connection not found, creating new connection for 192:168:200:10 (57250) 192:168:200:3 (5246)
*spamApTask4: Feb 11 16:31:08.472: 84:80:2d:bd:fa:1e DTLS Session established server (192.168.200.3:5246), client (192.168.200.10:57250)
*spamApTask4: Feb 11 16:31:08.472: 84:80:2d:bd:fa:1e Starting wait join timer for AP: 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Join Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:1e Deleting AP entry 192.168.200.10:57250 from temporary database.
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Finding DTLS connection to delete for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 Disconnecting DTLS Capwap-Ctrl session 0x8faa720 for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.477: 84:80:2d:bd:fa:10 CAPWAP State: Dtls tear down
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 DTLS connection closed event receivedserver (192:168:200:3/5246) client (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 Entry exists for AP (192:168:200:10/57250)
*spamApTask4: Feb 11 16:31:08.479: 84:80:2d:bd:fa:10 No AP entry exist in temporary database for 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.515: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 11 16:31:08.516: 84:80:2d:bd:fa:10 Discovery Response sent to 192.168.200.10:57250
*spamApTask0: Feb 11 16:31:08.516: 84:80:2d:bd:fa:1e Received LWAPP DISCOVERY REQUEST to 40:4a:03:79:d7:20 on port '1'
*spamApTask0: Feb 11 16:31:08.516: 84:80:2d:bd:fa:1e Discarding discovery request in LWAPP from AP supporting CAPWAP
Sadly I don`t have a debuging cable for the APs. Therefore I have no debuging output of the APs. (It is ordered ;-) )
But I hope the output of the APs is right now not important to solve this problem.
Thank you
//EDIT
On the firewall are no ports blockedOkay I upgraded the vWLC to 8.0.110.0.
I looked in the event log of the vWLC. It was successfully discovered and also the new image version was send to the AP.
Sadly the Ap does not join to the vWLC.
*apfReceiveTask: Feb 12 09:53:35.640: WARP IEs: (12)
*apfReceiveTask: Feb 12 09:53:35.640: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01
*apfReceiveTask: Feb 12 09:53:35.640: Wlan Feature status 0 for AP:84:80:2d:45:75:e0 (slotID 1)
*apfReceiveTask: Feb 12 09:53:35.640: Split tunnel status (Disabled) encoded in the vap payload for WLAN(1), AP:84:80:2d:45:75:e0 (slotID 1)
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Configuration Status from 192.168.200.10:57251
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 CAPWAP State: Configure
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Updating IP info for AP 84:80:2d:45:75:e0 -- static 0, 192.168.200.10/255.255.255.0, gtw 192.168.200.3
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Updating IP 192.168.200.10 ===> 192.168.200.10 for AP 84:80:2d:45:75:e0
*spamApTask5: Feb 12 09:53:35.789: 84:80:2d:45:75:e0 Invalid length (9) countedlen 6 sizeUserPayload 277 for vendor-specific element 0x00409600-unknown (185) from AP 84:80:2D:45:75:E0
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Setting MTU to 1485
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Finding DTLS connection to delete for AP (192:168:200:10/57251)
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 Disconnecting DTLS Capwap-Ctrl session 0xb947000 for AP (192:168:200:10/57251)
*spamApTask5: Feb 12 09:53:35.790: 84:80:2d:45:75:e0 CAPWAP State: Dtls tear down
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 DTLS connection closed event receivedserver (192.168.200.3/5246) client (192.168.200.10/57251)
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 Entry exists for AP (192.168.200.10/57251)
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 0
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 1
*spamApTask5: Feb 12 09:53:35.791: update ap status:84:80:2d:45:75:e0 ,index:60
*spamApTask5: Feb 12 09:53:35.791: 84:80:2d:45:75:e0 No AP entry exist in temporary database for 192.168.200.10:57251
*apfReceiveTask: Feb 12 09:53:35.792: 84:80:2d:45:75:e0 Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 0
*apfReceiveTask: Feb 12 09:53:35.792: 84:80:2d:45:75:e0 Deregister LWAPP event for AP 84:80:2d:45:75:e0 slot 1
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 12 09:53:35.918: apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.918: apType = 45 apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10 port 57250
*spamApTask4: Feb 12 09:53:35.918: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Request from 192.168.200.10:57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 12 09:53:35.919: apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.919: apType = 45 apModel: AIR-CAP702I-C-K9
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10 port 57250
*spamApTask4: Feb 12 09:53:35.919: 84:80:2d:45:75:e0 Discovery Response sent to 192.168.200.10:57250
Sadly I don`t understand what this debugging log says :-(
Maybe you can help me again
Thank you
//SOLUTION -----------------------------------------------------------------------------------------------------------------------------------------------------------
I found something on the internet, but for all people having also this problem here is the solution:
Change the country of your vWLC. Right now I am in China, so I changed it and then it was working flawlessly :-)
Step 1
Disable the 802.11 networks as follows:
Choose Wireless > 802.11a/n > Network.
Unselect the 802.11a Network Status check box.
Click Apply.
Choose Wireless > 802.11a/n > Network.
Unselect the 802.11b/g Network Status check box.
Click Apply.
Step 2
Choose Wireless > Country to open the Country page.
Thank you all for your help :-)
Paul -
I upgraded a controller yesterday 5508 it went from a low code version 6.x to 6.0.196.0 then to 7.0.116.0. However although all the access points joined code 6.0.196.0 they refused to join 7.0.116.0. The aps are all 1242s.
The country codes etc were all fine so I do not understand what was going on.
Any ideas?
*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065
*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065
*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discovery Request from 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask7: Jun 26 16:07:45.308: 00:3a:99:db:fa:20 Discovery Response sent to 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Discovery Request from 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:45.309: 00:3a:99:db:fa:20 Discovery Response sent to 10.0.0.95:55080
*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discovery Request from 10.0.1.232:20023
*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discovery Response sent to 10.0.1.232:20023
*spamApTask0: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:45.511: 00:13:c3:e1:4c:e0 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Discovery Request from 10.0.1.232:20023
*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:45.512: 00:13:c3:e1:4c:e0 Discovery Response sent to 10.0.1.232:20023
*spamApTask4: Jun 26 16:07:46.516: 00:3a:99:db:fa:10 DTLS connection not found, creating new connection for 10:0:0:101 (55079) 10:0:1:45 (5246)
*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:101/55079)
*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 No entry exists for AP (10:0:0:101/55079)
*spamApTask4: Jun 26 16:07:46.708: 00:3a:99:db:fa:10 No entry exists in database
*spamApTask4: Jun 26 16:07:47.759: 00:3a:99:db:fa:a0 Discovery Request from 10.0.0.184:55084
*spamApTask4: Jun 26 16:07:47.759: 00:3a:99:db:fa:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Response sent to 10.0.0.184:55084
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Request from 10.0.0.184:55084
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask4: Jun 26 16:07:47.760: 00:3a:99:db:fa:a0 Discovery Response sent to 10.0.0.184:55084
*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discovery Request from 10.0.1.239:20032
*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discovery Response sent to 10.0.1.239:20032
*spamApTask0: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:49.471: 00:13:c3:e1:4d:c0 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Discovery Request from 10.0.1.239:20032
*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask7: Jun 26 16:07:49.472: 00:13:c3:e1:4d:c0 Discovery Response sent to 10.0.1.239:20032
*spamApTask1: Jun 26 16:07:52.222: 00:13:c3:e1:4d:80 Discovery Request from 10.0.1.230:20027
*spamApTask1: Jun 26 16:07:52.222: 00:13:c3:e1:4d:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discovery Response sent to 10.0.1.230:20027
*spamApTask0: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask0: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Discovery Request from 10.0.1.230:20027
*spamApTask1: Jun 26 16:07:52.223: 00:13:c3:e1:4d:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask1: Jun 26 16:07:52.224: 00:13:c3:e1:4d:80 Discovery Response sent to 10.0.1.230:20027
*spamApTask5: Jun 26 16:07:52.267: 00:3a:99:da:c7:70 DTLS connection not found, creating new connection for 10:0:0:181 (34152) 10:0:1:45 (5246)
*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discovery Request from 10.0.0.182:55099
*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask0: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Received LWAPP DISCOVERY REQUEST to e8:b7:48:9b:86:4f on port '13'
*spamApTask1: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discovery Response sent to 10.0.0.182:55099
*spamApTask0: Jun 26 16:07:52.274: 00:3a:99:db:ff:20 Discarding discovery request in LWAPP from AP supporting CAPWAP
*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Discovery Request from 10.0.0.182:55099
*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0
*spamApTask1: Jun 26 16:07:52.275: 00:3a:99:db:ff:20 Discovery Response sent to 10.0.0.182:55099
*spamApTask1: Jun 26 16:07:52.306: 00:3a:99:db:f2:40 DTLS connection not found, creating new connection for 10:0:0:100 (55069) 10:0:1:45 (5246)
*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:181/34152)
*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 No entry exists for AP (10:0:0:181/34152)
*spamApTask5: Jun 26 16:07:52.463: 00:3a:99:da:c7:70 No entry exists in database
*spamApTask1: Jun 26 16:07:52.501: 00:3a:99:db:f2:40 DTLS connection closed event receivedserver (10:0:1:45/5246) client (10:0:0:100/55069)
*spamApTask1: Jun 26 16:07:52.502: 00:3a:99:db:f2:40 No entry exists for AP (10:0:0:100/55069)
*spamApTask1: Jun 26 16:07:52.502: 00:3a:99:db:f2:40 No entry exists in databaseSomething "weird" is on the newest 7.0.X. Here's my situation:
1. It doesn't happen to all new APs. When I mean "new", I mean out from a box including APs from RMA.
2. I've seen this in 1240, 1250, 1140. Haven't seen it on a 3500.
3. Here's how it goes ... When the AP, fresh from a box, connects to the networks, sees the WLC/WiSM and downloads the full IOS (OK so far). After the reboot the AP in question loads the new IOS and shows up in the WLC/WiSM. When I check CDP neighbors, NOTHING. What the ... ?
4. Go to the switch and do command "sh cdp neighbor" and what do I get? NOTHING.
5. Check PoE and show that it's IEEE.
For unknown reason, APs in this "trance" shuts off the CDP. I currently have a Cisco TAC Case trying to iron out this "feature". Doesn't appear on the 7.0.96.0 but happens to the newer one. -
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. -
3502i APs not joining controller
So basically my infrastructure consists of four 4402 WLCs running on 7.0.235.3. I'm trying to get new access points to join to the environment, but I am having difficulty doing so. All currently joined APs work fine and are operating well. I'm getting a red, green, off blink code which means it's trying to join, but never does. The other one I get a constantly blinking green but it never joins either. I've setup option 43 in DHCP, added cisco-capwap-controller entries in DNS thinking it was because those are missing, and still cannot get these two access points to join. Can anyone think why it would not be joining?
The access points and WLC are all on the Same VLAN by the way.Hello,
In a Cisco Unified Wireless network, the LAPs must first discover and join a WLC before they can service wireless clients.
Originally, the controllers only operated in Layer 2 mode. In Layer 2 mode, the LAPs are required to be on the same subnet as the management interface and the Layer 3 mode AP-manager interface is not present on the controller. The LAPs communicate with the controller using Layer 2 encapsulation only (ethernet encapsulation) and do not Dynamic Host Configuration Protocol (DHCP) an IP address.
When Layer 3 mode on the controller was developed, a new Layer 3 interface called AP-manager was introduced. In Layer 3 mode, the LAPs would DHCP an IP address first and then send their discovery request to the management interface using IP addresses (Layer 3). This allowed the LAPs to be on a different subnet than the management interface of the controller. Layer 3 mode is the dominate mode today. Some controllers and LAPs can only perform Layer 3 mode.
However, this presented a new problem: how did the LAPs find the management IP address of the controller when it was on a different subnet?
In Layer 2 mode, they were required to be on the same subnet. In Layer 3 mode, the controller and LAP are essentially playing hide and seek in the network. If you do not tell the LAP where the controller is via DHCP option 43, DNS resolution of "Cisco-lwapp-controller@local_domain", or statically configure it, the LAP does not know where in the network to find the management interface of the controller.
In addition to these methods, the LAP does automatically look on the local subnet for controllers with a 255.255.255.255 local broadcast. Also, the LAP remembers the management IP address of any controller it joins across reboots. Therefore, if you put the LAP first on the local subnet of the management interface, it will find the controller's management interface and remember the address. This is called priming. This does not help find the controller if you replace a LAP later on. Therefore, Cisco recommends using the DHCP option 43 or DNS methods.
When the LAPs discover the controller, they do not know if the controller is in Layer 2 mode or Layer 3 mode. Therefore, the LAPs always connect to the management interface address of the controller first with a discovery request. The controller then tells the LAP which mode it is in the discovery reply. If the controller is in Layer 3 mode, the discovery reply contains the Layer 3 AP-manager IP address so the LAP can send a join request to the AP-manager interface next.
Note: By default both management and AP-manager interfaces are left untagged on their VLAN during configuration. In case these are tagged, make sure they are tagged to the same VLAN in order to properly receive discovery and join response from the WLC.
The LWAPP AP goes through this process on startup for Layer 3 mode:
The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address.
The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:
DHCP option 43 (good for global companies where offices and controllers are on different continents)
DNS entry for cisco-capwap-controller (good for local businesses - can also be used to find where brand new APs join)
Note: If you use CAPWAP, make sure that there is a DNS entry for cisco-capwap-controller.
Management IP addresses of controllers the LAP remembers previously
A Layer 3 broadcast on the subnet
Over the air provisioning
Statically configured information
From this list, the easiest method to use for deployment is to have the LAPs on the same subnet as the management interface of the controller and allow the LAP’s Layer 3 broadcast to find the controller. This method should be used for companies that have a small network and do not own a local DNS server.
The next easiest method of deployment is to use a DNS entry with DHCP. You can have multiple entries of the same DNS name. This allows the LAP to discover multiple controllers. This method should be used by companies that have all of their controllers in a single location and own a local DNS server. Or, if the company has multiple DNS suffixes and the controllers are segregated by suffix.
DHCP option 43 is used by large companies to localize the information via the DHCP. This method is used by large enterprises that have a single DNS suffix. For example, Cisco owns buildings in Europe, Australia, and the United States. In order to ensure that the LAPs only join controllers locally, Cisco cannot use a DNS entry and must use DHCP option 43 information to tell the LAPs what the management IP address of their local controller is.
Finally, static configuration is used for a network that does not have a DHCP server.You can statically configure the information necessary to join a controller via the console port and the AP’s CLI. For information on how to statically configure controller information using the AP CLI, refer to Manually Configuring Controller Information Using the Access Point CLI.
For a detailed explanation on the different discovery algorithms that LAPs use to find controllers, refer to LAP Registration with WLC.
For information on configuring DHCP option 43 on a DHCP server, refer to DHCP OPTION 43 for Lightweight Cisco Aironet Access Points Configuration Example.
Send a discovery request to every controller on the list and wait for the controller's discovery reply which contains the system name, AP-manager IP addresses, the number of APs already attached to each AP-manager interface, and overall excess capacity for the controller.
Look at the controller list and send a join request to a controller in this order (only if the AP received a discovery reply from it):
Primary Controller system name (previously configured on LAP)
Secondary Controller system name (previously configured on LAP)
Tertiary Controller system name (previously configured on LAP)
Master controller (if the LAP has not been previously configured with any Primary, Secondary, or Tertiary controller names. Used to always know which controller brand new LAPs join)
If none of the above are seen, load balance across controllers using the excess capacity value in the discovery response.
If two controllers have the same excess capacity, then send the join request to the first controller that responded to the discovery request with a discovery response. If a single controller has multiple AP-managers on multiple interfaces, choose the AP-manager interface with the least number of APs.
The controller will respond to all discovery requests without checking certificates or AP credentials. However, join requests must have a valid certificate in order to get a join response from the controller. If the LAP does not receive a join response from its choice, the LAP will try the next controller in the list unless the controller is a configured controller (Primary/Secondary/Tertiary).
When it receives the join reply, the AP checks to make sure it has the same image as that of the controller. If not, the AP downloads the image from the controller and reboots to load the new image and starts the process all over again from step 1.
If it has the same software image, it asks for the configuration from the controller and moves into the registered state on the controller.
After you download the configuration, the AP might reload again to apply the new configuration. Therefore, an extra reload can occur and is a normal behavior. -
So today has been a disaster. I have 11 Cisco Aironet APs connected to a Cisco WLC 4402 running 7.0.235.3. When we lost power to the controller over the weekend I only had 8 come back. In the AP join log three of them were saying"Layer 3 discovery request not received on management VLAN". Mind you they were working before the power went out. So one of my colleagues advised me to shut down the controller, disable the switch ports the AP's are plugged into, restart the controller, and then reenable the ports on the switch. Well now I only have three. The rest get the same error message I mentioned before. I also tried disabled and reenabled the DHCP scope they work on as well. Like I said they were all working before the power went out. Can anyone help?
Nothing is wrong. That message simply means, that there was an LWAPP request and the code the AP is on is CAPWAP. This happens in case you have a WLC on older code, but get/convert one with newer code.
Is the dhcp server for the AP management network in another vlan and you have ip helper-address configured?
How are you doing your Discovery? L2 forwarding, option 43?
I think you may have to upgrade the code on your controller to support your aps... or downgrade the code on the aps manually before attempting the join process with your controller.
What model # AP ? -
Hello, I am Claudio
I have problems with register the APs in the module WiSM, the AP join statistics is null.
The IPs from APs are local DHCP in the module.
The softtware version in the WiSM is 7.0.116. The APs are 1140. The IOS version on the Cat6500 is 12.2.33SXI4a.
Some of you had a similar problem.
Thanks, best regardsThe option 43 is......
ip dhcp pool APs
network 172.23.24.0 255.255.255.0
default-router 172.23.24.1
option 43 hex f108ac140194ac140196
The problem is not the option 43, the problem is between the module WiSM and SUP720.
I Replace WiSM for a WLC4402 and APs were recorded without problems
debug WiSM.....
URA_NUNOA_SW_6500_CLH#
Aug 31 16:27:20.818: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd2f.2d22 for slot/port 2/1
Aug 31 16:27:20.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/1 got an ip 172.20.1.178 68ef.bd2f.2d22/68ef.bd2f.2d 22
Aug 31 16:27:20.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd30.58e2 for slot/port 2/2
Aug 31 16:27:20.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/2 got an ip 172.20.1.179 68ef.bd30.58e2/68ef.bd30.58 e2
Aug 31 16:27:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
Aug 31 16:27:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
Aug 31 16:27:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
Aug 31 16:27:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
Aug 31 16:28:00.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd30.58e2 for slot/port 2/2
Aug 31 16:28:00.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/2 got an ip 172.20.1.179 68ef.bd30.58e2/68ef.bd30.58 e2
Aug 31 16:28:00.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd2f.2d22 for slot/port 2/1
Aug 31 16:28:00.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/1 got an ip 172.20.1.178 68ef.bd2f.2d22/68ef.bd2f.2d 22
Aug 31 16:28:15.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
Aug 31 16:28:15.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
Aug 31 16:28:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
Aug 31 16:28:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
Aug 31 16:28:40.818: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd2f.2d22 for slot/port 2/1
Aug 31 16:28:40.818: WiSM-Evt:dman_reg_arp_added: cntrl 2/1 got an ip 172.20.1.178 68ef.bd2f.2d22/68ef.bd2f.2d22
Aug 31 16:28:40.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd30.58e2 for slot/port 2/2
Aug 31 16:28:40.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/2 got an ip 172.20.1.179 68ef.bd30.58e2/68ef.bd30.58e2
Aug 31 16:28:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
Aug 31 16:28:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2 -
1041N APs not joining 2100 WLC
Hopefully this will be an easy solution for some of you.
I have two LAP1041N APs I am trying to setup on a new 2100 WLC (7.0.116.0). THe APs will blink green fast; then go to a green, red, blue cycle for a min or so; then back to blinking green fast. Not sure what else to try here.
Thanks for the help.Please use a L2/ L3 switch
For a L2 swith the AP and WLC must be on the same VLAN iof the L2 switch
For AP:
config t
int gig 0/1
swithport access native vlan 1( for ex)
switchport mode access
no shut
For WLC :
config t
int gig 0/2
switchport mode trunk
switchport trunk encapsulation dot1q
switchport trunk native vlan 1
no shut
For L3 switch you can assign vlan interfaces :
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a0080665cdf.shtml#wlc
Also here is the link to the discovery process:
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml
Thanks,
Tuhin -
AP1042N not joining 5508 controller
I am trying to configure new 5508wireless controller, AP 1042N model access points are able to receive DHCP IP address from Controller, but not able to join them.
Please provide the requirements and basic configuration details for this.WLC : sh sysinfo:
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.220.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console
1.27
Build Type....................................... DATA + WPS
System Name...................................... Cisco_bc:56:44
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... 192.168.9.100
Last Reset....................................... Software reset
System Up Time................................... 0 days 2 hrs 45 mins 36 secs
System Timezone Location.........................
Current Boot License Level....................... base
Current Boot License Type........................ Permanent
Next Boot License Level.......................... base
Next Boot License Type........................... Permanent
WAP; Sh version:
Cisco IOS Software, C1040 Software (C1140-K9W7-M), Version 12.4(25d)JA1, RELEASE
SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 11-Aug-11 02:58 by prod_rel_team
ROM: Bootstrap program is C1040 boot loader
BOOTLDR: C1040 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA3, RELEASE SOFTWARE
(fc1)
ap uptime is 10 minutes
System returned to ROM by power-on
System image file is "flash:/c1140-k9w7-mx.124-25d.JA1/c1140-k9w7-mx.124-25d.JA1
ap#sh inventory
NAME: "AP1040", DESCR: "Cisco Aironet 1040 Series (IEEE 802.11n) Access Point"
PID: AIR-AP1042N-N-K9 , VID: V04, SN: FGL1620S21W -
We just completed deployment of (4) 5508-250's in a large enviroment. We are now trying to get some test AP's to join the new WLC's. At one point it appeared that one of the 5 joined but the other 4 did not. We rebboted everything including resetting the AP's to factory and upon doing that all 5 ap's came up and joined the legacy WISM's blades sitting in the core.
The new 5508's are sitting on a new stack of switches running 12.2.58(SE2) ip base. We have all new subnets for the new ap's as well as all vlan interfaces on the controllers themselves. IE: vlan 499 and vlan 500. Vlan 500 is Management and 499 is the ap-manager interfaces (32 of them).
1. Why would the new AP's prefer the old WISM to the 5508's?
2. What do we need to do to fix that until the we can do a migration?
3. The WLC's and the cores are not in the same stack. The WLC's are on the customers 6509 and the (4) 5508's are on a new 3750x stack with a port channel to the core 6509.
4. Does the new stack have to be running the L-3 IOS with a routing protocol running. The customers current enviroment is EIGRP.
5. I have looked at the new WLC configuration and compared it to other similar sites and they are the same with the exception of the L3 on the new 3750x stack.
Thanks,
Evan KalbachHere is my response to your queries.
1. Unless you configure primary,secondary (HA parameters) on your AP, it does not prefer 5508 as long as it can reach both controllers
2. You can configure the 5508 as primary controller ( & WiSM as secondary) to inluence AP to go to 5508 as first preference. You can try below CLI command on your WiSM for the APs you want to register to 5508 as primary & keep WiSM as secondary.
config ap secondary-base
config ap primary-base <5508 WLC name> <5508 Mgt IP>
3. WLC does not need to connect Core
4. As long as WLC have rachability to rest of networks, that's fine. No L3 routing required on the swich you connect the WLC.L3 gateway can be defined another L3 switch. Then you should have extend L2 from the WLC connect switch upto L3 defined switch.
5. Doesn't matter this.
HTH
Rasika
**** Pls rate all useful responses **** -
Dear All,
My WLC a 5508 version 8.0.100.0.Do not Join a CAP2602E, is the first time that i connect this model of AP to the WLC.
I have enabled some Debug and I see that on the controller I got the "Unknown AP type. Using Controller Version!!!" error on the WLC.
Following the trouble shooting guide lines about Join issue, I have also checked this:
(Cisco Controller) >show ap join stats detailed 84:80:2d:c2:9c:90 <-----This is the 2602E Mac
Sync phase statistics
- Time at sync request received............................ Not applicable
- Time at sync completed................................... Not applicable
Discovery phase statistics
- Discovery requests received.............................. 75
- Successful discovery responses sent...................... 75
- Unsuccessful discovery request processing................ 0
- Reason for last unsuccessful discovery attempt........... Not applicable
- Time at last successful discovery attempt................ Dec 02 16:43:17.470
- Time at last unsuccessful discovery attempt.............. Not applicable
Join phase statistics
- Join requests received................................... 0
- Successful join responses sent........................... 0
- Unsuccessful join request processing..................... 0
- Reason for last unsuccessful join attempt................ Not applicable
- Time at last successful join attempt..................... Not applicable
- Time at last unsuccessful join attempt................... Not applicable
Configuration phase statistics
--More-- or (q)uit
- Configuration requests received.......................... 0
- Successful configuration responses sent.................. 0
- Unsuccessful configuration request processing............ 0
- Reason for last unsuccessful configuration attempt....... Not applicable
- Time at last successful configuration attempt............ Not applicable
- Time at last unsuccessful configuration attempt.......... Not applicable
Last AP message decryption failure details
- Reason for last message decryption failure............... Not applicable
Last AP disconnect details
- Reason for last AP connection failure.................... Not applicable
- Last AP disconnect reason................................ Not applicable
Last join error summary
- Type of error that occurred last......................... None
- Reason for error that occurred last...................... Not applicable
- Time at which the last join error occurred............... Not applicable
AP disconnect details
- Reason for last AP connection failure.................... Not applicable
WLC Policy config is: Someone can help pls?Dear All,
I have done other tests, and I hope this time I will be more precise.
The AP are on the same vlan where is located the WLC.
I found a way to work around the problem.
If I take a out-of-the-box AP and connect if on the same vlan of WLC, and after the boot I configure on the Ap:
capwap ap ip address 172.xx.xx.xx mask
capwap ap ip defaut-gataway 172.xx.xx.xx
capwap ap controller ip address ip_addressxx.xx.xx.xx
capwap ap primary-base controller_name controller_ip_address
The Ap try to Join the WLC but with no success:
User Access Verification
Username: cisco
Password:
AP1c6a.7ae2.ab11>en
Password:
% Access denied
AP1c6a.7ae2.ab11>en
Password:
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#capwap
AP1c6a.7ae2.ab11#capwap ap
AP1c6a.7ae2.ab11#capwap ap controll
AP1c6a.7ae2.ab11#capwap ap controller ip address 172.26.110.4
AP1c6a.7ae2.ab11#capwap ap controller ip address 172.26.110.4 prima
AP1c6a.7ae2.ab11#capwap ap primary-base wlc01 172.26.110.4
AP1c6a.7ae2.ab11#capwap ap primary-base wlc01 172.26.110.4controller ip address 172.26.110.4 ip addess
AP1c6a.7ae2.ab11#capwap ap ip addess
AP1c6a.7ae2.ab11#capwap ap ip
*Mar 1 00:03:56.479: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 1 00:03:56.479: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 1 00:03:56.479: %MESH-6-LINK_UPDOWN: Mesh station 1c6a.7ae2.ab11 link Down
*Mar 1 00:03:58.479: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:03:59.479: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
% Incomplete command.
AP1c6a.7ae2.ab11#capwap ap ip ?
address Configure ap static IP address
default-gateway Configure Default-gateway IP address
AP1c6a.7ae2.ab11#capwap ap ip defa
AP1c6a.7ae2.ab11#capwap ap ip default-gateway 172.26.110.1
AP1c6a.7ae2.ab11#capwap ap ip default-gateway 172.26.110.1 address\
AP1c6a.7ae2.ab11#capwap ap ip address 172.26.110.
*Mar 1 00:04:39.891: %IP-4-CLASS: Bad IP address and mask 0.0.0.0/0 in class_resolve()
*Mar 1 00:04:40.391: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 1 00:04:41.555: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 1 00:04:41.555: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Mar 1 00:04:41.555: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar 1 00:04:41.555: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Mar 1 00:04:42.391: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Mar 1 00:04:43.391: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:04:45.439: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:04:45.447: %PARSER-4-BADCFG: Unexpected end of configuration file.
*Mar 1 00:04:45.467: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:04:46.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:04:46.471: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 1 00:04:46.479: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:04:47.499: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:04:48.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up?
A.B.C.D
AP1c6a.7ae2.ab11#capwap ap ip address 172.26.110.30 255.255.254.0
You should configure Domain and Name Server from controller CLI/GUI.
AP1c6a.7ae2.ab11#
*Mar 1 00:05:16.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to downsh
*Mar 1 00:05:16.507: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:05:17.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:05:17.527: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:05:18.527: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
% Type "show ?" for a list of subcommands
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#sh cap
AP1c6a.7ae2.ab11#sh cap
*Mar 1 00:05:26.467: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Mar 1 00:05:26.467: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:46:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to downw
AP1c6a.7ae2.ab11#sh capwap
*Dec 4 07:46:23.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 4 07:46:23.707: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.707: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4
*Dec 4 07:46:23.711: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.26.110.4
*Dec 4 07:46:23.711: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.26.110.4:5246
*Dec 4 07:46:23.711: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Dec 4 07:46:23.711: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:46:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.291: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Dec 4 07:46:23.319: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:46:23.723: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.723: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4
*Dec 4 07:46:23.727: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.26.110.4
*Dec 4 07:46:23.727: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.26.110.4:5246
*Dec 4 07:46:23.727: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Dec 4 07:46:23.727: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:46:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.627: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:46:23.635: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 4 07:46:23.719: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.719: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4
*Dec 4 07:46:23.723: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.26.110.4
*Dec 4 07:46:23.723: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.26.110.4:5246
*Dec 4 07:46:23.723: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Dec 4 07:46:23.723: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:46:23.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.723: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:46:23.727: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4
*Dec 4 07:46:24.327: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:46:24.335: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 4 07:46:24.343: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 4 07:46:24.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.9 peer_port: 5246
*Dec 4 07:46:24.467: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.9
*Dec 4 07:46:24.467: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Dec 4 07:46:24.467: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Dec 4 07:46:24.467: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Dec 4 07:46:24.467: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.26.110.9
*Dec 4 07:46:25.363: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:46:25.371: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 4 07:46:25.379: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 4 07:46:26.399: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:46:27.399: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Dec 4 07:46:29.467: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.9
*Dec 4 07:46:29.471: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 4 07:46:29.479: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 4 07:46:30.471: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Dec 4 07:46:30.499: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:46:31.499: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
% Incomplete command.
AP1c6a.7ae2.ab11#sh capwap
AP1c6a.7ae2.ab11#sh capwap ip
AP1c6a.7ae2.ab11#sh capwap ip ?
config CAPWAP IP static configuration
AP1c6a.7ae2.ab11#sh capwap ip con
AP1c6a.7ae2.ab11#sh capwap ip config
LWAPP Static IP Configuration
IP Address 172.26.110.30
IP netmask 255.255.254.0
Default Gateway 172.26.110.1
Primary Controller 172.26.110.4
AP1c6a.7ae2.ab11#
*Dec 4 07:47:22.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.26.110.9:5246
*Dec 4 07:47:23.035: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Dec 4 07:47:23.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Dec 4 07:47:23.071: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:47:24.047: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Dec 4 07:47:24.079: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 4 07:47:24.087: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 4 07:47:25.107: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:47:26.107: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Dec 4 07:47:33.071: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Dec 4 07:47:33.071: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:47:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:47:36.003: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 4 07:47:36.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Dec 4 07:47:36.711: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:47:36.715: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4
*Dec 4 07:47:36.715: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.26.110.4
*Dec 4 07:47:36.715: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.26.110.4:5246
*Dec 4 07:47:36.715: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Dec 4 07:47:36.715: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:47:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:47:36.287: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Dec 4 07:47:36.315: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:47:36.719: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:47:36.719: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4
*Dec 4 07:47:36.723: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.26.110.4
*Dec 4 07:47:36.723: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.26.110.4:5246
*Dec 4 07:47:36.723: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Dec 4 07:47:36.723: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:47:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:47:36.627: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Dec 4 07:47:36.635: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Dec 4 07:47:36.719: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:47:36.719: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4
*Dec 4 07:47:36.723: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.26.110.4
*Dec 4 07:47:36.723: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.26.110.4:5246
*Dec 4 07:47:36.723: %CAPWAP-3-ERRORLOG: Go join a capwap controller
On the WLC side at the same time:
*spamApTask0: Dec 04 08:46:34.619: ðcIÝ
*spamApTask0: Dec 04 08:46:34.619: f0:9e:63:49:dd:a0 Radius Authentication failed. Closing dtls Connection.
*spamApTask0: Dec 04 08:46:34.627: Unable to find deleted AP f0:9e:63:49:dd:a0
*spamApTask0: Dec 04 08:46:34.628: 1c:6a:7a:e2:ab:11 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 172.26.110.30:10930)since DTLS session is not established
*spamApTask0: Dec 04 08:46:35.345: f0:9e:63:49:dd:a0 State machine handler: Failed to process msg type = 3 state = 0 from 172.26.110.30:10930
*spamApTask0: Dec 04 08:46:35.346: 1c:6a:7a:e2:ab:11 Failed to parse CAPWAP packet from 172.26.110.30:10930
*spamApTask0: Dec 04 08:46:35.346: ðcIÝ
*spamApTask0: Dec 04 08:46:35.346: f0:9e:63:49:dd:a0 Radius Authentication failed. Closing dtls Connection.
*spamApTask0: Dec 04 08:46:35.354: Unable to find deleted AP f0:9e:63:49:dd:a0
*spamApTask0: Dec 04 08:46:35.354: 1c:6a:7a:e2:ab:11 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 172.26.110.30:10930)since DTLS session is not established
*spamApTask0: Dec 04 08:46:36.070: f0:9e:63:49:dd:a0 State machine handler: Failed to process msg type = 3 state = 0 from 172.26.110.30:10930
*spamApTask0: Dec 04 08:46:36.070: 1c:6a:7a:e2:ab:11 Failed to parse CAPWAP packet from 172.26.110.30:10930
*spamApTask0: Dec 04 08:46:36.071: ðcIÝ
*spamApTask0: Dec 04 08:46:36.071: f0:9e:63:49:dd:a0 Radius Authentication failed. Closing dtls Connection.
*spamApTask0: Dec 04 08:46:36.079: Unable to find deleted AP f0:9e:63:49:dd:a0
*spamApTask0: Dec 04 08:46:36.080: 1c:6a:7a:e2:ab:11 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 172.26.110.30:10930)since DTLS session is not established
*spamApTask0: Dec 04 08:46:36.799: f0:9e:63:49:dd:a0 State machine handler: Failed to process msg type = 3 state = 0 from 172.26.110.30:10930
*spamApTask0: Dec 04 08:46:36.799: 1c:6a:7a:e2:ab:11 Failed to parse CAPWAP packet from 172.26.110.30:10930
*spamApTask0: Dec 04 08:46:36.799: ðcIÝ
*spamApTask0: Dec 04 08:46:36.799: f0:9e:63:49:dd:a0 Radius Authentication failed. Closing dtls Connection.
*spamApTask0: Dec 04 08:46:36.807: Unable to find deleted AP f0:9e:63:49:dd:a0
*spamApTask0: Dec 04 08:46:36.808: 1c:6a:7a:e2:ab:11 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 172.26.110.30:10930)since DTLS session is not established
*spamApTask1: Dec 04 08:47:36.875: Unknown AP type. Using Controller Version!!!
*spamApTask1: Dec 04 08:47:36.876: Unknown AP type. Using Controller Version!!!
*spamApTask1: Dec 04 08:47:36.876: Unknown AP type. Using Controller Version!!!
*spamApTask1: Dec 04 08:47:36.876: Unknown AP type. Using Controller Version!!!
But If I take thw same Ap unplug the power cord, and press the MODE button, then I go in Rommode, I do the command Boot, the Ap restart, I configure again the same capwap ap commands, and the Ap JOIN the WLC!!!!! Somone can explain me why?
AP1c6a.7ae2.ab11#
IOS Bootloader - Starting system.
flash is writable
FLASH CHIP: Macronix Mirrorbit (00C2)
Xmodem file system is available.
flashfs[0]: 42 files, 8 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31997952
flashfs[0]: Bytes used: 11515904
flashfs[0]: Bytes available: 20482048
flashfs[0]: flashfs fsck took 16 seconds.
Reading cookie from SEEPROM
Base Ethernet MAC address: 1c:6a:7a:e2:ab:11
Ethernet speed is 100 Mb - FULL Duplex
button is pressed, wait for button to be released...
button pressed for 24 seconds
process_config_recovery: set IP address and config to default 10.0.0.1
process_config_recovery: image recovery
image_recovery: Download default IOS tar image tftp://255.255.255.255/ap3g2-k9w7-tar.default
examining image...
DPAA Set for Independent Mode
DPAA_INIT = 0x0
%Error opening tftp://255.255.255.255/ap3g2-k9w7-tar.default (connection timed out)ap:
ap:
ap:
ap:
ap:
ap:
ap: boot
Rebooting system to reset DPAA...
IOS Bootloader - Starting system.
flash is writable
FLASH CHIP: Macronix Mirrorbit (00C2)
Xmodem file system is available.
flashfs[0]: 42 files, 8 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31997952
flashfs[0]: Bytes used: 11515904
flashfs[0]: Bytes available: 20482048
flashfs[0]: flashfs fsck took 15 seconds.
Reading cookie from SEEPROM
Base Ethernet MAC address: 1c:6a:7a:e2:ab:11
Ethernet speed is 100 Mb - FULL Duplex
Loading "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-mx.152-4.JA1"...###########################
File "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-mx.152-4.JA1" uncompressed and installed, entry point: 0x2003000
executing...
Secondary Bootloader - Starting system.
Xmodem file system is available.
flashfs[0]: 42 files, 8 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31997952
flashfs[0]: Bytes used: 11515904
flashfs[0]: Bytes available: 20482048
flashfs[0]: flashfs fsck took 8 seconds.
Base Ethernet MAC address: 1c:6a:7a:e2:ab:11
Boot CMD: 'boot flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-xx.152-4.JA1'
Loading "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-xx.152-4.JA1"...###############################
File "flash:/ap3g2-k9w8-mx.152-4.JA1/ap3g2-k9w8-xx.152-4.JA1" uncompressed and installed, entry point: 0x2003000
executing...
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.2(4)JA1, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 30-Jul-13 22:57 by prod_rel_team
Initializing flashfs...
flashfs[3]: 42 files, 8 directories
flashfs[3]: 0 orphaned files, 0 orphaned directories
flashfs[3]: Total bytes: 31739904
flashfs[3]: Bytes used: 11515904
flashfs[3]: Bytes available: 20224000
flashfs[3]: flashfs fsck took 8 seconds.
flashfs[3]: Initialization complete.
flashfs[4]: 0 files, 1 directories
flashfs[4]: 0 orphaned files, 0 orphaned directories
flashfs[4]: Total bytes: 11999232
flashfs[4]: Bytes used: 1024
flashfs[4]: Bytes available: 11998208
flashfs[4]: flashfs fsck took 0 seconds.
flashfs[4]: Initialization complete.
Copying radio files from flash: to ram:
Copy in progress...CCCCC
Copy in progress...CCC
Copy in progress...CCCC
Copy in progress...CCCC
Copy in progress...CC
Uncompressing radio files...
...done Initializing flashfs.
Radio0 present 8764 8000 0 A8000000 A8010000 0
Rate table has 244 entries (64 SGI/104 BF variants)
Radio1 present 8764 8000 0 88000000 88010000 4
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].
%Error opening flash:/ap3g2-rcvk9w8-mx/info (No such file or directory)cisco AIR-CAP2602E-E-K9 (PowerPC) processor (revision A0) with 180214K/81920K bytes of memory.
Processor board ID FCZ1843Q0WD
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.5.1.73
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 1C:6A:7A:E2:AB:11
Part Number : 73-14511-03
PCA Assembly Number : 800-37898-01
PCA Revision Number : B0
PCB Serial Number : FOC18403PBM
Top Assembly Part Number : 800-38357-02
Top Assembly Serial Number : FCZ1843Q0WD
Top Revision Number : A0
Product/Model Number : AIR-CAP2602E-E-K9
% Please define a domain-name first.
Press RETURN to get started!
*Mar 1 00:00:11.299: FIPS IOS test Image Checksum successful
*Mar 1 00:00:11.299: FIPS IOS test Crypto RNG DEK Key Test successful
*Mar 1 00:00:11.299: FIPS IOS test SHA-1 successful
*Mar 1 00:00:11.299: FIPS IOS test HMAC-SHA1 successful
*Mar 1 00:00:11.299: FIPS IOS test AES CBC 128-bit Encrypt successful
*Mar 1 00:00:11.299: FIPS IOS test AES CBC 128-bit Decrypt successful
*Mar 1 00:00:11.299: FIPS IOS test IOS AES CMAC Encrypt successful
*Mar 1 00:00:11.299: FIPS IOS test IOS CCM Encrypt successful
*Mar 1 00:00:11.299: FIPS IOS test IOS CCM Decrypt successful
*Mar 1 00:00:11.331: FIPS IOS test RSA Signature Generation successful
*Mar 1 00:00:11.335: FIPS IOS test RSA Signature Verification successful
*Mar 1 00:00:11.335: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:11.335: %IFMGR-7-NO_IFINDEX_FILE: Unable to open nvram:/ifIndex-table No such file or directory
*Mar 1 00:00:11.791: Registering HW DTLS
*Mar 1 00:00:14.591: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:18.271: FIPS RADIO test AES 128-bit encrypt for TX on Dot11Radio 0 successful
*Mar 1 00:00:18.271: FIPS RADIO test AES 128-bit CCM encrypt on Dot11Radio 0 successful
*Mar 1 00:00:18.271: FIPS RADIO test AES 128-bit CCM decrypt on Dot11Radio 0 successful
*Mar 1 00:00:18.271: FIPS RADIO test AMAC AES 128-bit CMAC encrypt on Dot11Radio 0 successful
*Mar 1 00:00:18.271: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:24.399: FIPS RADIO test AES 128-bit encrypt for TX on Dot11Radio 1 successful
*Mar 1 00:00:24.399: FIPS RADIO test AES 128-bit CCM encrypt on Dot11Radio 1 successful
*Mar 1 00:00:24.399: FIPS RADIO test AES 128-bit CCM decrypt on Dot11Radio 1 successful
*Mar 1 00:00:24.399: FIPS RADIO test AMAC AES 128-bit CMAC encrypt on Dot11Radio 1 successful
*Mar 1 00:00:24.399: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:24.483: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
*Mar 1 00:00:26.831: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power source
*Mar 1 00:00:26.859: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.2(4)JA1, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 30-Jul-13 22:57 by prod_rel_team
*Mar 1 00:00:26.859: %SNMP-5-COLDSTART: SNMP agent on host ap is undergoing a cold start
*Mar 1 00:00:26.915: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:26.923: %LWAPP-3-CLIENTERRORLOG: Config load from flash failed. Initialising Cfg
*Mar 1 00:00:26.923: %CAPWAP-3-ERRORLOG: Failed to load configuration from flash. Resetting to default config
*Mar 1 00:00:26.927: %PARSER-4-BADCFG: Unexpected end of configuration file.
*Mar 1 00:00:26.939: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to uplwapp_crypto_init: MIC Present and Parsed Successfully
*Mar 1 00:00:27.031: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:27.031: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:27.915: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:27.915: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:28.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:28.083: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:29.071: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:00:29.159: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:29.167: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 1 00:00:29.175: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:30.063: FIPS HW test SHA-1 successful
*Mar 1 00:00:30.063: FIPS HW test HMAC-SHA1 successful
*Mar 1 00:00:30.063: FIPS HW test AES CBC 128-bit Encrypt successful
*Mar 1 00:00:30.063: FIPS HW test AES CBC 128-bit Decrypt successful
*Mar 1 00:00:30.159: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:00:30.167: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:30.195: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:30.563: FIPS HW test SHA-1 successful
*Mar 1 00:00:30.563: FIPS HW test HMAC-SHA1 successful
*Mar 1 00:00:30.563: FIPS HW test AES CBC 128-bit Encrypt successful
*Mar 1 00:00:30.563: FIPS HW test AES CBC 128-bit Decrypt successful
*Mar 1 00:00:30.563: %SOAP_FIPS-2-SELF_TEST_HW_SUCCESS: HW crypto FIPS self test passed
*Mar 1 00:00:30.563: DPAA Initialization Complete
*Mar 1 00:00:30.563: %SYS-3-HARIKARI: Process DPAA INIT top-level routine exited
*Mar 1 00:00:31.195: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:00:31.563: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up%Default route without gateway, if not a point-to-point interface, may impact performance
*Mar 1 00:00:55.703: Logging LWAPP message to 255.255.255.255.
Not in Bound state.
*Mar 1 00:01:55.707: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
User Access Verification
Username: cisco
Password:
AP1c6a.7ae2.ab11>en
Password:
AP1c6a.7ae2.ab11#sh capwap
AP1c6a.7ae2.ab11#sh capwap ip
AP1c6a.7ae2.ab11#sh capwap ip con
AP1c6a.7ae2.ab11#sh capwap ip config
LWAPP Static IP Configuration
AP1c6a.7ae2.ab11#
Not in Bound state.
*Mar 1 00:02:45.707: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#cap
AP1c6a.7ae2.ab11#capwap ap
AP1c6a.7ae2.ab11#capwap ap co
AP1c6a.7ae2.ab11#capwap ap controller 172.26.110.4
^
% Invalid input detected at '^' marker.
AP1c6a.7ae2.ab11#capwap ap controller 172.26.110.4i172.26.110.4p172.26.110.4 172.26.110.4a172.26.110.4d172.26.110.4d172.26.110.4r172.26.110.4e172.26.110.4s172.26.110.4s172.26.110.4 172.26.110.4
AP1c6a.7ae2.ab11#capwap ap controller ip address 172.26.110.4 prim
AP1c6a.7ae2.ab11#capwap ap prima
AP1c6a.7ae2.ab11#capwap ap primary-base wlc01 172.2
Not in Bound state.6.
*Mar 1 00:03:35.707: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.110.4 ?
<cr>
AP1c6a.7ae2.ab11#capwap ap primary-base wlc01 172.26.110.4
AP1c6a.7ae2.ab11#capwap ap primary-base wlc01 172.26.110.4 ip def
AP1c6a.7ae2.ab11#capwap ap ip default-gateway 172.26.110.4 1
AP1c6a.7ae2.ab11#capwap ap ip default-gateway 172.26.110.1 add
AP1c6a.7ae2.ab11#capwap ap ip address 172.26.110.30 255.255.254.0
Not in Bound state.
*Mar 1 00:04:25.707: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
You should configure Domain and Name Server from controller CLI/GUI.
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#
AP1c6a.7ae2.ab11#sh cap
AP1c6a.7ae2.ab11#sh capw
AP1c6a.7ae2.ab11#sh capwap ip
AP1c6a.7ae2.ab11#sh capwap ip con
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
AP1c6a.7ae2.ab11#sh capwap ip config
LWAPP Static IP Configuration
IP Address 172.26.110.30
IP netmask 255.255.254.0
Default Gateway 172.26.110.1
Primary Controller 172.26.110.4
AP1c6a.7ae2.ab11#
*Mar 1 00:04:47.067: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
examining image...!
extracting info (283 bytes)
Image info:
Version Suffix: k9w8-.153-3.JA
Image Name: ap3g2-k9w8-mx.153-3.JA
Version Directory: ap3g2-k9w8-mx.153-3.JA
Ios Image Size: 225792
Total Image Size: 13455872
Image Feature: WIRELESS LAN|LWAPP
Image Family: AP3G2
Wireless Switch Management Version: 8.0.100.0
Extracting files...
*Mar 1 00:04:57.067: %CAPWAP-3-ERRORLOG: Selected MWAR 'wlc01'(index 0).
*Mar 1 00:04:57.067: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 4 07:57:47.000: %CAPWAP-5-DTLSREQSEND: DT
ap3g2-k9w8-mx.153-3.JA/ (directory) 0 (bytes)
extracting ap3g2-k9w8-mx.153-3.JA/V2.bin (12826 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/Y2.bin (5830 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/file_hashes (7254 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/8004.img (561134 bytes)!!!LS connection request sent peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:57:47.707: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.26.110.4 peer_port: 5246
*Dec 4 07:57:47.707: %CAPWAP-5-SENDJOIN: sending Join Request to 172.26.110.4perform archive download capwap:/ap3g2 tar file
*Dec 4 07:57:47.751: %CAPWAP-6-AP_IMG_DWNLD: Required image not found on AP. Downloading image from Controller.
*Dec 4 07:57:47.751: Loading file /ap3g2...
extracting ap3g2-k9w8-mx.153-3.JA/U2.bin (6996 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/X5.bin (1566 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/final_hash.sig (513 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/R5.bin (3423 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/ap3g2-k9w8-tx.153-3.JA (73 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/R2.bin (13992 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/img_sign_rel_sha2.cert (1371 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/B2.bin (9328 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/info (283 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/F5.bin (3662 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/8006.img (563979 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ap3g2-k9w8-mx.153-3.JA/html/ (directory) 0 (bytes)
ap3g2-k9w8-mx.153-3.JA/html/level/ (directory) 0 (bytes)
ap3g2-k9w8-mx.153-3.JA/html/level/1/ (directory) 0 (bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/forms.js (20125 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/appsui.js (563 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/ap_home.shtml.gz (1370 bytes)!
ap3g2-k9w8-mx.153-3.JA/html/level/1/images/ (directory) 0 (bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/images/info.gif (399 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/images/cisco-logo-2007.gif (1648 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/images/background_web41.jpg (732 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/images/login_homeap.gif (19671 bytes)!!
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/images/itp-logo.png (2822 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/config.js (27254 bytes)!!
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/sitewide.js (17250 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/officeExtendap.css (41801 bytes)!!!!
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/back.shtml (512 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/1/config-oeap.js (779 bytes)
ap3g2-k9w8-mx.153-3.JA/html/level/15/ (directory) 0 (bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/15/officeExtendapBanner.htm (7514 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/15/officeExtendapConfig.shtml.gz (2864 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/html/level/15/officeExtendapSummary.htm (985 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/15/officeExtendapHelp.htm (5721 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/html/level/15/officeExtendapMain.shtml.gz (3350 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/html/level/15/officeExtendapEvent.shtml.gz (988 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/B5.bin (1963 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/E5.bin (1846 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/Y5.bin (1511 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/C2.bin (19822 bytes)!!
extracting ap3g2-k9w8-mx.153-3.JA/final_hash (141 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/ap3g2-k9w8-xx.153-3.JA (11381713 bytes)!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
*Dec 4 07:59:47.723: %CAPWAP-3-ERRORLOG: Invalid event 48 & state 10 combination.
*Dec 4 07:59:47.723: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 48, state 10
*Dec 4 07:59:47.723: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Dec 4 07:59:47.723: %CAPWAP-3-ERRORLOG: Failed to process timer message.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
extracting ap3g2-k9w8-mx.153-3.JA/C5.bin (6936 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/ap3g2-k9w8-mx.153-3.JA (215867 bytes)!!!!!!!!!!!!!!!!!
extracting ap3g2-k9w8-mx.153-3.JA/U5.bin (3048 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/img_sign_rel.cert (1375 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/Q5.bin (2806 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/X2.bin (16324 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/E2.bin (19822 bytes)!!
extracting ap3g2-k9w8-mx.153-3.JA/Q2.bin (6996 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/ap3g2-bl-2600 (190140 bytes)!!!!!!!!!!!!!!
extracting ap3g2-k9w8-mx.153-3.JA/V5.bin (512 bytes)
extracting ap3g2-k9w8-mx.153-3.JA/F2.bin (13992 bytes)!
extracting ap3g2-k9w8-mx.153-3.JA/ap3g2-bl-3600 (189183 bytes)!!!!!!!!!!!!!!!
extracting info.ver (283 bytes)
Deleting current version: flash:/ap3g2-k9w8-mx.152-4.JA1...
Set booting path to recovery image: ''...done.
New software image installed in flash:/ap3g2-k9w8-mx.153-3.JA
Configuring system to use
n
e
wW riimtaigneg. .o.udto nteh.e
eavrecnhti vleo gd otwon lfolaads:h :t/aekveesn t1.5l1o gs e.c.o.n
d
s -
Dynamic port configured for FILE adapter is not working
Hi,
I have a simple dynamic port in an orchestration that writes a file to a file location. Here is the configuration
================
FilePort(Microsoft.XLANGs.BaseTypes.Address) = "FILE://c:\\TestFolder\\Out";
FilePort(Microsoft.XLANGs.BaseTypes.TransportType) = "FILE";
================
When I run this orchestration, the dynamic port does not write the file to the folder, however I does not show any error either. It is always in "Ready to Run" state where the message is "Queued Awaiting".
I tried all sorts of combinations like FILE:// FILE:\\ File: file:// file:\\ etc... and also without the moniker, just c:\.... I get the same problem.
when I use a static port(subscribed to the same message) it works fine. When I use a static port ALONGWITH this dynamic port then both works fine !!! I receive 2 files.
but when I use only dynamic port it does not work!!
Anybody knows how to solve it.
THANKS IN AVANCE
PLEASE HELP
SuryaIt could be becasue you 're not passing in the file name, Try something like this..
SndPort_Dynamic(Microsoft.XLANGs.BaseTypes.Address)=@"file://C:\Test\Try\Out\Test1.xml";
But even when you don't pass the file name, i was expecting the erro to be like:
The FILE send adapter cannot open file C:\TestFolder\Out\ for writing.
Details: The system cannot find the path specified.
But try with File Name and restart the host instance after the change.
Or use somehting like this:
FilePort(Microsoft.XLANGs.BaseTypes.Address)=@"file://C:\Test\Try\Out\\%MessageID%.xml";
FilePort(Microsoft.XLANGs.BaseTypes.TransportType) = "File";
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful. -
Dynamic pdf created in adobe 8 not working in Adobe reader 9
Hi ,
I designed dynamic pdf using Adobe 8 livecylce.
I am able to generate the dynamic pdf with values filled in from the database in Adobe 8 reader,standard and professional versions.
I recently installed Adobe 9 reader and when I try to generate the dynamic pdf , the pdf if generated but the values of the fields comes as null.
Is dynamic pdfs created in 8 not compatable with adobe 9 reader? Do I need to redesign the documents in 9 again ?
Please let me know, I designed a lot of pdf documents using 8 livecycle under the assumption that it is going to work in future versions.
Thanks,
VidyaHi,
I figured our there was a setting to enable/disable Javascript which caused this issue.
I was using javascript in the LC 8 for manipulations in the dynamic pdfs.
I enabled the javascript and now it is working fine.
Thanks,
Vidya
Maybe you are looking for
-
I am using the remote app and I have to enter my iTunes password to purchase a movie, the problem is that some of the keys are missing on my remote app, this is on my iphone and my iPad. I am missing the Parenthasis keys. Both open and close. They ar
-
Javac bug database still being maintained?
After the Oracle acquisition, is the javac bug database still being maintained? I submitted a bug report on 04/20/2010 and received an e-mail response back confirming it was a new bug on 04/22/2010. The e-mail said it would be posted in the external
-
Using Time capsule via internet
if my time capsule is at home, can i have access via internet from my company?
-
Mac HD option greyed out in Disk Utility
Hey, This all started after Mountain Lion, which slowed down my MacBook a lot. I tried to do a clean install and reformat my HD, and doing so it removed the partition already on it. When I went to restore the HD, every option is greyed out except for
-
Importing music from cassettes
Is there a way to get music from cassettes into iTunes? I don't have a sophisticated stereo setup, only a boombox with a headphone out jack, but I'd be willing to buy something, if necessary. I've gotten most of my CD's transferred (and synced with m