Mobility Groups and RF Groups

Unanswered Question
Oct 10th, 2007

Is there a general recommendation for the grouping of WLCs for mobility and RF (RRM)? It seems to me that they are totally separate features. So, if I had a site with 2 mobility groups, I could technically configure all of the WLCs with the same RF Group name? Should I do that?

Or should I just keep the RF Group name the same as the Mobility Group name?

Is there any tradeoff for configuring multiple RF groups vs. configuring one big RF Group for a site?

I haven't seen any documentation that discusses this. Everything seems to assume a single mobility group and a single RF Group per site.


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
ankbhasi Wed, 10/10/2007 - 09:16

Hi Paul,

RF groups and mobility groups are similar in that they both define clusters of controllers, but they are different in terms of their use.

These two concepts are often confused because the mobility group name and RF group name are configured to be the same in the Startup Wizard. Most of the time, all of the controllers in an RF group are also in the same mobility group and vice versa. However, an RF group facilitates scalable, system-wide dynamic RF management while a mobility group facilitates scalable, system-wide mobility and controller redundancy.

So it is not necessary to have same mobility group name as RF Group name.

RF Groups are clusters of controllers who not only share the same RF Group Name, but whose APs hear each other. AP logical collocation, and thus controller RF Grouping, is determined by APs receiving other APs? Neighbor Messages.

So if your WLCs on different site have APs which cannot see each other there is no use to keep the 2 controllers in same RF group.

May be these links can help you with something

A very good link for RRM



*Pls rate all helpfull post


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