configuring WLC and AP'S

Unanswered Question
May 13th, 2008

Hi all, some questions

1.Do I need to put an ip on the ap manager interface?

2.does the ap manager interface go on the same subnet at the access points?

3.Im using 2 wlc's for redudancy, what special config do I need to do on them, do I need to tell each WLC what the other WLC is?

4.should I set the WLC addresses on the access points manually to avoid inter controller roaming?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
ericgarnel Tue, 05/13/2008 - 05:32

1) Yes

2) Yes

3) They will participate in the same group

here are some good links:

wlc 4400 configuration

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

This is a great link

http://www.cisco.com/en/US/products/ps6366/prod_configuration_examples_list.html

failover example:

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml

4) that depends... some people prefer to assign static ips to the APs, it really depends on your preference and how many APs.

Currently, I use dhcp with the scope split between 2 dhcp servers with a long lease

Scott Fella Wed, 05/14/2008 - 18:29

Eric has some good docs there.

The management and ap-manager must be on the same subnet and of course must have an ip address. So you will need 4 ip addresses in that subnet if you have two WLC's and if you configure LAG. Cisco mentions not having more than 20 ap's on the same subnet as the ap-manager, so if you have more, You should create an AP subnet but have no more than 60 ap's on that subnet.

To avoid inter-controller roaming, make sure ap's are grouped together and is primary on one of the controllers. For example, if you have 6 floors 1-6, floors 1-3 should be put on wlc1 and 4-6 on wlc2. Don't try to mix and match on the same floor. I think they call it salt-n-pepper design.

Take a look at this doc also:

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a0080810880.shtml

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode