Mobility Group Issue

Unanswered Question
Sep 15th, 2009
User Badges:

I have a WiSM configured with the same mobility group name and all pre-reqs are ok but the roaming does not works and the client lost connection when change of access-point.

I saw that RF-group are diferents and bootloader version is diferent too.

Does any one Know if bootloader and RF-group diferent can be the reason for that.

thanks a lot

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
tstanik Mon, 09/21/2009 - 13:00
User Badges:
  • Bronze, 100 points or more

An incorrect or incomplete mobility group configuration should be the most common reason for your problem. In order to overcome this, you need to ensure that your WiSM mobility group is configured correctly as follows:

The mobility group name configured must be the same on all the controllers that belong to a particular mobility group. This mobility group name is case sensitive.

The mobility group members list configured on each controller needs to contain all the controllers of that particular mobility group.

These configurations ensure that the failover occurs seamlessly and also that when the primary controller comes back on, the previously registered APs fall back to it.

danielnunes Mon, 09/21/2009 - 14:51
User Badges:


My mobility group does not working because the Time Server ís diferent in every controller.

The first controller was 7 hours shifted on the second controller.

After I fix it, roaming on mobility group start working.

thanks a lot

George Stefanick Mon, 09/21/2009 - 16:56
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, October 2015

That is interesting... Thanks for sharing ...

danielnunes Mon, 09/21/2009 - 17:17
User Badges:

I was wondering, i think that Controller is right, because how can it make a roaming of the a LAP at 02:00 to other LAP in other controller at 09:00 for example. I think it's make a sense.



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