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?

Similar Messages

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

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"

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

Mobility Anchor between a 5700WLC and a 8500WLC

Hi
I've been apporached to possibly setup a Mobility Anchor between the company I work for and an external company.
We currenly implamenting the 8500WLC, but the external company have 5700 WLC converged wireless, which of around 12 months ago wasn't able to create a Mobility Anchor.
As the external company will only want to broadcast over our APs, we wont be broadcasting over theirs, would it be possible to create a mobility anchor then?
I remember speaking to Cisco last year, and they said it is on their road map, but not sure it it is there yet.
cheers

I think it is possible as long as you have compatible software version on your 8500. It has to be either 7.6.x or 8.x where you can configure new mobility, then only it can be peer with 5760. Refer this for mobility peering config for those platforms
http://mrncciew.com/2014/05/06/configuring-new-mobility/
Once you have the above then you need to configure the mobility anchor feature for specific SSID. Since you want to advertise their SSID on your AP, on their 5760 SSID to be configured as mobility anchor
wlan XYC
mobility anchor
On your 8500 mobilty anchor config for the given SSID (XYZ) you need to specify the 5760 management IP as mobility anchor.
HTH
Rasika
**** Pls rate all useful responses ****

Mobility groups - Sync Controller Configuration

I have 2 5508 controllers in a mobility group. Does anyone have a good way to keep the configuration between the 2 controllers synched up?
I thought about copying the config from my primary controller to the secondary controller, but I would think there is a more elegant way to make this happen.
Thanks
Larnel

Wat exactly do u wantto sync up??
here is the deployment guide which u can use!!
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob41dg/ch2_Arch.html#wp1028143
lemme know if that helps!! please dont forget to rate the usefull posts!!
Regards
Surendra

What is the difference between "Invisible" (11g) and "virtual" index?

Hi
What is the difference between the "Invisible" index and "virtual" index?
Thanks
Balaji

Indexes can be visible or invisible. An invisible index is maintained by DML operations and cannot be used by the optimizer. Actually takes space, but is not to be used as part of a potential access path.
AFAIK, a virtual index is created by the tools used in SQL statement access path tuning to provide an alternative for the optimizer to test. It does not take any real space as it is a pure in memory definition.

Routing issue between Cisco device and Virtual machine

Hi Guys,
We have two local subnets in a virtualized environment, subnet 1 has a VM operating as a firewall, we would like all traffic for subnet 2 to go via VM on subnet 1, this will police traffic on subnet 2 and then reroute.
The infrastructure involved comprises,
Internet Edge Switch -> ASA -> Core Switch -> IBM Flex chassis
The Internet edge switch is directly connected between the ISP routers and the Cisco ASA firewall pair (A/S). The ASA is then connected to the Core switch. Connected from the core switch is an IBM Flex chassis, via a port channel (all vlans allowed)
The local subnets in question are as follows:
Vlan 101 (10.1.1.0/24)
Vlan 102 (10.2.1.0/24)
The VM in question has two NIC cards having IP address of both subnets.
NIC 1: 10.1.1.1
NIC 2: 10.2.1.1
We would like packets destined for 10.2.1.1 to land on 10.1.1.1 IP address. At the moment traffic for each vlan routes from the outside to their respective local subnets successfully, what we are having difficulty with is directing traffic for subnet 2 via subnet 1 VM firewall.
At the moment we have tried adding a static route on the core switch but it didn’t work
ip route 10.2.0.0 255.255.255.0 10.1.1.1
I will appreciate if you could share your knowledge and guide me how to achieve this goal.
Thanks in advance :-)

Hi,
I think for this to work you need a transit vlan between the VMs and the core switch. So, if you have 2 vlans on the VM (101 and 102) you use the VM switch to route between the vlans and in order to go outside the local vlans you would use the core switch. In this scenario you would not have an SVI (layer-3) interface on the core. The only thing that core will have is the layer-2 vlans (101 and102). You would than need a static route on the core switch to point to the transit vlan on the VM side.
so, for example, if the transit vlan is vlan 110 and the ip is 192.168.1.0/24
on the core you have static routes:
ip route 10.1.1.0/24 192.168.1.2 (VM side)
ip route 10.1.2.0/24 192.168.1.2 (VM side)
You also need an SVI for vlan 110 with ip address 192.168.1.1/24 on the core.
on the VM you need a default route to point to the core (192.168.1.1).
Is this what you are trying to do?
HTH

What are the bandwidth requirements between a WCS and a WLC?

We have a customer who has two locations Site A (approx. 30 APs) and Site B (approx. 50 APs). Each site has a WLC. The customer wants to deploy a WCS at Site A that will monitor both WLCs.
What I have been unable to find is how much traffic is going to be generated between the WCS at Site A and the WLC at Site B?
Primarily, I would like to understand how this configuration will impact their point to point WAN link.
Also, are there any known requirements in terms of max. allowable latency between the WCS and WLC?
Any anectdotal evidence would also be appreciated - such as any experiences running this over a T1.
In this particular case, the customer has a 100Mbps wireless point-to-point link as their WAN link, but I do not know the actual throughput capacity and/or if it is half or full duplex.
Thanks,
John

John,
This is very interesting question and I will try to answer with what I know after supporting WCS for a while.
WLC and the WCS communicate over SNMP only. The generated traffic is SNMP (UDP). It's not a lot in terms of bandwidth, should I say quite minimal. Running over a T1 (not congested!) should be completly fine.
There are a few things we can control about snmp as you are over a WAN link: we can increase the SNMP timeout, we can increase the SNMP retries and also, we can reduce the max varbinds per PDU, so the snmp packets sent are smaller and dont get fragmented over your WAN ISP.
As SNMP is UDP, the only things you can control is the timeout and the number of retries because UDP doesnt have the control that TCP offers.
The most intense traffic will be when you first add your controllers in WCS.
I have seen quite a few deployments with WCS over WAN link and tweaking those settings I mentioned made it possible.
You can find those settings in WCS -> Administration -> Settings -> SNMP
HTH

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.

Mapping Roles/Groups between OBIEE 11g and Oracle EBS R12

Hi,
We are implementing OBIEE 11g with Oracle EBS R12 as source system. Also we are using Out of the box RPD for Oracle EBS R12.
But we are facing lot of challenges to map OBIEE 11g groups and EBS roles and responsibilities. We do not have prior experience with EBS as source system.
Can anyone tell how to map between obiee groups with Oracle E-Business suit R12
Is there any document link or notes regarding this.
Any help regarding this will really save us.
Thanks in advance

Please read:
Integrating with EBS Suite Security: http://docs.oracle.com/cd/E28280_01/bi.1111/e16364/ebs_actions.htm#BIEIT1321
As I understand you need to create a Connection Pool to your EBS database. I think that would be a serious security aspect for the integration to work over two different networks. But I don't think it's impossible.
Domain Prerequisites is another challenge in this scenario.
More specifically: http://docs.oracle.com/cd/E28280_01/bi.1111/e16364/ebs_actions.htm#CHDHCAFD

Syncing smart groups between Address Book and iPhone

When I do my regular iPhone synch, it will import regular groups but doesn't seem to want to import Smart Groups. Am I doing something wrong? If not, is there a workaround? Thanks, Katie

That's the only solution I've been able to come up with, but it makes Smart Groups useless in my Address Book. I was hoping I was doing something wrong.
Glad to know others are doing the same thing.
Thanks so much.
Katie

WLC 5508 and mobility groups

Hi,
We are using 2 WLC 5508 running 7.0.98.0 sw (AP's are 1142) at our primary site. They are hosting 3 different WLAN/SSID's, one for guest and the
other 2 are for corporate access. We have put the WLC's in a mobility group, say "AAAA".
Now we have the need for our UK peer site to publish a corp WLAN that exists in UK - at our site, and when trying to configure for that (following the c70cg.pdf) - I put the WLC's for UK in a new mobility group, say "BBBB". But i can't add our WLC's into that mobilty group
(i get a duplicate mac address message).
What's the correct way of configuring this, does all WLCs need to be in the same mobility group?
Is there some reason why we can't have 2 mobility groups? Is there any upside/downside to configuring 2 mob. groups?
Any clearification would be greatly appreciated
BR
//Mikael

I think you are misunderstanding , so far what you did on your local swedish site is correct. Your two swedish WLCs have to be in their own same mobility group so you can give seamless roaming to your wireless users across your swedish area without interruption.
On a WLC mobility group config page, you can have only one entry per WLC, this is why you are getting the duplicate error message.
WEBGUI - CONTROLLER - MOBILITY MANAGEMENT - MOBILITY GROUPS
If you want to put your 4 WLCs so they exchange mobility messages, the following has to happen on all 4 WLCs.
xx:xx:xx:xx:xx:xx 192.168.1.1 uk
yy:yy:yy:yy:yy:yy 192.168.1.2 uk
zz:zz:zz:zz:zz:zz 172.17.1.1 sweden
aa:aa:aa:aa:aa:aa 172.17.1.2 sweden
Note when you add WLC on the mobility section, the WLC start sending messages to each like, hey i have this client and you have that client and so on. But this has nothing to do with what you are trying to achieve.
With regards to the execs that are coming, yes, replicate the SSID and point it to the Radius Server they have in UK, add your swedish WLC(s) as a NAS on the Radius Server and it should work as if they were in UK. that should be enough and i advise you to do the following for mobility groups config.
on the two UK WLCs
xx:xx:xx:xx:xx:xx 192.168.1.1 uk
yy:yy:yy:yy:yy:yy 192.168.1.2 uk
on the two Swedish WLCs
zz:zz:zz:zz:zz:zz 172.17.1.1 sweden
aa:aa:aa:aa:aa:aa 172.17.1.2 sweden
hope i cleared it out for you. greeting from cold Belgium tonight :-) and hope the execs will enjoy Sweden!

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.

Mobility group between controller 4400 and virtual wlc

Similar Messages

Maybe you are looking for