cIfMonNotifCount 1.3.6.1.4.1.9.10.999.1.1

This object will be incremented and included in the varbind list of the cIfMonNotifEvent notification. This object is guaranteed to increase once per notification originated from the MIB. NMSes should track the value of this object received in each notification. If the difference in the value of this object across two consecutive notifications is more than one, a notification has been delayed, dropped, lost or routed out of sequence. The only reliable way to recover such notifications is via the NOTIFICATION-LOG-MIB. The NMS should preferably configure/create a log in the NOTIFICATION-LOG-MIB to capture cIfMonNotifEvent notifications. If possible, a named log should be created. When a notification loss is detected, the NMS can then poll the log to determine which notification was lost. The reader can look up RFC 3014 for more information on the NOTIFICATION-LOG-MIB. In addition to tracking the value of this object in each notification, the NMS should periodically poll this object. If the polled value of this object is two or more counts greater than the value from the last received notification, a notification has likely been dropped, and the NMS must use the NOTIFICATION-LOG-MIB to poll for the dropped notification.