Paradyne 9128-II User Manual
Page 336
B. SNMP MIBs and Traps, and RMON Alarm Defaults
B-14
April
2002
9128-A2-GB20-60
enterpriseMissedSLV-
Down(16)
T
devFrExtDlciIfIndex
(devFrExt.mib)
T
devFrExtDlciDlci
(devFrExt.mib)
T
devFrExtDlciMissed-
SLVs (devFrExt.mib)
T
devLastTrapString
(devHealthAndStatus.-
mib.)
Received SLV communications
have been missed; 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.’
enterpriseMissedSLV-
Up(116)
SLV Timeout Error Event has
been cleared.
String:
‘SLV up on $ifString because SLV
communication was
reestablished. Total SLV packets
lost is $numLost.’
enterprisePrimary-
ClockFail(1)
T
devLastTrapString
(devHealthAndStatus.-
mib)
Operating software has detected
that the primary clock source has
failed.
String:
‘Primary clock failed.’
enterprisePrimary-
ClockFailClear(101)
Operating software has detected
that the primary clock source is
operational again.
String:
‘Primary clock restored.’
enterpriseRMON-
ResetToDefault(13)
T
devLastTrapString
(devHealthAndStatus.-
mib)
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.’
enterpriseSecondary-
ClockFail(4)
T
devLastTrapString
(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.’
Table B-7.
enterprise-Specific Traps and Variable-Bindings (2 of 3)
Trap
Variable-Bindings
Possible Cause