We have a recurring discovery job in Prime that runs every 3 hours. For the most part it works great. Every now and then though, it gets stuck and can't be cancelled or aborted from the Jobs Dashboard. The only cure seems to be a "ncs stop" and then a "ncs start". Not exactly ideal. Has anyone else seen this behavior before? Any possible solutions or workarounds other than stopping and restarting the service?
We're running 184.108.40.206.87. Discovery job uses only CDP and goes 6 hops from our campus network core VSS, checking one SNMP credential along the way.
I have this exact same problem only stopping NCS and starting NCS has no influence. The discovery job remains in a RUNNING state and has been in this state for over a week. I have opened a TAC case now. Additionally I have configured discovery jobs that I am simply not able to delete.
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...