APs not joining WLC
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 blocked
Okay 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
Similar Messages
-
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 **** -
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 -
3702i AP's not Joining WLC - Layer 3 discovery request not received on management VLAN
Hi Guys,
This is a follow up post to this thread: https://supportforums.cisco.com/discussion/12400481/3702i-not-joint-2504
Have been playing around with my AP's and made sure the time is correct on all the devices ( WLC and Switch). I have also moved the AP's to the same Vlan as the management IP of the WLC.
if I move the AP's to the same Vlan as the WLC they join and are happy, as soon as I move them to a different Vlan they cant join and there time goes back to the default plus they do not seem to save the WLC details to flash but still remember the test names I give them.
it appears that option 43 is working fine as I can see it look for the WLC IP and I have done some trouble shooting on the WLC and it looks like it see's the AP but doesn't except it.
please see below for the boot up of the AP and the WLC logs:
AP
IIOS Bootloader - Starting system.
*** deleted for breverity *****
Loading "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-mx.153-3.JA1"...#########################
File "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-mx.153-3.JA1" uncompressed and installed, entry point: 0x2003000
executing...
Secondary Bootloader - Starting system.
Montserrat Board
*** deleted for breverity *****
Boot CMD: 'boot flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1;flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1'
Loading "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1"...###############################################
File "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1" uncompressed and installed, entry point: 0x1003000
executing...
*** deleted for breverity *****
cisco AIR-CAP3702I-Z-K9 (PowerPC) processor (revision A0) with 376810K/134656K bytes of memory.
Processor board ID FGL1838X4T1
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.0.110.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: F4:4E:05:B7:1E:84
Part Number : 73-15243-01
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC18343WPR
Top Assembly Part Number : 068-05054-03
Top Assembly Serial Number : FGL1838X4T1
Top Revision Number : A0
Product/Model Number : AIR-CAP3702I-Z-K9
% Please define a domain-name first.
Press RETURN to get started!
*Mar 1 00:00:19.295: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed (15)
*Mar 1 00:00:19.755: Registering HW DTLS
*Mar 1 00:00:19.763: APAVC: Initial WLAN Buffers Given to System is 2500
*Mar 1 00:00:19.815: APAVC: WlanPAKs 42878 RadioPaks 42270
*Mar 1 00:00:22.127: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:26.055: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0 (4)
*Mar 1 00:00:26.167: Loading Power Tables from ram:/Q2.bin. Class = A
*Mar 1 00:00:26.167: record size of 3ss: 1168 read_ptr: 4F9698E
*Mar 1 00:00:31.207: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1 (4)
*Mar 1 00:00:31.251: Loading Power Tables from ram:/Q5.bin. Class = Z
*Mar 1 00:00:31.251: record size of vht: 2904 read_ptr: 4F9698E
*Mar 1 00:00:31.407: Wait until the stile protocol list is initialized.
*Mar 1 00:00:32.651: Start STILE Activation
*Mar 1 00:00:34.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
*Mar 1 00:00:35.447: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C3700 Software (AP3G2-K9W8-M), Version 15.3(3)JA1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 19-Dec-14 11:20 by prod_rel_team
*Mar 1 00:00:35.447: %SNMP-5-COLDSTART: SNMP agent on host Test_1 is undergoing a cold start
*Mar 1 00:00:36.563: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:37.787: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to uplwapp_crypto_init: MIC Present and Parsed Successfully
*Mar 1 00:00:37.939: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:37.939: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:38.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:38.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:47.567: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:00:48.567: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Mar 1 00:00:50.431: %SOAP_FIPS-2-SELF_TEST_HW_SUCCESS: HW crypto FIPS self test passed (2-16)
*Mar 1 00:00:50.431: DPAA Initialization Complete
*Mar 1 00:00:50.431: %SYS-3-HARIKARI: Process DPAA INIT top-level routine exited
*Mar 1 00:00:51.431: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:53.435: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Mar 1 00:00:53.867: Currently running a Release Image
*Mar 1 00:00:54.287: Incorrect certificate in SHA2 PB !
*Mar 1 00:00:54.287: Using SHA-1 signed certificate for image signing validation.
*Mar 1 00:00:54.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:59.787: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.2, mask 255.255.255.0, hostname Test_1
*Mar 1 00:01:02.707: APAVC: Succeeded to activate all the STILE protocols.
*Mar 1 00:01:02.707: APAVC: Registering with CFT
*Mar 1 00:01:02.707: APAVC: CFT registration of delete callback succeeded
*Mar 1 00:01:02.707: APAVC: Reattaching Original Buffer pool for system use
*Mar 1 00:01:02.707: Pool-ReAtach: paks 42878 radio42270
%Default route without gateway, if not a point-to-point interface, may impact performance
*Mar 1 00:01:10.103: AP image integrity check PASSED
*Mar 1 00:01:10.187: Incorrect certificate in SHA2 PB !
*Mar 1 00:01:10.203: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:01:10.203: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:01:11.591: %CDP_PD-4-POWER_OK: 15.4 W power - NEGOTIATED inline power source
*Mar 1 00:01:12.691: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:01:13.691: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:01:13.947: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:01:14.947: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:01:20.211: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 port 514 CLI Request Triggered
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:01:31.215: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained through DHCP
*Mar 1 00:02:11.599: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:02:11.603: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 1 00:02:11.611: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:02:12.603: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:02:12.639: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:02:12.647: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Mar 1 00:02:12.655: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:02:13.639: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:02:13.647: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:02:13.699: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:02:14.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
Not in Bound state.
*Mar 1 00:02:44.719: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 00:02:49.839: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.3, mask 255.255.255.0, hostname Test_1
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:02:55.719: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained through DHCP
Not in Bound state.
*Mar 1 00:03:59.219: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 00:04:04.343: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.4, mask 255.255.255.0, hostname Test_1
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:04:10.223: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained through DHCP
WLC:
isco Controller) >show time
Time............................................. Tue Jan 27 17:44:47 2015
Timezone delta................................... 0:0
Timezone location................................ (GMT +8:00) HongKong, Bejing, Chongquing
NTP Servers
NTP Polling Interval......................... 3600
Index NTP Key Index NTP Server NTP Msg Auth Status
1 0 150.101.176.226 AUTH DISABLED
(Cisco Controller) >show ap join stats summary
Incorrect input! Use 'show ap join stats summary [all/<ap-mac>]'
(Cisco Controller) >show ap join stats summary all
Number of APs.............................................. 2
Base Mac AP EthernetMac AP Name IP Address Status
f4:4e:05:aa:a6:a0 f4:4e:05:94:c3:98 APf44e.0594.c398 10.1.1.22 Joined
f4:4e:05:b6:ce:f0 N A Test_1 10.1.20.7 Not Joined
(Cisco Controller) >show ap join stats detailed f4:4e:05:b6:ce:f0
Sync phase statistics
- Time at sync request received............................ Not applicable
- Time at sync completed................................... Not applicable
Discovery phase statistics
- Discovery requests received.............................. 45
- Successful discovery responses sent...................... 21
- Unsuccessful discovery request processing................ 24
- Reason for last unsuccessful discovery attempt........... Layer 3 discovery request not received on management VLAN
- Time at last successful discovery attempt................ Jan 27 17:45:49.705
- Time at last unsuccessful discovery attempt.............. Jan 27 17:45:49.705
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......................... Lwapp discovery request rejected
- Reason for error that occurred last...................... Layer 3 discovery request not received on management VLAN
- Time at which the last join error occurred............... Jan 27 17:45:49.705
AP disconnect details
- Reason for last AP connection failure.................... Not applicable
Ethernet Mac : 00:00:00:00:00:00 Ip Address : 10.1.20.7
(Cisco Controller) >show interface summary
Number of Interfaces.......................... 4
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
ap LAG 20 10.1.20.231 Dynamic No No
guest LAG 30 10.1.30.231 Dynamic No No
management LAG 10 10.1.1.231 Static Yes No
virtual N/A N/A 1.1.1.1 Static No No
SWITCH
witch#show run
Building configuration...
*** deleted for breverity *****
no aaa new-model
clock timezone AWST 8
system mtu routing 1500
ip routing
ip dhcp pool WAP_Pool
network 10.1.20.0 255.255.255.0
default-router 10.1.20.1
option 43 hex f104.0a01.01e7
ip dhcp pool Clients
network 10.1.30.0 255.255.255.0
default-router 10.1.30.1
dns-server 203.0.178.191
ip dhcp pool test
network 10.1.1.0 255.255.255.0
default-router 10.1.1.1
crypto pki trustpoint TP-self-signed-4082587776
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-4082587776
revocation-check none
rsakeypair TP-self-signed-4082587776
*** deleted for breverity *****
*** deleted for breverity ***** !
interface FastEthernet0/3
description *** WLC ****
switchport trunk encapsulation dot1q
switchport mode trunk
interface FastEthernet0/4
description **** AP *****
switchport access vlan 20
switchport mode access
spanning-tree portfast
interface FastEthernet0/5
description **** AP ****
switchport access vlan 20
switchport mode access
spanning-tree portfast
interface FastEthernet0/6
i*** deleted for breverity ***** !
interface Vlan10
description *** Managment ***
ip address 10.1.1.230 255.255.255.0
interface Vlan20
description *** WIRELESS APS ***
ip address 10.1.20.1 255.255.255.0
interface Vlan30
ip address 10.1.30.1 255.255.255.0
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.1.1
ip http server
ip http secure-server
ip sla enable reaction-alerts
l*** deleted for breverity *****
ntp clock-period 36028827
ntp source FastEthernet0/1
ntp server 121.0.0.42
ntp server 202.127.210.37
end
I have also placed a Device in Vlan 20 and it is able to ping the WLC and the WLC can ping it s routing is working.
ThanksHey Scott,
I gave that a shot and still no luck, log's from AP boot up:
IIOS Bootloader - Starting system.
flash is writable
Tide XL MB - 40MB of flash
Xmodem file system is available.
flashfs[0]: 67 files, 9 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 41158656
flashfs[0]: Bytes used: 20894208
flashfs[0]: Bytes available: 20264448
flashfs[0]: flashfs fsck took 20 seconds.
Base Ethernet MAC address: f4:4e:05:b7:1e:84
Ethernet speed is 100 Mb - FULL Duplex
Loading "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-mx.153-3.JA1"...#########################
File "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-mx.153-3.JA1" uncompressed and installed, entry point: 0x2003000
executing...
Secondary Bootloader - Starting system.
Montserrat Board
40MB format
Tide XL MB - 40MB of flash
Xmodem file system is available.
flashfs[0]: 67 files, 9 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 41158656
flashfs[0]: Bytes used: 20894208
flashfs[0]: Bytes available: 20264448
flashfs[0]: flashfs fsck took 21 seconds.
flashfs[1]: 0 files, 1 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 12257280
flashfs[1]: Bytes used: 1024
flashfs[1]: Bytes available: 12256256
flashfs[1]: flashfs fsck took 1 seconds.
Base Ethernet MAC address: f4:4e:05:b7:1e:84
Boot CMD: 'boot flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1;flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1'
Loading "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1"...###############################################
File "flash:/ap3g2-k9w8-mx.153-3.JA1/ap3g2-k9w8-xx.153-3.JA1" uncompressed and installed, entry point: 0x1003000
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, C3700 Software (AP3G2-K9W8-M), Version 15.3(3)JA1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 19-Dec-14 11:20 by prod_rel_team
Montserrat Board
40MB format
Tide XL MB - 40MB of flash
Initializing flashfs...
flashfs[2]: 67 files, 9 directories
flashfs[2]: 0 orphaned files, 0 orphaned directories
flashfs[2]: Total bytes: 40900608
flashfs[2]: Bytes used: 20894208
flashfs[2]: Bytes available: 20006400
flashfs[2]: flashfs fsck took 14 seconds.
flashfs[2]: 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
Copy in progress...CCCC
Copy in progress...CC
Copy in progress...CCCCC
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 650 entries (20 legacy/224 11n/406 11ac)
POWER TABLE FILENAME = ram:/Q2.bin
Radio1 present 8864 8000 0 80000000 80100000 4
POWER TABLE FILENAME = ram:/Q5.bin
Radio2 not present 0 0 0 0 0 8
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco AIR-CAP3702I-Z-K9 (PowerPC) processor (revision A0) with 376810K/134656K bytes of memory.
Processor board ID FGL1838X4T1
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 8.0.110.0
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: F4:4E:05:B7:1E:84
Part Number : 73-15243-01
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC18343WPR
Top Assembly Part Number : 068-05054-03
Top Assembly Serial Number : FGL1838X4T1
Top Revision Number : A0
Product/Model Number : AIR-CAP3702I-Z-K9
% Please define a domain-name first.
Press RETURN to get started!
*Mar 1 00:00:19.295: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed (15)
*Mar 1 00:00:19.755: Registering HW DTLS
*Mar 1 00:00:19.763: APAVC: Initial WLAN Buffers Given to System is 2500
*Mar 1 00:00:19.815: APAVC: WlanPAKs 42878 RadioPaks 42270
*Mar 1 00:00:22.127: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:26.055: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0 (4)
*Mar 1 00:00:26.167: Loading Power Tables from ram:/Q2.bin. Class = A
*Mar 1 00:00:26.167: record size of 3ss: 1168 read_ptr: 4F9698E
*Mar 1 00:00:31.207: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1 (4)
*Mar 1 00:00:31.251: Loading Power Tables from ram:/Q5.bin. Class = Z
*Mar 1 00:00:31.251: record size of vht: 2904 read_ptr: 4F9698E
*Mar 1 00:00:31.407: Wait until the stile protocol list is initialized.
*Mar 1 00:00:32.651: Start STILE Activation
*Mar 1 00:00:34.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
*Mar 1 00:00:35.447: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C3700 Software (AP3G2-K9W8-M), Version 15.3(3)JA1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Fri 19-Dec-14 11:20 by prod_rel_team
*Mar 1 00:00:35.447: %SNMP-5-COLDSTART: SNMP agent on host Test_1 is undergoing a cold start
*Mar 1 00:00:36.563: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:37.787: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to uplwapp_crypto_init: MIC Present and Parsed Successfully
*Mar 1 00:00:37.939: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:37.939: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:38.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:38.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:47.567: %LINK-6-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:00:48.567: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
*Mar 1 00:00:50.431: %SOAP_FIPS-2-SELF_TEST_HW_SUCCESS: HW crypto FIPS self test passed (2-16)
*Mar 1 00:00:50.431: DPAA Initialization Complete
*Mar 1 00:00:50.431: %SYS-3-HARIKARI: Process DPAA INIT top-level routine exited
*Mar 1 00:00:51.431: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:53.435: %LINK-6-UPDOWN: Interface BVI1, changed state to up
*Mar 1 00:00:53.867: Currently running a Release Image
*Mar 1 00:00:54.287: Incorrect certificate in SHA2 PB !
*Mar 1 00:00:54.287: Using SHA-1 signed certificate for image signing validation.
*Mar 1 00:00:54.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:59.787: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.2, mask 255.255.255.0, hostname Test_1
*Mar 1 00:01:02.707: APAVC: Succeeded to activate all the STILE protocols.
*Mar 1 00:01:02.707: APAVC: Registering with CFT
*Mar 1 00:01:02.707: APAVC: CFT registration of delete callback succeeded
*Mar 1 00:01:02.707: APAVC: Reattaching Original Buffer pool for system use
*Mar 1 00:01:02.707: Pool-ReAtach: paks 42878 radio42270
%Default route without gateway, if not a point-to-point interface, may impact performance
*Mar 1 00:01:10.103: AP image integrity check PASSED
*Mar 1 00:01:10.187: Incorrect certificate in SHA2 PB !
*Mar 1 00:01:10.203: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:01:10.203: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:01:11.591: %CDP_PD-4-POWER_OK: 15.4 W power - NEGOTIATED inline power source
*Mar 1 00:01:12.691: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:01:13.691: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:01:13.947: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:01:14.947: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Mar 1 00:01:20.211: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 port 514 CLI Request Triggered
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:01:31.215: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained through DHCP
*Mar 1 00:02:11.599: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:02:11.603: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 1 00:02:11.611: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:02:12.603: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:02:12.639: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:02:12.647: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Mar 1 00:02:12.655: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:02:13.639: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:02:13.647: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:02:13.699: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:02:14.699: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
Not in Bound state.
*Mar 1 00:02:44.719: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 00:02:49.839: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.3, mask 255.255.255.0, hostname Test_1
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:02:55.719: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained through DHCP
Not in Bound state.
*Mar 1 00:03:59.219: %CAPWAP-3-DHCP_RENEW: Could not discover WLC. Either IP address is not assigned or assigned IP is wrong. Renewing DHCP IP.
*Mar 1 00:04:04.343: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.1.20.4, mask 255.255.255.0, hostname Test_1
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:04:10.223: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.1.1.231 obtained through DHCP -
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
MatthewHmmm...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 -
Hi all
my customer has a 2504 WLC, and has problems to join APs (There are no aps joined to the controller at this moment).
What are the Bold lines tell me?
in the debug I see the following:
*spamApTask0: Oct 10 09:20:06.019: 58:f3:9c:78:d1:10 Discovery Request from 10.37.24.116:41508
*spamApTask0: Oct 10 09:20:06.019: 58:f3:9c:78:d1:10 ApModel: AIR-CAP3702I-N-K9
*spamApTask0: Oct 10 09:20:06.019: 58:f3:9c:78:d1:10 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 50, 0
*spamApTask0: Oct 10 09:20:06.019: apModel: AIR-CAP3702I-N-K9
*spamApTask0: Oct 10 09:20:06.020: apType = 38 apModel: AIR-CAP3702I-N-K9
*spamApTask0: Oct 10 09:20:06.020: Unknown AP type. Using Controller Version!!!
*spamApTask0: Oct 10 09:20:06.020: 58:f3:9c:78:d1:10 Discovery Response sent to 10.37.24.116 port 41508
*spamApTask0: Oct 10 09:20:06.020: 58:f3:9c:78:d1:10 Discovery Response sent to 10.37.24.116:41508
*spamApTask0: Oct 10 09:20:06.021: 58:f3:9c:78:d1:10 Discovery Request from 10.37.24.116:41508
*spamApTask0: Oct 10 09:20:06.021: 58:f3:9c:78:d1:10 ApModel: AIR-CAP3702I-N-K9
*spamApTask0: Oct 10 09:20:06.021: 58:f3:9c:78:d1:10 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 50, 0
*spamApTask0: Oct 10 09:20:06.021: apModel: AIR-CAP3702I-N-K9
*spamApTask0: Oct 10 09:20:06.021: apType = 38 apModel: AIR-CAP3702I-N-K9
*spamApTask0: Oct 10 09:20:06.021: Unknown AP type. Using Controller Version!!!
*spamApTask0: Oct 10 09:20:06.021: 58:f3:9c:78:d1:10 Discovery Response sent to 10.37.24.116 port 41508
*spamApTask0: Oct 10 09:20:06.021: 58:f3:9c:78:d1:10 Discovery Response sent to 10.37.24.116:41508
*spamApTask0: Oct 10 09:20:16.031: 58:f3:9c:7a:22:30 DTLS connection not found, creating new connection for 10:37:24:116 (41508) 10)
*spamApTask0: Oct 10 09:20:16.498: acDtlsPlumbControlPlaneKeys: lrad:10.37.24.116(41508) mwar:10.37.24.11(5246)
*spamApTask0: Oct 10 09:20:16.498: 58:f3:9c:7a:22:30 Allocated index from main list, Index: 55
*spamApTask0: Oct 10 09:20:16.498: 58:f3:9c:7a:22:30 Using CipherSuite AES128-SHA
*spamApTask0: Oct 10 09:20:16.499: 58:f3:9c:7a:22:30 DTLS keys for Control Plane are plumbed successfully for AP 10.37.24.116. Inde6
*spamApTask1: Oct 10 09:20:16.499: 58:f3:9c:7a:22:30 DTLS Session established server (10.37.24.11:5246), client (10.37.24.116:41508)
*spamApTask1: Oct 10 09:20:16.499: 58:f3:9c:7a:22:30 Starting wait join timer for AP: 10.37.24.116:41508
*spamApTask0: Oct 10 09:20:16.517: 58:f3:9c:78:d1:10 Join Request from 10.37.24.116:41508
*spamApTask0: Oct 10 09:20:16.517: 58:f3:9c:7a:22:30 Deleting AP entry 10.37.24.116:41508 from temporary database.
*spamApTask0: Oct 10 09:20:16.518: 58:f3:9c:7a:22:30 spamProcessJoinRequest : RAP, Check MAC filter
*spamApTask0: Oct 10 09:20:16.518: 58:f3:9c:78:d1:10 In AAA state 'Idle' for AP 58:f3:9c:78:d1:10
*spamApTask0: Oct 10 09:20:16.518: 58:f3:9c:7a:22:30 Mesh AP username 58f39c7a2230.
*spamApTask0: Oct 10 09:20:16.518: 58:f3:9c:78:d1:10 Join Request failed!
*spamApTask0: Oct 10 09:20:16.518: 58:f3:9c:78:d1:10 State machine handler: Failed to process msg type = 3 state = 0 from 10.37.248
*spamApTask0: Oct 10 09:20:16.518: 58:f3:9c:7a:22:30 Failed to parse CAPWAP packet from 10.37.24.116:41508
*spamApTask0: Oct 10 09:20:16.519: XóxÑ
*spamApTask0: Oct 10 09:20:16.519: 58:f3:9c:78:d1:10 Finding DTLS connection to delete for AP (10:37:24:116/41508)
*spamApTask0: Oct 10 09:20:16.519: 58:f3:9c:78:d1:10 Disconnecting DTLS Capwap-Ctrl session 0x179437d8 for AP (10:37:24:116/41508)
*spamApTask0: Oct 10 09:20:16.519: 58:f3:9c:78:d1:10 CAPWAP State: Dtls tear down
*spamApTask0: Oct 10 09:20:16.520: acDtlsPlumbControlPlaneKeys: lrad:10.37.24.116(41508) mwar:10.37.24.11(5246)
*spamApTask0: Oct 10 09:20:16.520: 58:f3:9c:78:d1:10 DTLS keys for Control Plane deleted successfully for AP 10.37.24.116
*spamApTask0: Oct 10 09:20:16.526: 58:f3:9c:78:d1:10 DTLS connection closed event receivedserver (10.37.24.11/5246) client (10.37.2)
*spamApTask0: Oct 10 09:20:16.526: 58:f3:9c:78:d1:10Hi all, the AP was in Mesh (Bridge) mode and could not connect to the controller
Ok, how to find out that a AP is in bridge mode, without a join (No Access to the AP).
go to monitor > statistics > AP Join
you will see the AP here that tries to connect (clear the list before)
if the ethernet MAC Address is the same as the Base radio MAC, than the AP is in bridge mode.
normally ( in local mode) the Ethernet MAC Address reflects the APname
To allow the AP to join, add in the Authorization list the APName mac Address!
See: http://supertekboy.com/2014/01/13/cisco-lightweight-access-point-will-not-join-to-a-wireless-lan-controller/
The case is solved now. -
AP not joining WLC b/c of DHCP.
This is the first time that I've dealt with a WLC, so I'm trying to do a real simple setup. I have a WLC 2106 and a few LAP 1141N's. I'm trying to set them up on a single VLAN, no RADIUS server, and I want my router to handle DHCP (not the WLC). Here's the info I setup the WLC with:
Welcome to the Cisco Wizard Configuration Tool
Use the '-' character to backup
System Name [Cisco_94:40:40]: WLC
Enter Administrative User Name (24 characters max): cisco
Enter Administrative Password (24 characters max): *****
Management Interface IP Address: 192.168.3.5
Management Interface Netmask: 255.255.255.0
Management Interface Default Router: 192.168.3.1
Management Interface VLAN Identifier (0 = untagged): 0
Management Interface Port Num [1 to 4]: 1
Management Interface DHCP Server IP Address: 192.168.3.1
AP Manager Interface IP Address: 192.168.3.6
AP-Manager is on Management subnet, using same values
AP Manager Interface DHCP Server (192.168.3.1):
Virtual Gateway IP Address: 1.1.1.1
Mobility/RF Group Name: GroupRF
Network Name (SSID): Test
Allow Static IP Addresses [YES][no]: yes
Configure a RADIUS Server now? [YES][no]: no
Warning! The default WLAN security policy requires a RADIUS server.
Please see documentation for more details.
Enter Country Code (enter 'help' for a list of countries) [US]: US
Enable 802.11b Network [YES][no]: Yes
Enable 802.11a Network [YES][no]: no
Enable 802.11g Network [YES][no]: yes
Enable Auto-RF [YES][no]: yes
Configuration saved!
Resetting system with new configuration...
When I login to the web interface of the WLC (https://192.168.3.5) it doesn't show any AP's as joining even though I have one plugged in to the WLC. I console'd into the AP and this is the error that keeps on repeating:
*Mar 1 00:51:45.962: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does
not have an Ip !!
Am I missing something? I already checked the WLC, and the date/time is setup correctly. And I know my router (at 192.168.3.1) is handing out DHCP. Everything is on the same subnet so I don't understand why I'm having such a hard time with this. I've tried my hardest searching online but haven't found anything. Any help would REALLY be appreciated. Thank you very much.
P.S. If you have any other questions please feel free to ask.The answer is that LWAPP / CAPWAP APs need to be connected to an access port on a swtich (configured with the proper VLAN) as they do nothing more than pass the traffic to the WLC through the LWAPP / CAPWAP tunnel. The WLC ethernet ports are configured as trunks and can not be change. This is because the WLC is where all the VLAN tagging takes place.
Hope that helps,
Scott
Please rate this post if you found it helpful. -
Hello
I am running WLC4404 image 6.0 the latest one. the AP is not joining the controller and it is saying invalid license in configuration request.
This is a boot of one of the access point:
Dec 11 11:05:59.025: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 11 11:05:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.140.248 peer_port: 5246
*Dec 11 11:05:59.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Dec 11 11:06:02.862: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.140.248 peer_port: 5246
*Dec 11 11:06:02.863: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.140.248
*Dec 11 11:06:02.863: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Dec 11 11:06:03.619: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Dec 11 11:06:03.764: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.140.248
*Dec 11 11:06:03.764: %DTLS-5-PEER_DISCONNECT: Peer 172.16.140.248 has closed connection.
*Dec 11 11:06:03.764: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 172.16.140.248:5246
*Dec 11 11:06:03.803: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Dec 11 11:06:03.803: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Dec 11 11:06:13.824: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Dec 11 11:06:14.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.140.248 peer_port: 5246
*Dec 11 11:06:14.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Dec 11 11:06:18.644: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.140.248 peer_port: 5246
*Dec 11 11:06:18.644: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.140.248
*Dec 11 11:06:18.644: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Dec 11 11:06:19.587: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Dec 11 11:06:19.722: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.140.248
*Dec 11 11:06:19.722: %DTLS-5-PEER_DISCONNECT: Peer 172.16.140.248 has closed connection.
*Dec 11 11:06:19.722: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 172.16.140.248:5246
*Dec 11 11:06:19.761: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Dec 11 11:06:19.761: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
Any advise,
ElieHi Elie,
As it looks like the AP is closing the DTLS connection:
~
*Dec 11 11:06:03.764: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.140.248
~
I would also suggest to connect to the AP through the serial console and collect the output there during the boot/join process.
In regard to the the WLC debugs I would also add the "debug pm pki enable", so to further troubleshoot certificate related issues.
I hope this helps.
Regards,
Federico -
Hello,
I am currently having issue relating to my AP not joining the WLC. Have made the WLC the internal DHCP server and the AP has picked an IP Address but the below is what i get from the AP:
*Feb 14 22:48:56.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Feb 14 22:48:56.759: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Feb 14 22:48:56.783: status of voice_diag_test from WLC is false
*Feb 14 22:49:12.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:12.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Feb 14 22:49:12.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:12.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Feb 14 22:49:12.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Feb 14 22:49:17.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Feb 14 22:49:17.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2
*Feb 14 22:49:17.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.
*Feb 14 22:49:17.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246
*Feb 14 22:49:12.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:12.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Feb 14 22:49:12.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:12.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Feb 14 22:49:12.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
% CDP is not supported on this interface, or for this encapsulation
*Feb 14 22:49:17.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Feb 14 22:49:17.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2
*Feb 14 22:49:17.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.
*Feb 14 22:49:17.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246
*Feb 14 22:49:17.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Feb 14 22:49:17.707: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Feb 14 22:49:17.759: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Feb 14 22:49:17.783: status of voice_diag_test from WLC is false
*Feb 14 22:49:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Feb 14 22:49:34.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:34.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Feb 14 22:49:34.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Feb 14 22:49:39.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Feb 14 22:49:39.663: %DTLS-5-ALERT: Received WARNING : Close notify alert from 192.168.1.2
*Feb 14 22:49:39.663: %DTLS-5-PEER_DISCONNECT: Peer 192.168.1.2 has closed connection.
*Feb 14 22:49:39.663: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 192.168.1.2:5246
*Feb 14 22:49:34.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:34.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Feb 14 22:49:34.663: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.1.2 peer_port: 5246
*Feb 14 22:49:34.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2
*Feb 14 22:49:34.663: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Feb 14 22:49:38.591: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Feb 14 22:49:38.591: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Feb 14 22:49:38.591: %MESH-6-LINK_UPDOWN: Mesh station f029.29c2.effc link Down
*Feb 14 22:49:39.663: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.1.2Platform: AIR-CT2504-K9, Version :
Manufacturer's Name: Cisco Systems Inc. Product Name: Cisco Controller Product Version: 7.0.220.0 RTOS Version: Erro Bootloader Version: 1.0.18 Build Type: DATA + WPS
Platform: cisco AIR-CAP1552E-E-K9 Version :
Cisco IOS Software, C1550 Software (C1520-K9W8-M), Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
Proceeding with system init
Proceeding to unmask interrupts
Initializing flashfs...
flashfs[1]: 22 files, 3 directories
flashfs[1]: 0 orphaned files, 0 orphaned directories
flashfs[1]: Total bytes: 31610880
flashfs[1]: Bytes used: 6631936
flashfs[1]: Bytes available: 24978944
flashfs[1]: flashfs fsck took 5 seconds.
flashfs[1]: Initialization complete.
flashfs[2]: 0 files, 1 directories
flashfs[2]: 0 orphaned files, 0 orphaned directories
flashfs[2]: Total bytes: 5806080
flashfs[2]: Bytes used: 1024
flashfs[2]: Bytes available: 5805056
flashfs[2]: flashfs fsck took 1 seconds.
flashfs[2]: Initialization complete....done Initializing flashfs.
Warning: the compile-time code checksum does not appear to be present.
Radio0 present 8364B 8000 A8020000 0 A8030000 30
Radio1 present 8364B 8000 B8020000 0 B8030000 13
Radio2 not present 0 0 0 0 0 11
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:/c1520-rcvk9w8-mx/info (No such file or directory)cisco AIR-CAP1552E-E-K9 (PowerPC 8349) processor (revision A0) with 49142K/16384K bytes of memory.
Processor board ID FCZ1718H01Y
PowerPC 8349 CPU at 533Mhz, revision number 0x0031
Last reset from power loss
LWAPP image version 7.0.220.0
4 Gigabit Ethernet interfaces
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: F0:29:29:C2:EF:E0
Part Number : 73-13538-02
PCA Assembly Number : 800-31224-01
PCA Revision Number : 03
PCB Serial Number : FOC1705241P
Top Assembly Part Number : 800-34853-05
Top Assembly Serial Number : FCZ1718H01Y
Top Revision Number : A0
Product/Model Number : AIR-CAP1552E-E-K9
% Please define a domain-name first.
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
Press RETURN to get started!
*Mar 1 00:00:07.307: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:07.723: m8349_ether_enable: MACCFG1 sync timeout
*Mar 1 00:00:09.819: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:09.819: %LINK-3-UPDOWN: Interface Ethernet4, changed state to up
*Mar 1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet1, changed state to up
*Mar 1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to up
*Mar 1 00:00:09.819: %LINK-3-UPDOWN: Interface GigabitEthernet3, changed state to up
*Mar 1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
*Mar 1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to down
*Mar 1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down
*Mar 1 00:00:11.375: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3, changed state to down
*Mar 1 00:00:11.963: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:12.039: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 1024 messages)
*Mar 1 00:00:12.051: AP identified to be in Fenway/Huck Jr/1240/1130 configuration
*Mar 1 00:00:12.055: status of voice_diag_test from WLC is false
*Mar 1 00:00:14.079: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1550 Software (C1520-K9W8-M), Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Tue 18-Oct-11 15:13 by prod_rel_team
*Mar 1 00:00:14.079: %SNMP-5-COLDSTART: SNMP agent on host APf029.29c2.efe0 is undergoing a cold start
*Mar 1 00:00:14.143: %MESH-6-BVI_CREATED: Mesh BVI1 interface created
*Mar 1 00:00:14.163: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:14.163: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:15.163: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:15.163: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:16.143: %LINK-3-UPDOWN: Interface BVI1, changed state to down
*Mar 1 00:00:17.139: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitE
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)thernet0, changed state to down
*Mar 1 00:00:17.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to down
*Mar 1 00:00:17.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down
*Mar 1 00:00:17.143: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3, changed state to down
*Mar 1 00:00:18.579: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet4, changed state to up
*Mar 1 00:00:20.723: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:32.743: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 1 00:00:32.795: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 1 00:00:32.959: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:33.107: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:00:33.307: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Mar 1 00:00:46.383: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C2960-24PC-S (189c.5d95.2d18)
Username:
*Mar 1 00:01:27.119: %MESH-6-ADJACENCY_STATE_MACHINE_STARTED: Mesh adjacency state machine started
Username:
*Mar 1 00:01:32.163: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 1 00:01:34.119: %LINK-3-UPDOWN: Interface BVI1, changed state to up
*Mar 1 00:01:35.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:01:37.207: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
% CDP is not supported on this interface, or for this encapsulation
*Mar 1 00:01:40.887: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 1 00:01:40.907: status of voice_diag_test from WLC is false
*Mar 1 00:01:46.387: %CDP_PD-2-POWER_LOW: All radios disabled - NEGOTIATED WS-C2960-24PC-S (189c.5d95.2d18)
Regards,
Obinna Samuel -
I am deploying WLC 4402 with LWAP 1131 but AP fail to join the WLC .The resone that I dont have DNS server.The error message in the AP is :
AP001d.451f.8582>
*Mar 1 00:00:38.005: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned D
HCP address 172.26.5.12, mask 255.255.255.0, hostname AP001d.451f.8582
Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
*Mar 1 00:00:49.371: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve
I tried to configure the Controller address in LAP but I fail ,The error when I tried to configure AP is below:
AP001d.451f.8582#lwapp ap controller ip address 172.26.5.10
ERROR!!! Command is disabled.
my question is :
is it possible to make LAP join WLC with out DNS,if yes how ?Hi Yhab,
There are other ways besides DNS to help in the AP and WLC Discovery process. Have a look in this good doc;
Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC)
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml#topic2
For the Static entry problem;
If this AP was ever registered you can use this command from the LAP CLI to clear the LWAPP configuration on the LAP:
clear lwapp private-config
This allows you to use the AP LWAPP static configuration commands again.
Here is an example:
Enable (enter password)
AP1240#clear lwapp private-config
AP1240#lwapp ap hostname AP1240
AP1240#lwapp ap ip address 10.77.244.199 255.255.255.224
AP1240#lwapp ap ip default-gateway 10.77.244.220
AP1240#lwapp ap controller ip address 172.16.1.50
Note: You cannot use the clear lwapp private-config command when the LAP is registered with the controller.
http://www.cisco.com/en/US/products/hw/wireless/ps430/products_tech_note09186a00808e2d27.shtml#t2
Hope this helps!
Rob -
Hello All,
I am trying to deploy several AIR-CAP3502E-E-K9 access points from a cisco 5508 wire lan contoller running ver 7 code. However iam having difficulty regiserting the access points with the WLC. The wlc is connect to a 3650 switch, and each access point is connected to a 2960 switch.
Problem Solved. A bad update was not allowing the access points to get their correct firmware.You need to provide what Leo stated, that would help a lot. Anyways you can't telnet or ssh into a capwap AP if it has not joined the WLC. So that being said, provide the info Leo requested and then console into the ap and provide use with output from the console. Make sure you reboot the AP and then start capturing the output for around 5 minutes.
Sent from Cisco Technical Support iPad App -
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 -
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. -
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 ? -
Hi , i have the problem that one AP in one location doesnt join the WLC.
i checked DHCP scope options , time on WLC and AP etc.
I also check all this issues:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml
I only see an DTLS error
debug AP
*Oct 24 08:23:02.307: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Oct 24 08:23:02.332: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Oct 24 08:23:10.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.X.X:X peer_port: 5246
*Oct 24 08:23:10.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Oct 24 08:23:40.198: DTLS_CLIENT_ERROR: ../dtls/dtls_connection_db.c:2017 Max retransmission count reached!
*Oct 24 08:23:40.198: %DTLS-3-HANDSHAKE_RETRANSMIT: Max retransmit count for 10.X.X:X is reached.
*Oct 24 08:24:10.051: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.X.X.X:5246
debug:
*spamReceiveTask: Oct 24 08:54:53.308: 0c:85:25:30:14:20 DTLS connection closed event receivedserver (10.X:X:X/5246) client (10.X:X:X/4270)
*spamReceiveTask: Oct 24 08:54:53.308: 0c:85:25:30:14:20 No entry exists for AP (10.X:X:X/4270)
*spamReceiveTask: Oct 24 08:54:53.308: 0c:85:25:30:14:20 No AP entry exist in temporary database for 10.X:X:X:4270
*spamReceiveTask: Oct 24 08:54:53.443: 0c:85:25:30:14:20 Discovery Request from 10.X:X:X:4271
*spamReceiveTask: Oct 24 08:54:53.443: 0c:85:25:30:14:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =1
*spamReceiveTask: Oct 24 08:54:53.443: 0c:85:25:30:14:20 Discovery Response sent to 10.X:X:X:4271
*spamReceiveTask: Oct 24 08:55:03.378: 0c:85:25:30:14:20 DTLS connection not found, creating new connection for 10.X:X:X (4271) 10.X:X:X (5246)
*spamReceiveTask: Oct 24 08:55:03.378: sshpmGetCID: called to evaluate <cscoDefaultIdCert>
I wanne find out if, for this location it is an provider problem (WAN)
Have someone else such a problem ?
best regardsBut it is only with this location though, that's why I think is related to something in the carrier side, althgouth I can't understand what could it be. Here is what it comes down to:
Debug of a working AP:
*Jan 31 16:36:09.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.143.254.254 peer_port: 5246
*Jan 31 16:36:09.000: DTLS_CLIENT_EVENT_DETAIL: dtls_secret_inc_ref_count: Secret reference count= 2
*Jan 31 16:36:09.000: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_flush_handshake_msgs: Called...
*Jan 31 16:36:09.000: DTLS_CLIENT_EVENT_DETAIL: dtls_secret_delete: Secret not deleted, reference count = 1
*Jan 31 16:36:09.000: DTLS_CLIENT_EVENT_DETAIL: dtls_send_ClientHello: Called...
*Jan 31 16:36:09.000: DTLS_CLIENT_EVENT_DETAIL: dtls_send_handshake_msg: Called...
*Jan 31 16:36:09.000: DTLS_CLIENT_EVENT_DETAIL: dtls_record_send: Called...
*Jan 31 16:36:09.000: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_send: Called...
*Jan 31 16:36:09.187: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x026C9F00
06738EA0: 16FEFF00 00000000 .~......
06738EB0: 00000000 2F030000 23000000 00000000 ..../...#.......
06738EC0: 23FEFF20 0A00DECB 7EAA1234 56789ABC #~. ..^K~*.4Vx.<
06738ED0: 930E45B2 C60AB26E 9F96C225 0F0726E9 ..E2F.2n..B%..&i
06738EE0: AD8A6517 -.e.
*Jan 31 16:36:09.188: DTLS_CLIENT_EVENT: dtls_process_HelloVerifyRequest: Processing...
*Jan 31 16:36:09.188: DTLS_CLIENT_EVENT_DETAIL: dtls_send_ClientHello: Called...
*Jan 31 16:36:09.189: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_flush_handshake_msgs: Called...
*Jan 31 16:36:09.189: DTLS_CLIENT_EVENT_DETAIL: dtls_send_handshake_msg: Called...
*Jan 31 16:36:09.189: DTLS_CLIENT_EVENT_DETAIL: dtls_record_send: Called...
*Jan 31 16:36:09.189: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_send: Called...
*Jan 31 16:36:09.189: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: End of datagram reached.
*Jan 31 16:36:09.261: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x026C9F00
06704AF0: 16FEFF00 .~..
06704B00: 00000000 00000100 52020000 46000100 ........R...F...
06704B10: 00000000 46FEFF51 0A9DBF76 DA0F0B66 ....F~.Q..?vZ..f
06704B20: 72B28A8A A5B29EF1 B66E8A24 FB5539C3 r2..%2.q6n.${U9C
06704B30: 2F267366 2D02AC20 7B40A093 2488AC76 /&sf-., {@ .$.,v
06704B40: D0D694A9 2661230B CBA7A413 E010474D PV.)&a#.K'$.`.GM
06704B50: 0A494E66 EE0BE4EE 002F00 .INfn.dn./.
*Jan 31 16:36:09.262: DTLS_CLIENT_EVENT: dtls_process_ServerHello: Processing...
*Jan 31 16:36:09.262: DTLS_CLIENT_EVENT: dtls_connection_set_cipher: Setting cipher to TLS_RSA_WITH_AES_128_CBC_SHA
*Jan 31 16:36:09.262: DTLS_CLIENT_EVENT_DETAIL: dtls_secret_pki_init: Called...
*Jan 31 16:36:09.262: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Attempting to extract next record....
*Jan 31 16:36:09.262: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x026C9F00
06704B50: 16 FEFF0000 .~...
06704B60: 00000000 000201B4 0B00047F 00020000 .......4........
06704B70: 000001A8 00047C00 04793082 04753082 ...(..|..y0..u0.
06704B80: 035DA003 02010202 0A5021F6 ED000000 .] ......P!vm...
06704B90: 2EB59930 0D06092A 864886F7 0D010105 .5.0...*.H.w....
06704BA0: 05003039 31163014 06035504 0A130D43 ..091.0...U....C
06704BB0: 6973636F 20537973 74656D73 311F301D isco Systems1.0.
06704BC0: 06035504 03131643 6973636F 204D616E ..U....Cisco Man
06704BD0: 75666163 74757269 6E672043 41301E17 ufacturing CA0..
06704BE0: 0D313030 36313131 39323731 315A170D .100611192711Z..
06704BF0: 32303036 31313139 33373131 5A308194 200611193711Z0..
06704C00: 310B3009 06035504 06130255 53311330 1.0...U....US1.0
06704C10: 11060355 0408130A 43616C69 666F726E ...U....Californ
06704C20: 69613111 300F0603 55040713 0853616E ia1.0...U....San
06704C30: 204A6F73 65311630 14060355 040A130D Jose1.0...U....
06704C40: 43697363 6F205379 7374656D 73312330 Cisco Systems1#0
06704C50: 21060355 0403131A 4149522D 43543535 !..U....AIR-CT55
06704C60: 30382D4B 392D3638 65666264 39333833 08-K9-68efbd9383
06704C70: 32303120 301E0609 2A864886 F70D0109 201 0...*.H.w...
06704C80: 01161173 7570706F 72744063 6973636F ...support@cisco
06704C90: 2E636F6D 30820122 300D0609 2A864886 .com0.."0...*.H.
06704CA0: F70D0101 01050003 82010F00 3082010A w...........0...
06704CB0: 02820101 00DE519C EBD5DE04 BBE84810 .....^Q.kU^.;hH.
06704CC0: B796C26A 19B3C0C4 039F5946 8C5BA9D5 [email protected].[)U
06704CD0: 6C3FFD50 E95163DA A4ADB7DB 280198D7 l?}PiQcZ$-7[(..W
06704CE0: E5606E5A FA165D1C FD97E8A7 3259FED7 e`nZz.].}.h'2Y~W
06704CF0: C043DEBC 6653727D D2B514E3 C6ABDCB8 @C^
06704D00: 848C65F2 4A96A5A7 11881F0C 90A3CB03 ..erJ.%'.....#K.
06704D10: 3FA69851 1112E7EF FF173971 ?&.Q..go..9q
*Jan 31 16:36:09.264: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Reassembly required for handshake seq 2. frag_len (424) < length (1151)
*Jan 31 16:36:09.264: DTLS_CLIENT_EVENT_DETAIL: dtls_handshake_fragment_new: Called...
*Jan 31 16:36:09.264: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Not ready to assemble yet.
*Jan 31 16:36:09.264: DTLS_CLIENT_EVENT_DETAIL: dtls_client_process_record: DTLS handshake buffered for reassembly later
*Jan 31 16:36:09.265: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: End of datagram reached.
*Jan 31 16:36:09.266: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x026C9F00
067000F0: 16FEFF00 00000000 00000302 130B0004 .~..............
06700100: 7F000200 01A80002 07198FBE E5CB79E6 .....(.....>eKyf
06700110: 2ED9EF2F 0F66C568 73D72351 54BB111F .Yo/.fEhsW#QT;..
06700120: 40A7B3BD 2294943F 61ADAD6C 54C95FFC @'3="..?a--lTI_|
06700130: 6E0DA143 004C0C1D 200A17DC 0E61D224 n.!C.L.. ..\.aR$
06700140: EF6DDBB9 72DAF726 001AC973 1E228D8D om[9rZw&..Is."..
06700150: A745158B F13D646E 1CCDF808 AEA47A7D 'E..q=dn.Mx..$z}
06700160: 10DBF88A 2FB02F5F 15A71982 BF458124 .[x./0/_.'..?E.$
06700170: 3159A9CD 6EC72B43 D5541C04 291B83F4 1Y)MnG+CUT..)..t
06700180: F6A667D9 6125AB38 74C55671 9CC46CC4 v&gYa%+8tEVq.DlD
06700190: C78146FA B4FB10B5 620E9C03 3FDE0261 G.Fz4{.5b...?^.a
067001A0: 17530203 010001A3 82012130 82011D30 .S.....#..!0...0
067001B0: 0B060355 1D0F0404 030205A0 301D0603 ...U....... 0...
067001C0: 551D0E04 1604148F 93BB23DE B485C5F2 U........;#^4.Er
067001D0: 3553F941 3ED2A81F CD53AA30 1F060355 5SyA>R(.MS*0...U
067001E0: 1D230418 30168014 D0C52226 AB4F4660 .#..0...PE"&+OF`
067001F0: ECAE0591 C7DC5AD1 B047F76C 303F0603 l...G\ZQ0Gwl0?..
06700200: 551D1F04 38303630 34A032A0 30862E68 U...80604 2 0..h
06700210: 7474703A 2F2F7777 772E6369 73636F2E ttp://www.cisco.
06700220: 636F6D2F 73656375 72697479 2F706B69 com/security/pki
06700230: 2F63726C 2F636D63 612E6372 6C304C06 /crl/cmca.crl0L.
06700240: 082B0601 05050701 01044030 3E303C06 .+........@0>0<.
06700250: 082B0601 05050730 02863068 7474703A .+.....0..0http:
06700260: 2F2F7777 772E6369 73636F2E 636F6D2F //www.cisco.com/
06700270: 73656375 72697479 2F706B69 2F636572 security/pki/cer
06700280: 74732F63 6D63612E 63657230 3F06092B ts/cmca.cer0?..+
06700290: 06010401 82371402 04321E30 00490050 .....7...2.0.I.P
067002A0: 00530045 00430049 006E0074 00650072 .S.E.C.I.n.t.e.r
067002B0: 006D0065 00640069 00610074 0065004F .m.e.d.i.a.t.e.O
067002C0: 00660066 006C0069 006E0065 300D0609 .f.f.l.i.n.e0...
067002D0: 2A864886 F70D0101 05050003 82010100 *.H.w...........
067002E0: 2134BFC4 607F0AC1 4E74DE75 ABC95334 !4?D`..ANt^u+IS4
067002F0: 68B4CA08 E6774486 03367B24 4DFAE43E h4J.fwD..6{$Mzd>
06700300: 8D74380C 581C4242 949D7E4B 235E3B5E .t8.X.BB..~K#^;^
06700310:
*Jan 31 16:36:09.269: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Reassembly required for handshake seq 2. frag_len (519) < length (1151)
*Jan 31 16:36:09.269: DTLS_CLIENT_EVENT_DETAIL: dtls_handshake_fragment_new: Called...
*Jan 31 16:36:09.269: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Not ready to assemble yet.
*Jan 31 16:36:09.269: DTLS_CLIENT_EVENT_DETAIL: dtls_client_process_record: DTLS handshake buffered for reassembly later
*Jan 31 16:36:09.269: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: End of datagram reached.
*Jan 31 16:36:09.269: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x026C9F00
06775BD0: 16FEFF00 00000000 .~......
06775BE0: 00000400 D00B0004 7F000200 03AF0000 ....P......../..
06775BF0: C47FE7D0 6D49F7D3 955B2084 6C8E2701 D.gPmIwS.[ .l.'.
06775C00: 024858B8 B23679B2 D4DFE94B E3524454 .HX826y2T_iKcRDT
06775C10: 3F1C7F89 8916D838 CCECEA24 34C3E68A ?.....X8Llj$4Cf.
06775C20: 427B83DE 6F02FB0D 8FDE45A1 04274B95 B{.^o.{..^E!.'K.
06775C30: 9FDBD8A5 7DC5C94B 030613C6 047F0937 .[X%}EIK...F...7
06775C40: 6F24F619 9C7B93B2 4BA2E768 5A4ABA58 o$v..{.2K"ghZJ:X
06775C50: 2EEECD3D B1BFAD3B D6184F9A 6034BDF0 .nM=1?-;V.O.`4=p
06775C60: 981D6FEE E044918C 81ED9BD8 4D01B350 ..on`D...m.XM.3P
06775C70: FBCDF285 8007C7BE 90C885FD 821ED93E {Mr...G>.H.}..Y>
06775C80: B07FFF2C 67FDA948 78B816A2 029498DE 0..,g})Hx8."...^
06775C90: FB4C21B2 E8095673 C9A590E0 E16F5499 {L!2h.VsI%.`aoT.
06775CA0: E4639F34 E48479C7 D3E7EFE7 61DFAF48 dc.4d.yGSgoga_/H
06775CB0: 19E5563B 2D .eV;-
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Reassembly required for handshake seq 2. frag_len (196) < length (1151)
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_handshake_fragment_new: Called...
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Not ready to assemble yet.
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_client_process_record: DTLS handshake buffered for reassembly later
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Attempting to extract next record....
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x026C9F00
06775CB0: 16FEFF 00000000 00000005 .~.........
06775CC0: 00180B00 047F0002 00047300 000C3D27 ..........s...='
06775CD0: 3B623688 29C8CA64 2167 ;b6.)HJd!g
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Reassembly required for handshake seq 2. frag_len (12) < length (1151)
*Jan 31 16:36:09.271: DTLS_CLIENT_EVENT_DETAIL: dtls_handshake_fragment_new: Called...
*Jan 31 16:36:09.272: DTLS_CLIENT_EVENT_DETAIL: local_reassembly_check: Handshake sequence 2 is ready for assembly
*Jan 31 16:36:09.272: DTLS_CLIENT_EVENT_DETAIL: local_reassemble: Message assembled
Debug of failed AP:
*Jan 31 16:52:51.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.143.254.254 peer_port: 5246
*Jan 31 16:52:51.000: DTLS_CLIENT_EVENT_DETAIL: dtls_secret_inc_ref_count: Secret reference count= 2
*Jan 31 16:52:51.000: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_flush_handshake_msgs: Called...
*Jan 31 16:52:51.000: DTLS_CLIENT_EVENT_DETAIL: dtls_secret_delete: Secret not deleted, reference count = 1
*Jan 31 16:52:51.000: DTLS_CLIENT_EVENT_DETAIL: dtls_send_ClientHello: Called...
*Jan 31 16:52:51.000: DTLS_CLIENT_EVENT_DETAIL: dtls_send_handshake_msg: Called...
*Jan 31 16:52:51.000: DTLS_CLIENT_EVENT_DETAIL: dtls_record_send: Called...
*Jan 31 16:52:51.001: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_send: Called...
*Jan 31 16:52:51.235: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x0278009C
067E02E0: 16FEFF00 .~..
067E02F0: 00000000 00000000 2F030000 23000000 ......../...#...
067E0300: 00000000 23FEFF20 0A00E9CD 5AC11234 ....#~. ..iMZA.4
067E0310: 56789ABC 49623895 65565B89 4FC53D11 Vx.
067E0320: 2340A364 B6970C60 #@#d6..`
*Jan 31 16:52:51.236: DTLS_CLIENT_EVENT: dtls_process_HelloVerifyRequest: Processing...
*Jan 31 16:52:51.236: DTLS_CLIENT_EVENT_DETAIL: dtls_send_ClientHello: Called...
*Jan 31 16:52:51.236: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_flush_handshake_msgs: Called...
*Jan 31 16:52:51.236: DTLS_CLIENT_EVENT_DETAIL: dtls_send_handshake_msg: Called...
*Jan 31 16:52:51.236: DTLS_CLIENT_EVENT_DETAIL: dtls_record_send: Called...
*Jan 31 16:52:51.236: DTLS_CLIENT_EVENT_DETAIL: dtls_connection_send: Called...
*Jan 31 16:52:51.236: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: End of datagram reached.
*Jan 31 16:52:51.360: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x0278009C
06803E20: 16FEFF00 00000000 00000100 .~..........
06803E30: 52020000 46000100 00000000 46FEFF51 R...F.......F~.Q
06803E40: 0AA1E669 386F805D F3907CEB C6212A7C .!fi8o.]s.|kF!*|
06803E50: 7D0DAB83 0B8079F3 380B43C0 2DCDCD20 }.+...ys8.C@-MM
06803E60: 729501D9 456FE544 3CADEE74 690F27C7 r..YEoeD<-nti.'G
06803E70: 47AE362C 3E274CB2 6C5DDE4E CDC5FC10 G.6,>'L2l]^NME|.
06803E80: 002F00 ./.
*Jan 31 16:52:51.360: DTLS_CLIENT_EVENT: dtls_process_ServerHello: Processing...
*Jan 31 16:52:51.360: DTLS_CLIENT_EVENT: dtls_connection_set_cipher: Setting cipher to TLS_RSA_WITH_AES_128_CBC_SHA
*Jan 31 16:52:51.360: DTLS_CLIENT_EVENT_DETAIL: dtls_secret_pki_init: Called...
*Jan 31 16:52:51.360: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Attempting to extract next record....
*Jan 31 16:52:51.360: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x0278009C
06803E80: 16 FEFF0000 00000000 000201B4 .~..........4
06803E90: 0B00047F 00020000 000001A8 00047C00 ...........(..|.
06803EA0: 04793082 04753082 035DA003 02010202 .y0..u0..] .....
06803EB0: 0A5021F6 ED000000 2EB59930 0D06092A .P!vm....5.0...*
06803EC0: 864886F7 0D010105 05003039 31163014 .H.w......091.0.
06803ED0: 06035504 0A130D43 6973636F 20537973 ..U....Cisco Sys
06803EE0: 74656D73 311F301D 06035504 03131643 tems1.0...U....C
06803EF0: 6973636F 204D616E 75666163 74757269 isco Manufacturi
06803F00: 6E672043 41301E17 0D313030 36313131 ng CA0...1006111
06803F10: 39323731 315A170D 32303036 31313139 92711Z..20061119
06803F20: 33373131 5A308194 310B3009 06035504 3711Z0..1.0...U.
06803F30: 06130255 53311330 11060355 0408130A ...US1.0...U....
06803F40: 43616C69 666F726E 69613111 300F0603 California1.0...
06803F50: 55040713 0853616E 204A6F73 65311630 U....San Jose1.0
06803F60: 14060355 040A130D 43697363 6F205379 ...U....Cisco Sy
06803F70: 7374656D 73312330 21060355 0403131A stems1#0!..U....
06803F80: 4149522D 43543535 30382D4B 392D3638 AIR-CT5508-K9-68
06803F90: 65666264 39333833 32303120 301E0609 efbd9383201 0...
06803FA0: 2A864886 F70D0109 01161173 7570706F *.H.w......suppo
06803FB0: 72744063 6973636F 2E636F6D 30820122 [email protected].."
06803FC0: 300D0609 2A864886 F70D0101 01050003 0...*.H.w.......
06803FD0: 82010F00 3082010A 02820101 00DE519C ....0........^Q.
06803FE0: EBD5DE04 BBE84810 B796C26A 19B3C0C4 kU^.;hH.7.Bj.3@D
06803FF0: 039F5946 8C5BA9D5 6C3FFD50 E95163DA ..YF.[)Ul?}PiQcZ
06804000: A4ADB7DB 280198D7 E5606E5A FA165D1C $-7[(..We`nZz.].
06804010: FD97E8A7 3259FED7 C043DEBC 6653727D }.h'2Y~W@C^
06804020: D2B514E3 C6ABDCB8 848C65F2 4A96A5A7 R5.cF+\8..erJ.%'
06804030: 11881F0C 90A3CB03 3FA69851 1112E7EF .....#K.?&.Q..go
06804040: FF173971 ..9q
*Jan 31 16:52:51.363: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Reassembly required for handshake seq 2. frag_len (424) < length (1151)
*Jan 31 16:52:51.363: DTLS_CLIENT_EVENT_DETAIL: dtls_handshake_fragment_new: Called...
*Jan 31 16:52:51.363: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Not ready to assemble yet.
*Jan 31 16:52:51.363: DTLS_CLIENT_EVENT_DETAIL: dtls_client_process_record: DTLS handshake buffered for reassembly later
*Jan 31 16:52:51.364: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: End of datagram reached.
*Jan 31 16:52:51.364: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: Called... for connection 0x0278009C
06846A80: 16FEFF00 00000000 .~......
06846A90: 00000302 130B0004 7F000200 01A80002 .............(..
06846AA0: 07198FBE E5CB79E6 2ED9EF2F 0F66C568 ...>eKyf.Yo/.fEh
06846AB0: 73D72351 54BB111F 40A7B3BD 2294943F sW#QT;..@'3="..?
06846AC0: 61ADAD6C 54C95FFC 6E0DA143 004C0C1D a--lTI_|n.!C.L..
06846AD0: 200A17DC 0E61D224 EF6DDBB9 72DAF726 ..\.aR$om[9rZw&
06846AE0: 001AC973 1E228D8D A745158B F13D646E ..Is."..'E..q=dn
06846AF0: 1CCDF808 AEA47A7D 10DBF88A 2FB02F5F .Mx..$z}.[x./0/_
06846B00: 15A71982 BF458124 3159A9CD 6EC72B43 .'..?E.$1Y)MnG+C
06846B10: D5541C04 291B83F4 F6A667D9 6125AB38 UT..)..tv&gYa%+8
06846B20: 74C55671 9CC46CC4 C78146FA B4FB10B5 tEVq.DlDG.Fz4{.5
06846B30: 620E9C03 3FDE0261 17530203 010001A3 b...?^.a.S.....#
06846B40: 82012130 82011D30 0B060355 1D0F0404 ..!0...0...U....
06846B50: 030205A0 301D0603 551D0E04 1604148F ... 0...U.......
06846B60: 93BB23DE B485C5F2 3553F941 3ED2A81F .;#^4.Er5SyA>R(.
06846B70: CD53AA30 1F060355 1D230418 30168014 MS*0...U.#..0...
06846B80: D0C52226 AB4F4660 ECAE0591 C7DC5AD1 PE"&+OF`l...G\ZQ
06846B90: B047F76C 303F0603 551D1F04 38303630 0Gwl0?..U...8060
06846BA0: 34A032A0 30862E68 7474703A 2F2F7777 4 2 0..http://ww
06846BB0: 772E6369 73636F2E 636F6D2F 73656375 w.cisco.com/secu
06846BC0: 72697479 2F706B69 2F63726C 2F636D63 rity/pki/crl/cmc
06846BD0: 612E6372 6C304C06 082B0601 05050701 a.crl0L..+......
06846BE0: 01044030 3E303C06 082B0601 05050730 ..@0>0<..+.....0
06846BF0: 02863068 7474703A 2F2F7777 772E6369 ..0http://www.ci
06846C00: 73636F2E 636F6D2F 73656375 72697479 sco.com/security
06846C10: 2F706B69 2F636572 74732F63 6D63612E /pki/certs/cmca.
06846C20: 63657230 3F06092B 06010401 82371402 cer0?..+.....7..
06846C30: 04321E30 00490050 00530045 00430049 .2.0.I.P.S.E.C.I
06846C40: 006E0074 00650072 006D0065 00640069 .n.t.e.r.m.e.d.i
06846C50: 00610074 0065004F 00660066 006C0069 .a.t.e.O.f.f.l.i
06846C60: 006E0065 300D0609 2A864886 F70D0101 .n.e0...*.H.w...
06846C70: 05050003 82010100 2134BFC4 607F0AC1 ........!4?D`..A
06846C80: 4E74DE75 ABC95334 68B4CA08 E6774486 Nt^u+IS4h4J.fwD.
06846C90: 03367B24 4DFAE43E 8D74380C 581C4242 .6{$Mzd>.t8.X.BB
06846CA0: 949D7E4B 235E3B5E ..~K#^;^
*Jan 31 16:52:51.367: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Reassembly required for handshake seq 2. frag_len (519) < length (1151)
*Jan 31 16:52:51.367: DTLS_CLIENT_EVENT_DETAIL: dtls_handshake_fragment_new: Called...
*Jan 31 16:52:51.367: DTLS_CLIENT_EVENT_DETAIL: dtls_reassemble_handshake: Not ready to assemble yet.
*Jan 31 16:52:51.367: DTLS_CLIENT_EVENT_DETAIL: dtls_client_process_record: DTLS handshake buffered for reassembly later
*Jan 31 16:52:51.367: DTLS_CLIENT_EVENT_DETAIL: dtls_process_packet: End of datagram reached.
*Jan 31 16:53:51.044: DTLS_CLIENT_EVENT: dtls_disconnect: Disconnecting DTLS connection 0x0278009C
*Jan 31 16:53:51.044: DTLS_CLIENT_EVENT_DETAIL: dtls_free_connection: Called... for connection 0x0278009C
*Jan 31 16:53:51.044: DTLS_CLIENT_EVENT_DETAIL: dtls_send_Alert: Called...
*Jan 31 16:53:51.044: DTLS_CLIENT_EVENT: dtls_send_Alert: Sending FATAL : Close notify Alert
*Jan 31 16:53:51.045: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.143.254.254:5246
As you can see there are identical up to handshake seq 2. frag_len (519) < length (1151). The working AP receives the last fragment and succesfully reassembles it. The failed AP never receives that last fragment.
I can't think of any reason why this could be happening.
Maybe you are looking for
-
Iphoto not displaying imported photos
hello i would appreciate it if someone could give me an idea of what is happening with my iphoto programme.i transfer photo from the camera via usb iphoto displays the photos in abumn format but as soon as i click on it to make it viewable as a large
-
Expand Size of Second Partition - OS X Lion
Resurrecting for Lion the partition resizing problem, previously discussed on archived Leopard posts. When you have created two partitions in an os / x journaled volume for data storage and backups. You want to shrink partition #1 and give the freed
-
Fusesmb always connect timed out
Hi All: I come across a problem which confused me for days. I just install the fusesmb to share the file with window. I followed the instructions at this website http://ubuntuforums.org/showthread.php?t=300310, but didn't success. I can o
-
Adding F5-VE cluster into APIC: Status remains as init
Hi, This is my 2nd thread about L4-L7 integration.. the previous one was about the ASAv which I managed to get working thanks to Zachary Seils. I've been trying to integrate a F5 VM cluster into the APIC, but couldn't seem to get it working. The sta
-
when trying to type the IMG command at the bash promt i recieved command not found, also after the Linux kernal loads it displays a message stating that the Network card is not supported. I am using ZENworks for Desktop 4, maybe it doesn't have linux