I want to create a anchor controller that has a dot1q leg into our DMZ then make foreign contorllers for the rest of my company which would be 34 controllers in different geographic locations. The problem I see is that I can only add 24 mobility members to the group to create the mobility peer as stated in this document.
Well... not all your WLC are in one area per say.... so each location can be one mobility group and your guest anchor would be in a seperate mobility group. Mobility group helps a user roam from an ap in one controller to an ap in another. You don't have to have every WLC on the same Mobility group nor RF Group. Have one mobility group per location (one building, multiple buildings) where you can roam from one to another.
As of 5.1 or later you can add up to 72 controllers in a controller's mobility group list. The mobility groups are still limited to 24 controllers but with the other controllers and mobility groups defined you can then have roaming between the mobility groups.
I need to add all the controllers as static mobility group members on the anchor and add the anchor as a member on the peers in order to get the data/control path up and be able to add the anchor on the wlan...correct? My RF group names and default mobility domain are unique per site.
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...