I spent half a day by testing and the conclusion is: SNMP is not working in Cisco cluster the way described in the documentation, it is not working at all!!
I was not able to force the member switch to send any SNMP trap using @e1 string, neither the manager switch to send any SNMP packet to the member. No matter if the member switch has IP address configured or not.
So the only reasonable way of Cisco cluster config is to configure IP addresses on all member switches, delete @en strings from all configs, and use common community strings for direct communication with the management station.
More: AFAIK neither HP OV NNM nor CiscoWorks support Cisco clusters. The only remaining reason for using it is that via CMS you can see all the cluster devices at one browser window.
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...