After checking the WLCs at several sites using the WLC Config Analyzer, one of the errors that came up was that the service-port interface was invalid because it was set to 0.0.0.0. We're not using the service-port interface, so how should this be set? In the web interface, if I uncheck DHCP, it wants a real static IP address... should I use 127.0.0.1? Do I need to do this in the CLI?
Generally I set them to something so that some stuff like WCS & Config Analyzer don't complain about it. I wouldn't set it to 127.0.0.1.; Although if it's a WiSM module then they should be configured to match the WiSM VLAN in the switch chassis otherwise the WLC can generate lost heartbeat alarms.
Typically if my internal network is a 10.x.x.x network I will use 192.168.1.(last octet of management address), then reverse that as necessary. The service port is for out of band management, which mean it generally isn't connected to any unless you need an alternate to the console port.
As fo setting it, you can either set it via the gui or via the cli
If it's not a WiSM, and we don't have a WCS (yet anyway), is there any need to change it, other than stopping the error in the Config Analyzer? I'd like to do that, but I'd probably need more justification to actually do it.
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...