07-18-2013 06:23 AM - edited 07-04-2021 12:27 AM
Hi all,
we have a lot of problem in joining AP 1600e lightw to a vWLC.
Following the details:
- vWLC: 7.4.100 (with SSC disabled)
- AP: ap1g2-rcvk9w8-tar.152-2.JB
We followed these steps:
- AP directly to vWLC: results: DTLS Error
"*spamApTask3: Jul 18 13:16:26.389: #DTLS-3-HANDSHAKE_FAILURE: openssl_dtls.c:681 Failed to complete DTLS handshake with peer 10.143.174.200"
- AP to a 7.4 5508 WLC and then to vWLC: results as per previous point
Any clue?
Thanks in advance
Luciano
07-18-2013 08:13 AM
Hi Luciano,
Connect to the AP1602 via console cable and issue these commands:
#test capwap erase
#test capwap restart
Turn off and turn on the AP. It should successfully join your vWLC now.
07-18-2013 09:07 AM
Ciao,
sorry but I don't have those commands on the AP (we are via console cable):
AP0006.f6d6.05fc#test capwap ?
am CAPWAP KAM-AP test commands
controller Configuring AP's controller
dtls dtls enable/disable
ids LWAPP IDS test commands
message Send CAPWAP message to AC
pppoe Change AP sub-mode to PPPoE
rm CAPWAP RM test commands
Tnx!
Luciano
07-18-2013 09:53 AM
OK,
they are hidden command.
After that we see that this AP is going to reach the 5508 WLC (which is in another net) and not the local vWLC (10.143.174.196) ... it is still try the 5508 WLC even after a capwap ap controlle ip command and a reload ...
07-18-2013 10:18 AM
After:
#test capwap erase
#test capwap restart
You turned off AP, then turned it on, and it still tries to reach 5508? Can you ping your vWLC from AP? Can vWLC ping AP?
07-18-2013 10:50 AM
After both commands I restard the AP by shutting down the poe switch port. And yes I can ping each others. The strange thing is that when I reload tha AP it goes directly to the 5508 :(
Sent from Cisco Technical Support Android App
07-18-2013 12:28 PM
Hi,
can you please join the AP to the 5508 WLC then assign a primary, and secondary WLC in the High availablity tab under the AP.
set the primary as vWLC and secondary as 5508
then reboot the AP and attach the complete log for the join process.
after that, please attach also show flash from the AP.
07-18-2013 02:17 PM
Hi all,
now it's a little bit late here in Italy (11:00PM).
Tomorrow I'll do as per your suggestion.
Tnx!
Luciano
07-19-2013 02:05 AM
Hi,
this morning the AP is still try to connect to the WLC 5508 ... but no success ...
Please find below the dir:
AP0006.f6d6.05fc#dir
Directory of flash:/
2 -rwx 210 Jul 19 2013 08:56:47 +00:00 env_vars
12 drwx 128 Mar 1 1993 00:03:15 +00:00 ap1g2-rcvk9w8-mx
4 -rwx 77124 Jul 18 2013 15:45:55 +00:00 event.log
5 -rwx 6168 Jul 19 2013 08:56:47 +00:00 private-multiple-fs
6 drwx 0 Jul 18 2013 12:46:18 +00:00 configs
8 drwx 512 Jul 18 2013 12:56:55 +00:00 ap1g2-k9w8-mx.152-2.JB1
Below the boot:
Boot from flash
###################################################################
IOS Bootloader - Starting system.
FLASH CHIP: Micronix MX25L256_35F
Xmodem file system is available.
flashfs[0]: 29 files, 9 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31936000
flashfs[0]: Bytes used: 16387584
flashfs[0]: Bytes available: 15548416
flashfs[0]: flashfs fsck took 16 seconds.
Reading cookie from SEEPROM
Base Ethernet MAC address: 00:06:f6:d6:05:fc
************* loopback_mode = 0
Loading "flash:/ap1g2-k9w8-mx.152-2.JB1/ap1g2-k9w8-mx.152-2.JB1"...############################
File "flash:/ap1g2-k9w8-mx.152-2.JB1/ap1g2-k9w8-mx.152-2.JB1" uncompressed and installed, entry point: 0x100000
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, C1600 Software (AP1G2-K9W8-M), Version 15.2(2)JB1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 07-May-13 09:37 by prod_rel_team
Initializing flashfs...
FLASH CHIP: Micronix MX25L256_35F
flashfs[3]: 29 files, 9 directories
flashfs[3]: 0 orphaned files, 0 orphaned directories
flashfs[3]: Total bytes: 31808000
flashfs[3]: Bytes used: 16387584
flashfs[3]: Bytes available: 15420416
flashfs[3]: flashfs fsck took 14 seconds.
flashfs[3]: Initialization complete.
flashfs[4]: 0 files, 1 directories
flashfs[4]: 0 orphaned files, 0 orphaned directories
flashfs[4]: Total bytes: 11999232
flashfs[4]: Bytes used: 1024
flashfs[4]: Bytes available: 11998208
flashfs[4]: flashfs fsck took 1 seconds.
flashfs[4]: Initialization complete....done Initializing flashfs.
Warning: the compile-time code checksum does not appear to be present.
Radio0 present 8764B 8000 0 A8000000 A8010000 0
Rate table has 180 entries (48 SGI/72 BF variants)
Radio1 present 8764B 8000 0 88000000 88010000 4
This product contains cryptographic features and is subject to United
memory validate-checksum 30
^
% Invalid input detected at '^' marker.
login authentication default
^
% Invalid input detected at '^' marker.
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
Warning: the compile-time code checksum does not appear to be present.
cisco AIR-CAP1602E-A-K9 (PowerPC) processor (revision B0) with 98294K/32768K bytes of memory.
Processor board ID FGL1720X2Q5
PowerPC CPU at 533Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.4.100.60
1 Gigabit Ethernet interface
2 802.11 Radios
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:06:F6:D6:05:FC
Part Number : 73-14508-04
PCA Assembly Number : 000-00000-00
PCA Revision Number :
PCB Serial Number : FOC170902NW
Top Assembly Part Number : 800-38553-01
Top Assembly Serial Number : FGL1720X2Q5
Top Revision Number : A0
Product/Model Number : AIR-CAP1602E-A-K9
% Please define a domain-name first.
Press RETURN to get started!
*Mar 1 00:00:16.531: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:18.955: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
*Mar 1 00:00:19.079: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:20.071: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
*Mar 1 00:00:22.827: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1600 Software (AP1G2-K9W8-M), Version 15.2(2)JB1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Tue 07-May-13 09:37 by prod_rel_team
*Mar 1 00:00:22.827: %SNMP-5-COLDSTART: SNMP agent on host AP0006.f6d6.05fc is undergoing a cold start
*Mar 1 00:00:22.863: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 1 00:00:22.863: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Mar 1 00:00:23.367: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
*Mar 1 00:00:23.987: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Mar 1 00:00:26.243: %SSH-5-ENABLED: SSH 2.0 has been enabledlwapp_crypto_init: MIC Present and Parsed Successfully
%Default route without gateway, if not a point-to-point interface, may impact performance
*Mar 1 00:00:51.635: Logging LWAPP message to 255.255.255.255.
*Mar 1 00:00:55.111: %CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
*Mar 1 00:00:56.167: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 1 00:00:56.491: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.143.174.201, mask 255.255.255.224, hostname AP0006.f6d6.05fc
*Mar 1 00:00:57.167: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 1 00:00:57.223: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Mar 1 00:00:58.223: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER.saipemnet.saipem.intranet"...domain server (8.8.8.8)
*Mar 1 00:01:07.423: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:01:08.551: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.saipemnet.saipem.intranet
*Mar 1 00:01:18.551: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 18 16:42:30.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:42:32.267: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:42:32.267: %CAPWAP-5-SENDJOIN: sending Join Request to 10.129.139.2
*Jul 18 16:42:32.919: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jul 18 16:42:32.919: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jul 18 16:42:32.919: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jul 18 16:42:32.919: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.129.139.2
*Jul 18 16:42:51.399: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
., 1)
*Jul 18 16:42:51.399: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Jul 18 16:42:51.399: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.129.139.2:5246
*Jul 18 16:42:51.443: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jul 18 16:42:51.463: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jul 18 16:42:51.463: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jul 18 16:42:51.475: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:42:51.519: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:42:52.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:42:52.511: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jul 18 16:42:52.519: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jul 18 16:42:53.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:42:53.511: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jul 18 16:42:53.555: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:42:53.563: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 18 16:42:53.571: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 18 16:42:54.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jul 18 16:42:54.563: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:42:54.599: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:42:55.599: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:43:01.519: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 18 16:43:02.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:43:04.279: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:43:04.279: %CAPWAP-5-SENDJOIN: sending Join Request to 10.129.139.2
*Jul 18 16:43:04.923: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jul 18 16:43:04.923: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jul 18 16:43:04.923: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jul 18 16:43:04.923: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.129.139.2
*Jul 18 16:43:23.095: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
., 1)
*Jul 18 16:43:23.095: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Jul 18 16:43:23.095: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.129.139.2:5246
*Jul 18 16:43:23.139: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jul 18 16:43:23.159: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jul 18 16:43:23.159: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jul 18 16:43:23.175: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:43:23.207: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:43:24.159: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:43:24.207: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jul 18 16:43:24.215: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jul 18 16:43:25.199: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:43:25.207: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jul 18 16:43:25.251: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:43:25.259: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 18 16:43:25.267: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 18 16:43:26.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jul 18 16:43:26.259: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:43:26.295: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:43:27.295: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:43:33.207: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 18 16:43:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:43:35.283: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:43:35.283: %CAPWAP-5-SENDJOIN: sending Join Request to 10.129.139.2
*Jul 18 16:43:35.935: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jul 18 16:43:35.935: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jul 18 16:43:35.935: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jul 18 16:43:35.935: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.129.139.2
*Jul 18 16:43:54.103: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
., 1)
*Jul 18 16:43:54.103: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Jul 18 16:43:54.103: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.129.139.2:5246
*Jul 18 16:43:54.455: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jul 18 16:43:54.475: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jul 18 16:43:54.475: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jul 18 16:43:54.487: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:43:54.523: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:43:55.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:43:55.523: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jul 18 16:43:55.531: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jul 18 16:43:56.515: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:43:56.523: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jul 18 16:43:56.567: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:43:56.575: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 18 16:43:56.583: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 18 16:43:57.567: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jul 18 16:43:57.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:43:57.611: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:43:58.611: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:44:04.519: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 18 16:44:05.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:44:07.447: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:44:07.447: %CAPWAP-5-SENDJOIN: sending Join Request to 10.129.139.2
*Jul 18 16:44:08.087: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jul 18 16:44:08.087: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jul 18 16:44:08.087: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jul 18 16:44:08.087: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.129.139.2
*Jul 18 16:44:26.259: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)
., 1)
*Jul 18 16:44:26.259: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
*Jul 18 16:44:26.259: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.129.139.2:5246
*Jul 18 16:44:26.303: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Jul 18 16:44:26.323: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Jul 18 16:44:26.323: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jul 18 16:44:26.339: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:44:26.371: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:44:27.323: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:44:27.371: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
*Jul 18 16:44:27.379: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
*Jul 18 16:44:28.363: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:44:28.371: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Jul 18 16:44:28.415: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
*Jul 18 16:44:28.423: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
*Jul 18 16:44:28.431: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Jul 18 16:44:29.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
*Jul 18 16:44:29.423: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Jul 18 16:44:29.459: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
*Jul 18 16:44:30.459: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Jul 18 16:44:36.371: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 18 16:44:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:44:38.271: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.129.139.2 peer_port: 5246
*Jul 18 16:44:38.271: %CAPWAP-5-SENDJOIN: sending Join Request to 10.129.139.2
*Jul 18 16:44:38.911: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
*Jul 18 16:44:38.911: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Jul 18 16:44:38.911: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Jul 18 16:44:38.911: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.129.139.2
###################################################################
Tnx!
Luciano
07-19-2013 03:49 AM
Do you use NTP server for your WLC5508 and vWLC? Is the time correct?
Also, check your regulatory domain configuration on AP and WLCs.
Your AP model is : AIR-CAP1602E-A-K9
On WLC5508 go to :Wireless > Country
Check this for country list:
07-19-2013 05:20 AM
Ciao,
both of the controllers uses an NTP server, but the WLC5508 is located in Italy ... the 2nd one is locate in another site, the time difference between the 2 WLC is 3 hours.
Ciao!
Luciano
07-19-2013 05:27 AM
So it joins a 5508 with no issues correct? Well if it joins, then click on the AP and then under the high availability set the primary WLC to the vWLC. Remember that the hostname is case sensitive and also put the IP of the vWLC. Then bounce the AP and see if it joins.
Sent from Cisco Technical Support iPhone App
07-19-2013 06:12 AM
Ciao,
no ... it's not joinin' the 5508 nor the vWLC
07-19-2013 06:13 AM
The 5508 is also on v7.4 correct?
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
07-19-2013 06:16 AM
Ciao Scott,
yep!
Ciao!
Luciano
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide