We have multiple 4404 controllers in the same mobility group. Because our controllers are placed into different buildings and our common SSID is set on WLANs on different VLANs/subnets, I would like to ensure "inter-subnet roaming" occurs in case a client inadvertently roams between access points on controllers in different WLANs (subnets).
Do I have to manually set every controller to be a mobility anchor for the same WLAN? Does a mobility anchor have to be set before "inter-subnet" roaming will occur? (In this case, every controller would be an anchor.)
I have read the section of the 4.0 guide on inter-subnet roaming, mobility anchors, etc. but it is still unclear.
The concept of mobility anchor is that you can manually define which controller will going to be a anchor controller for your client no matter client connectes to whicever controller first but if your requirement if just internet subnet roaming then you do not need mobility anchor and to whichever controller client associate first via an AP that controller will going to be an anchor controller and when client roams to other controller then that controller will going to be a foreign controller.
So in short in internet subnet setup whicever controller client associate first becomes an anchor controller and in mobility anchor setup you can manually define which controller should be an anchor controller.
If that is the case, then inter-subnet roaming is not working correctly in our environment. I have roamed between two access points that are associated with different controllers. These controllers are in separate buildings with the common SSID on different subnets. When I roam between the access points, I do not keep the same IP address. The IP address changes when the client associates between access points. Isn't the IP addresses supposed to remain on the client during inter-subnet roaming?
I created a new WLAN/SSID and set the mobility anchor as "local" on each controller for that WLAN. I was then able to roam between WLANs on different subnets and did not lose the IP address. So, I think it is resolved.
Just in case, I'll go ahead and post output from "sh mob summary":
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...