Solved: AP to WLC

leewray01 · ‎10-03-2013

Hi All

Ive set up a wireless network today consisting of 5 Cisco Aironet 2600 WAP's and a 5508 WLC. For some reason the AP's will not join the controller. I have a console connection to an AP and this is the output I receive;

Mar 1 00:43:35.639: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.6.0.250 obtained through DHCP

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.6.0.250

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

*Mar 1 00:43:35.639: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.6.0.250

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar 1 00:43:45.639: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.6.0.250

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar 1 00:43:55.639: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar 1 00:43:58.043: %IP-4-DUPADDR: Duplicate address 10.6.0.155 on BVI1, sourced by 60eb.69b8.4150

*Mar 1 00:44:05.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

*Mar 1 00:44:05.639: %CAPWAP-3-ERRORLOG: Failed to decode discovery response.

*Mar 1 00:44:05.639: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 2 state 2.

*Mar 1 00:44:05.639: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Mar 1 00:44:05.639: %CAPWAP-3-ERRORLOG: Failed to process unencrypted capwap packet from 10.6.0.250

*Mar 1 00:44:05.639: %CAPWAP-3-ERRORLOG: Discovery response from MWAR 'Wifi-Controller'running version 7.0.240.0 is rejected.

The Controller and AP's are on the same VLAN and as you can see they can see each other.

Im new to wireless and was hoping someone could help me?

Stephen Rodriguez · ‎10-24-2013

ok, so I'm seeing Regulatory Domain issues.

Regulatory Domain Mismatch: AP d0:c7:89:24:76:60 not allowed to join. Regulatory Domain check failed.

per the link below, the Philipines should be a -A AP, not a -E

http://www.cisco.com/en/US/prod/collateral/wireless/ps5679/ps5861/product_data_sheet0900aecd80537b6a_ps6087_Products_Data_Sheet.html

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

View solution in original post

Stephen Rodriguez · ‎10-03-2013

You need to upgrade the 5508 to at least 7.2.110.0 to support the 2600 series AP

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

leewray01 · ‎10-23-2013

Sorry for the late reply. I have updates to new firware and im getting a different error now.

AP

., 1)23 06:27:22.635: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)

*Oct 23 06:27:22.635: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Oct 23 06:27:22.635: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.6.0.250:5246

*Oct 23 06:27:22.695: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Oct 23 06:27:22.707: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Oct 23 06:27:22.707: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Oct 23 06:27:22.719: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 23 06:27:22.735: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 23 06:27:23.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 23 06:27:23.743: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Oct 23 06:27:23.751: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Oct 23 06:27:24.735: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 23 06:27:24.743: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Oct 23 06:27:24.771: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 23 06:27:24.779: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Oct 23 06:27:24.787: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Oct 23 06:27:25.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Oct 23 06:27:25.779: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 23 06:27:25.807: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 23 06:27:26.807: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 23 06:27:32.731: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 23 06:27:33.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.6.0.250 peer_port: 5246

*Oct 23 06:27:33.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.6.0.250 peer_port: 5246

*Oct 23 06:27:33.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 23 06:27:33.467: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.

*Oct 23 06:27:33.467: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.

*Oct 23 06:27:33.467: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller

*Oct 23 06:27:33.467: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.6.0.250

CONTROLLER

*spamApTask2: Oct 23 06:33:01.411: d0:c7:89:24:76:60 Join Request from 10.6.0.42:42112

*spamApTask2: Oct 23 06:33:01.412: 6c:41:6a:ca:47:f0 Deleting AP entry 10.6.0.42:42112 from temporary database.

*spamApTask2: Oct 23 06:33:01.413: d0:c7:89:24:76:60 Join Version: = 117730816

*spamApTask2: Oct 23 06:33:01.413: d0:c7:89:24:76:60 Join resp: CAPWAP Maximum Msg element len = 98

*spamApTask2: Oct 23 06:33:01.414: d0:c7:89:24:76:60 Join Response sent to 10.6.0.42:42112

*spamApTask2: Oct 23 06:33:01.414: d0:c7:89:24:76:60 CAPWAP State: Join

*spamApTask2: Oct 23 06:33:01.414: d0:c7:89:24:76:60 capwap_ac_platform.c:1225 - Operation State 0 ===> 4

*apfReceiveTask: Oct 23 06:33:01.414: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 23 06:33:01.415: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 23 06:33:02.463: d0:c7:89:24:76:60 Configuration Status from 10.6.0.42:42112

*spamApTask2: Oct 23 06:33:02.463: d0:c7:89:24:76:60 CAPWAP State: Configure

*spamApTask2: Oct 23 06:33:02.463: d0:c7:89:24:76:60 Updating IP info for AP d0:c7:89:24:76:60 -- static 0, 10.6.0.42/255.255.255 .0, gtw 10.6.0.1

*spamApTask2: Oct 23 06:33:02.463: d0:c7:89:24:76:60 Updating IP 10.6.0.42 ===> 10.6.0.42 for AP d0:c7:89:24:76:60

*spamApTask2: Oct 23 06:33:02.463: d0:c7:89:24:76:60 Setting MTU to 1485

*spamApTask2: Oct 23 06:33:02.464: d0:c7:89:24:76:60 Finding DTLS connection to delete for AP (10:6:0:42/42112)

*spamApTask2: Oct 23 06:33:02.464: d0:c7:89:24:76:60 Disconnecting DTLS Capwap-Ctrl session 0x1700d000 for AP (10:6:0:42/42112)

*spamApTask2: Oct 23 06:33:02.464: d0:c7:89:24:76:60 CAPWAP State: Dtls tear down

*spamApTask2: Oct 23 06:33:02.465: d0:c7:89:24:76:60 DTLS keys for Control Plane deleted successfully for AP 10.6.0.42

*spamApTask2: Oct 23 06:33:02.472: d0:c7:89:24:76:60 DTLS connection closed event receivedserver (10:6:0:250/5246) client (10:6:0 :42/42112)

*spamApTask2: Oct 23 06:33:02.472: d0:c7:89:24:76:60 Entry exists for AP (10:6:0:42/42112)

*spamApTask2: Oct 23 06:33:02.472: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7: 89:24:76:60 slot 0

*apfReceiveTask: Oct 23 06:33:02.472: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 0

*spamApTask2: Oct 23 06:33:02.472: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7: 89:24:76:60 slot 1

*apfReceiveTask: Oct 23 06:33:02.472: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 23 06:33:02.473: d0:c7:89:24:76:60 No AP entry exist in temporary database for 10.6.0.42:42112

*spamApTask3: Oct 23 06:33:20.558: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 23 06:33:20.558: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 23 06:33:20.559: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

*spamApTask3: Oct 23 06:33:20.559: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 23 06:33:20.559: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 23 06:33:20.559: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

*spamApTask3: Oct 23 06:33:20.559: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 23 06:33:20.560: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 23 06:33:20.560: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

kaaftab · ‎10-03-2013

kindly check the following link for AP compatibility.

http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html

Scott Fella · ‎10-23-2013

Can you make sure that the WLC has the correct time. Also put the AP on the SE subnet as the WLC management and make sure the AP's are getting an IP address. Post the whole boot up process by reloading or powering up the AP if you still have issues.

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***

leewray01 · ‎10-23-2013

Hey

They are on the same subnet and they are getting IP addresses. Layer 2,3 connectivity between the devices is fine. I Will have to wait until tomorrow until I can get the boot up info as its in the Philippines. I will report back first thing

leewray01 · ‎10-23-2013

Just though I should point this out. In the debug output you will see the controller (10.6.0.250) can see the requests coming from my test AP (10.6.0.42)

How is the time zone going to make a difference? The AP's should just accept the controllers setting, correct?

Stephen Rodriguez · ‎10-23-2013

Yes, it should just pull it's time from the WLC.

So you need to upgrade your WLC to support the 2600. You need to be running at least 7.2.110.0

Your WLC is currently running 7.0.240.0

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

leewray01 · ‎10-23-2013

Hey

It's not I upgraded it this morning. Its now running the new firmware. Its now on 10.4.110.0

Stephen Rodriguez · ‎10-23-2013

I"m blaming that last post on lack of sleep.....=)

are you doing both capwap events and errors on the WLC debug? If not can you do both and repost the join attempt?

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

leewray01 · ‎10-24-2013

Hey Stephen

PLease see the debug output below

AP

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.10.24 21:46:08 =~=~=~=~=~=~=~=~=~=~=~=

flashfs[0]: 39 files, 9 directories

flashfs[0]: 0 orphaned files, 0 orphaned directories

flashfs[0]: Total bytes: 31997952

flashfs[0]: Bytes used: 18546688

flashfs[0]: Bytes available: 13451264

flashfs[0]: flashfs fsck took 18 seconds.

Reading cookie from SEEPROM

Base Ethernet MAC address: 6c:41:6a:ca:47:f8

Ethernet speed is 100 Mb - FULL Duplex

Loading "flash:/ap3g2-k9w8-mx.152-2.JB2/ap3g2-k9w8-mx.152-2.JB2"...###########################

File "flash:/ap3g2-k9w8-mx.152-2.JB2/ap3g2-k9w8-mx.152-2.JB2" uncompressed and installed, entry point: 0x2003000

executing...

Secondary Bootloader - Starting system.

Xmodem file system is available.

flashfs[0]: 39 files, 9 directories

flashfs[0]: 0 orphaned files, 0 orphaned directories

flashfs[0]: Total bytes: 31997952

flashfs[0]: Bytes used: 18546688

flashfs[0]: Bytes available: 13451264

flashfs[0]: flashfs fsck took 8 seconds.

Base Ethernet MAC address: 6c:41:6a:ca:47:f8

Boot CMD: 'boot flash:/ap3g2-k9w8-mx.152-2.JB2/ap3g2-k9w8-xx.152-2.JB2;flash:/ap3g2-k9w8-mx.152-2.JB2/ap3g2-k9w8-mx.152-2.JB2'

Loading "flash:/ap3g2-k9w8-mx.152-2.JB2/ap3g2-k9w8-xx.152-2.JB2"...#############################

File "flash:/ap3g2-k9w8-mx.152-2.JB2/ap3g2-k9w8-xx.152-2.JB2" uncompressed and installed, entry point: 0x2003000

executing...

Restricted Rights Legend

Use, duplication, or disclosure by the Government is

subject to restrictions as set forth in subparagraph

(c) of the Commercial Computer Software - Restricted

Rights clause at FAR sec. 52.227-19 and subparagraph

(c) (1) (ii) of the Rights in Technical Data and Computer

Software clause at DFARS sec. 252.227-7013.

cisco Systems, Inc.

170 West Tasman Drive

San Jose, California 95134-1706

Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.2(2)JB2, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Compiled Mon 29-Jul-13 11:27 by prod_rel_team

Initializing flashfs...

flashfs[3]: 39 files, 9 directories

flashfs[3]: 0 orphaned files, 0 orphaned directories

flashfs[3]: Total bytes: 31739904

flashfs[3]: Bytes used: 18546688

flashfs[3]: Bytes available: 13193216

flashfs[3]: flashfs fsck took 9 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 8764 8000 0 A8000000 A8010000 0

Rate table has 244 entries (64 SGI/104 BF variants)

Radio1 present 8764 8000 0 88000000 88010000 4

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

memory validate-checksum 30

^

% Invalid input detected at '^' marker.

login authentication default

^

% Invalid input detected at '^' marker.

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

export@cisco.com.

Warning: the compile-time code checksum does not appear to be present.

cisco AIR-CAP2602I-E-K9 (PowerPC) processor (revision A0) with 180214K/81920K bytes of memory.

Processor board ID FCZ1725D0YZ

PowerPC CPU at 800Mhz, revision number 0x2151

Last reset from power-on

LWAPP image version 7.4.110.0

1 Gigabit Ethernet interface

2 802.11 Radios

32K bytes of flash-simulated non-volatile configuration memory.

Base ethernet MAC Address: 6C:41:6A:CA:47:F8

Part Number : 73-14588-02

PCA Assembly Number : 800-37899-01

PCA Revision Number : A0

PCB Serial Number : FOC17194GLV

Top Assembly Part Number : 800-38356-01

Top Assembly Serial Number : FCZ1725D0YZ

Top Revision Number : A0

Product/Model Number : AIR-CAP2602I-E-K9

% Please define a domain-name first.

Press RETURN to get started!

*Mar 1 00:00:10.315: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed

*Mar 1 00:00:10.315: %IFMGR-7-NO_IFINDEX_FILE: Unable to open nvram:/ifIndex-table No such file or directory

*Mar 1 00:00:13.827: %LINK-6-UPDOWN: Interface GigabitEthernet0, changed state to up

*Mar 1 00:00:17.495: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0

*Mar 1 00:00:23.867: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1

*Mar 1 00:00:26.403: %SYS-5-RESTART: System restarted --

Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.2(2)JB2, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Compiled Mon 29-Jul-13 11:27 by prod_rel_team

*Mar 1 00:00:26.403: %SNMP-5-COLDSTART: SNMP agent on host AP6c41.6aca.47f8 is undergoing a cold start

*Mar 1 00:00:26.459: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar 1 00:00:26.459: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to resetlwapp_crypto_init: MIC Present and Parsed Successfully

*Mar 1 00:00:26.623: %SSH-5-ENABLED: SSH 2.0 has been enabled

*Mar 1 00:00:26.971: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down

*Mar 1 00:00:27.455: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up

*Mar 1 00:00:27.467: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Mar 1 00:00:27.467: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Mar 1 00:00:30.003: %SOAP_FIPS-2-SELF_TEST_HW_SUCCESS: HW crypto FIPS self test passed

*Mar 1 00:00:30.003: DPAA Initialization Complete

*Mar 1 00:00:30.003: %SYS-3-HARIKARI: Process DPAA INIT top-level routine exited

*Mar 1 00:00:31.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up%Default route without gateway, if not a point-to-point interface, may impact performance

*Mar 1 00:00:55.327: Logging LWAPP message to 255.255.255.255.

*Mar 1 00:00:55.575: %CDP_PD-4-POWER_OK: Full power - LOW_POWER_CLASSIC_NO_INJECTOR_CONFIGURED inline power source

*Mar 1 00:00:55.939: %CDP_PD-4-POWER_OK: Full power - INJECTOR_DETECTED_MULTIPLE_MACS_ON_HUB inline power source

*Mar 1 00:00:56.671: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar 1 00:00:57.671: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Mar 1 00:00:57.763: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Mar 1 00:00:58.763: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Mar 1 00:01:00.695: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.6.0.42, mask 255.255.255.0, hostname AP6c41.6aca.47f8

Translating "CISCO-CAPWAP-CONTROLLER.ph.truphone.local"...domain server (10.6.0.30) [OK]

*Mar 1 00:01:11.671: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar 1 00:01:21.671: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 24 09:47:28.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:47:28.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:47:28.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:47:33.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:47:51.635: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)

., 1)

*Oct 24 09:47:51.635: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Oct 24 09:47:51.635: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.6.0.250:5246

*Oct 24 09:47:51.695: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Oct 24 09:47:51.707: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Oct 24 09:47:51.707: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Oct 24 09:47:51.719: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:47:51.739: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:47:52.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:47:52.747: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Oct 24 09:47:52.755: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Oct 24 09:47:53.739: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 24 09:47:53.747: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Oct 24 09:47:53.775: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:47:53.783: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Oct 24 09:47:53.791: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Oct 24 09:47:54.775: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Oct 24 09:47:54.783: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:47:54.811: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:47:55.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 24 09:48:01.735: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 24 09:48:01.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:48:01.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:48:01.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:48:06.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:48:24.635: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)

., 1)

*Oct 24 09:48:24.635: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Oct 24 09:48:24.635: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.6.0.250:5246

*Oct 24 09:48:24.695: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Oct 24 09:48:24.707: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Oct 24 09:48:24.707: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Oct 24 09:48:24.719: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:48:24.731: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:48:25.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:48:25.743: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Oct 24 09:48:25.751: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Oct 24 09:48:26.735: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 24 09:48:26.743: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Oct 24 09:48:26.771: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:48:26.779: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Oct 24 09:48:26.787: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Oct 24 09:48:27.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Oct 24 09:48:27.779: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:48:27.807: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:48:28.807: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 24 09:48:34.731: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 24 09:48:35.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:48:35.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:48:35.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:48:40.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:48:58.635: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)

., 1)

*Oct 24 09:48:58.635: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Oct 24 09:48:58.635: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.6.0.250:5246

*Oct 24 09:48:58.691: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Oct 24 09:48:58.707: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Oct 24 09:48:58.707: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Oct 24 09:48:58.719: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:48:58.731: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:48:59.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:48:59.743: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Oct 24 09:48:59.751: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Oct 24 09:49:00.735: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 24 09:49:00.743: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Oct 24 09:49:00.771: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:49:00.779: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Oct 24 09:49:00.787: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Oct 24 09:49:01.771: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Oct 24 09:49:01.779: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:49:01.807: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:49:02.807: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 24 09:49:08.731: %CAPWAP-3-ERRORLOG: Go join a capwap controller

*Oct 24 09:49:09.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:49:09.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.6.0.250 peer_port: 5246

*Oct 24 09:49:09.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:49:14.467: %CAPWAP-5-SENDJOIN: sending Join Request to 10.6.0.250

*Oct 24 09:49:32.639: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(UNKNOWN_MESSAGE_TYPE (5)

., 1)

*Oct 24 09:49:32.639: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE

*Oct 24 09:49:32.639: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.6.0.250:5246

*Oct 24 09:49:32.695: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255

*Oct 24 09:49:32.711: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Oct 24 09:49:32.711: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Oct 24 09:49:32.723: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:49:32.735: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:49:33.711: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:49:33.747: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down

*Oct 24 09:49:33.755: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Oct 24 09:49:34.739: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Oct 24 09:49:34.747: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Oct 24 09:49:34.775: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up

*Oct 24 09:49:34.783: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down

*Oct 24 09:49:34.791: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Oct 24 09:49:35.775: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Oct 24 09:49:35.783: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down

*Oct 24 09:49:35.811: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up

*Oct 24 09:49:36.811: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

Controller

(Cisco Controller) >*spamApTask2: Oct 24 09:47:28.240: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:28.240: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask2: Oct 24 09:47:28.241: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:28.241: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:28.241: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask2: Oct 24 09:47:28.242: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:38.239: 6c:41:6a:ca:47:f0 DTLS connection not found, creating new connection for 10:6:0:42 (42112) 10:6:0:250 (5246)

*spamApTask2: Oct 24 09:47:38.705: 6c:41:6a:ca:47:f0 Allocated index from main list, Index: 479

*spamApTask2: Oct 24 09:47:38.705: 6c:41:6a:ca:47:f0 DTLS keys for Control Plane are plumbed successfully for AP 10.6.0.42. Index 480

*spamApTask2: Oct 24 09:47:38.706: 6c:41:6a:ca:47:f0 DTLS Session established server (10.6.0.250:5246), client (10.6.0.42:42112)

*spamApTask2: Oct 24 09:47:38.706: 6c:41:6a:ca:47:f0 Starting wait join timer for AP: 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:43.707: d0:c7:89:24:76:60 Join Request from 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:43.707: 6c:41:6a:ca:47:f0 Deleting AP entry 10.6.0.42:42112 from temporary database.

*spamApTask2: Oct 24 09:47:43.708: d0:c7:89:24:76:60 Join Version: = 117730816

*spamApTask2: Oct 24 09:47:43.708: d0:c7:89:24:76:60 Join resp: CAPWAP Maximum Msg element len = 98

*spamApTask2: Oct 24 09:47:43.708: d0:c7:89:24:76:60 Join Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:43.708: d0:c7:89:24:76:60 CAPWAP State: Join

*spamApTask2: Oct 24 09:47:43.708: d0:c7:89:24:76:60 capwap_ac_platform.c:1225 - Operation State 0 ===> 4

*apfReceiveTask: Oct 24 09:47:43.709: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 24 09:47:43.710: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 Configuration Status from 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 CAPWAP State: Configure

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 Updating IP info for AP d0:c7:89:24:76:60 -- static 0, 10.6.0.42/255.255.255.0, gtw 10.6.0.1

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 Updating IP 10.6.0.42 ===> 10.6.0.42 for AP d0:c7:89:24:76:60

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 Channel 13 is invalid in the domain

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask2: Oct 24 09:47:43.878: d0:c7:89:24:76:60 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamApTask2: Oct 24 09:47:43.879: d0:c7:89:24:76:60 Channel 140 is invalid in the domain

*spamApTask2: Oct 24 09:47:43.879: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask2: Oct 24 09:47:43.879: d0:c7:89:24:76:60 Regulatory Domain Mismatch: AP d0:c7:89:24:76:60 not allowed to join. Regulatory Domain check failed.

Allow

*spamApTask2: Oct 24 09:47:43.879: d0:c7:89:24:76:60 Finding DTLS connection to delete for AP (10:6:0:42/42112)

*spamApTask2: Oct 24 09:47:43.879: d0:c7:89:24:76:60 Disconnecting DTLS Capwap-Ctrl session 0x1705a848 for AP (10:6:0:42/42112)

*spamApTask2: Oct 24 09:47:43.879: d0:c7:89:24:76:60 CAPWAP State: Dtls tear down

*spamApTask2: Oct 24 09:47:43.880: d0:c7:89:24:76:60 DTLS keys for Control Plane deleted successfully for AP 10.6.0.42

*spamApTask2: Oct 24 09:47:43.887: d0:c7:89:24:76:60 Failed post decode processing of config status from 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:43.887: d0:c7:89:24:76:60 State machine handler: Failed to process msg type = 5 state = 5 from 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:43.887: 6c:41:6a:ca:47:f0 Failed to parse CAPWAP packet from 10.6.0.42:42112

*spamApTask2: Oct 24 09:47:43.887: d0:c7:89:24:76:60 DTLS connection closed event receivedserver (10:6:0:250/5246) client (10:6:0:42/42112)

*spamApTask2: Oct 24 09:47:43.887: d0:c7:89:24:76:60 Entry exists for AP (10:6:0:42/42112)

*spamApTask2: Oct 24 09:47:43.887: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 0

*spamApTask2: Oct 24 09:47:43.887: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 24 09:47:43.888: d0:c7:89:24:76:60 No AP entry exist in temporary database for 10.6.0.42:42112

*apfReceiveTask: Oct 24 09:47:43.889: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 24 09:47:43.889: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 24 09:48:01.876: 6c:41:6a:ca:47:f0 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 10.6.0.42:42112)since DTLS session is not established

*spamApTask3: Oct 24 09:48:01.979: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:01.979: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 24 09:48:01.979: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:01.980: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:01.980: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 24 09:48:01.980: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:01.980: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:01.980: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 24 09:48:01.981: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:11.976: d0:c7:89:24:76:60 DTLS connection not found, creating new connection for 10:6:0:42 (42113) 10:6:0:250 (5246)

*spamApTask3: Oct 24 09:48:12.444: d0:c7:89:24:76:60 Allocated index from main list, Index: 480

*spamApTask3: Oct 24 09:48:12.444: d0:c7:89:24:76:60 DTLS keys for Control Plane are plumbed successfully for AP 10.6.0.42. Index 481

*spamApTask3: Oct 24 09:48:12.444: d0:c7:89:24:76:60 DTLS Session established server (10.6.0.250:5246), client (10.6.0.42:42113)

*spamApTask3: Oct 24 09:48:12.445: d0:c7:89:24:76:60 Starting wait join timer for AP: 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:17.444: d0:c7:89:24:76:60 Join Request from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:17.444: d0:c7:89:24:76:60 Deleting AP entry 10.6.0.42:42113 from temporary database.

*spamApTask3: Oct 24 09:48:17.445: d0:c7:89:24:76:60 Join Version: = 117730816

*spamApTask3: Oct 24 09:48:17.445: d0:c7:89:24:76:60 Join resp: CAPWAP Maximum Msg element len = 98

*spamApTask3: Oct 24 09:48:17.445: d0:c7:89:24:76:60 Join Response sent to 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:17.445: d0:c7:89:24:76:60 CAPWAP State: Join

*spamApTask3: Oct 24 09:48:17.445: d0:c7:89:24:76:60 capwap_ac_platform.c:1225 - Operation State 0 ===> 4

*apfReceiveTask: Oct 24 09:48:17.445: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 24 09:48:17.446: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 Configuration Status from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 CAPWAP State: Configure

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 Updating IP info for AP d0:c7:89:24:76:60 -- static 0, 10.6.0.42/255.255.255.0, gtw 10.6.0.1

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 Updating IP 10.6.0.42 ===> 10.6.0.42 for AP d0:c7:89:24:76:60

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 Channel 13 is invalid in the domain

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask3: Oct 24 09:48:17.614: d0:c7:89:24:76:60 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamApTask3: Oct 24 09:48:17.615: d0:c7:89:24:76:60 Channel 140 is invalid in the domain

*spamApTask3: Oct 24 09:48:17.615: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask3: Oct 24 09:48:17.615: d0:c7:89:24:76:60 Regulatory Domain Mismatch: AP d0:c7:89:24:76:60 not allowed to join. Regulatory Domain check failed.

Allow

*spamApTask3: Oct 24 09:48:17.615: d0:c7:89:24:76:60 Finding DTLS connection to delete for AP (10:6:0:42/42113)

*spamApTask3: Oct 24 09:48:17.615: d0:c7:89:24:76:60 Disconnecting DTLS Capwap-Ctrl session 0x1705a9a0 for AP (10:6:0:42/42113)

*spamApTask3: Oct 24 09:48:17.615: d0:c7:89:24:76:60 CAPWAP State: Dtls tear down

*spamApTask3: Oct 24 09:48:17.616: d0:c7:89:24:76:60 DTLS keys for Control Plane deleted successfully for AP 10.6.0.42

*spamApTask3: Oct 24 09:48:17.623: d0:c7:89:24:76:60 Failed post decode processing of config status from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:17.623: d0:c7:89:24:76:60 State machine handler: Failed to process msg type = 5 state = 5 from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:17.623: d0:c7:89:24:76:60 Failed to parse CAPWAP packet from 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:17.623: d0:c7:89:24:76:60 DTLS connection closed event receivedserver (10:6:0:250/5246) client (10:6:0:42/42113)

*spamApTask3: Oct 24 09:48:17.623: d0:c7:89:24:76:60 Entry exists for AP (10:6:0:42/42113)

*spamApTask3: Oct 24 09:48:17.623: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 24 09:48:17.623: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 24 09:48:17.624: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask3: Oct 24 09:48:17.625: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask3: Oct 24 09:48:17.626: d0:c7:89:24:76:60 No AP entry exist in temporary database for 10.6.0.42:42113

*spamApTask3: Oct 24 09:48:35.613: d0:c7:89:24:76:60 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 10.6.0.42:42113)since DTLS session is not established

*spamApTask2: Oct 24 09:48:35.711: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:35.711: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask2: Oct 24 09:48:35.711: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:35.712: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:35.712: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:35.712: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask2: Oct 24 09:48:35.713: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:35.713: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:35.713: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask2: Oct 24 09:48:35.713: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:45.709: 6c:41:6a:ca:47:f0 DTLS connection not found, creating new connection for 10:6:0:42 (42112) 10:6:0:250 (5246)

*spamApTask2: Oct 24 09:48:46.177: 6c:41:6a:ca:47:f0 Allocated index from main list, Index: 481

*spamApTask2: Oct 24 09:48:46.177: 6c:41:6a:ca:47:f0 DTLS keys for Control Plane are plumbed successfully for AP 10.6.0.42. Index 482

*spamApTask2: Oct 24 09:48:46.178: 6c:41:6a:ca:47:f0 DTLS Session established server (10.6.0.250:5246), client (10.6.0.42:42112)

*spamApTask2: Oct 24 09:48:46.178: 6c:41:6a:ca:47:f0 Starting wait join timer for AP: 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:51.177: d0:c7:89:24:76:60 Join Request from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:51.177: 6c:41:6a:ca:47:f0 Deleting AP entry 10.6.0.42:42112 from temporary database.

*spamApTask2: Oct 24 09:48:51.178: d0:c7:89:24:76:60 Join Version: = 117730816

*spamApTask2: Oct 24 09:48:51.178: d0:c7:89:24:76:60 Join resp: CAPWAP Maximum Msg element len = 98

*spamApTask2: Oct 24 09:48:51.178: d0:c7:89:24:76:60 Join Response sent to 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:51.178: d0:c7:89:24:76:60 CAPWAP State: Join

*spamApTask2: Oct 24 09:48:51.178: d0:c7:89:24:76:60 capwap_ac_platform.c:1225 - Operation State 0 ===> 4

*apfReceiveTask: Oct 24 09:48:51.179: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 24 09:48:51.179: d0:c7:89:24:76:60 Register LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 24 09:48:51.346: d0:c7:89:24:76:60 Configuration Status from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:51.346: d0:c7:89:24:76:60 CAPWAP State: Configure

*spamApTask2: Oct 24 09:48:51.346: d0:c7:89:24:76:60 Updating IP info for AP d0:c7:89:24:76:60 -- static 0, 10.6.0.42/255.255.255.0, gtw 10.6.0.1

*spamApTask2: Oct 24 09:48:51.346: d0:c7:89:24:76:60 Updating IP 10.6.0.42 ===> 10.6.0.42 for AP d0:c7:89:24:76:60

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 Channel 13 is invalid in the domain

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 Channel 140 is invalid in the domain

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 AP d0:c7:89:24:76:60: Invalid country code ().

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 Regulatory Domain Mismatch: AP d0:c7:89:24:76:60 not allowed to join. Regulatory Domain check failed.

Allow

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 Finding DTLS connection to delete for AP (10:6:0:42/42112)

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 Disconnecting DTLS Capwap-Ctrl session 0x1705aaf8 for AP (10:6:0:42/42112)

*spamApTask2: Oct 24 09:48:51.347: d0:c7:89:24:76:60 CAPWAP State: Dtls tear down

*spamApTask2: Oct 24 09:48:51.348: d0:c7:89:24:76:60 DTLS keys for Control Plane deleted successfully for AP 10.6.0.42

*spamApTask2: Oct 24 09:48:51.355: d0:c7:89:24:76:60 Failed post decode processing of config status from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:51.355: d0:c7:89:24:76:60 State machine handler: Failed to process msg type = 5 state = 5 from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:51.356: 6c:41:6a:ca:47:f0 Failed to parse CAPWAP packet from 10.6.0.42:42112

*spamApTask2: Oct 24 09:48:51.356: d0:c7:89:24:76:60 DTLS connection closed event receivedserver (10:6:0:250/5246) client (10:6:0:42/42112)

*spamApTask2: Oct 24 09:48:51.356: d0:c7:89:24:76:60 Entry exists for AP (10:6:0:42/42112)

*spamApTask2: Oct 24 09:48:51.356: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 0

*spamApTask2: Oct 24 09:48:51.356: d0:c7:89:24:76:60 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 24 09:48:51.357: d0:c7:89:24:76:60 No AP entry exist in temporary database for 10.6.0.42:42112

*apfReceiveTask: Oct 24 09:48:51.357: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 0

*apfReceiveTask: Oct 24 09:48:51.357: d0:c7:89:24:76:60 Deregister LWAPP event for AP d0:c7:89:24:76:60 slot 1

*spamApTask2: Oct 24 09:49:09.346: 6c:41:6a:ca:47:f0 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 10.6.0.42:42112)since DTLS session is not established

*spamApTask3: Oct 24 09:49:09.444: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 24 09:49:09.444: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 24 09:49:09.445: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

*spamApTask3: Oct 24 09:49:09.445: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 24 09:49:09.445: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 24 09:49:09.446: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

*spamApTask3: Oct 24 09:49:09.446: d0:c7:89:24:76:60 Discovery Request from 10.6.0.42:42113

*spamApTask3: Oct 24 09:49:09.446: d0:c7:89:24:76:60 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0

*spamApTask3: Oct 24 09:49:09.446: d0:c7:89:24:76:60 Discovery Response sent to 10.6.0.42:42113

Joseph Vasanth Louis · ‎10-24-2013

Hi lee,

Looks like you there is a Reg domain mismatch. check your country code settings on the controller.

leewray01 · ‎10-24-2013

Configured Country............................... PH - Philippines

How do I know what country code my AP's are using? I can just change this on the controller correct?

leewray01 · ‎10-24-2013

Looking at the debug, the following jumps out at me;

Updating IP info for AP d0:c7:89:24:76:60 -- static 0, 10.6.0.42/255.255.255.0, gtw 10.6.0.1