B. SNMP MIBs, Traps, and RMON Alarm Defaults
9700-A2-GB20-20 December 2002 B-11
Trap: enterprise-Specific

These traps indicate that an enterprise-specific event has occurred. Suppor ted

enterprise-specific traps are listed alphabetically below.

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

Trap Variable-Bindings Possible Cause
enterpriseCIR-
Change(15)
devFrExtDlciIfIndex
(devFrExt.mib)
devFrExtDlciDlci
(devFrExt.mib)
devFrExtDlciCIR
(devFrExt.mib)
devLastTrapString
(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
$CIRbps.’
enterpriseConfig-
Change(6)
devLastTrapString
(devHealthAndStatus.mib)
Configuration has been changed
via the menu-driven user interface,
an SNMP Manager,
orauto-configuration after 60
seconds has elapsed without
another change.
String:
‘Device configuration change.
enterpriseDLCI-
delete(17)
devFrExtDlciIfIndex
(devFrExt.mib)
devFrExtDlciDlci
(devFrExt.mib)
devLastTrapString
(devHealthAndStatus.mib)
The DLCI has been deleted. The
network no longer supports the
DLCI, and it was removed.
String:
‘$ifString deleted by Auto-DLCI
delete.’
enterpriseDLCI-
Down(11)
DLCI Status is set to Inactive; the
DLCI is down.
Strings:
‘$ifString down.’ (Due to LMI or
physical failure.)
‘$ifString administratively
shutdown.’ (Due to an intentional
shutdown.)
enterpriseDLCI-
Up(12)
DLCI Status is set to Active; DLCI
is up again.
String:
‘$ifString up.’
enterpriseLatency-
Exceeded(21)
ifIndex (RFC1573)
devLastTrapString
(devHealthAndStatus.-
mib
An IP SLV latency threshold has
been exceeded for a particular
Class of Service for a path.
String:
‘Latency exceeded
xxx.xxx.xxx.xxx
, COS
nn
,
DLCI
nnnn