SNMP MIBs and Traps, and RMON Alarm Defaults
B-139124-A2-LB20-00 March 2000
Table B-7. enterprise-Specific Traps and Variable-Bindings (3 of 3)
Trap Possible CauseVariable-Bindings
enterpriseSecondary-
ClockFail(4) HdevLastTrapString
(devHealthAndStatus.-
mib)
Operating software has detected
that the secondary clock source
has failed.
String:
‘Secondary clock failed.’
enterpriseSecondary-
ClockFailClear(104) Operating software has detected
that the secondary clock source
is operational again.
String:
‘Secondary clock restored.’
enterpriseSelfTest-
Fail(2) HdevLastTrapString
(devHealthAndStatus.-
mib)
Unit has completed
(re)initialization and a hardware
failure was detected.
String:
‘Self test failed: $s.’ ($s is the
contents of devSelfTestResult.)
enterpriseTest-
Start(5) For physical interfaces and
frame relay links:
HifIndex (RFC 1573)
H.0.0 (placeholder)
HdevLastTrapString
(devHealthAndStatus.-
mib
F i l i i (DLCI )
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)
For virtual circuits (DLCIs):
HdevFrExtDlciIfIndex
(devFrExt.mib)
HdevFrExtDlciDlci
(devFrExt.mib)
HdevLastTrapString
(devHealthAndStatus.-
mib
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.’)