A rttMonNotification indicates the occurrence of a
threshold violation, and it indicates the previous
violation has subsided for a subsequent operation.
When the RttMonRttType is 'pathEcho', this
notification will only be sent when the threshold
violation occurs during an operation to the target and
not to a hop along the path to the target. This also
applies to the subsiding of a threshold condition.
If History is not being collected, the instance values
for the rttMonHistoryCollectionAddress object will not
be valid. When RttMonRttType is not 'echo' or 'pathEcho'
the rttMonHistoryCollectionAddress object will be null.
rttMonReactVar defines the type of reaction that is
configured for the probe ( e.g jitterAvg, rtt etc ).
In the rttMonReactTable there are trap definitions
for the probes and each probe may have more than
one trap definitions for various types ( e.g rtt,
jitterAvg, packetLoossSD etc ). So the object rttMonReactVar
indicates the type ( e.g. rtt, packetLossSD, timeout etc )
for which threshold violation traps has been generated.
The object rttMonEchoAdminLSPSelector will be valid only
for the probes based on 'mplsLspPingAppl' RttMonProtocol. For
all other probes it will be null.
Parsed from file CISCO-RTTMON-MIB.mib
Module: CISCO-RTTMON-MIB
A rttMonNotification indicates the occurrence of a
threshold violation, and it indicates the previous
violation has subsided for a subsequent operation.
When the RttMonRttType is 'pathEcho', this
notification will only be sent when the threshold
violation occurs during an operation to the target and
not to a hop along the path to the target. This also
applies to the subsiding of a threshold condition.
If History is not being collected, the instance values
for the rttMonHistoryCollectionAddress object will not
be valid. When RttMonRttType is not 'echo' or 'pathEcho'
the rttMonHistoryCollectionAddress object will be null.
rttMonReactVar defines the type of reaction that is
configured for the probe ( e.g jitterAvg, rtt etc ).
In the rttMonReactTable there are trap definitions
for the probes and each probe may have more than
one trap definitions for various types ( e.g rtt,
jitterAvg, packetLoossSD etc ). So the object rttMonReactVar
indicates the type ( e.g. rtt, packetLossSD, timeout etc )
for which threshold violation traps has been generated.
The object rttMonEchoAdminLSPSelector will be valid only
for the probes based on 'mplsLspPingAppl' RttMonProtocol. For
all other probes it will be null.
Parsed from file cisco-rttmon.mib.txt
Company: None
Module: CISCO-RTTMON-MIB
A rttMonNotification indicates the occurrence of a
threshold violation, and it indicates the previous
violation has subsided for a subsequent operation.
When the RttMonRttType is 'pathEcho', this
notification will only be sent when the threshold
violation occurs during an operation to the target and
not to a hop along the path to the target. This also
applies to the subsiding of a threshold condition.
If History is not being collected, the instance values
for the rttMonHistoryCollectionAddress object will not
be valid. When RttMonRttType is not 'echo' or 'pathEcho'
the rttMonHistoryCollectionAddress object will be null.
rttMonReactVar defines the type of reaction that is
configured for the probe ( e.g jitterAvg, rtt etc ).
In the rttMonReactTable there are trap definitions
for the probes and each probe may have more than
one trap definitions for various types ( e.g rtt,
jitterAvg, packetLoossSD etc ). So the object rttMonReactVar
indicates the type ( e.g. rtt, packetLossSD, timeout etc )
for which threshold violation traps has been generated.
The object rttMonEchoAdminLSPSelector will be valid only
for the probes based on 'mplsLspPingAppl' RttMonProtocol. For
all other probes it will be null.
rttMonNotification object is superseded by
rttMonNotificationV2.
rttMonNotification NOTIFICATION-TYPE OBJECTS { rttMonCtrlAdminTag, rttMonHistoryCollectionAddress, rttMonReactVar, rttMonReactOccurred, rttMonReactValue, rttMonReactThresholdRising, rttMonReactThresholdFalling, rttMonEchoAdminLSPSelector } STATUS current DESCRIPTION "A rttMonNotification indicates the occurrence of a threshold violation, and it indicates the previous violation has subsided for a subsequent operation. When the RttMonRttType is 'pathEcho', this notification will only be sent when the threshold violation occurs during an operation to the target and not to a hop along the path to the target. This also applies to the subsiding of a threshold condition. If History is not being collected, the instance values for the rttMonHistoryCollectionAddress object will not be valid. When RttMonRttType is not 'echo' or 'pathEcho' the rttMonHistoryCollectionAddress object will be null. rttMonReactVar defines the type of reaction that is configured for the probe ( e.g jitterAvg, rtt etc ). In the rttMonReactTable there are trap definitions for the probes and each probe may have more than one trap definitions for various types ( e.g rtt, jitterAvg, packetLoossSD etc ). So the object rttMonReactVar indicates the type ( e.g. rtt, packetLossSD, timeout etc ) for which threshold violation traps has been generated. The object rttMonEchoAdminLSPSelector will be valid only for the probes based on 'mplsLspPingAppl' RttMonProtocol. For all other probes it will be null." ::= { rttMonNotifications 5 }
Vendor: Cisco
Module: CISCO-RTTMON-MIB
[Automatically extracted from oidview.com]
rttMonNotification NOTIFICATION-TYPE OBJECTS { rttMonCtrlAdminTag, rttMonHistoryCollectionAddress, rttMonReactVar, rttMonReactOccurred, rttMonReactValue, rttMonReactThresholdRising, rttMonReactThresholdFalling, rttMonEchoAdminLSPSelector } STATUS current DESCRIPTION "A rttMonNotification indicates the occurrence of a threshold violation, and it indicates the previous violation has subsided for a subsequent operation. When the RttMonRttType is 'pathEcho', this notification will only be sent when the threshold violation occurs during an operation to the target and not to a hop along the path to the target. This also applies to the subsiding of a threshold condition. If History is not being collected, the instance values for the rttMonHistoryCollectionAddress object will not be valid. When RttMonRttType is not 'echo' or 'pathEcho' the rttMonHistoryCollectionAddress object will be null. rttMonReactVar defines the type of reaction that is configured for the probe ( e.g jitterAvg, rtt etc ). In the rttMonReactTable there are trap definitions for the probes and each probe may have more than one trap definitions for various types ( e.g rtt, jitterAvg, packetLoossSD etc ). So the object rttMonReactVar indicates the type ( e.g. rtt, packetLossSD, timeout etc ) for which threshold violation traps has been generated. The object rttMonEchoAdminLSPSelector will be valid only for the probes based on 'mplsLspPingAppl' RttMonProtocol. For all other probes it will be null." ::= { rttMonNotifications 5 }
rttMonNotification NOTIFICATION-TYPE OBJECTS { rttMonCtrlAdminTag, rttMonHistoryCollectionAddress, rttMonReactVar, rttMonReactOccurred, rttMonReactValue, rttMonReactThresholdRising, rttMonReactThresholdFalling, rttMonEchoAdminLSPSelector } STATUS deprecated DESCRIPTION "A rttMonNotification indicates the occurrence of a threshold violation, and it indicates the previous violation has subsided for a subsequent operation. When the RttMonRttType is 'pathEcho', this notification will only be sent when the threshold violation occurs during an operation to the target and not to a hop along the path to the target. This also applies to the subsiding of a threshold condition. If History is not being collected, the instance values for the rttMonHistoryCollectionAddress object will not be valid. When RttMonRttType is not 'echo' or 'pathEcho' the rttMonHistoryCollectionAddress object will be null. rttMonReactVar defines the type of reaction that is configured for the probe ( e.g jitterAvg, rtt etc ). In the rttMonReactTable there are trap definitions for the probes and each probe may have more than one trap definitions for various types ( e.g rtt, jitterAvg, packetLoossSD etc ). So the object rttMonReactVar indicates the type ( e.g. rtt, packetLossSD, timeout etc ) for which threshold violation traps has been generated. The object rttMonEchoAdminLSPSelector will be valid only for the probes based on 'mplsLspPingAppl' RttMonProtocol. For all other probes it will be null. rttMonNotification object is superseded by rttMonNotificationV2." ::= { rttMonNotifications 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.42.2.0.1 | rttMonConnectionChangeNotification | 0 | 0 | This notification is only valid when the RttMonRttType is 'echo' or 'pathEcho'. A rttMonConnectionChangeNotification indicates th… |
| 1.3.6.1.4.1.9.9.42.2.0.2 | rttMonTimeoutNotification | 0 | 0 | A rttMonTimeoutNotification indicates the occurrence of a timeout for a RTT operation, and it indicates the clearing of such a co… |
| 1.3.6.1.4.1.9.9.42.2.0.3 | rttMonThresholdNotification | 0 | 0 | A rttMonThresholdNotification indicates the occurrence of a threshold violation for a RTT operation, and it indicates the previou… |
| 1.3.6.1.4.1.9.9.42.2.0.4 | rttMonVerifyErrorNotification | 0 | 0 | A rttMonVerifyErrorNotification indicates the occurrence of a data corruption in an RTT operation. |
| 1.3.6.1.4.1.9.9.42.2.0.6 | rttMonLpdDiscoveryNotification | 0 | 0 | A rttMonLpdDiscoveryNotification indicates that the LSP Path Discovery to the target PE has failed, and it also indicates the cle… |
| 1.3.6.1.4.1.9.9.42.2.0.7 | rttMonLpdGrpStatusNotification | 0 | 0 | A rttMonLpdGrpStatusNotification indicates that the LPD Group status rttMonLpdGrpStatsGroupStatus has changed indicating some con… |
| 1.3.6.1.4.1.9.9.42.2.0.8 | rttMonNotificationV2 | 0 | 0 | A rttMonNotification indicates the occurrence of a threshold violation, and it indicates the previous violation has subsided for … |