SNMP MIBs and Traps, and RMON Alarm Defaults

Table B-7. enterprise-Specific Traps and Variable-Bindings (2 of 3)

Trap

Variable-Bindings

Possible Cause

 

 

 

enterpriseMissedSLV-

H devFrExtDlciIfIndex

SLV Timeout Error Event

Down(16)

(devFrExt.mib)

Threshold has been exceeded.

 

H devFrExtDlciDlci

String:

 

(devFrExt.mib)

`SLV down on $ifString due to

 

H devFrExtDlciMissed-

excessive SLV packet loss. Total

 

SLV packets lost is $numLost.'

 

SLVs (devFrExt.mib)

 

 

enterpriseMissedSLV-

H devLastTrapString

SLV Timeout Error Event has

Up(116)

been cleared.

(devHealthAndStatus.-

 

mib.)

String:

 

 

 

 

`SLV up on $ifString because

 

 

SLV communication was

 

 

reestablished. Total SLV packets

 

 

lost is $numLost.'

 

 

 

enterprisePrimary-

H devLastTrapString

Operating software has detected

ClockFail(1)

(devHealthAndStatus.-

that the primary clock source has

 

mib)

failed.

 

 

String:

 

 

`Primary clock failed.'

 

 

 

enterprisePrimary-

 

Operating software has detected

ClockFailClear(101)

 

that the primary clock source is

 

 

operational again.

 

 

String:

 

 

`Primary clock restored.'

 

 

 

enterpriseRMON-

H devLastTrapString

All RMON-related option

ResetToDefault(13)

(devHealthAndStatus.-

changes have been reset to their

 

mib)

default values.

 

 

Default Factory Configuration

 

 

settings have been reloaded,

 

 

returning RMON-related options

 

 

to their original settings.

 

 

String:

 

 

`RMON database reset to

 

 

defaults.'

 

 

 

enterpriseSelfTest-

H devLastTrapString

Unit has completed

Fail(2)

(devHealthAndStatus.-

(re)initialization and a hardware

 

mib)

failure was detected.

 

 

String:

 

 

`Self test failed: $s.' ($s is the

 

 

contents of devSelfTestResult.)

 

 

 

B-12

July 2000

9123-A2-GB20-10

Page 238
Image 238
Paradyne 9123 manual SLVs devFrExt.mib