tmnxOamPmThrRaise

[CAUSE] A tmnxOamPmThrRaise trap is sent when an OAM-PM loss or delay
counter meets or exceeds its configured raise threshold.
          
If an Average Frame Loss Ratio (FLR) threshold (i.e.
tmnxOamPmCfgThrLossAvgFlrRaise) is met or exceeded, the
tmnxOamPmThrRaise trap is sent at the end of the measurement interval.
If another type of threshold (e.g. tmnxOamPmCfgThrLossHliRaise) is met
or exceeded, the tmnxOamPmThrRaise trap is sent when the problem is
detected.  The Average FLR threshold is a special case because the
measured Average FLR can fluctuate during a measurement interval.
          
At most one tmnxOamPmThrRaise trap is sent per threshold type during
one OAM-PM measurement interval.  For example, at most one
tmnxOamPmThrRaise trap is sent to record an excessive High Loss
Indicator (HLI) count in the forward direction seen in a particular 15
minute interval belonging to the SLM test belonging to OAM-PM session
'oamPmSession1'.
          
OAM-PM thresholds are explained in the DESCRIPTION clauses of
tmnxOamPmCfgThrDelayTable, tmnxOamPmCfgThrLossFwBwAgTable, and
tmnxOamPmCfgThrLossFwBwTable.
          
OAM-PM counters are explained in the DESCRIPTION clauses of the
tmnxOamPmStatsTableObjs tables.
          
[EFFECT] For an LMM test, the loss of live traffic has met or exceeded
a configured threshold.  For the other test types, the loss or delay of
OAM-PM test probes has met or exceeded a configured threshold,
indicating possible excessive loss or excessive delay of live traffic.
          
[RECOVERY] Fix the cause of the excessive loss or excessive delay.

MIB

TIMETRA-OAM-PM-MIB

OID

.1.3.6.1.4.1.6527.3.1.3.92.0.1

Type

notification

Status

current

Parent

tmnxOamPmNotifications

Groups

1