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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Brand new outdoor 1552E can not join WLC 5508 v7.2

I just have a brand new Aironet 1552E , just took it out of the box and connect to the same subnet with a WLC 5508 v7.2 fully config and working

However, it could not join the WLC 5508

                  

*spamApTask0: May 14 17:18:09.788: %LWAPP-3-RADIUS_ERR: spam_radius.c:137 The system could not send join reply, AP authorization failed; AP:0c:85:25:35:81:80

*spamApTask0: May 14 17:18:09.787: %CAPWAP-3-DUP_AP_NAME: capwap_ac_decode.c:1088 AP with same name AP0c85.2535.8180 exist. Using default name AP0c85.2535.8180 for this AP.

*spamApTask0: May 14 17:18:09.777: %DTLS-5-ESTABLISHED_TO_PEER: openssl_dtls.c:576 DTLS connection established to 172.16.10.62

Please advise.

Thank you.

Everyone's tags (8)
1 ACCEPTED SOLUTION

Accepted Solutions
Bronze

Re: Brand new outdoor 1552E can not join WLC 5508 v7.2

Did you add the AP MAC to your AP Policies section of the WLC?  It seems like the WLC may be rejecting the AP join due to this.

Updated link:http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mesh.html#wp147245

If you debug the AP MAC address

>debug mac addr

>debug capwap events enable

>debug capwap errors enable

>debug mesh security enable

You will be able to see what is happening from the WLCs perspective

4 REPLIES
New Member

Brand new outdoor 1552E can not join WLC 5508 v7.2

I plugged in a console cable and got these, the messages keep repeating themselves

% CDP is not supported on this interface, or for this encapsulation98 peer_port: 5246

*May 14 21:37:28.715: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.10.198

*May 14 21:37:28.715: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*May 14 21:37:28.723: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.10.198

*May 14 21:37:28.723: %DTLS-5-PEER_DISCONNECT: Peer 172.16.10.198 has closed connection.

*May 14 21:37:28.723: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.10.198:5246

*May 14 21:37:28.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.198 peer_port: 5246

*May 14 21:37:28.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*May 14 21:37:28.719: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.10.198 peer_port: 5246

*May 14 21:37:28.719: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.10.198

*May 14 21:37:28.719: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*May 14 21:37:28.727: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.10.198

*May 14 21:37:28.727: %DTLS-5-PEER_DISCONNECT: Peer 172.16.10.198 has closed connection.

*May 14 21:37:28.727: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.10.198:5246

*May 14 21:37:28.767: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*May 14 21:37:28.767: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*May 14 21:37:28.835:  status of voice_diag_test from WLC is false

*May 14 21:37:40.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.198 peer_port: 5246

*May 14 21:37:40.000: %CAPWAP-5-CHANGED: CAPWAP changed state to

*May 14 21:37:40.711: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.10.198 peer_port: 5246

*May 14 21:37:40.711: %CAPWAP-5-SENDJOIN: sending Join Request to 172.16.10.198

*May 14 21:37:40.711: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*May 14 21:37:40.719: %DTLS-5-ALERT: Received WARNING : Close notify alert from 172.16.10.198

*May 14 21:37:40.719: %DTLS-5-PEER_DISCONNECT: Peer 172.16.10.198 has closed connection.

*May 14 21:37:40.719: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.16.10.198:5246

*May 14 21:37:40.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.10.198 peer_port: 5246

*May 14 21:37:40.715: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.16.10.198 peer_port: 5246

*May 14 21:37:40.719: %CAPWAP-5-SENDJOIN: sendin

% CDP is not supported on this interface, or for this encapsulationg Join Request to 172.16.10.198

Hall of Fame Super Gold

Re: Brand new outdoor 1552E can not join WLC 5508 v7.2

I'm no expert of the MESH WAPs but if you can console into the WAP, can I ask if you provide the following output:

1.  WAP:  sh version;

2.  WAP:  sh inventory;

3.  WLC:  sh sysinfo

You're output is showing the WAP is running OK and gets the correct time so my next question is "country regulatory domain". 

Bronze

Re: Brand new outdoor 1552E can not join WLC 5508 v7.2

Did you add the AP MAC to your AP Policies section of the WLC?  It seems like the WLC may be rejecting the AP join due to this.

Updated link:http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mesh.html#wp147245

If you debug the AP MAC address

>debug mac addr

>debug capwap events enable

>debug capwap errors enable

>debug mesh security enable

You will be able to see what is happening from the WLCs perspective

New Member

Re: Brand new outdoor 1552E can not join WLC 5508 v7.2

I found the answer.

By default, access to the wireless LAN for access point is managed by

- MAC authentication

- External Radius authentication

7046
Views
0
Helpful
4
Replies
CreatePlease login to create content