We have a wlc connected to a core switch. At the core switch have configured 3 vlans (vlan management, vlan for wireless network users, and to vlan access-point). At a remote site, we have another core switch where there are 3 other vlans which serve the same functions as in the other switch. Between these switch, two routers exist that allow the network routing between the two switches. In wlc have configured an interface with vlan ID for users of the local wireless network. Also a WLAN to which the said interface is configured assigned. Two groups of one access-point access-point groups the local site and another is created to group access-point the remote site. That recommendation should be followed to configure an interface to the remote site, whereas the vlan identifier of the remote site users to work with a different vlan to the local site dhcp.
2. The APs provisioned there have been primed/pre-configured/pre-detected by the WLC
A. For this one just simple manage your AP in your main site, once it is primed/it has loaded the image of the controller, you can deploy in your new site. If the AP is already in the site, you need to manually assign(Static) the WLC's IP by #capwap ap controller ip address <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...