Hello, you have to set the engine ID manually on some Cisco devices because Cisco set the default ID (800000090300000000000000) on a lot of devices (modular switches, gigabit switches, ...) and the engine ID is not unique.
Regards Andreas -----Original Message----- From: Kenneth Kirchner [mailto:[email protected]] Sent: Thursday, April 12, 2012 3:28 AM To: spectrum Subject: Re: [spectrum] Duplicate SNMPv3 Engine ID - Alarms On Apr 11, 2012, at 3:53 PM, Rob wrote: > Been staring at an issue in Spectrum for about 3 days now and think I finally > have it sorted out. > > About 2 weeks ago the Network team at my site started to configure V2 Routers > and Switches to V3 and enabling Traps to Spectrum. I suddenly got about 90 > Orange "SNMP NOT RESPONDING" alarms and bunches of Pingables in my "New > Devices" container. (I have Trap Based Discovery enabled) > ... > Now to get the Network Team to update all the duplicate engineIDs... easier > said than done... > > <BIG SIGH> > > -Rob I would also recommend to set your trap source interface so that the router/switch doesn't tag it with the IP of the egress interface. We had a few issues with duplicate engine ID's, but I think that was due to copy/past of configs. Why would you manually set the EngineID unless you really had to? Just have them remove the manual setting and the router should generate a unique new one. -Ken --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately. --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
