Roaming between 4400 and 5500 controllers

Hi, we are planning to do an AP migration, but there is a doubt for this.
Actually we have a 4402 controller with 1120 APs both of which are marked as EoL products, we want to jump over the new 2600 APs and 5508 Controller for increase signal coverage but we have the following deals:
Last firmware for 4402 controller is 7.0
Firmware needed for 5508 to support 2600 APs is 7.3
Is it possible to configure mobility between 4402 and 5508 even with different firmware branch?

Inter-Release Controller Mobility (IRCM)
Table 10 lists the inter-release Controller Mobility (IRCM) compatibility matrix.
Table 10 Inter-Release Controller Mobility Compatibility Matrix
CUWN Service
4.2.x.x
5.0.x.x
5.1.x.x
6.0.x.x
7.0.x.x
7.2.x.x
7.3.x.x
Layer 2 and Layer 3 Roaming
X
X
X
X
X
Guest Access/Termination
X
X
X
X
X
X
X
Rogue Detection
X
X
X
X
X
Fast Roaming (CCKM) in a mobility group
X
X
X
X
X
Location Services
X
X
X
X
X
Radio Resource Management (RRM)
X
X
X
-1
Management Frame Protection (MFP)
X
X
X
X
X
AP Failover
X
X
X
X
X
1 In the 7.2.x.x release, RF Groups and Profiles were introduced. RRM for 7.2.x.x and later releases is not compatible with RRM for any previous release.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin

Similar Messages

Diifference between WLC 2100 and 4400 and 5500

Hi
what is the difference between wire lan controllers(WLAN) 2100 and 4400 and 5500.

Hello syed
Cisco 5500 Series Controllers:
The Cisco 5500 Series Wireless LAN Controller is currently available in one model: 5508. The 5508 controller supports up to 250 lightweight access points and 7000 wireless clients (or 5000 wireless clients and 2500 RFID tags when using the client location feature), making it ideal for large enterprises and high-density applications.
Cisco 4400 Series Controllers:
Because the Cisco 4400 Series Wireless LAN Controller supports 802.11a/b/g and the IEEE 802.11n draft 2.0 standard, organizations can deploy the solution that best meets their individual requirements. Organizations can offer robust coverage with 802.11 a/b/g or deliver greater performance with 5x the throughput and unprecedented reliability using 802.11n and Cisco's Next-Generation Wireless Solutions and Cisco Enterprise Wireless Mesh.
The Cisco 4400 Series Wireless LAN Controller is available in two models. The Cisco 4402 Wireless LAN Controller with two 1 GB Ethernet ports comes in configurations that support 12, 25, and 50 access points. The Cisco 4404 Wireless LAN Controller with four 1 GB Ethernet ports supports 100 access points. The Cisco 4402 controller provides one expansion slot. The Cisco 4404 controller provides two expansion slots that can be used to add VPN termination.
Cisco 2100 Series Controllers:
These controllers are part of a Payment Card Industry (PCI) certified architecture, and are well suited for retail customers who deploy transactional data applications such as scanners and kiosks. With performance up to 100 Mbps, the Cisco 2100 Series Wireless LAN Controllers also enable small and medium branch offices to deploy collaboration applications such as guest access and mobile voice.

WLC 4400 and 5500 Fail-over

Can we do the same thing with WCL 4400 and 5500 series for failover? We have 1 existing 4400 WLC and we wanted to purchase another 1 for fail-over as well as backup. But right now, 4400 is EOL already. The only option is to have the 5500 WLC.
So if you do have previous set-up like this, so I would need your inputs.. Otherwise, same as usual, will gonna test to work this out.

You can have both in a primary and backup, but make sure they are on the same code version. I'm assuming that you also have the configuration correct for the two wlc to communicate.
I would put them both on the 7.0.220.0.
Sent from Cisco Technical Support iPhone App

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

Roaming between 1231A and 1142N

Gday Everyone,
Just would like to know your experience in roaming between LWAPP converted 1231A and 1142N APs?

Inter-Release Controller Mobility (IRCM)
Table 10 lists the inter-release Controller Mobility (IRCM) compatibility matrix.
Table 10 Inter-Release Controller Mobility Compatibility Matrix
CUWN Service
4.2.x.x
5.0.x.x
5.1.x.x
6.0.x.x
7.0.x.x
7.2.x.x
7.3.x.x
Layer 2 and Layer 3 Roaming
X
X
X
X
X
Guest Access/Termination
X
X
X
X
X
X
X
Rogue Detection
X
X
X
X
X
Fast Roaming (CCKM) in a mobility group
X
X
X
X
X
Location Services
X
X
X
X
X
Radio Resource Management (RRM)
X
X
X
-1
Management Frame Protection (MFP)
X
X
X
X
X
AP Failover
X
X
X
X
X
1 In the 7.2.x.x release, RF Groups and Profiles were introduced. RRM for 7.2.x.x and later releases is not compatible with RRM for any previous release.
"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin

Roaming between mesh and non mesh and mesh AP design

Hi There,
I need some verification on the following:
- Can client roam between Mesh AP 1550 series and Non-Mesh AP?
- I have 1550 series AP to be installed and all the mounting area are with data point ready, which connects back to switch. Would configuring mesh for this outdoor units recommended, and guide on this. Current guide i am looking from cisco site is basically the AP do not have wired ethernet connection, my design here a bit different, all the AP's have wired connection back to the switch.
Kindly assist.
Thank you
Rama

I have seen and done installs like this. The advantage is that you don't have to worry about the backhaul dropping. So it's like any LAP but big chunky outdoor AP. If the RAP looses Ethernet connectivity... Well it changes to a MAP. So you can look at
It as a benefit. It's always nice to be able to have Ethernet when you can.
Sent from Cisco Technical Support iPhone App

Compatibility with 4400 and 5500

Folks,
I have a doubt, there is an existing setup of 4400 series controller. I would like to add more access points , which the current controller cannot accommodate, also client requires redundancy in the solution. I was wondering, if it is possible to add 5500 controller and configure one to one redundancy b/w 4400 controller and 5500 series.
Regards,
Siddarth .

I see no reason why you couldn't. But make sure you share the same code and update the
mobility group.

Preventive maintenance WLC 4400 and 5500?

Hi good morning,
i asking for help in order to make a preventive maintenance for WLC 4000 and 5500.
the main problem is: can i open the WLC´s and clean all the circuits they have inside? or must i only cleaning out the WLC?
And i would like to know if there are documentation about this topic.
thanks.

thanks
I thought of opening the WLC, and use compressed air to remove dust only.
but like you mention would be better not open it.
Greetings

Roaming between WLC and vWLC on different code versions

Hi,
I have the following setup in our environment, a HA 5508 pair running 7.4.100 and a vWLC running 7.6.130. I have mobility setup between the two with the control and data path up and running. All the access points are setup for FlexConnect.
When I join an SSID using PSK on an AP associated with the vWLC and then roam to an AP on the 5508, I drop a few pings but stay connected no problem. However when I join an SSID using PEAP (both WLC's using Radius to Cisco ISE 1.2 for this) and repeat the test, my client actually drops my wireless connection and then rejoins.
Is this expected behaviour when running controllers on different versions? This is only temporary until I upgrade the 5508 pair.
Cheers
Brian

Oh... Forgot. With FlexConnect, you also want to create FlexConnect Groups. See this link:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_010001111.html
-Scott

4400 and 5500 in same mobility group

Hello
Has anyone experience or know if its possible to join 4400 wlc and 5508 to the same mobility group? Can't find much info out there, just want to find out if there are any gotchas.
Thanks

Yes you can but reference this link.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp123314
Sent from Cisco Technical Support iPhone App

Difference between 4400 and 7220

The 4400 was released in Australia (and possibly other countries) as the 7220. Apart from the model number on the front panel, does anybody know what differences there were between them?

According to this article, no difference:
http://www.everymac.com/systems/apple/powermac/stats/powermac7220200.html

WLC 4400 to 5500 Migration

We have a single 4404 that was setup long before I arrived with Guest networks that timeout and other such tweaks. Is there a document somewhere that shows a way to migrate the old settings to a new 5508 that we are purchasing? By the time the 5508 arrives I will have a very small window to setup the unit before a new wing goes live. I need the new unit as we have reached our limit of licensed AP's on the old 4404. It seems like everyone keeps talking about an easy way but no one says how to do it.
Sorry, I have never setup one of these units before from scratch so I don't know how long it will take.
Thanks for your input,
Todd

#4400 and 5500 are different platforms. At config level you will see different no. of ports, AP-manager, Passive client,.... Backed up config of 4400 should not be uploaded to 5500 and it is not cisco suggested practice.
http://www.cisco.com/en/US/partner/docs/wireless/controller/7.0MR1/configuration/guide/cg_managing_ctrlr.html#wp1063850
Configuring the same manually is the best practice.
If you've more controllers that needs migration then compare the config between 4400 and 5500 that look dissimilar and edit it manually and port it to target 5500 WLC.
Few Tips:-
#4400 doesn't support 7.2 while 5500 does, you can use the 7.2.110.x(MR1) which is recently released for 5508.
#Also, 5508 needs FUS update to avoid critical bug.

Voice over IP Roaming problems between 2 Wireless Lan Controllers.

Hello,
we have problems with Voice over IP roaming between 2 Wireless Lan Controllers, this problem is not always happening. I have attached the detailed configuration. We are using LWAPP 1242 & WLC 2106 Controllers.
The phones they are using are Siemens Enterprise optiPoint WL2.
Is there maybe something wrong with the configuration our can I try some different settings?
Regards,
Jordy Broekhuizen

When a wireless client associates and authenticates to a WLC, it places an entry for that client in its client database. This entry includes the MAC and IP addresses of the client, security context and associations, quality of service (QoS) contexts, the WLAN, and the associated LAP. When a client roams to another LAP associated to the same WLC, it just updates the client database with the new LAP information so that the data can be forwarded appropriately to the client. When a client roams to a LAP associated with a different WLC, either in same or different subnets, it sends the information in the client database to the new WLC. This helps client to retain its IP address across roams and maintain uninterrupted TCP sessions. For more information on roaming in the WLC environment.
For the further description following URL for the WLC may help you
http://www.cisco.com/en/US/docs/wireless/controller/5.1/configuration/guide/c51ovrv.html

Component and custom controllers

Hi! Can someone tell me the difference between custom and component controllers? and any guidelines as when to use what?

Hi,
Majority Component/Coustom controllers resembles same. Still I found following differences
There will be only one default Component controller (called global) in a particular project but there can be any number of coustom controllers (we can create depending upon the requirement).
Component controller has the follwing methods apart from wdDoInit(), wdDoExit()
public void wdDoPostProcessing(boolean isCurrentRoot)[
This method is called to handle data retrieval errors before rendering.After doModifyView(), the Web Dynpro Framework gets all context data needed
*for rendering by validating the contexts (which in turn calls the supply
functions and supplying relation roles). In this hook, the application
should handle the errors which occurred during validation of the contexts.
public void wdDoBeforeNavigation(boolean isCurrentRoot)[This allows you to flush the model queue and handle any
errors that occur. Firing outbound plugs is allowed.]
Genarally all the coustom code is coded in coustom controller for example if you want to add additional methods of your own, in case if you want to validate webdynpro UI elements input this validation code is coded in coustom controllers
go through the following URL
http://help.sap.com/saphelp_webas630/helpdata/en/eb/e1cb5eea012b4481f8077c6023a70e/content.htm
I hope it helped you
RK

WLC 4400 and WLC 5500

We have a site with a WLC 4400 and we would like to setup a Controller failover. The WLC 4400 is EOS/EOL and the replacement available is WLC 5508. Can someone advice me on how to configure these units in Primary /Secondary mode so that if any of the Controllers fail, the other one can take over?
Thanks,

Hi Akil,
You are most welcome
Yes, you can configure 4400's and 5500's in a redundant configuration, but both should be runningthe
same code version. I believe the latest version that is compatible for both is 7.0.220.0.
this is the last version that supports the 4400 series.
Here's a note that reflects the support;
Note
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.
http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mobil.html
Cheers!
Rob
"Show a little faith, there's magic in the night" - Springsteen

Roaming between 4400 and 5500 controllers

Similar Messages

Maybe you are looking for