This is very bad advice. Reinitializing the ANI database will cause you to lose all topology and user information and may not actually clear the discrepancy. If the discrepancy is truly fixed, simply re-discovering or re-data collecting the network will be sufficient to clear it. If that does not work, there is a device instrumentation issue or a bug in Campus, and reinitializing the database will most likely not help.
Typically, if the discrepancy has been fixed on the network, all you need to do to clear it in Campus is run a new Discovery (Campus 3.x) or a new Campus Data Collection (Campus 4.x). If the discrepancy remains after that, there is most likely an SNMP issue on one of the associated devices that is causing Campus to think a discrepancy still exists.
For example, if you're seeing a BPDU Guard discrepancy on 2950 switches, that is related to the bug CSCsg01956.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...