7920 roaming between two WLCs

hi,
- i have two WLCs 4404 and 4402 in the same mobility group and all connections seem to be ok.
- one ssid for voip.
- two 7920 phones
when i roam between the WLCs i will lose the connection.
What should i configure on the WLC??
thx

Are you doing L3 mobility?
If so, would configure the voice ssid for the same VLAN on both controllers to see if that works or not.
Of course for mobility group setup, need the mac and IP configured on each contoller in that mobility group.
Ensure that 3.02 is loaded on the 7920 phones.
Would recommend 4.0.217.0 or later for the controller version.
Refer to WLAN SRND for more info.
http://www.cisco.com/univercd/cc/td/doc/solution/emblty30.pdf

Similar Messages

Roaming between two extreme

with an IPad 1..How to roam between two Apple expreme without loosing connection?
Thanks

See the second message of this thread for instructions on creating a "roaming network":
https://discussions.apple.com/thread/2273124?threadID=2273124

Roaming between two WiFi access points fails

Hi...
I just bought a Hawking WiFi range extender...a device that acts like a second wireless access point for rooms that are far from your wireless router. It's also known as a repeater. It has the same SSID (network name) as the one set up by the router.
You are supposed to be able to move about the house and you will connect to whichever device has the higher signal strength, transparently, with no hiccups, like moving your cell phone from one cell antenna to another.
The setup works fine with my Dell laptop, but not with my MacBook Pro or my iPad. When I change "zones", the Network locks up. This is repeatable and consistent.
I've heard rumors about Apple product difficulties with this "WiFi roaming."
Can anyone help?
Thx
Steve

I've been using a roaming setup in my home for years. The company I work for has building wide WiFi roaming setup with multiple WiFi access points on each floor. At home and at work, I frequently move my MacBook between access points without loosing things like my VPN, Screen Sharing, File Sharing, ssh terminal sessions, etc....
But 3rd party networking hardware has not always been well tested against Apple products. Many times 3rd party networking vendors test against some version of Windows and then ship it. Sometimes the 3rd party vendor offers a firmware update that corrects issues with Apple products.
At home I have Apple Airport Extreme base stations for my roaming setup. At work, the company is using Cisco commercial WiFi access points.
A roaming setup needs to have all WiFi devices on the same network "Subnet". That means a 2nd WiFi base station cannot act as a router, but must be just a bridge on the existing router's subnet (generally that means it cannot be offering DHCP services nor NAT services).
The 2nd WiFi base station must have the same SSID (as you said you setup).
And it must have the same security password using the same encryption algorithm (WPA2 preferred from a security stand point). You did not mention this, but I'll assume you did this as well.

Mobility between Cisco WLC and Meraki(other vendor)

Is it possible that users can roam between Cisco WLC and other vendor wireless gear? Meraki keeps saying it is possible.
They keep saying it is a IEEE feature and everone should support but I do not understand how?

While theoretically possible with the adoption of capwap, it would require all the manufacturers to follow the specs exactly the same. Kind of like hearding cats, not impossible, but highly unlikely.. That's just my opinion
Sent from Cisco Technical Support iPad App

Roaming with Airport Express (bridging) between two Airport Extreme AP's

I have two Airport Extreme base stations set up on a company LAN that provide wireless coverage for our very large facility. Both are set up with the same SSID and WPA settings and they are 5 channels apart, 1 and 6. We have a cart with a computer and it uses an Airport Express / WDS to allow wired Ethernet bridging to our LAN via the wireless. I can't seem to get the Airport Express to "roam" between the two access points, ie, when one AP's signal gets too weak I would expect that the Airport Express would switch to the stronger of the two AP's. Is this a correct assumption?
In the AirPort utility when you set an Airport Express as a remote it only allows you to specify one "main" AP, so I don't know if this is why I can't seem to get it to roam between both AP's. Anyone have any experience / success doing this? Thanks for any information you can provide.
Joe Jenkins

if possible, it sounds like you need to configure a "roaming" network, not a WDS. Of course, I am assuming that all your base stations have access to your LAN via ethernet...
- Configure each base station with the same network name and authentication/password.
- Put each base station in bridge mode (unless you need 1 of them to distribute ip addresses).
- Each base station needs to be on a different channel - and make sure they spread apart, like 3 and 11, as opposed to 3 and 4.
Basically make sure they are configured exactly the same except for the wireless channel.
Roaming should improve.

Inter-Controller and Inter-Subnet Roaming between WLC 4402 and 5508?

Hi!
Will it support roaming between WLC 5508 ver. 7.0 and WLC 4402 ver. 4.2?

Here is the matrix for support of IRCM, but the answer is yes.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html#wp116668
Sent from Cisco Technical Support iPhone App

WLC - 7920 roam reason troubleshooting

Hi,
I have one WLC 4402 (4.1.185) and i have some cisco 7920 . I'm only use local mac filtering.
I also have WCS 4.1 and i tried to generate roam reason report but report didn't show any info.
How can i see in this info in WLC or in WCS.
Best Regards,
MC

Hi,
I didn't saw also PC's roaming. I thought i should I have to config CCKM instead of mac-filtering to see 7920 roam in WLC.
Regards,
MC

Client Roaming Within Single WLC with Different AP Groups

I am trying to setup a 4400 WLC with 2 different AP Groups mapped to its respective Dynamic Interfaces / Vlans. AP's are equally mapped to both the AP groups by Floor wise ex: First floor AP's connect to one AP group and the Second Floor AP's connecting to other AP group.
Goal is to create separate Network policy for each Floor using ACL's and apply to their respective Vlans on Layer 3 Switch. Wireless Raoming should happen seamlessly between these Ap groups making the DHCP changes by not disconnecting and connecting every time user roam across the Floors.
Problem is When Clients Roam between Floors i,e moving between AP Groups, they still maintain their old DHCP IP addresses when moved to new AP group even after Client re-authetication. This defies our goal of creating a Wireless Network Policy using single WLC.
Knobs i have tuned in WLC to acheive our goal includes....
1. WLAN Session Timeout - No use
2. DHCP Proxy Disable - No Use
3. ARP Time out - No use
Looks like WLC is storing the IP address and MAC information of the Client unconditonally during roaming and clearing out untill a manual or forced disconnect or disassociation is done.
Did anyone tried to implement this setup and made it running? Any help or suggestion would be higly appreciated.
Thanks
Guru

abit late for a reply but....try going to the SSID>Advanced and ticking the "DHCP Addr. Assignment" Required checkbox and test again.
What does the DHCP Required field under a WLAN signify?
A. DHCP Required is an option that can be enabled for a WLAN. It necessitates that all clients that associate to that particular WLAN obtain IP addresses through DHCP. Clients with static IP addresses are not allowed to associate to the WLAN. This option is found under the Advanced tab of a WLAN. WLC allows the traffic to/from a client only if its IP address is present in the MSCB table of the WLC. WLC records the IP address of a client during its DHCP Request or DHCP Renew. This requires that a client renews its IP address every time it re-associates to the WLC because every time the client disassociates as a part of its roam process or session timeout, its entry is erased from the MSCB table. The client must again re-authenticate and reassociate to the WLC, which again makes the client entry in the table.

Roaming between RV220W wireless router and WAP121 Access Point

Hello, I have recently purchased a RV220W wireless router and a WAP121 access point and i would like to allow my users to "roam" between the two networks as needed (so when the user is closer to whichever one they connect to that one since it has a better signal). For the most part I only have experience in cisco IOS and in actual routers not the wireless stuff so my knowledge has not exactly transfered over well.

William,
WDS will not work between the RV220W and WAP121 due to incompatible chipsets. The RV220W can be repeated using WDS by another RV220W or RV180W only. You will need to plug the WAP121 into the RV220W or try WorkGroup Bridge mode to repeat the signal.
Regarding roaming, the router or AP are not aware of each other and do not have the capability to disconnect a client and help them connect to the AP with the stronger signal. The client will switch to the stronger AP only when the original signal is lost.
The Aironet (enterprise) devices have the ability to utilize a wireless LAN controller which can help keep devices connected to the stronger signal and allow truly seamless roaming between APs.
- Marty

Roaming between E3000 wireless router and WAP300N

Hi all
The Linksys router I’ve got in my office room at home is providing poor coverage in my living room. Thus I’ve purchased a WAP300N and connected it by wire to the build-in 4 port switch of my Router (E3000). The set-up is providing a significant improvement in the living room, but… it seems as if the two wireless access points are “competing” over the “clients”.
When I move from the office room into the living room, my wireless equipment seems to be stuck on the connection to the wireless router in the office room – even though the signal from the WAP300N in the living room is much stronger.
The situation is exactly the same, when I move from the living room to the office room – the wireless equipment is stock on the weak signal from the living room.
I have to turn off and on the radio on my wireless equipment to get them to connect to the strongest signal.
Is there a way to make the “roaming” between wireless access points more smooth?
Kind regards
vonRasmussen

vonRasmussen :
Change the channel on the WAP or your router are on.
Not the 802.11?, but the transmission channels, which are probably transmitting on the same channel. I find the best results are at lease 2 numbers apart. if on is transmitting on channel 1 the next closest will be on 3. With multiple WAPs in a large area you would have to play Sudoko to make sure every one is 2 channels apart.
to quote Lisa Phifer:
Multiple access point configuration: Distinguish transmission signals;
Why should you access points use different channels? In a typical micro-cell Wlan, adjacent APs should always use non-overlapping channels, ( e.g., 1 ,6 ,11), to avoid co-channel interference.
Good Luck.
Dave

Roaming between Flexconnect groups for scaling

I have a customer that needs flexconnect at each of his 10 locations to access local servers and printers. The customer has a pair of 5508 WLCs running 7.6.130.0.
While the customer currently has 25 and under AP count per site, they are considering an expansion to 50 - 60 per site.
We are considering the mobility agent on 3650/3850/4500 switches, but the multi-hop restriction will drive the cost too high.
What is the downside for defining multiple flexconnect groups per site?
The customer is also considering Unified Communications. For example, would the voice RTP stream on a wireless IP phone roaming between APs on different flexconnect groups appear to be seamless?

If you plan on utilizing any real-time applications such as voice, you would not want these devices to be roaming between FlexConnect Groups. There will be a full re-authentication of the client; with the exception of OKC capable machines, which "may" roam more cleanly. This means some standard data clients may perform a fast roam, or at least not notice much of a hiccup even with a full re-auth.
In either scenario, you would want to make sure this is NOT a L3 mobility roam (ie. FlexConnect WLAN/VLAN mapping to different networks). This will cause major problems for all your clients as they will most likely end up talking on the new VLAN with their old IP address.
Mobility / Roaming Scenarios
WLAN Configuration
Local Switching
Central Switching
CCKM
PMK (OKC)
Others
CCKM
PMK (OKC)
Others
Mobility Between Same Flex Group
Fast Roam(1)
Fast Roam(1)
Full Auth(1)
Fast Roam
Fast Roam
Full Auth
Mobility Between Different Flex Group
Full Auth(1)
Fast Roam(1)
Full Auth(1)
Full Auth
Fast Roam
Full Auth
Inter Controller Mobility
N/A
N/A
N/A
Full Auth
Fast Roam
Full Auth
(1) Provided WLAN is mapped to the same VLAN (same subnet).

How DHCP scope will work between two Wireless contoller

Dear All,
I would like to inform you that we are going to deploy Wireless Network with redundancy of Wireless LAN Controller and we need to figure out how DHCP scope would work during fail over any one of Wireless LAN controller and DHCP Server .I have two site where Two Differenet DHCP Server would be palced with different DHCP socpe.So My query is that if Site-A(according to attached diagram) DHCP Server and controller fails how Wireless client will take the DHCP scope from Site-B(according to attached diagram) DHCP Server as it has been configured different DHCP Scope.Can any one tell me whether i can configure same DHCP Scope at Both Site's DHCP Server.
Is there any way to configure same DHCP Scope for two sites.For your infromation client wants two Different DHCP Server with different scope for Two Site and how redundancy would be ensured if any one WLC or DHCP goes down.
I am eagerly waiting for your reply as early as possible.Please help to figure out the solution.
I am going to attached Sample Design for your reference.
Thanks and regards
Erfan

Erfan:
My query was that if one wireless client already associated
WLC-A with one IP block of Location-A (DHCP Server) using SSID named TEST. If DHCP-A or WLC-A goes down then how that same client would associate with WLC-B and get the IP Block from Location-B (DHCP Server) using same SSID name TEST.
In this case the clinets connected to the APs in location A will disconnect (if the WLC went down) and they have to connect again when the APs join WLC-B. They will get IP address from location B block then.
If DHCP went down when new clinets try to connect the primary DHCP is down so they are referred to the secondary DHCP. connected clinets will disconnect only when their DHCP lease times out. They will try to renew but the DHCP server is not available. They will disconnect then and connect again and getting IP from B site.
1. How we will create same policy for that two different block using same SSID.
what policy? where?..etc?
2. client would be connected with Access point but they will get the IP through VLAN interface of the Controller and we have to assign IP helper address in the interface vlan.So how the the client would get the IP block if we assign two IP helper address in the interface vlan in case of failure of DHCP and WLC of one location.
3. If we assign two IP helper address then which DHCP Server will release the IP for client and we can make delay between two DHCP Server to release the IP address.
If two IP helpers are configured the switch will send them both the client's request and they client receives two offers. The clients chooses one of the offers. Usually the clinet will accept the faster DHCP server to respond.
If you are using the DHCP on the WLC then it is different. The WLC will always try to reach the primary DHCP server as long as it is reachable. If the primary DHCP is not reachable then it falls back to the secondary DHCP server.
Note that when you use IP helper then you usually disable DHCP Proxy feature on the controller. Do you have it disabled?

HA betewwn two wlc

Hi .
I hace 24 wlc 5508 with 250 license for each. I m planning to get 3new 8500 wlc as back up. Can I mix between two siffetent model. And what is the license coubt for the 8500 wlcs. Cab I order HA 8500 .
Sent from Cisco Technical Support Android App

Please refer to the below points esp. highlighted sections ( taken from link posted by Leo ) , it completely answers your query:
Configure one WLC as Primary (by default, the WLC HA Unit ID is Primary and should have a valid AP-BASE count license installed) and another WLC as Secondary (AP base count from the Primary WLC will be inherited by this unit) using the CLI in this step. In this example, WLC 1 is configured as Primary, and WLC 2 is configured as Secondary:
You do not need to configure the unit as Secondary if it is a factory ordered HA SKU that can be ordered from release 7.3 onwards. A factory ordered HA SKU is a default Secondary unit, and will take the role of the Standby WLC the first time it is paired with an Active WLC that has a valid AP Count License.
If you want to convert any existing WLC as a Standby WLC, do so using the config redundancy unit secondary command in the CLI. This CLI command will only work if the WLC which is intended to work as Standby has some number of permanent license count. This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500, and 8500.
Configure one WLC as Primary (by default, the WLC HA Unit ID is Primary and should have a valid AP-BASE count license installed) and another WLC as Secondary (AP base count from the Primary WLC will be inherited by this unit) using the CLI in this step. In this example, WLC 1 is configured as Primary, and WLC 2 is configured as Secondary:
You do not need to configure the unit as Secondary if it is a factory ordered HA SKU that can be ordered from release 7.3 onwards. A factory ordered HA SKU is a default Secondary unit, and will take the role of the Standby WLC the first time it is paired with an Active WLC that has a valid AP Count License.
If you want to convert any existing WLC as a Standby WLC, do so using the config redundancy unit secondary command in the CLI. This CLI command will only work if the WLC which is intended to work as Standby has some number of permanent license count. This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500, and 8500.

Wireless mobility between 2 WLC's

Hi all, when using 2 controllers, is it possible to sync the config between them automatically? or do you always have to do it on both manually?

I agree, pushing templates via WCS is definitely the right way to manage the WLCs. We have been asking about a feature that would allow you to compare two WLC configs for quite some time. I understand that WCS will have a feature soon that will help with that.
If you don't have WCS, you could always take a config you're confident with from a WLC and upload that to another WLC. You'll have to have that second WLC off the network of course and use the service port to accomplish this. Once you have the config on the second WLC, you just have to change specific settings (like system name, interface ip's, mobility members, etc.) before putting it back on the network.
No doubt more work that it should be...

How i can configure the time of response between two APs if one of they "fail" for the reconnection for customers?

Hi
I whis to know how i can configure the WLC (2500) for reduce the time of responce between Two Lightweight APs (1040 and 1602) if one of they are disconnected for any reason (energy, malfunction, etc.) for the reconnection of the clients.
I realized the next test: I have 2 APs connected, connect my laptop to the AP 1602 and start to making a TFTP transfer between my laptop and a server, then disconnect the AP 1602 and showing the laptop, the laptop makes the change to AP 1040, but the connection to the service, the TFTP transfer is cut because it takes about 30 seconds to resume the connection with the network
How i can reduce this time, because my clients want their connection is not lost when passing a situation similar, i look in the pages of cisco but did not find any information pudisese help me, any help is welcome.
thank you very much in advance
Jonathan

Not much you can do as its up to the client card to know it has no network connectivity and then to try to associate and obtain a DHCP address again. This is client dependent.
Sent from Cisco Technical Support iPhone App

7920 roaming between two WLCs

Similar Messages

Maybe you are looking for