The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for notification interval
- atmx Soft Pvc Notification Interval
- atmxSoftPvcNotificationInterval 1.3.6.1.4.1.800.2.9.2.1.1.5 (defined in XYLAN-SOFT-PVC-MIB)
The minimum interval between the sending of atmSoftPvcCallFailuresTrap notifications. - Enterasys Flow Limiting System Notification Interval
- etsysFlowLimitingSystemNotificationInterval 1.3.6.1.4.1.5624.1.2.43.1.1.4 (defined in enterasys-flow-limiting-mib)
The number of seconds to wait before generating another notification of the same type for the same interface. This allows notification generation to be throttled in the case of a flow counter or rate that is repeatedly transitioning across a threshold. A value of zero indicates that the entity should not suppress any notifications related to the Flow Limiting feature. Maintaining the value of this object across agent reboots is REQUIRED. - Cisco ATM Soft Pvc Notification Interval
- atmSoftPvcNotificationInterval 1.3.6.1.4.1.353.5.5.1.1.1.5 (defined in ATM-SOFT-PVC-MIB)
The minimum interval between the sending of atmSoftPvcCallFailuresTrap notifications. - Cisco ATM Interface Pvc Notification Interval
- atmIntfPvcNotificationInterval 1.3.6.1.2.1.37.1.14.1.14.1.24 (defined in ATM2-MIB)
The minimum interval between the sending of atmIntfPvcFailuresTrap notifications for this interface. - Cisco's ASN Gateway Repeat Notification Interval
- cagwRepeatNotifInterval 1.3.6.1.4.1.9.9.638.1.4.3 (defined in CISCO-ASN-GATEWAY-MIB)
The purpose of this object is to define the length of interval used to prevent the excessive generations of notifications. Notification related to the same event(alarm) will be suppressed for the duration of the interval. Notifications for the same entity(object with same indexes) will be suppressed for length of interval. For example, the ciscoAgwMaxBaseStationExceededOnsetNotif and ciscoAgwMaxBaseStationExceededAbateNotif notification are used to indicate the event were the number of basestations that can be supported has been reached and requests from additional base stations will be reject. Here is an example of how the suppression mechanism works: cagwMaxBaseStationExceededNotifThreshold = 90% cagwMaximumBaseStations = 1000 threshold = 900 Time 9:00:00 cagwCurrentBaseStations = 901 device sends ciscoAgwMaxBaseStationExceededOnsetNotif Time 9:00:04 cagwCurrentBaseStations = 899 device does not send ciscoAgwMaxBaseStationExceededAbateNotif Time 9:00:07 cagwCurrentBaseStations = 901 device does not send ciscoAgwMaxBaseStationExceededOnsetNotif Time 9:00:11 cagwCurrentBaseStations = 899 device does not send ciscoAgwMaxBaseStationExceededAbateNotif . . Time 9:05:00 Interval Ends and cagwCurrentBaseStations = 822 device sends ciscoAgwMaxBaseStationExceededAbateNotif When this object is set to zero notification will not be suppressed. - CISCO Express Forwarding Notification Throttling Interval
- cefNotifThrottlingInterval 1.3.6.1.4.1.9.9.492.1.9.4 (defined in CISCO-CEF-MIB)
This object controls the generation of the cefInconsistencyDetection notification. If this object has a value of zero, then the throttle control is disabled. If this object has a non-zero value, then the agent must not generate more than one cefInconsistencyDetection 'notification-event' in the indicated period, where a 'notification-event' is the transmission of a single trap or inform PDU to a list of notification destinations. If additional inconsistency is detected within the throttling period, then notification-events for these inconsistencies 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 inconsistency was detected since the start of the throttling period. In such a case, another throttling period is started right away. An NMS should periodically poll cefInconsistencyRecordTable to detect any missed cefInconsistencyDetection notification-events, e.g., due to throttling or transmission loss. If cefNotifThrottlingInterval notification generation is enabled, the suggested default throttling period is 60 seconds, but generation of the cefInconsistencyDetection notification should be disabled by default. If the agent is capable of storing non-volatile configuration, then the value of this object must be restored after a re-initialization of the management system. The actual transmission of notifications is controlled via the MIB modules in RFC 3413. - Cisco ATM Intf Pvc Notification Interval
- atmIntfPvcNotificationInterval 1.3.6.1.2.1.37.1.14.1.14.1.24 (defined in CISCO-IETF-ATM2-PVCTRAP-MIB)
The minimum interval between the sending of cIntfPvcFailuresTrap notifications for this interface. - Juniper Mac Notification Interval
- jnxMacNotificationInterval 1.3.6.1.4.1.2636.3.40.1.7.1.1.1.2 (defined in JUNIPER-EX-MAC-NOTIFICATION-MIB)
This object specifies the maximum interval of time between jnxMacChangedNotifications being generated by the device. If the value of jnxNotificationsEnabled is true(1), the device will send out the generated jnxMacChangedNotifications and archive the MAC change notification events in the jnxMacHistoryTable. If the value of jnxNotificationEnabled is false(2), the device will not send out the generated jnxMacChangedNotifications but it will archive these events in the jnxMacHistoryTable. If the value of this object is equal to 0, the device will generate jnxMacChangedNotifications and archive the MAC change notification events in the jnxMacHistoryTable as soon as there is MAC address learnt or removed by the device. If the value of this object is greater than 0, the device will wait for a period of time equal to the value of this object before generate the jnxMacChangedNotifications and archive the MAC change notification events in the jnxMacHistoryTable.
