SNMP MIBs and Traps, and RMON Alarm Defaults

Traps: enterprise-Specific

These traps indicate that an enterprise-specific event has occurred. Supported enterprise-specific traps are listed below.

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

Trap

Variable-Bindings

Possible Cause

enterpriseCIR- Change(15)

HdevFrExtDlciIfIndex (devFrExt.mib)

HdevFrExtDlciDlci (devFrExt.mib)

HdevFrExtDlciCIR (devFrExt.mib)

HdevLastTrapString (devHealthAndStatus.- mib)

CIR has changed due to the LMI report. LMI Protocol is set to Standard and the network's CIR changed.

String:

`CIR on $ifString changed to $CIR bps.'

enterpriseConfig-

H devLastTrapString

Configuration has been changed

Change(6)

(devHealthAndStatus.-

via the menu-driven user

 

mib)

interface, an SNMP Manager,

 

 

or auto-configuration after 60

 

 

seconds has elapsed without

 

 

another change.

 

 

String:

 

 

`Device configuration change.'

 

 

 

enterpriseDLCI-

H devFrExtDlciIfIndex

The DLCI has been deleted. The

delete(17)

(devFrExt.mib)

network no longer supports the

 

H devFrExtDlciDlci

DLCI, and it was removed.

 

 

 

(devFrExt.mib)

Strings:

 

H devLastTrapString

`$ifString deleted by Auto-DLCI

 

delete.'

 

(devHealthAndStatus.-

 

 

enterpriseDLCI-

mib.)

DLCI Status is set to Inactive; the

 

Down(11)

 

DLCI is down.

 

 

Strings:

 

 

`$ifString down.' (Due to LMI or

 

 

physical failure.)

 

 

`$ifString administratively

 

 

shutdown.' (Due to an intentional

 

 

shutdown.)

 

 

 

enterpriseDLCIUp(12)

 

DLCI Status is set to Active;

 

 

DLCI is up again.

 

 

String:

 

 

`$ifString up.'

 

 

 

9123-A2-GB20-00

May 2000

B-11

Page 229
Image 229
Paradyne 9123 manual Traps enterprise-Specific, DevHealthAndStatus