<div>
<div class="content wysiwyg-content">
On standard Cisco hardware I can send a trap using &quot;snmp-server enable trap config&quot; and it sends a number of traps with different entries status's and I am using CISCO-CONFIG-MAN-MIB:ccmHi<wbr />storyEvent<wbr />ConfigDest<wbr />ination 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:cisco<wbr />ConfigManM<wbr />IBNotifica<wbr />tions.2 which appears to be everytime a command is submitted. There only seems to be one option for snmp config traps &quot;snmp-server enable traps config ccmCLIRunningConfigChanged<wbr />&quot; even though the syntax says &quot;CLI Running/Startup config change trap&quot;, but it only picks up when the running config changes.<br />
<br />
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.
</div>
</div>


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.

Nexus SNMP

A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.

Switches / Hubs

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.