Paradyne FrameSaver SLV 9124 User Manual page 230

SNMP MIBs and Traps, and RMON Alarm Defaults
B-12
Table B-7. enterprise-Specific Traps and Variable-Bindings (2 of 3)
Trap Variable-Bindings
enterpriseMissedSLV-
Down(16)
enterpriseMissedSLV-
Up(116)
enterprisePrimary-
ClockFail(1)
enterprisePrimary-
ClockFailClear(101)
enterpriseRMON-
ResetToDefault(13)
March 2000
devFrExtDlciIfIndex
(devFrExt.mib)
devFrExtDlciDlci
(devFrExt.mib)
devFrExtDlciMissed-
SLVs (devFrExt.mib) SLVs (devFrExt.mib)
devLastTrapString
(devHealthAndStatus.-
mib.)
devLastTrapString
(devHealthAndStatus.-
mib)
devLastTrapString
(devHealthAndStatus.-
mib)
Possible Cause
SLV Timeout Error Event
Threshold has been exceeded.
String:
'SLV down on $ifString due to
excessive SLV packet loss. Total
SLV packets lost is $numLost.'
SLV Timeout Error Event has
been cleared.
String:
'SLV up on $ifString because
SLV communication was
reestablished. Total SLV packets
lost is $numLost.'
Operating software has detected
that the primary clock source has
failed.
String:
'Primary clock failed.'
Operating software has detected
that the primary clock source is
operational again.
String:
'Primary clock restored.'
All RMON-related option
changes have been reset to their
default values.
Default Factory Configuration
settings have been reloaded,
returning RMON-related options
to their original settings.
String:
'RMON database reset to
defaults.'
9124-A2-GB20-00