I have a WCS server that is an old WLSE box that I have installed Windows Server 2003 on to be able to run WCS. I was running 220.127.116.11 and it was running fine. Then one day, the application stopped running. I have since upgraded to 18.104.22.168 and installed it fresh on a VM Ware server. I then restored the database and it ran fine for a couple of days. Now it is stopped again.
When I start the WCS Service, it will usually run for about 4 minutes, then stop. I can RDP back into the server, restart it, and it will run for another 4 minutes.
It is usually good to upgrade from the existing software version rather than a fresh install. Morever I guess you would have installed WCS as a service. Try installing it as a appilcation and start everytime you restart the computer.
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...