Mobility Groups Between...

Hi experts,
I am managing 3 WLC:
1- WLC 2112 - code version 7.0.235.0
2- WLC 2112 - code version 7.0.235.0
3- WLC 5508 - code version 7.6.130.0 (new purchase)
Is possible to group this 3 WLCs in one Mobility Group

Thanks for you replay,
please correct me, i understand over your replay that directly this versiosn is not supported, for compatibility to work must be in sequence as is release from CISCO, see the image.
The WLC 2112 with CODE version 7.0.235.0 is only compatible with version such as 7.2.x and 7.4.x right?
The WLC 5508 with CODE version 7.6.130.0 is only compatible win versions such as 8.x and 7.4.x right?
Thanks for your quickly replay.

Similar Messages

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?

Mobility groups between WLC 4400 & 5500

Can I configure a mobility groups between 4404 Wireless LAN Controllers and 5500 Wireless LAN Controllers?
Thanks.

Yes, the platform doesn't matter. The code used to matter but recent versions are ok between each others.
Nicolas
===
Don't forget to rate answers that you find useful

Mobility groups between WLC 2106 & 5500

Can I configure a mobility groups between 2106 Wireless LAN Controller and 5500 Wireless LAN Controllers?
Thanks.

Hi Patricia:
Welcome to the forums then.
Actually Scott's answer was the correct one. Not mine. So just to appreciate Scott's efforts (Thanks Scott) try please to mark his answer as the correct answer. Just below his answer there is a button to mark it as correct answer.
Come back soon.
Amjad
Rating useful replies is more useful than saying "Thank you"

Can we create Mobility group between WISM2 and WLC 5500

Dears,
I need your feedback urgent please,
Can we create Mobility Group between WISM2 and WLC 5500
Firmware for WISM2 > 7.4.121.0
Firmware for WLC5500 > 6.0.196.0
I created Mobility Group with (IP address , MAC Address and Mobility group name) for Foreign Controller. if any configuration required from my side.
Wait your feedback urgent please
Regards,

Hi,
Controllers do not have to be of the same model to be a member of a mobility group. Mobility groups can be comprised of any combination of controller platforms.
Thats enough :)
Regards
Dont forget to rate helpful posts

WLC mobility group between 4404 and 5508 controllers

Mobility 'Control and Data Path Down' between 4404 and 5508 WLC's.
Hello, we have 5 x 4404 WLC's running 7.0.240.0 with mobility configured fine between them.
We have installed a 5508 with HA running 7.4.110.0, and have tried to add it to the mobility group, however we see 'Control and Data Path Down' between the new 5508 and all the 4404 controllers.
All controllers have:
The same virtual address
Management interfaces are in the same VLAN, and indeed all the controllers connect via the same pair of 3750X stacked switches.
The default mobility domain name is the same
4404 output when issung the command 'show mobility summary'
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
5508 ouput when issueing the command 'show mobility summary'
Mobility Architecture ........................... Flat
Mobility Protocol Port........................... 16666
Default Mobility Domain.......................... SGH-Mobility
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0xe209
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 6
Mobility Control Message DSCP Value.............. 0
I've spent quite some time double checking all the configurations to no avail.
Has anybody seen this problem before?
Kind regards
Dave Bell

Thanks Sandeep.
I am well versed with WLC's and mobility, however trying to add a 5508 to a mobility group with 4404's has come up with a bit of a curve ball.
All the 4404 controllers all joined the mobility group fine, no problems at all - its only the 5508 I am struggling with.
In theory its simple, populate the IP address, and MAC addres of the management interface of the remote WLC, as long as the management interfaces are in the same VLAN, and the Default Mobility Domain Name are the same it should come up.
Interestingly I have found the 5508 reports its own management interface MAC address incorrectly when viewing the Mobility Groups:
For example:
{Screen shot WLC1.jpg}
5508 management address is 10.95.x.x and when viewing the Mobility Management screen it shows its own MAC address as bc:16:65:f9:37:60.
however!
From our router is I do an sh arp | i 10.95.x.x (controller management address), I see:f872.eaee.becf.
{Screen shot wlc2.jpg}
Hence the WLC reports as: bc:16:65:f9:37:60
and
The network reports as: f872.eaee.becf for the same IP address.
I have changed the other WLC's to the MAC adress seen on the network for the new controller, aka changed from
bc:16:65:f9:37:60
to
f8:72:ea:ee:be:cf
I now see the controllers reporting the mobility with the new controller as 'Control Path Down', however I am at a loss as to what may be causing this?
Kind regards
Dave Bell

Problem configuring mobility group

Hi, I'm trying to configure a mobility group between 4 WLC's. 2 of 4 form a group and those two are the two on the same cards.
The two cards are on separate subnets and each have are connected to a FW. I've opened up for UDP12222-12223 UDP16666-16667 protocol 50 and protocol 97
any other ideas?

Yes these are WiSM blades!
##from .15## Controllers configured in the Mobility Group
MAC Address IP Address Group Name Status
00:1e:4a:fa:68:c0 x.x.x.10 brf Control and Data Path Down
00:1e:4a:fa:68:e0 x.x.x.42 brf Control Path Down
00:1e:4a:fa:99:60 x.x.x.15 brf Up
00:1e:4a:fa:99:80 x.x.x.47 brf Control Path Down
##from .10## Controllers configured in the Mobility Group
MAC Address IP Address Group Name Status
00:1e:4a:fa:68:c0 x.x.x.10 brf Up
00:1e:4a:fa:68:e0 x.x.x.42 brf Control and Data Path Down
00:1e:4a:fa:99:60 x.x.x.15 brf Control and Data Path Down
00:1e:4a:fa:99:80 x.x.x.47 brf Control and Data Path Down
10 and 15 are on the same subnet and the same wism
42 and 47 are on the same subnet and the same wism

Bandwidth requirement between controllers in mobility group

We have a potential project spanning two sites a few miles apart. We are hoping of putting 1 controller at each site in a single mobility group to provide AP failover if one controller is to fail. We are planning on a total of 25-30 APs, roughly half at each site.
Questions:
Whats the minimum bandwidth required between sites?
If bandwidth isn't adequate can this be done with both controllers at one site and H-Reap access points for the other site? Am I correct in thinking that you can have no more than 8 H-Reap access points per WLAN (16 Reap APs per WLAN)?
Thanks!

Thanks! I think it will be fine. I was more worried about the event of a failed controller which would cause more traffic between the other APs and the backup controller at the other site. However with all the APs in H-Reap local switching mode it should work.

Multicast between wirless clients on same AP and Mobility Group

We have a autonomous wireless setup with a WLSM and WLSE. I have an issue with where I have 2 wirless clients that need to communicate using a multicast address for an application to work.
The clients can ping each other but the multicast stream is not working between the clients. The SSID is part of a mobility group that sits on a Cat 6509 sup720.
A debug on the sup720 shows the upstream multicast from one of the clients but you see no activity downstream to the other client.
Tunnel multicast stats: -
Tunnel176 is up, line protocol is up
Internet address is 53.32.176.33/27
Multicast routing: enabled
Multicast switching: fast
Multicast packets in/out: 2619/0
Multicast boundary: not set
Multicast TTL threshold: 0
Multicast Tagswitching: disabled
Sup 720 Debug: -
May 9 15:15:31: IGMP(0): Send v2 Report for 224.0.1.40 on Tunnel176
May 9 15:15:31: IGMP(0): Received v2 Report on Tunnel176 from 53.32.176.33 for 224.0.1.40
May 9 15:15:31: IGMP(0): Received Group record for group 224.0.1.40, mode 2 from 53.32.176.33 for 0 sources
May 9 15:15:31: IGMP(0): Updating EXCLUDE group timer for 224.0.1.40
May 9 15:15:31: IGMP(0): MRT Add/Update Tunnel176 for (*,224.0.1.40) by 0
May 9 15:16:15: IP(0): s=53.32.176.40 (Tunnel176) d=225.0.0.38 id=11765, prot=17, len=68(54), mroute olist null
May 9 15:16:15: IP(0): s=53.32.176.40 (Tunnel176) d=225.0.0.37 id=11766, prot=17, len=68(54), mroute olist null
May 9 15:16:25: IGMP(0): Send v2 general Query on Tunnel176
May 9 15:16:25: IGMP(0): Set report delay time to 0.9 seconds for 224.0.1.40 on Tunnel176
Please help as I need to get the 2 clients communicating using the multicast stream.
Thanks
Martin

Have you enabled multicast mode on the controller ?
If so, in what mode ? Unicast or multicast ?
If you selected multicast mode, do you see the controller joining the original stream and sending it to the LWAPP distribution group to the other APs ?

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

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 Group Requirements for Guest Anchor WLC

Hello -
I've alway assumed you can't create a guest tunnel between a local WLC and an anchor WLC that are in different mobility groups.   However, I was told recently (without much detail) that this is possible. So I have set out to test this.
I am trying to point one of my local WLCs guest SSIDs to a guest anchor WLC in a different mobility group.   I have a maintenance window coming up and I am looking to anchor the clients on one campus to the anchor WLC on the other campus so guest service does not go down.   Each campus is it's own mobility group.   In trying to set this up I went to the "mobility anchors" screen for the guest SSID on one of the local WLCs and I am unable to add the anchor WLC from the other campus because it's non in the drop-down menu. This is because it's not in the same mobility group.   So my question is how do I anchor clients coming through a local WLC in one mobility group to an anchor WLC in another mobility group?
To me it doesn't seem possible without significant configuration changes.   I don't want to reconfigure/recreate mobility groups.
Thanks
Chuck

Not only is it possible, I would recommend it. However, you may be confusing some concepts.
The Mobility Group is different than the Mobility Domain. I generally refer to the Mobility Group as those WLCs with the same Default Mobility Group Name, and the Mobility Domain as the entire Mobility List (where you can define up to 72 controllers from various mobility groups).
The point is that if WLCs 1-10 are GroupA, and WLCs 11-20 are GroupB, for anchoring to work you at least need to add the anchor to the mobility list of the foreign wlc, and vice versa.
If you notice, when you add a mobility entry to the list, it should ask you for mobility group. If you leave it blank, it should default to that of that WLC, but on GroupA controllers, you could define GroupB controllers (and specific GroupB) and then you should now have mobility established between your controllers and the Anchor configuration will have your anchors in the drop-down....
Does that make sense?

Mobility group same ssid multiple WLC

I have a 4400 and a 5508 WLC in the same location
We want to be able to roam between ap joined to both the 4400 and the 5508 using only one ssid
Do I only need to create a mobility group and add both WLC
then create only one WLAN on one of the controllers and it will be shared across bot WLC.
Or something else?

Resolution :
Yes you are correct. Please follow this link for Mobility groups and Roaming :
http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_mobility.html

WLC 5500 mobility group failover

Hey
I have a Question i am testing mobility group with
Failover for redundend connection between 2
Cisco 5500 Wlc.
On both the controllers i got the mobility working
And both the controllers have the same version
And configuration.
But when i unplug the main controller the access-
Points don't convers to the second one
The just keep on creaming can't find the main controller
Also with this thus the second wlc need to have the same
Interface ip address like managment..??
Thanks

What do you mean by "convers". An AP will only join one wlc and when that primary wlc is no longer available, should failover to the other/secondary wlc. Mobility is required for an AP to know about all the other APs in that mobility group. And if not configured correct, your AP will only be able to join that wlc.
Thanks,
Scott Fella
Sent from my iPhone

5508 Mobility Group

Clients are not able to roam between WCS controllers. Our mobility groups are working but we are not able to pass DHCP addresses between controllers

When you say mobility is working, what do you mean? Are you trying to use WLCB to assign a client on WLCA an address?

Mobility Groups Between...

Similar Messages

Maybe you are looking for