2500 series support mobility groups?

Do you know if the new 2500 series controller supports things like mobility groups? Could I use 2 of these and do inter-controller roaming.
Also do you know if this would work with a 2106 controller and a 2505 controller or are they 2 completely independent controllers only knowing about their own APs??

Hi smailmilak,
no mobility and roaming is not the same. You need for roaming between controllers a mobility configuration.
If you have only one 2500 WLC and 25 or more or less AP roaming between the AP on the one WLC will work well.
This calls Intra-Controller roaming
If you have 2 or more WLCs you need a proper mobility config for roaming between APs located on differen WLC.
This Calls Inter-Controller roaming.
More informations are here:
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mobil.html

Similar Messages

Does a 2504 WLC support mobility group with WiSM1 on 6500 Series

if a 2504 WLC support mobility group with WiSM1 on 6500 Series.
Model: WLC 2504
Software version: 7.3.101.0
Model: WiSM1
Software verion: 7.x.x.x

Yes and no.
Yes, mobility is supported.
No because I personally won't recommend inter-controller roaming. This is more true when you're dealing with 4400/WiSM-1. This is even more true when you've got WLC running two (or more) different codes.

Wireless Mobility Groups - Concerns...

Hi,
I recently set up two wireless controllers (2000 series) with a total of 7 access points. The first controller was already running with a total of 5 ap's. I fired up the second controller, and got everything configured and added one access point to it. Everything was running fine yesterday, I had a few clients on the new controller and the rest on the old one. When I got in this morning and checked out the new controller, I saw that all of the access points had moved over to the new controller, and by extension all of the clients. The old controller now has nothing on it as far as ap's or clients. Is this supposed to happen? I didn't know mobility groups shifted over ap's as well? My only concern is that I have one more ap to set up which will make seven and the 2000 only supports 6 ap's. When I fire it up, will one of the ap's move back to it's original controller? Any input is appreciated. Thank you.

Hi Tate,
Have a look at this info which may help;
AP Fail-over Between Different Mobility Groups
From this good Troubleshooting doc;
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a00806c9e51.shtml#APfail
Hope this helps!
Rob

5508 Mobility Groups

Hello.
2 questions
1) Is it possible for 2 WLCs installed in seperate data centres with L3 seperation to be joined in a mobility group? We will have aps in the branch offices split between controllers so we want to make sure roaming work ok. Also all guest access should be anchored to data centre 2.
2) in flexconnect local switching mode, do I need to create flexconnect groups if I'm only using radius servers in the data centre with no requirement to use local radius as a backup?

Mobility groups can work when the WLC's are in different subnet asl long as UDP 16666 and IP 97 allowed between the two WLC's.
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mobil.html#wp1102312
You will not be able to configure for guest, what wlc is primary or secondary. The foreign WLC will decide which guest anchor controller (if there is two) it will use.
You don't need to use flexconnect groups if you don't want to. If your devices are not cckm compliant, then I wouldn't worry about it personally. Here are the numbers, but some has changed with the 7.3.
The number of FlexConnect groups and access point support depends on the platform that you are using. You can configure the following:
•Up to 100 FlexConnect groups for a Cisco 5500 Series Controller
•Up to 1000 FlexConnect groups for a Cisco Flex 7500 Series Controller. The Cisco Flex 7500 Series Controller can accommodate up to 50 access points per FlexConnect group.
•Up to 20 FlexConnect groups with up to 25 access points per group for the remaining platforms.
https://supportforums.cisco.com/docs/DOC-26778#Increased_scale_for_Cisco_Flex_7500_Series_Controllers_668166
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

WLC 5508 * 2 & Mobility Group

What I am trying to configure is Mobility Groups.
My understanding is that this will allow AP to successfully register and fail over over seamlessly if any of the WLC had to fail ?
It could be I am confusing two things into one :( & I am totally confused and not understanding the benefits of mobility group mentioned above.
Also when a AP starts up and registers with the WLC ......I click on a registered AP > High Availability ( Primary / Sec / Tertiary ) all fields are blank...
Initially I also thought that once my SSO is all setup and working than those options "AP > High Availability" will get populated automatically but clearly not unless something is not working.
My current config is as follows:-
WLC 5508 * 2
WLC 1 - Primary
WLC 2 - HA SKU (Secondary )
Redundancy = SSO (Both AP and Client SSO)
=============
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.6.130.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. FPGA 1.7, Env 1.8, USB console 2.2
Build Type....................................... DATA + WPS
System Name...................................... WLC5508
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. SSO (Both AP and Client SSO)
IP Address....................................... 10.31.66.21
Last Reset....................................... Software reset
System Up Time................................... 0 days 22 hrs 39 mins 57 secs
System Timezone Location......................... (GMT) London, Lisbon, Dublin, Edinburgh
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +38 C
External Temperature............................. +21 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
Number of Active Clients......................... 0
Burned-in MAC Address............................ F8:72:EA:EE:5B:B2
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 500
============================================
TA

TA,
Mobility and mobility groups are used for the wireless users roaming. What we know that a wireless users can roam between different APs within the same WLC, but when the SSID is used within multiple WLCs, and the client wanted to roam to an AP joined to another WLC, you would need to configure WLC mobility to maintain seamless roaming. For more info:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_010001101.html
Now, I understand that your purpose is to have high availability for your APs. No this is done traditionally from the AP page, under HA tab, where you configure the WLCs names and IPs there. This can be done manually on each AP (you can use CLI to make it easier) or you can push a configuration template using a management server (WCS/NCS/CPI).
Configuring HA on the AP:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01110000.html
http://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_01110001.html
Using CPI to push AP configuration templates:
http://www.cisco.com/c/en/us/td/docs/wireless/prime_infrastructure/2-0/configuration/guide/pi_20_cg/temp.html
Now mobility may play a role in this, as if you have already configured mobility for your WLCs, then you won't need to configure a "name" for the WLCs when you add them under the HA tab in AP configuration page. That's it.
BR, Ala

What will happen when I remove controllers from mobility groups?

Hi,
I'm wondering what exactly will happen when I remove a controller from a mobility group?
1) Will it require a reboot? (I don't think so, nothing I've found says so)
2) Will it deauth/reauth the AP's connected (I don't think so, nothing I've found says so)
3) Will it do anything else goofy?
I have 2 RF groups spanning continents over low speed links. All that is transmitted over mobility groups is session data correct? Not usernames, not ??? What am I missing here? I'm banging my head against the wall because I can't figure out why someone would configure the system in this way.
Setup:
WLC 4404, WLC 2100's
WCS 5.2.148
11xx series AP's
Radius Auth for domain users
a few SSID's, one guest SSID, no DHCP on any of the controllers
Thanks in advance,

Hi,
I'm wondering what exactly will happen when I remove a controller from a mobility group?
1) Will it require a reboot? (I don't think so, nothing I've found says so)
2) Will it deauth/reauth the AP's connected (I don't think so, nothing I've found says so)
3) Will it do anything else goofy?
I have 2 RF groups spanning continents over low speed links. All that is transmitted over mobility groups is session data correct? Not usernames, not ??? What am I missing here? I'm banging my head against the wall because I can't figure out why someone would configure the system in this way.
Setup:
WLC 4404, WLC 2100's
WCS 5.2.148
11xx series AP's
Radius Auth for domain users
a few SSID's, one guest SSID, no DHCP on any of the controllers
Thanks in advance,

N+1 redundancy and different mobility groups

Is it possible to backup 2 controllers with 2 different mobility groups (for example GROUP1 and GROUP2) to the same backup controller (running HA SKU N+1 (7.4)) ?
Since a controller can only be configured in 1 mobility group, this doesn't seem to be possible. Can someone confirm ?
regards,
Geert

Hello,
As per your query i can suggest you the following solution-
In all Wireless LAN Controller (WLC) versions earlier than 4.2.61.0, when a WLC goes "down," the LAP registered to this WLC can failover only to another WLC of the same Mobility Group, if the LAP is configured for failover. From Cisco WLC version 4.2.61.0 and later, a new feature called Backup Controller Support is introduced for access points to failover to controllers even outside the Mobility Group. Refer to Wireless LAN Controller and Light Weight Access Points Failover Outside the Mobility Group Configuration Example for more information.
Hope this will help you.

WiSM redundancy, mobility groups and RF groups

Hi there
we would like to implement the following:
- Support for about 2000 LAP's
- 1 x Catalyst 6509
- 1 x Sup 720
- 7 x WiSM's
What I'm interesting is are the following points:
1. I thought that we would build the switch completly redudant, so we have to wlan switches (switch A and B) with 7 WiSM's eatch. So I can garanty a N+N redundancy --> each LAP's has a primary controller on switch A and it's secondary controller on switch B. The LAP's can be splitted on the two switches, but for your understanding there is a 1:1 redundancy. What do you think of this design, is the too much or is this appropriate?
2. As I know you can build up a mobility group of a maximum of 24 controllers or 12 WiSM's. I would put only these controllers in a mobility group, where Layer 2 roaming can occure.
3. But what is about the RF groups - there is a maximum of 1000 LAP's, so I can put only 3 WiSM's in one group. But this would not work form me, then I would have 2 WiSM's on switch A and only 1 WiSM on switch B in a RF group (not a 1:1 redundancy). First is it possible to put WiSM-A and WiSM-B into different RF groups, I think so because they are logically splitted, aren't they?
And what RF group design would be best (just as a reference)? I thought that it would make sense to form a RF group for each of the seven pairs (1 WiSM on switch A and 1 WiSM on switch B) for redundancy? What do you think of that approach?
4. So I would have 1 mobility group and 7 RF groups. Or do you recommend to form the mobility groups like the RF groups? But what happens with Layer 2 roaming in that case?
I'm sorry for the long and messy text, but I hope you can see my design questions?
Thanks a lot in advance.
Dominic

It sounds like you already have some good replies. Personally I like N+1 redundancy, but that is a designers choice. One thing I should point out is that the 6500 can only support 5 WiSM cards each. In this case a 4 WiSM x 3 chassis option would give your more spare capacity with only 12 total cards. The lower WiSM cost (12 vs 14) would help offset the cost of the extra chassis. You could also support 2400 APs with 8 WiSM cards even if one switch is down.
Not too long ago Cisco added the ability to set the priority of APs so your critical ones would join a controller and the less critical ones would go down if a controller failed and there were no redundancy. That is something to keep in mind when designing wireless. You may not need redundancy for all APs and that could affect your design and costs.
Randy

WLC 7.3.101.0 Mobility group peer cannot up.

Hi Guys,
It seems the 7.3.101 version Mobility group peer cannot up,: refer to the attach,
Peer 1: version: 7.3.101
Peer 2: version 7.0.98
Peer3: version 7.2.103
Today we got new two WLC for Anchor use, and config the mobility group, but it's failed and cannot up, the ping is ok.

Chris is right here. One thing I tell my clients is to allow everything between the foreign and the anchor WLC's just to verify that the mobility can come up, then lock it down. Here is some links that explain what test is for what port.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00809a30cc.shtml#qa8
Anchor Controller Positioning
Because the anchor controller is responsible for termination of guest WLAN traffic and subsequent access to the Internet, it is typically positioned in the enterprise Internet DMZ. In doing so, rules can be established within the firewall to precisely manage communications between authorized controllers throughout the enterprise and the anchor controller. Such rules might including filtering on source or destination controller addresses, UDP port 16666 for inter-WLC communication, and IP protocol ID 97 Ethernet in IP for client traffic. Other rules that might be needed include the following:
•TCP 161 and 162 for SNMP
•UDP 69 for TFTP
•TCP 80 or 443 for HTTP, or HTTPS for GUI access
•TCP 23 or 22 for Telnet, or SSH for CLI access
Depending on the topology, the firewall can be used to protect the anchor controller from outside threats.
For the best possible performance and because of its suggested positioning in the network, it is strongly recommended that the guest anchor controller be dedicated to supporting guest access functions only. In other words, the anchor controller should not be used to support guest access in addition to controlling and managing other LWAPP APs (LAPs) in the enterprise.
Sent from Cisco Technical Support iPhone App

Mobility groups with multicast - 7.4.100.60

Hello all,
I am not sure if this is a bug, but here we go. I configured 2 controllers in a mobility group using multicast signalling.
I expect that from the moment i enable multicast, the controller joins this group AND STAYS IN THIS GROUP so he will get messages from all other controllers.
On the first hop router, i can see the join:
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.248.10               10.102.78.98    00:00:05 02:54 2A     Vl350
However, this entry does not get refreshed. I have the impression that the controller does not reply to the IGMP general queries:
IGMP(0): Send v2 general Query on Vlan350 -> no replies
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.248.10               10.102.78.98    00:02:35 00:24 2A     Vl350
>> 20 seconds from expiry.
#sh ip igmp mem 239.194.248.10
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       <mac-or-ip-address> - last reporter if group is not explicitly tracked
       <n>/<m>      - <n> reporter in include mode, <m> reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
>> 20 seconds later, gone
>> At this moment the controller doesn't receive any messages anymore from remote controllers:
>>sh ip mroute 239.194.248.10
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report,
       Z - Multicast Tunnel, z - MDT-data group sender,
       Y - Joined MDT-data group, y - Sending to MDT-data group
       V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.194.248.10), 00:05:38/00:00:21, RP 10.102.90.20, flags: SP
Incoming interface: Port-channel30, RPF nbr 10.102.78.13, RPF-MFD
Outgoing interface list: Null
This is seen on 8500 platform running 7.4.100.60
We have also WISMs running at 7.0.230.0, and there it can be seen that the entry refreshes every minute (like it should be)
IGMP(0): Received v2 Report on Vlan950 from 10.96.9.67 for 239.194.240.1
IGMP(0): Received Group record for group 239.194.240.1, mode 2 from 10.96.9.67 for 0 sources
IGMP(0): Updating EXCLUDE group timer for 239.194.240.1
IGMP(0): MRT Add/Update Vlan950 for (*,239.194.240.1) by 0
Shouldn't the controller at all times stay joined in its mobiility group ?

ok, some more debugging.
I loaded up 7.4.100.60 on a 5500 controller and got the same result.
NOTE: my global multicast settings are:
Controller->General: AP Multicast Mode: UNICAST
Controller->Multicast->Global Multicast is NOT enabled
Controller->Mobility->Multicast Messaging: enabled and group is 239.194.240.3
With this config, the IGMP entry is not retained, and i see on the controller the message (debug bcast all):
>>processEthernetIGMPpacket Received IGMP Pkt from DS when either igmp snooping or global multicast is disabled.
So, i then enabled Global Multicast (Controller->Multicast->Global Multicast to enable), and then the IGMP entry is refreshed:
bcastReceiveTask: Sep 05 13:11:17.734: IGMP packet received over vlanid = 102 from DS side
*bcastReceiveTask: Sep 05 13:11:17.734: received an IGMP query for multicast vlan = 102 address 0.0.0.0 intfnum = 3
*bcastReceiveTask: Sep 05 13:11:17.734: IGMP report scheduled for grp=0xefc2f003, vlan=102, intf=3, slot=70, maxRespTime=100
>>sh ip igmp membership 239.194.240.3
004586: Sep 5 15:11:50.710 CEST: IGMP(0): Send v2 general Query on Vlan101
Flags: A - aggregate, T - tracked
       L - Local, S - static, V - virtual, R - Reported through v3
       I - v3lite, U - Urd, M - SSM (S,G) channel
       1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
       / - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
       - last reporter if group is not explicitly tracked
       /      - reporter in include mode, reporter in exclude
Channel/Group                  Reporter        Uptime   Exp. Flags Interface
*,239.194.240.3                10.102.180.218 00:38:51 02:28 2A     Vl102
Now, on the 5500 controller i can enable global multicast, while AP multicast mode is in UNICAST.
However, on the 8500 controller, running the same firmware (7.4.100.60), when i try to enable "Global Multicast", i get:
"Multicast-Unicast mode does not support IGMP/MLD snooping. Config mode to multicast-multicast first". I did not get this message on the 5500.
So when switching to Multicast->Multicast mode, and then enabled "Global Multicast", then it works.
This means that in order to have mobility messaging working on 8500 in multicast, you MUST put the AP Multicast Mode to Multicast AND you must enabled "Global Multicast", otherwise it won't work.

Mobility group between controller 4400 and virtual wlc

Hello everybody...
I read the configuration guide about the 7.3 release. And I figured out that you will need a hash key for establishing a mobility group relation between a controller and a virtual controller. The 7.3 release for the 5500 series works fine for me.
But the latest release 7.0.235.0 for the wireless lan controller series 4400 does not have a functionality to add a hash key while creating a new mobility group member.
The command "config mobility group member hash" is totally missing.
Does anybody have an idea how to establish a mobility group between a 4400 controller and a virtual then?
Best regards,
Sebastian Wieseler

The vWLC is out since yesterday.
We installed it in our lab and the deployment guide is out now, too.
Anyway... the hash is "god-given" in the vWLC. I can't change it to "none". So it is quite mandatory to enter a hash in the 4400 controller otherwise it just do not pair. So I am unable to establish a mobility group.
Any other ideas?

Cisco 526 WLC and 2106 WLC in one Mobility Group

Hi,
is it possbile to build a solution with one Cisco 526 Wireless Express Mobility Controller and one Cisco 2106 Wireless LAN Controller in one Mobility Group regarding seamless roaming??
Thank for your answers
Best regards
Stephan

I don't know if it is possible, but I would think if you had any issues, TAC wouldn't support it. Try opening a case with TAC to see.

Is it possible to have 2500 series management interface out of band of APs?

I currently have 2500 series WLCs. Our wireless network is completely separate from our internal network, keeping the WLC from talking to any internal servers. The company would like to start using AD(LDAP authentication) for end users while still keeping the APs on a completely separate network. Since the 2500 series does not support a "service port", Is there any way to move the management port out-of-band with no access to APs and just use the other ports for AP management?

I haven't had my morning coffee ... But let me give this a shot..
I am going to say no. The managment interface is needed for APs to join. If you isloate this interface no APs can join. Even if AP managers are used, the AP requries to touch the managment interface when booting up.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."
"Im like bacon, I make your wireless better"

WLC4402 mobility group for failover

Anyone know what the return time is for an AP to jump back to the primary controller from the secondary controller once it comes back online? I have a backup controller over a WAN connection that I'm using to backup four different locations. WLC is runnign 3.2.78 code. APs are 1000 series.

We're trying to figure this out as well; we have a WiSM, and try to get the APs to fail over from one side to the other. They do, but it takes them a good 30 seconds and obviously no traffic is passed during this time. Both controllers share a mobility group, and each mobility group peer can ping the other.
The APs are converted 1131AGs an 12xx series. We've used http://www.cisco.com/warp/public/102/wlc_failover.pdf to set this up, but there reregistration is hardly immediate, and the APs don't seem to ever switch back to the primary controller once it comes back up. Any suggestions?

Mobility Group

How man wirelesslancontrollers are permited configure into the same mobility group?

Hi Ricardo,
Just to add a clip to the good info from David and Larry (5 points to both of you!);
A mobility group can include up to 24 controllers of any type. The number of access points supported in a mobility group is bound by the number of controllers and controller types in the group.
Examples:
1. A 4404-100 controller supports up to 100 access points. Therefore, a mobility group consisting of 24 4404-100 controllers supports up to 2400 access points (24 * 100 = 2400 access points).
2. A 4402-25 controller supports up to 25 access points, and a 4402-50 controller supports up to 50 access points. Therefore, a mobility group consisting of 12 4402-25 controllers and 12 4402-50 controllers supports up to 900 access points (12 * 25 + 12 * 50 = 300 + 600 = 900 access points).
From this good doc;
http://www.cisco.com/en/US/docs/wireless/controller/4.0/configuration/guide/c40mobil.html
Hope this helps!
Rob

2500 series support mobility groups?

Similar Messages

Maybe you are looking for