Client handoff and Roaming

Unanswered Question
Apr 4th, 2009

Hi all,

I've installed four WLC 5.1.151.0 and the clients have roaming issues. When a client roams i can see it as "Mobility Role: Anchor" on the first WLC it connected and as "Mobility Role: Foreign" on the WLC it roamed to. The problem is after the roaming the client can't reach the network, no ping, no communication. I can ping the client from the controller it roamed to, but not from the first controller it connected (the anchor). Mobility groups are configured correctly, "Symmetric mobility tunneling mode" and "AP Groups VLAN Feature Enable" are disabled. I've configured all the controllers as DHCP with different scopes on the same subnet, so its a inter-controller roaming, not inter-subnet. I can't upgrade the controller software soon because its a production environment. To fix the problem I remove the client from the first controller, refresh its Wifi interface so it connects directly to the second controller and the network works again. Any help is welcome. Thank you.

Gian Paolo

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Scott Fella Sat, 04/04/2009 - 08:49

If you can post your show run-config.

But what you can look at is make sure that the vlans are being passed on the trunk and the wlan interface is pointing to the correct subnet. If you can mping and eping between the wlc that eliminates mobility issues. Does this happen when roam occurs form either wlc?

Gian Paolo Boarina Sat, 04/04/2009 - 09:11

I've tried mping and eping and both work. VLANS are passed correctly to the interface and correctly configured. All virtual interfaces have the same address on the controllers.

I've followed step by step the configuration guide, using unicast messages for mobility traffic. The four controllers are on the same switch Cat3750.

Scott Fella Sat, 04/04/2009 - 18:31

Post your show run-config and also your switchport configuration. Something isn't set right if you can't roam from wlc to wlc.

nikhilcherian Sun, 04/05/2009 - 20:35

Hi Gian,

Can you try to connect the client to the first WLC(anchor) and ping the client from the same WLC.

Can you make sure there is no ACL configure in the WLC of the ip address

Thanks

NikhiL

Gian Paolo Boarina Sun, 04/05/2009 - 22:40

Maybe I've fixed. All the WLCs wireless interfaces associated to the SSID have address in 10.110.0.0/16 subnet but from the first controller I can't ping anything above 10.110.0.0/24 network. I've changed the netmask of all WLCs some days ago but looks like WLC_01 didn't accepted the new netmask (I've used the web interface). It's odd, maybe a problem of browser caching or something, reviewing the saved configuration of yesterday the netmask is definitely wrong. I've changed the netmask from command line and now roaming works, I can ping any client in 10.110.0.0/16 subnet.

What confused me was checking eping and mping that worked all the time because WLCs have addresses 10.110.0.x.

Thank you all for the support.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode