AP groups and redundancy

Unanswered Question
Jun 17th, 2009

Is it possible for APs to failover between controllers when AP groups are in use? I have seen separate documentation on AP groups and AP failover but nothing that says how to implement both at the same time.

I have tried to work it out but when I created the group on the back up controller I am not able to add the AP to the group as it is not asociated to it.

Has anyone else come across this or have any ideas?

We are currently using 4400 controllers running 5.2.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
naks Wed, 06/17/2009 - 05:52

Hi,

I have tried to work it out but when I created the group on the back up controller I am not able to add the AP to the group as it is not asociated to it.

>>Did you create the same ap group on both the controllers? What happens when the aps failover to the back up controller?

Regards,

Nagendra

John.Gerlach Wed, 06/17/2009 - 08:32

Are your controllers in the same mobility group? (Controller|General|Default Mobility Name)

You can also check under Controller|Mobility Management|Mobility Groups to see if other controllers are set up to exchange Mobility Management info.

If you are in the same Mobility Management group then when failover to another member/controller in that group occurs and the AP Group name is the same on both controllers the APs should automatically join that AP Group name on the controller they failed over to.

Our implementation (still in the early stages) includes 8 WiSMs Controllers that are in the same Mobility Management group and will fail across campuses if we lose a WiSM module or chassis.

We will be using smaller controllers (4402's) at remote sites with their own Mobility Name. That is to prevent constantly exchanging client info with other controllers over wan links. If/when those failover to the main campus they will wind up being in the AP Group default-group on the WiSM environment.

danhosking Wed, 06/17/2009 - 16:03

Thanks for the help. I will give it another try and let you know how it goes.

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