Trap: rmon-specific, B-13 – Paradyne 9788 User Manual
Page 253
B. SNMP MIBs, Traps, and RMON Alarm Defaults
9700-A2-GB20-20
December 2002
B-13
Trap: RMON-Specific
Two traps are defined to support the Alarm and Events Groups of RMON. See
on page B-14 for the default values that will
generate RMON-specific traps.
enterpriseTest-
Start(5)
For physical interfaces and
frame relay links:
ifIndex (RFC 1573)
.0.0 (placeholder)
devLastTrapString
(devHealthAndStatus.mib)
For virtual circuits (DLCIs):
devFrExtDlciIfIndex
(devFrExt.mib)
devFrExtDlciDlci
(devFrExt.mib)
devLastTrapString
(devHealthAndStatus.mib)
At least one test has been started
on an interface or virtual circuit.
String:
‘$testString test started on
$ifString.’
(e.g., ‘DTE Loopback test started
on Sync Data Port S01P1.’)
enterpriseTest-
Stop(105)
All tests have been halted on an
interface or virtual circuit.
String:
‘$testString test stopped on
$ifString.’ (e.g., ‘Disruptive PVC
Loopback test stopped on
DLCI 100 of Sync Data Port
S01P1 frame relay.’)
Table B-7.
enterprise-Specific Traps and Variable-Bindings (3 of 3)
Trap
Variable-Bindings
Possible Cause
Table B-8.
RMON-Specific Traps and Variable-Bindings
Trap
Variable-Bindings
Possible Cause
risingAlarm
alarmIndex (RFC 1757)
alarmVariable (RFC 1757)
alarmSampleType
(RFC 1757)
alarmValue (RFC 1757)
alarmRisingThreshold or
alarmFalling Threshold
(RFC 1757)
devLastTrapString
(devHealthAndStatus.mib)
Object being monitored has risen
above the set threshold.
String:
‘Change in $variableName
$typeString threshold of
$alarmRisingThreshold by $
(alarmValue –
AlarmRisingThreshold.’)
fallingAlarm
alarmIndex (RFC 1757)
alarmVariable (RFC 1757)
alarmSampleType
(RFC 1757)
alarmValue (RFC 1757)
alarmFallingThreshold
(RFC 1757)
devLastTrapString
(devHealthAndStatus.mib)
Object being monitored has fallen
below the set threshold.
String:
‘Change in $variableName
$typeString threshold of
$alarmRisingThreshold by $
(alarmValue –
AlarmRisingThreshold.’)