entConfigChange
CPQ-TRAPS-MIB ·
.1.3.6.1.2.1.47.2.0.0.1
Object
notification
An entConfigChange notification is generated when the value
of entLastChangeTime changes. It can be utilized by an NMS
to trigger logical/physical entity table maintenance polls.
An agent should not generate more than one entConfigChange
'notification-event' in a given time interval (five seconds
is the suggested default). A 'notification-event' is the
transmission of a single trap or inform PDU to a list of
notification destinations.
If additional configuration changes occur within the
throttling period, then notification-events for these
changes should be suppressed by the agent until the current
throttling period expires. At the end of a throttling
period, one notification-event should be generated if any
configuration changes occurred since the start of the
throttling period. In such a case, another throttling period
is started right away.
An NMS should periodically check the value of
entLastChangeTime to detect any missed entConfigChange
notification-events, e.g., due to throttling or transmission
loss.
Context
- MIB
- CPQ-TRAPS-MIB
- OID
.1.3.6.1.2.1.47.2.0.0.1- Type
- notification
- Status
- current
- Parent
- entityMIBTrapPrefix
Net-SNMP examples
How SNMP and these commands workNotifications are emitted by an agent; they cannot be read with snmpget or walked.
Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'CPQ-TRAPS-MIB' -M '/opt/observium/mibs/hp:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CPQ-TRAPS-MIB::entConfigChange'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'CPQ-TRAPS-MIB' -M '/opt/observium/mibs/hp:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CPQ-TRAPS-MIB::entConfigChange'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.