topic WLC and AP in Wireless

WLC and AP

Kamran Mustafayev — Sun, 04 Jul 2021 05:03:19 GMT

Hello guys,

I have an error when wlc trying to connect my 1042 access point

here is error

my wlc is nm-wlc intergrated module

ap and wlc have the same code version 7.0

%LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Apr 26 09:02:27.419: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Apr 26 09:02:27.445: status of voice_diag_test from WLC is false

*Apr 26 09:02:38.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.1.11 peer_port: 5246

*Apr 26 09:02:38.001: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Apr 26 09:02:39.116: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.1.11 peer_port: 5246

*Apr 26 09:02:39.117: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.1.11

*Apr 26 09:02:39.118: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Apr 26 09:02:39.291: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Apr 26 09:02:39.292: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.1.11

*Apr 26 09:02:39.293: %DTLS-5-PEER_DISCONNECT: Peer 172.16.1.11 has closed connection.

*Apr 26 09:02:39.293: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.1.11:5246

*Apr 26 09:02:39.346: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Apr 26 09:02:39.447: status of voice_diag_test from WLC is false

*Apr 26 09:02:49.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.1.11 peer_port: 5246

*Apr 26 09:02:49.001: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Apr 26 09:02:50.114: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.1.11 peer_port: 5246

*Apr 26 09:02:50.115: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.1.11

*Apr 26 09:02:50.115: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Apr 26 09:02:50.287: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Apr 26 09:02:50.289: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.1.11

*Apr 26 09:02:50.289: %DTLS-5-PEER_DISCONNECT: Peer 172.16.1.11 has closed connection.

*Apr 26 09:02:50.289: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.1.11:5246

*Apr 26 09:02:50.344: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Apr 26 09:02:50.370: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Apr 26 09:02:50.370: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down

*Apr 26 09:02:51.325: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Apr 26 09:02:51.352: status of voice_diag_test from WLC is false

*Apr 26 09:02:51.352: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Apr 26 09:02:51.360: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Apr 26 09:02:51.372: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset

*Apr 26 09:02:51.372: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down

*Apr 26 09:02:51.386: %LINK-3-UPDOWN: Interface Dot11Radio1, changed state to up

*Apr 26 09:02:52.386: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up

*Apr 26 09:03:02.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.1.11 peer_port: 5246

*Apr 26 09:03:02.001: %CAPWAP-5-CHANGED: CAPWAP changed state to

*Apr 26 09:03:03.109: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.1.11 peer_port: 5246

*Apr 26 09:03:03.110: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.1.11

*Apr 26 09:03:03.110: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Apr 26 09:03:03.285: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG

*Apr 26 09:03:03.287: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.1.11

Building configuration...

CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination

WLC and AP

Stephen Rodriguez — Wed, 25 Apr 2012 17:10:58 GMT

what version of 7.0 are you running on the WLC?

Steve

WLC and AP

Kamran Mustafayev — Wed, 25 Apr 2012 17:13:15 GMT

7,0.240.0 version, when i connected AP to switch, its automaticaly joined to it, received Image from wlc, but after that an error

%DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.1.11 appears, and it begin to discover process again

WLC and AP

Stephen Rodriguez — Wed, 25 Apr 2012 17:21:49 GMT

can you grab the following debugs from the WLC:

debug mac-address < ap mac address>

debug capwap events enable

debug capwap erros enable

Steve

WLC and AP

Kamran Mustafayev — Wed, 25 Apr 2012 17:24:58 GMT

WLC and AP

Leo Laohoo — Wed, 25 Apr 2012 22:22:57 GMT

Can you please post the output to the following commands:

1. WLC: sh sysinfo;

2. WAP: sh inventory

WLC and AP

Kamran Mustafayev — Thu, 26 Apr 2012 04:38:27 GMT

Guys here is all diagnostics

WAP

#show inventory

NAME: "AP1040", DESCR: "Cisco Aironet 1040 Series (IEEE 802.11n) Access Point"

PID: AIR-AP1042N-E-K9 , VID: V02, SN: FCZ1537W1MW

WLC

show sysinfo

Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version.................................. 7.0.230.0

RTOS Version..................................... 7.0.230.0

Bootloader Version............................... 7.0.230.0

Emergency Image Version.......................... N/A

Build Type....................................... DATA + WPS

System Name...................................... Cisco_cc:c4:20

System Location..................................

System Contact...................................

System ObjectID.................................. 1.3.6.1.4.1.9.1.818

IP Address....................................... 172.16.1.10

System Up Time................................... 0 days 19 hrs 17 mins 2 secs

System Timezone Location.........................

Configured Country............................... US - United States

State of 802.11b Network......................... Enabled

State of 802.11a Network......................... Enabled

--More-- or (q)uit

Number of WLANs.................................. 1

Number of Active Clients......................... 0

Burned-in MAC Address............................ 00:1E:BE:CC:C4:20

Maximum number of APs supported.................. 8

debug capwap events enable

>debug capwap events enable

(Cisco Controller) >*spamReceiveTask: Apr 26 16:30:25.589: 68:bc:0c:0b:ca:a0 DTLS connection not found, creating new connection for 172:16:100:132 (38305) 172:16:1:11 (5246)

*spamReceiveTask: Apr 26 16:30:26.715: 68:bc:0c:0b:ca:a0 DTLS Session established server (172.16.1.11:5246), client (172.16.100.132:38305)

*spamReceiveTask: Apr 26 16:30:26.715: 68:bc:0c:0b:ca:a0 Starting wait join timer for AP: 172.16.100.132:38305

d*spamReceiveTask: Apr 26 16:30:26.718: 68:bc:0c:0b:ca:a0 Join Request from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:26.718: 68:bc:0c:0b:ca:a0 Deleting AP entry 172.16.100.132:38305 from temporary database.

*spamReceiveTask: Apr 26 16:30:26.720: 68:bc:0c:0b:ca:a0 Join Version: = 117499392

*spamReceiveTask: Apr 26 16:30:26.720: 68:bc:0c:0b:ca:a0 Join resp: CAPWAP Maximum Msg element len = 91

*spamReceiveTask: Apr 26 16:30:26.720: 68:bc:0c:0b:ca:a0 Join Response sent to 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:26.720: 68:bc:0c:0b:ca:a0 CAPWAP State: Join

*spamReceiveTask: Apr 26 16:30:26.720: 68:bc:0c:0b:ca:a0 capwap_ac_platform.c:1217 - Operation State 0 ===> 4

*apfReceiveTask: Apr 26 16:30:26.721: 68:bc:0c:0b:ca:a0 Register LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*apfReceiveTask: Apr 26 16:30:26.721: WARP IEs: (12)

*apfReceiveTask: Apr 26 16:30:26.721: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*apfReceiveTask: Apr 26 16:30:26.721: 68:bc:0c:0b:ca:a0 Register LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*apfReceiveTask: Apr 26 16:30:26.721: WARP IEs: (12)

*apfReceiveTask: Apr 26 16:30:26.721: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*spamReceiveTask: Apr 26 16:30:26.840: 68:bc:0c:0b:ca:a0 Configuration Status from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:26.840: 68:bc:0c:0b:ca:a0 CAPWAP State: Configure

*spamReceiveTask: Apr 26 16:30:26.840: Invalid channel 1 spacified for the AP AP7081.05c9.5a08, slotId = 0

*spamReceiveTask: Apr 26 16:30:26.840: Invalid channel 64 spacified for the AP AP7081.05c9.5a08, slotId = 1

*spamReceiveTask: Apr 26 16:30:26.840: 68:bc:0c:0b:ca:a0 Updating IP info for AP 68:bc:0c:0b:ca:a0 -- static 1, 10.0.0.4/255.255.255.0, gtw 172.30.30.1

*spamReceiveTask: Apr 26 16:30:26.841: 68:bc:0c:0b:ca:a0 Updated IP Domain info for AP 68:bc:0c:0b:ca:a0 -- set 0, Domain

*spamReceiveTask: Apr 26 16:30:26.841: 68:bc:0c:0b:ca:a0 Updating IP NamServer info for AP 68:bc:0c:0b:ca:a0 -- set 0, nameserver 0.0.0.0

*spamReceiveTask: Apr 26 16:30:26.841: 68:bc:0c:0b:ca:a0 Setting MTU to 1485

*spamReceiveTask: Apr 26 16:30:26.841: 68:bc:0c:0b:ca:a0 Finding DTLS connection to delete for AP (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:26.841: 68:bc:0c:0b:ca:a0 Disconnecting DTLS Capwap-Ctrl session 0xa0726f4 for AP (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:26.841: 68:bc:0c:0b:ca:a0 CAPWAP State: Dtls tear down

*spamReceiveTask: Apr 26 16:30:26.842: 68:bc:0c:0b:ca:a0 DTLS connection closed event receivedserver (172:16:1:11/5246) client (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:26.842: 68:bc:0c:0b:ca:a0 Entry exists for AP (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:26.842: 68:bc:0c:0b:ca:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*spamReceiveTask: Apr 26 16:30:26.842: 68:bc:0c:0b:ca:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*spamReceiveTask: Apr 26 16:30:26.842: 68:bc:0c:0b:ca:a0 No AP entry exist in temporary database for 172.16.100.132:38305

*apfReceiveTask: Apr 26 16:30:26.842: 68:bc:0c:0b:ca:a0 Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*apfReceiveTask: Apr 26 16:30:26.842: 68:bc:0c:0b:ca:a0 Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*spamReceiveTask: Apr 26 16:30:27.002: 68:bc:0c:0b:ca:a0 Discovery Request from 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:30:27.002: 68:bc:0c:0b:ca:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 8, joined Aps =0

*spamReceiveTask: Apr 26 16:30:27.002: 68:bc:0c:0b:ca:a0 Discovery Response sent to 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:30:37.243: 68:bc:0c:0b:ca:a0 DTLS connection not found, creating new connection for 172:16:100:132 (38306) 172:16:1:11 (5246)

*spamReceiveTask: Apr 26 16:30:38.365: 68:bc:0c:0b:ca:a0 DTLS Session established server (172.16.1.11:5246), client (172.16.100.132:38306)

*spamReceiveTask: Apr 26 16:30:38.365: 68:bc:0c:0b:ca:a0 Starting wait join timer for AP: 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:30:38.368: 68:bc:0c:0b:ca:a0 Join Request from 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:30:38.369: 68:bc:0c:0b:ca:a0 Deleting AP entry 172.16.100.132:38306 from temporary database.

*spamReceiveTask: Apr 26 16:30:38.370: 68:bc:0c:0b:ca:a0 Join Version: = 117499392

*spamReceiveTask: Apr 26 16:30:38.370: 68:bc:0c:0b:ca:a0 Join resp: CAPWAP Maximum Msg element len = 91

*spamReceiveTask: Apr 26 16:30:38.370: 68:bc:0c:0b:ca:a0 Join Response sent to 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:30:38.370: 68:bc:0c:0b:ca:a0 CAPWAP State: Join

*spamReceiveTask: Apr 26 16:30:38.370: 68:bc:0c:0b:ca:a0 capwap_ac_platform.c:1217 - Operation State 0 ===> 4

*apfReceiveTask: Apr 26 16:30:38.371: 68:bc:0c:0b:ca:a0 Register LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*apfReceiveTask: Apr 26 16:30:38.371: WARP IEs: (12)

*apfReceiveTask: Apr 26 16:30:38.371: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*apfReceiveTask: Apr 26 16:30:38.371: 68:bc:0c:0b:ca:a0 Register LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*apfReceiveTask: Apr 26 16:30:38.371: WARP IEs: (12)

*apfReceiveTask: Apr 26 16:30:38.371: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*spamReceiveTask: Apr 26 16:30:38.490: 68:bc:0c:0b:ca:a0 Configuration Status from 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:30:38.490: 68:bc:0c:0b:ca:a0 CAPWAP State: Configure

*spamReceiveTask: Apr 26 16:30:38.490: Invalid channel 1 spacified for the AP AP7081.05c9.5a08, slotId = 0

*spamReceiveTask: Apr 26 16:30:38.490: Invalid channel 157 spacified for the AP AP7081.05c9.5a08, slotId = 1

*spamReceiveTask: Apr 26 16:30:38.490: 68:bc:0c:0b:ca:a0 Updating IP info for AP 68:bc:0c:0b:ca:a0 -- static 1, 10.0.0.4/255.255.255.0, gtw 172.30.30.1

*spamReceiveTask: Apr 26 16:30:38.490: 68:bc:0c:0b:ca:a0 Updated IP Domain info for AP 68:bc:0c:0b:ca:a0 -- set 0, Domain

*spamReceiveTask: Apr 26 16:30:38.490: 68:bc:0c:0b:ca:a0 Updating IP NamServer info for AP 68:bc:0c:0b:ca:a0 -- set 0, nameserver 0.0.0.0

*spamReceiveTask: Apr 26 16:30:38.490: 68:bc:0c:0b:ca:a0 Setting MTU to 1485

*spamReceiveTask: Apr 26 16:30:38.491: 68:bc:0c:0b:ca:a0 Finding DTLS connection to delete for AP (172:16:100:132/38306)

*spamReceiveTask: Apr 26 16:30:38.491: 68:bc:0c:0b:ca:a0 Disconnecting DTLS Capwap-Ctrl session 0xa0727d8 for AP (172:16:100:132/38306)

*spamReceiveTask: Apr 26 16:30:38.491: 68:bc:0c:0b:ca:a0 CAPWAP State: Dtls tear down

*spamReceiveTask: Apr 26 16:30:38.491: 68:bc:0c:0b:ca:a0 DTLS connection closed event receivedserver (172:16:1:11/5246) client (172:16:100:132/38306)

*spamReceiveTask: Apr 26 16:30:38.491: 68:bc:0c:0b:ca:a0 Entry exists for AP (172:16:100:132/38306)

*spamReceiveTask: Apr 26 16:30:38.492: 68:bc:0c:0b:ca:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*spamReceiveTask: Apr 26 16:30:38.492: 68:bc:0c:0b:ca:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*spamReceiveTask: Apr 26 16:30:38.492: 68:bc:0c:0b:ca:a0 No AP entry exist in temporary database for 172.16.100.132:38306

*apfReceiveTask: Apr 26 16:30:38.492: 68:bc:0c:0b:ca:a0 Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*apfReceiveTask: Apr 26 16:30:38.492: 68:bc:0c:0b:ca:a0 Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*spamReceiveTask: Apr 26 16:30:39.795: 68:bc:0c:0b:ca:a0 Discovery Request from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:39.795: 68:bc:0c:0b:ca:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 8, joined Aps =0

*spamReceiveTask: Apr 26 16:30:39.795: 68:bc:0c:0b:ca:a0 Discovery Response sent to 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:50.035: 68:bc:0c:0b:ca:a0 DTLS connection not found, creating new connection for 172:16:100:132 (38305) 172:16:1:11 (5246)

*spamReceiveTask: Apr 26 16:30:51.158: 68:bc:0c:0b:ca:a0 DTLS Session established server (172.16.1.11:5246), client (172.16.100.132:38305)

*spamReceiveTask: Apr 26 16:30:51.158: 68:bc:0c:0b:ca:a0 Starting wait join timer for AP: 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:51.162: 68:bc:0c:0b:ca:a0 Join Request from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:51.162: 68:bc:0c:0b:ca:a0 Deleting AP entry 172.16.100.132:38305 from temporary database.

*spamReceiveTask: Apr 26 16:30:51.163: 68:bc:0c:0b:ca:a0 Join Version: = 117499392

*spamReceiveTask: Apr 26 16:30:51.163: 68:bc:0c:0b:ca:a0 Join resp: CAPWAP Maximum Msg element len = 91

*spamReceiveTask: Apr 26 16:30:51.164: 68:bc:0c:0b:ca:a0 Join Response sent to 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:51.164: 68:bc:0c:0b:ca:a0 CAPWAP State: Join

*spamReceiveTask: Apr 26 16:30:51.164: 68:bc:0c:0b:ca:a0 capwap_ac_platform.c:1217 - Operation State 0 ===> 4

*apfReceiveTask: Apr 26 16:30:51.164: 68:bc:0c:0b:ca:a0 Register LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*apfReceiveTask: Apr 26 16:30:51.164: WARP IEs: (12)

*apfReceiveTask: Apr 26 16:30:51.164: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*apfReceiveTask: Apr 26 16:30:51.164: 68:bc:0c:0b:ca:a0 Register LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*apfReceiveTask: Apr 26 16:30:51.164: WARP IEs: (12)

*apfReceiveTask: Apr 26 16:30:51.164: [0000] dd 0a 00 c0 b9 01 00 00 00 08 01 01

*spamReceiveTask: Apr 26 16:30:51.284: 68:bc:0c:0b:ca:a0 Configuration Status from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:30:51.284: 68:bc:0c:0b:ca:a0 CAPWAP State: Configure

*spamReceiveTask: Apr 26 16:30:51.284: Invalid channel 1 spacified for the AP AP7081.05c9.5a08, slotId = 0

*spamReceiveTask: Apr 26 16:30:51.284: Invalid channel 36 spacified for the AP AP7081.05c9.5a08, slotId = 1

*spamReceiveTask: Apr 26 16:30:51.284: 68:bc:0c:0b:ca:a0 Updating IP info for AP 68:bc:0c:0b:ca:a0 -- static 1, 10.0.0.4/255.255.255.0, gtw 172.30.30.1

*spamReceiveTask: Apr 26 16:30:51.285: 68:bc:0c:0b:ca:a0 Updated IP Domain info for AP 68:bc:0c:0b:ca:a0 -- set 0, Domain

*spamReceiveTask: Apr 26 16:30:51.285: 68:bc:0c:0b:ca:a0 Updating IP NamServer info for AP 68:bc:0c:0b:ca:a0 -- set 0, nameserver 0.0.0.0

*spamReceiveTask: Apr 26 16:30:51.285: 68:bc:0c:0b:ca:a0 Setting MTU to 1485

*spamReceiveTask: Apr 26 16:30:51.285: 68:bc:0c:0b:ca:a0 Finding DTLS connection to delete for AP (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:51.285: 68:bc:0c:0b:ca:a0 Disconnecting DTLS Capwap-Ctrl session 0xa0728bc for AP (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:51.285: 68:bc:0c:0b:ca:a0 CAPWAP State: Dtls tear down

*spamReceiveTask: Apr 26 16:30:51.286: 68:bc:0c:0b:ca:a0 DTLS connection closed event receivedserver (172:16:1:11/5246) client (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:51.286: 68:bc:0c:0b:ca:a0 Entry exists for AP (172:16:100:132/38305)

*spamReceiveTask: Apr 26 16:30:51.286: 68:bc:0c:0b:ca:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*spamReceiveTask: Apr 26 16:30:51.286: 68:bc:0c:0b:ca:a0 apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*spamReceiveTask: Apr 26 16:30:51.286: 68:bc:0c:0b:ca:a0 No AP entry exist in temporary database for 172.16.100.132:38305

*apfReceiveTask: Apr 26 16:30:51.286: 68:bc:0c:0b:ca:a0 Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 0

*apfReceiveTask: Apr 26 16:30:51.286: 68:bc:0c:0b:ca:a0 Deregister LWAPP event for AP 68:bc:0c:0b:ca:a0 slot 1

*spamReceiveTask: Apr 26 16:30:51.448: 68:bc:0c:0b:ca:a0 Discovery Request from 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:30:51.448: 68:bc:0c:0b:ca:a0 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 8, joined Aps =0

*spamReceiveTask: Apr 26 16:30:51.448: 68:bc:0c:0b:ca:a0 Discovery Response sent to 172.16.100.132:38306

(Cisco Controller) >debug capwap errors enable

(Cisco Controller) >*spamReceiveTask: Apr 26 16:32:02.548: 68:bc:0c:0b:ca:a0 AP 68:bc:0c:0b:ca:a0: Invalid country code ().

*spamReceiveTask: Apr 26 16:32:02.548: 68:bc:0c:0b:ca:a0 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamReceiveTask: Apr 26 16:32:02.548: 68:bc:0c:0b:ca:a0 AP 68:bc:0c:0b:ca:a0: Invalid country code ().

*spamReceiveTask: Apr 26 16:32:02.548: 68:bc:0c:0b:ca:a0 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamReceiveTask: Apr 26 16:32:02.548: 68:bc:0c:0b:ca:a0 Configured Static IP Address not valid for AP 68:bc:0c:0b:ca:a0

*spamReceiveTask: Apr 26 16:32:02.548: 68:bc:0c:0b:ca:a0 AP 68:bc:0c:0b:ca:a0: Invalid country code ().

*spamReceiveTask: Apr 26 16:32:02.548: 68:bc:0c:0b:ca:a0 Regulatory Domain Mismatch: AP 68:bc:0c:0b:ca:a0 not allowed to join. Regulatory Domain check failed.

Allow

*spamReceiveTask: Apr 26 16:32:02.549: 68:bc:0c:0b:ca:a0 Failed post decode processing of config status from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:32:02.549: 68:bc:0c:0b:ca:a0 State machine handler: Failed to process msg type = 5 state = 5 from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:32:02.549: 68:bc:0c:0b:ca:a0 Failed to parse CAPWAP packet from 172.16.100.132:38305

*spamReceiveTask: Apr 26 16:32:02.550: 68:bc:0c:0b:ca:a0 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 172.16.100.132:38305)since DTLS session is not established

*spamReceiveTask: Apr 26 16:32:14.196: 68:bc:0c:0b:ca:a0 AP 68:bc:0c:0b:ca:a0: Invalid country code ().

*spamReceiveTask: Apr 26 16:32:14.196: 68:bc:0c:0b:ca:a0 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamReceiveTask: Apr 26 16:32:14.196: 68:bc:0c:0b:ca:a0 AP 68:bc:0c:0b:ca:a0: Invalid country code ().

*spamReceiveTask: Apr 26 16:32:14.196: 68:bc:0c:0b:ca:a0 PHY_TX_POWER_PAYLOAD: Invalid Tx Power Level 0

*spamReceiveTask: Apr 26 16:32:14.196: 68:bc:0c:0b:ca:a0 Configured Static IP Address not valid for AP 68:bc:0c:0b:ca:a0

*spamReceiveTask: Apr 26 16:32:14.196: 68:bc:0c:0b:ca:a0 AP 68:bc:0c:0b:ca:a0: Invalid country code ().

*spamReceiveTask: Apr 26 16:32:14.196: 68:bc:0c:0b:ca:a0 Regulatory Domain Mismatch: AP 68:bc:0c:0b:ca:a0 not allowed to join. Regulatory Domain check failed.

Allow

*spamReceiveTask: Apr 26 16:32:14.197: 68:bc:0c:0b:ca:a0 Failed post decode processing of config status from 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:32:14.197: 68:bc:0c:0b:ca:a0 State machine handler: Failed to process msg type = 5 state = 5 from 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:32:14.197: 68:bc:0c:0b:ca:a0 Failed to parse CAPWAP packet from 172.16.100.132:38306

*spamReceiveTask: Apr 26 16:32:14.198: 68:bc:0c:0b:ca:a0 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 172.16.100.132:38306)since DTLS session is not established

debug capwap errors disable

Re: WLC and AP

Leo Laohoo — Thu, 26 Apr 2012 04:41:37 GMT

PID: AIR-AP1042N-E-K9 , VID: V02, SN:

Configured Country............................... US - United States

Your WLC is configured with the wrong regulatory domain.

The WLC is configured for US (aka "A") and the WAP is for European standard (aka "E").

Re: WLC and AP

Kamran Mustafayev — Thu, 26 Apr 2012 04:47:51 GMT

How can i change regulatory domain on wlc or ap

WLC and AP

Leo Laohoo — Thu, 26 Apr 2012 05:16:36 GMT

On the WLC GUI, go to Wireless, Country and set the correct country code there.

Please don't forget to rate our useful posts.

WLC and AP

Kamran Mustafayev — Thu, 26 Apr 2012 05:19:13 GMT

Thank you guys,

i entered wlc and wrote

country code SE(sweden)

then i reload wlc, and ap succesfully joined to it

WLC and AP

Leo Laohoo — Thu, 26 Apr 2012 05:51:35 GMT

Perfect. Glad to see it works.

WLC and AP

lordbigsack — Wed, 23 May 2012 10:50:53 GMT

Had exactly the same issue, this worked perfectly.

@leolaohoo thanks

Re: WLC and AP

Vinay Sharma — Wed, 30 May 2012 07:05:50 GMT

Thanks Leo for providing this useful information 5+

Sent from Cisco Technical Support iPhone App