B. SNMP MIBs and Traps, and RMON Alarm Defaults

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

Trap

Variable-Bindings

Possible Cause

 

 

 

enterpriseSecondary-

devLastTrapString

Operating software has detected

ClockFail(4)

T(devHealthAndStatus.-

that the secondary clock source

 

mib)

has failed.

 

 

String:

 

 

‘Secondary clock failed.’

 

 

 

enterpriseSecondary-

 

Operating software has detected

ClockFailClear(104)

 

that the secondary clock source is

 

 

operational again.

 

 

String:

 

 

‘Secondary clock restored.’

 

 

 

enterpriseSelfTest-

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.)

 

 

 

enterpriseTest-

For physical interfaces and

At least one test has been started

Start(5)

frame relay links:

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

 

enterpriseTest-

All tests have been halted on an

For virtual circuits (DLCIs):

Stop(105)

interface or virtual circuit.

 

devFrExtDlciIfIndex

String:

 

(devFrExt.mib)

‘$testString test stopped on

 

devFrExtDlciDlci

$ifString.’ (e.g., ‘Disruptive PVC

 

Loopback test stopped on DLCI

 

T(devFrExt.mib)

 

 

100 of Sync Data Port S01P1

 

devLastTrapString

frame relay.’)

 

(devHealthAndStatus.-

 

 

mib

 

 

 

 

9128-A2-GB20-80

September 2002

B-15

Page 363
Image 363
Paradyne CSU, DSU, 9126-II, 9128-II manual That the secondary clock source