Currently have a wireless deployment in a building across 3 floors. Have deployed AP/Mobility Groups to enable the use of a different subnet on each floor of the building. I have tested Roaming throughout the building and all appears fine.
However, should I pick up an IP address on the ground floor of the building, I can then roam to the 2nd floor, disconnect my wireless connectivity and re-connect (In theory, ending the roaming connection) I'm then unable to get an IP address at all for that floor of the building.
To resolve the issue, I connect to the WLC on which I was last connected to prior to disconnecting my wireless connection, remove my association and I'm then able to pick up an IP address for the floor on which I'm attempting too connect. Is there a specific piece of configuration I need in place for this, or is this normal behaivour?
That is working as designed. Basically you could look at this as layer-3 roaming. Until the client entry is deleted from the controller either manually or with by the idle timeout it will receive the same IP.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
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 f...