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

WLAN Controller 4404

We recently acquired a 4404 Cisco controller for our network and have been adding our 1200 and 1130 Access points to the controller.

This was accomplished by uprgading the APs to LWAPP and then they would automatically be discovered by the controller and then join. Lately, new 1131 APs that have undergone the same process, are not joining the controller. They are discovered but then the close the connection. We are running a flat network so all devices are in the same subnet.

Software Version of the controller 6.0.188.0

Here is the log from the AP:

*Mar 12 18:56:23.411: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully17e420.18fromrollerOVERYNregulations. If you are u

ion.
*Mar 12 18:56:49.413: %DTLS-5-ALERT: Received WARNING : Close notify alert from
10.0.0.18
*Mar 12 18:56:49.413: %DTLS-5-PEER_DISCONNECT: Peer 10.0.0.18 has closed connect
ion.
*Mar 12 18:56:49.413: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1
0.0.0.18:5246
*Mar 12 18:56:49.414: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 12 18:56:48.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_i
p: 10.0.0.18 peer_port: 5246
*Mar 12 18:56:48.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Mar 12 18:56:49.409: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
peer_ip: 10.0.0.18 peer_port: 5246
*Mar 12 18:56:49.411: %CAPWAP-5-SENDJOIN: sending Join Request to 10.0.0.18
*Mar 12 18:56:49.411: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Mar 12 18:56:49.415: %DTLS-5-ALERT: Received WARNING : Close notify alert from
10.0.0.18
*Mar 12 18:56:49.415: %DTLS-5-PEER_DISCONNECT: Peer 10.0.0.18 has closed connect
ion.
*Mar 12 18:56:49.416: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1
0.0.0.18:5246
*Mar 12 18:56:49.470: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 12 18:56:49.470: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Mar 12 18:56:49.481: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to a
dministratively down

- Show quoted text -

5 REPLIES
Hall of Fame Super Gold

Re: WLAN Controller 4404

Hi Paul,

The 6.X firmware has significantly improved how the the AP discovers a WLC.  Have you tried to console into the AP in question the command "config lwapp ap controller "?

How many APs are already associated to the WLC and how many AP can your WLC support?
Try to clear the config of the AP by using the command "clear lwapp private" followed by "clear lwapp ap controller ip address" and then reboot the AP

New Member

Re: WLAN Controller 4404

Thank you for your reply.

The issue has been solved. It acutally involed making another ap manager. There is only so much APs per management port.

Re: WLAN Controller 4404

Correct, each port / ap manger can handle 48 aps. If i can ask, why arent you using LAG?

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________

WLAN Controller 4404

Hi Paul

How did you setup another ap manager...I'm having the same problem

Thanks

Bronze

WLAN Controller 4404

Hi ,

If you enable LAG and have several ports of the WLC connected to the same switch and enable loadbalancing on the WLC then you just need one AP manager configured but if you are not using LAG since each port supports up to 48 Aps then you will need to configure several AP managers and link each AP manager interface to a port.

Also check on this link under Scaling the 440x WLC Beyond 48 Access Points

http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html#wp1061736

3903
Views
0
Helpful
5
Replies