We recently purchased a 4402 controller. It was running the 220.127.116.11 release, which I upgraded today to 18.104.22.168. I also updated the bootloader to 22.214.171.124-ER.
I configured everything like I did before the software upgrade. Same IP address, same subnet, no VLAN tags, and so forth.
The controller is on a segregated subnet, apart from my desktop machine. I have another machine on that segregate subnet, which I'm using for terminal access. I can remote desktop into that machine just fine.
I can also ping the controller from that machine.
I can not ping the gateway from the controller. I can ping the remote computer from the controller.
I can't ping the controller from my desktop, and I can't ping my desktop from the controller.
Any thoughts? The only difference is the upgraded software, as far as I can tell.
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...