Paradyne FrameSaver SLV 9124 User Manual page 231

Hide thumbs Also See for FrameSaver SLV 9124:
Table of Contents

Advertisement

9124-A2-GB20-00
Table B-7. enterprise-Specific Traps and Variable-Bindings (3 of 3)
Trap
Variable-Bindings
enterpriseSecondary-
ClockFail(4)
enterpriseSecondary-
ClockFailClear(104)
enterpriseSelfTest-
Fail(2)
enterpriseTest-
For physical interfaces and
Start(5)
frame relay links:
For virtual circuits (DLCIs):
F
enterpriseTest-
Stop(105)
March 2000
SNMP MIBs and Traps, and RMON Alarm Defaults
Possible Cause
devLastTrapString
Operating software has detected
(devHealthAndStatus.-
that the secondary clock source
mib)
has failed.
String:
'Secondary clock failed.'
Operating software has detected
that the secondary clock source
is operational again.
String:
'Secondary clock restored.'
devLastTrapString
Unit has completed
(devHealthAndStatus.-
(re)initialization and a hardware
mib)
failure was detected.
String:
'Self test failed: $ s .' ($ s is the
contents of devSelfTestResult.)
At least one test has been
started on an interface or virtual
circuit.
ifIndex (RFC 1573)
String:
.0.0 (placeholder)
'$testString test started on
$ifString.' (e.g., 'DTE Loopback
devLastTrapString
test started on Sync Data Port
(devHealthAndStatus.-
S01P1.')
mib
i t
l i
it (DLCI )
All tests have been halted on an
devFrExtDlciIfIndex
interface or virtual circuit.
(devFrExt.mib)
String:
devFrExtDlciDlci
'$testString test stopped on
(devFrExt.mib)
$ifString.' (e.g., 'Disruptive PVC
Loopback test stopped on
devLastTrapString
DLCI 100 of Sync Data Port
(devHealthAndStatus.-
S01P1 frame relay.')
mib
B-13

Advertisement

Table of Contents
loading

Table of Contents