Hi,
Are you saying that ccmCLIRunningConfigChanged is not triggered upon exit from config mode on a Nexus 5K? What version are you running?
.1.3.6.1.4.1.9.9.43.2.0.2
ccmCLIRunningConfigChanged OBJECT-TYPE
-- FROM CISCO-CONFIG-MAN-MIB
TRAP
VARBINDS { ccmHistoryRunningLastChanged, ccmHistoryEventTerminalType }
DESCRIPTION "This notification indicates that the running
configuration of the managed system has changed
from the CLI.
If the managed system supports a separate
configuration mode(where the configuration commands
are entered under a configuration session which
affects the running configuration of the system),
then this notification is sent when the configuration
mode is exited.
During this configuration session there can be
one or more running configuration changes."
Does the following return a value?
.1.3.6.1.4.1.9.9.43.1.3.1
ccmCLICfgRunConfNotifEnable OBJECT-TYPE
-- FROM CISCO-CONFIG-MAN-MIB
-- TEXTUAL CONVENTION TruthValue
SYNTAX Integer { true(1), false(2) }
MAX-ACCESS read-write
STATUS Current
DESCRIPTION "This variable indicates whether the system produces
the ccmCLIRunningConfigChanged notification. A false
value will prevent notifications from being generated
by this system."