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

1131 Not Joining controller

I am getting the following message on my 4404 (running 4.2.61).

We currently have 48 APs associated to it.

We do not have aggressive load balancing enabled.

I did a search on the error message below but I was not able to find much info about it on cisco or in these forums. Everything I have found points to load balancing accross WLC. Anyone experience this issue?

(Cisco Controller) >Wed Feb 25 13:02:57 2009: 00:23:04:25:f2:96 Received LWAPP DISCOVERY REQUEST from AP 00:23:04:25:f2:96 to 00:1a:e2:ea:3d:00 on port '1'

Wed Feb 25 13:02:57 2009: 00:23:04:25:f2:96 Refusing Discovery Request from AP 00:23:04:25:f2:96 - no AP manager with available capacity

Wed Feb 25 13:03:07 2009: 00:23:04:25:f2:96 Received LWAPP DISCOVERY REQUEST from AP 00:23:04:25:f2:96 to 00:1a:e2:ea:3d:00 on port '1'

Wed Feb 25 13:03:07 2009: 00:23:04:25:f2:96 Refusing Discovery Request from AP 00:23:04:25:f2:96 - no AP manager with available capacity

2 REPLIES
Silver

Re: 1131 Not Joining controller

Cisco controllers have a rather odd design restriction. No more than 24 APs can be on any physical port. Since you have a 4404, you must only have two ports connected to your network. As such, you cannot exceed 48 APs as it stands.

You can bypass this restriction by configuring LAG on the ports, or by simply connecting a new physical port to the 4404.

Hopefully that helps,

Jeff

New Member

Re: 1131 Not Joining controller

Thanks Jeff. I will connect another port on the 4404 and see what happens. I'll post back with my results.

217
Views
5
Helpful
2
Replies
CreatePlease login to create content