Filter
Top Products
SNMP MIBs and Traps, and RMON Alarm Defaults
B-11
9123-A2-GB20-10
July 2000
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)
H devFrExtDlciIfIndex
(devFrExt.mib)
H devFrExtDlciDlci
(devFrExt.mib)
H devFrExtDlciCIR
(devFrExt.mib)
H 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
$CIR bps.’
enterpriseConfig-
Change(6)
H devLastTrapString
(devHealthAndStatus.-
mib)
Configuration has been changed
via the menu-driven user
interface, an SNMP Manager,
or auto-configuration after 60
seconds has elapsed without
another change.
String:
‘Device configuration change.’
enterpriseDLCI-
delete(17)
H devFrExtDlciIfIndex
(devFrExt.mib)
H devFrExtDlciDlci
(devFrExt.mib)
H devLastTrapString
(
devHealthAndStatus.-
The DLCI has been deleted. The
network no longer supports the
DLCI, and it was removed.
Strings:
‘$ifString deleted by Auto-DLCI
delete.’
enterpriseDLCI-
Down(11)
(devHealthAndStatus
.-
mib.)
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.)
enterpriseDLCIUp(12) DLCI Status is set to Active;
DLCI is up again.
String:
‘$ifString up.’