troubleshooting Question

Nexus SNMP

Avatar of mam249
mam249 asked on
RoutersSwitches / Hubs
1 Comment1 Solution461 ViewsLast Modified:
On standard Cisco hardware I can send a trap using "snmp-server enable trap config" and it sends a number of traps with different entries status's and I am using CISCO-CONFIG-MAN-MIB:ccmHistoryEventConfigDestination is equal to 4 (being a change to start up config), but for Nexus when I use the same SNMP command the only trap it sends is a CISCO-CONFIG-MAN-MIB:ciscoConfigManMIBNotifications.2 which appears to be everytime a command is submitted. There only seems to be one option for snmp config traps "snmp-server enable traps config ccmCLIRunningConfigChanged" even though the syntax says "CLI Running/Startup config change trap", but it only picks up when the running config changes.

The aim of this is because I need to be able to capture a copy of the config everytime the start-up config is changed for realtime detection of changes as part of PCI audits. I have got this working fine for everyone of my Cisco devices bar the Nexus.
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 1 Comment.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 1 Comment.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros