Management and AP-manaager will be on the same subnet. Management is to manage the wlc, ap-manager is the interface the wlc uses to communicate to the ap's. Wireless users should be on a different subnet, thus requires a dynamic interface configured on the wlc. So the more SSID's you want and hopefully will be put on a different subnet, will require you to add additional dynamic interfaces on the wlc.
In short, all traffic goes back to the wlc, so the controller needs dynamic interfaces to dump the traffic on the subnet.
Service port is mainly used as out-of-band management and shouldn't be connected to the network... unless you are using WiSM's, in which this is used for communication between the wlc's and the chassis.
All ap configurations will be managed from the WLC's. SSID's, encryption type, data rates, radios.... it goes on and on.
In short, you are able to centrally managed all your ap's. You will not have to manage each ap anymore.
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...