If the anchor goes down, or mobility fails, the user should never egress from the Foreign WLC (in my opinion). However, if you are saying that the user gets an IP from the MGMT Interface of the Foreign WLC (not the Anchor), then it is doing exactly what it shouldn't.
What version of code is this?
I've seen a lot of deployments implement a "dummy interface" on the Foreign WLC. So a fake vlan/subnet is created on the WLC and mapped as the default interface for the Foreign's Guest WLAN. In the event anchoring does fail and the client sticks to the foreign WLC this dummy interface would actually prevent the user from having network access.
I had done this one.I had created a dummy vlan and mapped the guest ssid to this vlan.But now the issue is like sometimes users are not getting ip address.We have 4 internal controllers and one guest controller.We have wireless voice as well.So inorder to take place roaming all the controllers are added each in mobility groups.
now i removed all and added only guest controller in the mobility.
Strange thing is that all the laptops get connected succesfully.Now i need to know wireless phones will have any issue or not.
IntroductionHow to use the Wireless LAN Controller Configuration Analyzer (WLCCA)
Javier Contreras is a Senior Tech Lead for the Wireless Business Unit in Cisco, with over 2 decades of experi...
< PRE >
(#)For this reason being that : - application that doesn't use multicast, sends one copy of each packet ( data unit of traffic at layer 3 ) to each client (" who seeks the traffic ).- application that does use multicast, sends ...
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...