I have just entered a customer location where someone else has configured three controllers in the same mobility group. The one thing that I see that is not normal to me is that the third controller is configured in a different vlan.
For example, the management IP address of WLC1 is 10.10.0.5, the IP address of WLC2 is 10.10.0.6, and the IP address of WLC3 is 10.10.1.6.
This puts WLC's 1 and 2 in the same subnet and WLC3 in another subnet. I am having no issues connecting to the third controller but is there an advantage to doing it this way?
I have always configured all three controllers in the same subnet. I would love to hear some opinions on this so I will know whether to change the third WLC or not.
Controllers in a mobility group communicate using an Ethernet over IP tunnel; it doesn't matter what VLAN the controllers management interfaces are in providing IP connectivity exists between the VLANs used.
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...
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. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...