The simple rule of configuring mobility group is this.
If two sites are nearby where users need roaming when they are moving from one place to another, then you have to put this in same mobility group.
If sites are far away, where no users expect roaming services, then you have to put each site into their own mobility group.
Keep note that mobility communication is very chatty, every time client associate to wireless network WLC will announce it to entire mobility group, so by segregating using different mobility group you can control this chatty behavior only to the required WLC to know about a client association.
Yes, virtual IP should be same & 192.0.2.1 is the recommended IP for virtual interface.
Once you configure mobility group in each WLC, when a user move from point A to point B at a given site client connection will be not-disturbed.Depend on how you configured your SSID for fast roaming (like Stiky Key Chaching, Fast Transition -FT, CCKM) time taken for roam varies. In these fast roaming scenario, user won't be reauthenticated when connecting to the roamed-AP.
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...