28.3.2 Incident lifecycle state change notifications
The information in this section varies with the selections made to the Sending Options on the NNMi Northbound Interface Destination page.
- Organization of this subsection
(1) Enhanced closed traps
When the Northbound destination includes enhanced closed notifications, NNMi sends an nnmiEvClosed (1.3.6.1.4.1.11.2.17.19.2.0.1000) trap to the Northbound application when the lifecycle state of an incident changes to CLOSED in NNMi. The nnmiEvClosed trap includes much of the data from the original incident. The previous lifecycle state value is not included.
The nnmiEvClosed trap identifies the original incident in the sixth varbind, nnmiIncidentUuid (1.3.6.1.4.1.11.2.17.19.2.2.6).
(2) State change traps
When the Northbound destination includes lifecycle state changed notifications, NNMi sends a nnmiEvLifecycleStateChanged (1.3.6.1.4.1.11.2.17.19.2.0.1001) trap to the Northbound application when the lifecycle state of an incident changes to the IN PROGESS, COMPLETED, or CLOSED lifecycle state in NNMi. The Northbound application can associate the nnmiEvLifecycleStateChanged with the original incident.
The nnmiEvLifecycleStateChanged trap identifies the original incident and the lifecycle state change in the following varbinds:
nnmiIncidentUuid, the sixth varbind (1.3.6.1.4.1.11.2.17.19.2.2.6)
This value matches the value of the sixth varbind in a management event or the (n + 6)th varbind in a third-party SNMP trap varbind.
nnmiIncidentLifecycleStatePreviousValue, the seventh varbind (1.3.6.1.4.1.11.2.17.19.2.2.200)
nnmiIncidentLifecycleStateCurrentValue, the eighth varbind (1.3.6.1.4.1.11.2.17.19.2.2.201)
The following table lists the possible integer values for the lifecycle states:
Name |
Integer value |
|---|---|
registered |
1 |
inprogress |
2 |
completed |
3 |
closed |
4 |
dampened |
5 |