Sorry for so many questions, but I'm eager to learn.
Is there a guide anywhere that provides instruction on adding a second and third controller to a network? I'm specifically wondering how much of the second controller needs to mirror the first - as far as interfaces and SSIDs. I'm sure I have to duplicate the SSIDs, but when I do that on the second controller, those SSIDs will be associated with interfaces that, although they have the same interface name as controller 1, will have different IP addresses - correct?
Thanks - but none of those explain how to actually configure the second controller. I'm concerned about the interface IPs for the mirrored interfaces that must exist on the second controller. I'm thinking they must have a different ip address in the same subnet/vlan as the primary controller's dynamic interface. Correct? There's no doc I can find to tell me what must match and what must be different on the second controller in order for them to co-exist.
I know.....figure it out for myself...wah,wah, wah..... :-)
The easiest config would be to take the existing controller config and increment the interface IP addresses by one, so if your virtual interface is 192.168.1.2 on the first one, make the second one 192.168.1.3 (assuming it is free). The Virtual inteface needs to be the same.
You can use differnt IP ranges for the second controllers interface IP addresses, but this would probably not be necessary unless you are doing a large rollout.
You need to add the cotrollers to each other in the mobility gruop setup.
IP address assignment is at the discretion of the administrator/customer. Use whatever you want just as long as the controllers are in the same subnet or routing is configured appropriately if they aren't.
Use IP's in the same subnet as the other controller and access points. You can configure the controllers in the access point but they are perfectly capable of finding additional controllers on their own.
Assign a mobility group if you want it configured. Use the same configuration except for individual controller configuration options like interface IP's.
Use the same OS version on both. Leave all the packet transfering settings like MTU and timers the same on both controllers. That should be enough.
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...