Prime 2.0 auditing mismatch while AP is up and running
I've ran into the following issue:
Prime is reporting a auditing mismatch.
The mismatch is a config discrepancy where is states the reported AP's are in downloading state where one AP is actually up and running and the other AP is down and removed from the configuration on the WLC's (WISM2). Refreshing the configuration from the WLC's and rebooting the AP's doesn't resolve the reporting mismatch.
Is there another way to resolve this so the mismatches disappear?
I'm running Prime version 2.0 (220.127.116.11.294) and 18.104.22.168 on the WLC's.
The controller config is correct. I've already audited the controllers as you suggested but with no result.
The mismatches still appear in the PI after the audit and there is no way to clear them.
The mismatches state that the AP is in downloading state but actually the AP is fully up and running and the other AP isn't even in the configuration.
It looks like a database inconsistency but it cannot be cleared. The mismatches keep coming back after auditing the WLC's and refreshing the config from the controllers where I keep the config which is currently on the controllers.
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...