Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

1552AP not joining WLC

Customer has got a 2 x 1552AP that wont join a WLC.

This is the debugs from the WLC. Customer cant console to AP to capture as its up in the roof so not easily accessible. Any ideas why the AP wont join? Date/Time are fine on the WLC as is the region.

*spamReceiveTask: Jun 28 13:45:26.612: 2c:3f:38:be:23:c0 DTLS connection not found, creating new connection for 172:16:2:1 (57918) 172:16:0:1 (5246)

*spamReceiveTask: Jun 28 13:45:27.243: 2c:3f:38:be:23:c0 DTLS Session established server (172.16.0.1:5246), client (172.16.2.1:57918)

*spamReceiveTask: Jun 28 13:45:27.244: 2c:3f:38:be:23:c0 Starting wait join timer for AP: 172.16.2.1:57918

*spamReceiveTask: Jun 28 13:45:27.248: 2c:3f:38:be:23:c0 Join Request from 172.16.2.1:57918

*spamReceiveTask: Jun 28 13:45:27.249: 2c:3f:38:be:23:c0 Deleting AP entry 172.16.2.1:57918 from temporary database.

*spamReceiveTask: Jun 28 13:45:27.249: 2c:3f:38:be:23:c0 spamProcessJoinRequest : RAP, Check MAC filter

*spamReceiveTask: Jun 28 13:45:27.249: 2c:3f:38:be:23:c0 In AAA state 'Idle' for AP 2c:3f:38:be:23:c0

*spamReceiveTask: Jun 28 13:45:27.249: 2c:3f:38:be:23:c0 Mesh AP username 2c3f38be23c0.

*spamReceiveTask: Jun 28 13:45:27.251: 2c:3f:38:be:23:c0 Finding DTLS connection to delete for AP (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.251: 2c:3f:38:be:23:c0 Disconnecting DTLS Capwap-Ctrl session 0x13876510 for AP (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.251: 2c:3f:38:be:23:c0 CAPWAP State: Dtls tear down

*spamReceiveTask: Jun 28 13:45:27.253: 2c:3f:38:be:23:c0 DTLS connection closed event receivedserver (172:16:0:1/5246) client (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.253: 2c:3f:38:be:23:c0 Entry exists for AP (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.253: 2c:3f:38:be:23:c0 No AP entry exist in temporary database for 172.16.2.1:57918

*spamReceiveTask: Jun 28 13:45:27.258: 2c:3f:38:be:23:c0 DTLS connection not found, creating new connection for 172:16:2:1 (57918) 172:16:0:1 (5246)

*spamReceiveTask: Jun 28 13:45:27.891: 2c:3f:38:be:23:c0 DTLS Session established server (172.16.0.1:5246), client (172.16.2.1:57918)

*spamReceiveTask: Jun 28 13:45:27.891: 2c:3f:38:be:23:c0 Starting wait join timer for AP: 172.16.2.1:57918

*spamReceiveTask: Jun 28 13:45:27.896: 2c:3f:38:be:23:c0 Join Request from 172.16.2.1:57918

*spamReceiveTask: Jun 28 13:45:27.897: 2c:3f:38:be:23:c0 Deleting AP entry 172.16.2.1:57918 from temporary database.

*spamReceiveTask: Jun 28 13:45:27.897: 2c:3f:38:be:23:c0 spamProcessJoinRequest : RAP, Check MAC filter

*spamReceiveTask: Jun 28 13:45:27.897: 2c:3f:38:be:23:c0 In AAA state 'Idle' for AP 2c:3f:38:be:23:c0

*spamReceiveTask: Jun 28 13:45:27.897: 2c:3f:38:be:23:c0 Mesh AP username 2c3f38be23c0.

*spamReceiveTask: Jun 28 13:45:27.899: 2c:3f:38:be:23:c0 Finding DTLS connection to delete for AP (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.899: 2c:3f:38:be:23:c0 Disconnecting DTLS Capwap-Ctrl session 0x138765f8 for AP (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.899: 2c:3f:38:be:23:c0 CAPWAP State: Dtls tear down

*spamReceiveTask: Jun 28 13:45:27.901: 2c:3f:38:be:23:c0 DTLS connection closed event receivedserver (172:16:0:1/5246) client (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.901: 2c:3f:38:be:23:c0 Entry exists for AP (172:16:2:1/57918)

*spamReceiveTask: Jun 28 13:45:27.901: 2c:3f:38:be:23:c0 No AP entry exist in temporary database for 172.16.2.1:57918

*spamReceiveTask: Jun 28 13:45:27.905: 2c:3f:38:be:23:c0 DTLS connection not found, creating new connection for 172:16:2:1 (57918) 172:16:0:1 (5246)

Thanks

Jon

Everyone's tags (2)
2 REPLIES
Community Member

1552AP not joining WLC

Update - This has now been resolved. MAC filter in use on the WLC.

1552AP not joining WLC

Good that you found the root cause.
I wanted to point you to read the traplog because if it is a mac filter then you'll have a message there showing you problem with mac filter (mentioning the AP's MAC address).

But you resolved it anyway.

Amjad

Rating useful replies is more useful than saying "Thank you"
1621
Views
0
Helpful
2
Replies
CreatePlease to create content