All MIBs › TIMETRA-OAM-PM-MIB › tmnxOamPmThrRaise
tmnxOamPmThrRaise
Module: TIMETRA-OAM-PM-MIB
OID (symbolic): TIMETRA-OAM-PM-MIB::tmnxOamPmThrRaise
OID (numeric): 1.3.6.1.4.1.6527.3.1.3.92.0.1
Node type: NOTIFICATION-TYPE
Description: [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.
Examples
Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):
snmptrap -v2c -c public <manager> '' TIMETRA-OAM-PM-MIB::tmnxOamPmThrRaise snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.6527.3.1.3.92.0.1
Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):
snmptrapd -f -Lo -c /dev/null authCommunity log public
Example snmptrapd log entry:
zoo11-linux.zoo [UDP: [192.168.30.111]:56923->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (236210267) 27 days, 8:08:22.67 SNMPv2-MIB::snmpTrapOID.0 = OID: TIMETRA-OAM-PM-MIB::tmnxOamPmThrRaise
Start monitoring Nokia SR OS routers (Service OAM delay/loss performance-monitoring session status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-OAM-PM-MIB::tmnxOamPmThrRaise OID value, configure state conditions and alerts, and monitor any Nokia SR OS routers (Service OAM delay/loss performance-monitoring session status) from a single console.
OID Breakdown
Upper-level ancestors (10 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.6527 | timetra | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3 | timetraProducts | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1 | tmnxSRMIB | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1.3 | tmnxSRNotifyPrefix | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6527.3.1.3.92 | tmnxOamPmNotifyPrefix | TIMETRA-OAM-PM-MIB |
| 1.3.6.1.4.1.6527.3.1.3.92.0 | tmnxOamPmNotifications | TIMETRA-OAM-PM-MIB |
| 1.3.6.1.4.1.6527.3.1.3.92.0.1 | tmnxOamPmThrRaise | TIMETRA-OAM-PM-MIB |