WLC Mobility and Interface IP Address

Hello,
I am in the process of adding an additional WLC to an environment that currently has only 1 WLC. I am going to set up a single mobility group. Do the IP addresses of the vlan interfaces on both WLCs need to be the same value? I realize that the virtual interface does need to be the same, but not sure about the vlan interfaces.
Any comments are appreciated.
Thanks.
JT

Hi,
no they don't need to be the same. You don't even need your WLCs to have interfaces in the same subnets. They can have all interfaces completley different. Just the virtual interface needs to be the same.
Nicolas
===
Don't forget to rate answers that you find useful

Similar Messages

WLC 5508 and Client IP addresses

we have installed our first 5508 in a small remote office. I setup a DHCP range on the 5508 to give the AP's a IP address. After that I changed the AP's to have static IP address. I wish for the wireless clients to use our DHCP servers here at the home office, so I shut down the DHCP service on the 5508. Now the Clients will not get an IP address. So now I re-enable the scope and the clients get an IP address. How do I configure the 5508 so that the wireless clients will get an IP address from our DHCP servers and not the 5508?

Go to WLAN > click the SSID of your choice > Advanced tab > click on "DHCP Server" and enter the DHCP Server.

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

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!

Anchor mobility between WLC 5508 and Aruba/Clearpass

Hello. I have a question regarding the abiltiy to configure anchor mobility between a 5508 WLC and an Aruba controller. To date, my understanding is it has never been possible and I have never found any documentation that says it can be done.
Scenario: My organization and a partner organization co-own a hospital. We coexist on a large campus, with each org having a number of buildings that the owning org maintains the network presence in. We also maintain back-to-back firewalls between us and do not hand-off any direct layer 2 interfaces to each other. However, the two orgs do partner to provide each others business SSID's in each other's WiFi networks using anchor mobility. Our current solution utilizes an A/M tunnel between my org's 5508 controllers and the partner orgs 2504 controller and we explicitly permit the tunnel traffic between partner controllers for A/M to work. Last year, the partner org retired some old WiSM's and changed their wireless solution to Aruba and recently implemented Clearpass. In order to maintain A/M with us they left a 4404 operational, but due to the newer code we were running they were forced to purchase a 2504. So now they are only maintaining a limited footprint in their network with a few Cisco AP's and the rest of their coverage areas use Aruba AP's and they have indicated that they want to completely retire their Cisco WLC's. Because we host some of their SSID's on our controllers and can tunnel them to their 2504, they get all of their WiFi traffic coming from our network, however my org can only connect to our SSIDs on their campus in certain areas.
The solution I have been asked to provide is to find a way to continue providing some sort of anchor mobility services between our WLC's and their Aruba controllers. My org maintains that we do not want to simply hand them a layer 2 interface for security reasons, but they want our SSIDs to be available in all areas of the partner org's campus and vice versa. So far I have stalled the partner org's plans to retire their WLC's by telling them that retiring their WLC's will completely break WiFi between orgs, but they are adamant that some sort of A/M solution must be found.
Is there any way to do some sort of A/M between a WLC and Aruba controller and if so, is there any documentation showing configuration examples etc?
Thanks,
John

Hi John,
I do not think it will work. Even if it get working somehow, it will be operation nightmare to troubleshoot & fix a issue since both vendor will say it is NOT supported solution.
What about if you ask them to advertise your SSID (assuming it is dot1x) on their APs as another SSID on their network, but pointing it to your RADIUS & DHCP for IP connectivity (you do not have layer 2 requiremnt for this & can do this as long as you have L3 communication between each other)
HTH
Rasika
**** Pls rate all useful responses ****

How to sync contact list and yahoo contact list and macbook pro address book without mobile me

How does one merge the contents of my verizon iphone contact list and my macbook address book and my yahoo contact list and have ongoing syncing without mobile me? thanks

THANK YOU! I have been using companion link up until you posted this. This makes it so much easier to keep my business contacts on my phone. Much faster too! I use the Exchange Server so I'm hoping by doing this, my contacts will be synced via wireless. I'll let you know if it works. Thanks again for the great post.

WLC 5508 and LightWeight APs Deployment question

Hi There,
Can you please wit the following question in regards to the deployment of a new WLC and new LAPs,
I have configured and connected a 5508 WLC and 3500 series LAP.
LAG is enabled in the WLC and successfully connected to the neighboring switch (using etherchannel) and to the network.
The port-channel port is set to trunk mode obviously and certain vlan ids are currently allowed (3-5)
The management interface has this IP address 192.168.5.250/24
I created a WLAN with WLAN ID 3, Interface set to Management and say SSID test1
I have connected a new LAP to the network, which switchport interface is set to access mode and assigned with vlan id 3. The LAP is able to join the WLC successfully with an IP address, such as, 192.168.3.100 (assigned via DHCP).
When I try connecting a mobile client to the wireless LAN, it can successfully detect and connect to the WLAN, created in the WLC (test1) however it gets an IP address by DHCP, in the 192.168.5.0/24 network, which is the IP range of the management interface's IP address.
What can I do to get the clients connecting on network 192.168.3.0/24? I thought this would be the case since I allocated the WLAN Id of 3 in the WLAN test1 configuration and since the LAP switchport is set to access mode with vlan ID 3.
Cheers,
egua5261

Hi,
The WLAN ID has no effect with the VLAN ID. WLAN ID is just an identifier for the WLAN.
you said "Interface set to Management and say SSID test1" and here is your issue.
You set the interface of the WLAN to the management. So, the WLAN will be mapped to the VLAN to which the management interface is mapped to.
What you need to do is to create a dynamic interface with ip range in 192.168.3.0/24 and provide VLAN ID for that interface and assign your WLAN to this new interface. This way your clients will get an IP from this specified range.
HTH
Amjad

Use WLC's service interface IP when add WLC into WCS

Hi All,
Does anybody know if there's any limitations or bugs to use WLC's service interface IP when add WLC into WCS?
Another question is I remember there's a post previously says that there are a bug regarding to ARP if the WLC not using LAG but connect one port to one switch, connect another port to another switch, so that's why it is strongly suggested to use LAG, but I can't find it now, anybody know it? Thanks!

The service port is controlled by the service-port interface and is reserved for out-of-band management of the controller and system recovery and maintenance in the event of a network failure. It is also the only port that is active when the controller is in boot mode. The service port is not capable of carrying 802.1Q tags, so it must be connected to an access port on the neighbor switch.
If the service port is in use, the management interface must be on a different supernet from the service-port interface.
The service-port interface controls communications through and is statically mapped by the system to the service port. It must have an IP address on a different supernet from the management, AP-manager, and any dynamic interfaces, and it cannot be mapped to a backup port. This configuration enables you to manage the controller directly or through a dedicated operating system network, such as 10.1.2.x, which can ensure service access during network downtime.
The service port can obtain an IP address using DHCP, or it can be assigned a static IP address, but a default gateway cannot be assigned to the service-port interface. Static routes can be defined through the controller for remote network access to the service port.

WLC 2100 and DHCP strange issue.

Hi,
i have this scenario: 1 WLC 2100 and two LW AP 3500 connected. If the access points are connected via external switch evrything works well - AP and Clients get IP address from external DHCP and this is ok but when im connecting AP 3500 directly to one of ports on WLC i need to chceck in controller web Controller -> Advanced -> DHCP -> Enable DHCP proxy - after that AP get IP addres and clients get too but ip is assigned from external dhcp but the gateway is set as controller IP address (!!!) so clients not works. I want to configure access points connected directly do WLC.
I have small setup and i have configured all in the one vlan - management dla users are in the same vlan.
And the second is - for what usage is internal DHCP server - and how to use it?

When "Enable DHCP Proxy" is not enabled tha LW AP 3500 cannot get IP address if it is connected directly to LWC... when i add this option then on both LW AP 3500 - one connected to WLC and second directly to switch give me DHCP address from external DHCP but gateway sets as LWC management IP.
I made test - connected client witout "Enable DHCP Proxy":
Client IP 192.168.1.201 (correct in dhcp server logs), default GW 192.168.1.1 (correct gateway for this DHCP) correct dnses and in windws ipconfig i see "Server DHCP 192.168.1.1" all is correct.
Disconnected client and clicked "Enable DHCP Proxy":
Client IP 192.168.1.201 (correct in dhcp server logs), default GW 192.168.1.252 incorrect gateway - ip of WLC management interface) correct dnses and in windws ipconfig i see "Server DHCP 1.1.1.1" that shows that WLC modified DHCP packets... but what it try to set default GW as WLC?
WLC data:
Software Version
7.0.98.0
I can attach screenshots and any other configutation if you need.

Differences Between WLC 2000 and 4400 series

Besides the supported number of access points, what are the differences in features between the WLC 2000 and 4400 series?

On the 2006, you have 4 ports on the back, that can support up to 3 AP's being directly connected, and the other port as your connection to the network, and it does not support LAG (Link AGgregation). The ports are 10/100M, and it can not be an anchor for a mobility group.
On the 4400, you either have a 4402 or a 4404,the 2 has 2 Gig interfaces, and the 4404 has 4 Gig interfaces, you can not connect AP's directly to a 4400. Both 4400's will support LAG, and they can be used as anchors in a mobility group. Those are the big differences in them. They configure up the same, and interact with the wired and wireless networks the same.

Best practices for network design on WLC 2504 and 5508

Dear all:
I'm looking for some recommendations on WLC 2504 and 5508 about the the following:
Maximum amount of AP per port
The scenario when to use all ports in both WLC
Maximum number of clients(users) per port
Bandwidth comsumption of management vs data in order to assign one port for management
I've just found this:
Cisco 5508 controllers have eight Gigabit Ethernet distribution system ports, through which the controller can manage multiple access points. The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 models allow a total of 12, 25, 50, 100, or 250 access points to join the controller. Cisco 5508 controllers have no restrictions on the number of access points per port. However, Cisco recommends using link aggregation (LAG) or configuring dynamic AP-manager interfaces on each Gigabit Ethernet port to automatically balance the load. If more than 100 access points are connected to the 5500 series controller, make sure that more than one gigabit Ethernet interface is connected to the upstream switch.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/6-0/configuration/guide/Controller60CG/c60mint.html
Thanks for your help.

The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 models allow a total of 12, 25, 50, 100, or 250 access points to join the controller.
This is an old document. 5508 can now support up to 500 APs if you run firmware 7.X. 2504 can support up to 75 APs if you run firmware 7.4.X.
I'm looking for some recommendations on WLC 2504 and 5508 about the the following:
Best practice and recommendation is to LAG all ports so you will be able to form a link redundancy. If one link goes down, you have other link to push traffic.

HH4 and static IP addresses on home network

I want to assign a static IP outside the DHCP range to a server on my home network. I know I've done this in the past as I already have another server on the network which the HH4 recognises as having a static IP (and not in the DHCP range) but I can't for the life of me remember how to do it now.
I do recall that it wasn't obvious last time, but I've looked repeatedly through the HH config options and can't find it. The only place that looks likely is the Device Information page, where if "IP address assignment" is DHCP then you can select "Always use this IP address" and type an IP address, but only addresses within the DHCP range are accepted (this is reasonable). But there seems no way to provide a non-DHCP address.
I've read elsewhere that I should allocate the static IP on the device itself, but this doesn't work - while the device is able to connect to the LAN and can ping/can be pinged by other devices, the HH doesn't recognise the device and it's unable to connect to the internet.
I've constantly been frustrated by the non-standard interface of the HH4, and the fact that BT will provide little information on how to configure it (no manual is available). I called BT just hours ago to ask their tech support the same question I'm asking here, and their response was that "they don't have that information". When I said I was amazed that they don't know how to support their own hardware, they replied that it came ready configured and I shouldn't need to change it. Unbelievable. I was invited to subscribe to their tech expert support for £8 per month to get the answer, so I suspect that the claimed ignorance is just a revenue-earning opportunity.
Anyhow, any help will be very welcome.
Solved!
Go to Solution.

licquorice wrote:
Hmm, as far as I'm concerned the only 'true' static address is one configured on the device itself. Anything else is a non-changing dynamic address which is still at the mercy of the router dishing it out correctly.
That's a fair point. Perhaps I'm not used to routers (or just never used the feature) that allow "sticky" allocations within the DHCP range. So I see (saw?) DHCP and non-DHCP addresses as different.
However, I have to admit to feel a bit stupid at this point. I've just looked at the HH display and now I can see my device in all its static glory! This is after a number of days of testing and experimentation and getting nowhere (and before you ask, yes, regular refreshing). It's puzzling - perhaps it takes time for the HH to pick up a static allocation and I just didn't give it long enough.
So it does appear to be working now. I can confirm that your advice of just defining the address on the device is the way to go, and eventually the HH will recognise it.
Thanks to all for your patience!

Virtual Interface IP address

Hi,
In all Cisco documentation 1.1.1.1 is always specified as Virtual Interface IP address.
Here is my concern. When wireless client gets an IP address (through DHCP), 1.1.1.1 is entered as DHCP server which means that at 50% lease time client will attempt DHCP Request to 1.1.1.1
1.1.1.1 is not routable on the wired network, but controller makes sure that it is accessible on the wireless network.
The problem is if you have both wired and wireless connected, default gateway through wired connection wil have less cost, so client will attempt to send traffic to 1.1.1.1 using wired interface and will obviously fail.
At 83.5% of lease time client will attempt full DHCP process starting from Discovery and I guess this is when the IP on wireless NIC will be renewed, cause those Discovery messages are to 0.0.0.0....
Is my understanding correct?
Thanks!
David

Hi,
With both wired and wireless active at the same time (when laptop is docked for example)DHCP Request to 1.1.1.1 will fail cause it will be sent using wired interface and not wireless (default route metric in the host's routing table). This will cause this DHCP Request to fail at 50% lease time.
Next step is DHCP Discover at 83.5% of lease time. Destination IP will be 255.255.255.255 and it will be generated specifically on wireless interface, since this in the interface that needs to renew the IP.
This is exactly my question. Will this Discover to 255.255.255.255 go through wireless interface, cause this is the interface that needs IP addresses renewed. If so, I assume it will succeed and client's IP address will be renewed.
A bit worse than renewing at 50% lease time as a normal DHCP process, but better than loosing the IP at all when 100% lease time hits. 83.5% is somewhere in between...
Comments?
Can you also advise how do you disable DHCP Relay function on the controller? Do you need to remove DHCP IP addresses in WLAN configs?
Another question is about needing WLAN for Management interface. Is it needed for any reason? WLANs are always documented to be bound to Dynamic Interfaces and not Management, however Management interface does appear in the drop down menu under WLAN configuration. Thoughts?
Thanks!
David

Flex mobile and PHP project

Hi! Recently I've downloaded the Flash Builder for PHP to work with my Zend Server remotely located in OpenShift online. I did not download and install the Zend Server physically on my computer. Hence, when creating the Flex mobile and PHP project, I couldn't find my web root address. Now I have an error connecting to the MySQl database in the server from the Flash Builder. Can someone help me with this? I'm new to using these programs.
I'm following this guide on building mobile apps:
http://files.zend.com/help/Flash-Builder-for-PHP/Getting-Started/Mobile/build_a_mobile_(ph p)_application.htm#Step_13:_Preview_the_Mobile_Application_Using_the_Desktop_Emulator

PHP is server side.
If you want to have a app to function offline you would probably need sqlite and then code actionscript to synch data when the device regains it's connectivity.

How do I get about:config and other about: addresses to drop down from URL bar?

How do I get about:config and other about: addresses to drop down from URL bar?
It's a pain having to retype them in full... not sure why there is no easier interface to them.

hello, you can bookmark the sites for faster access.
[[How to use bookmarks to save and organize your favorite websites]]

WLC Mobility and Interface IP Address

Similar Messages

Maybe you are looking for