Home/Catalog/CISCO-ERR-DISABLE-MIB

CISCO-ERR-DISABLE-MIB

AI MIB Summary

The CISCO-ERR-DISABLE-MIB enables SNMP-based configuration and monitoring of the Cisco error-disable mechanism, which automatically shuts down interfaces, VLANs, or Layer 2 ports upon detecting specific abnormal conditions such as BPDU guard violations, storm-control thresholds, UDLD failures, or port-security breaches. It provides visibility into the operational state of these disabled entities and manages the global parameters for automatic error recovery, including the enablement of the feature and the specific re-enablement timer intervals.

This MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature via SNMP. The error-disable feature allows other software features running in a system to operationally disable a system entity upon detecting abnormal conditions. Examples of such a system entity include interfaces, a vlan configured in the system, or a VLAN allowed on specific layer 2 multi-vlan interface. More specific examples: a) When BPDU guard is enabled on an interface it is expected that no BPDU packets are received by the interface. If a BPDU packet is received, then the BPDU guard will operationally disable the interface. b) Users can configure a particular threshold of broadcast packets received on an interface. If the number of packets received exceeds the threshold, then storm-control will disable the interface. c) When unidirectional Link Detection (UDLD) detects a unidirectional link on an interface, it can disable the interface. d) On a trunk or a multi-vlan layer 2 port, if port-security detects violation on a particular vlan, then it can operationally disable that vlan on that port. The definition of 'abnormal condition' is under the control of features that make use of the error-disable feature to disable system entities. The error-disable feature supports the following configuration: 1) Whether software features can in fact use the error-disable feature upon detecting abnormal conditions. NOTE: Some software features will ALWAYS use the error-disable feature to disable entities upon detection of error. 2) Whether the system can attempt to automatically recover after a system entity has been disabled (e.g., A system can attempt to bring up a physical interface which had been disabled earlier) 3) If error recovery is possible, then the time interval to wait before the system starts the recovery attempt.
Main OID:
ciscoErrDisableMIB.1.3.6.1.4.1.9.9.548
30
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

30 total
Object Name
ciscoErrDisableMIBThis MIB module provides the ability for a Network Management Station (NMS) to configure and monitor the error-disable feature via SNMP. The error-disable feature allows other software features running in a system to operationally disable a system entity upon detecting abnormal conditions. Examples of such a system entity include interfaces, a vlan configured in the system, or a VLAN allowed on specific layer 2 multi-vlan interface. More specific examples: a) When BPDU guard is enabled on an interface it is expected that no BPDU packets are received by the interface. If a BPDU packet is received, then the BPDU guard will operationally disable the interface. b) Users can configure a particular threshold of broadcast packets received on an interface. If the number of packets received exceeds the threshold, then storm-control will disable the interface. c) When unidirectional Link Detection (UDLD) detects a unidirectional link on an interface, it can disable the interface. d) On a trunk or a multi-vlan layer 2 port, if port-security detects violation on a particular vlan, then it can operationally disable that vlan on that port. The definition of 'abnormal condition' is under the control of features that make use of the error-disable feature to disable system entities. The error-disable feature supports the following configuration: 1) Whether software features can in fact use the error-disable feature upon detecting abnormal conditions. NOTE: Some software features will ALWAYS use the error-disable feature to disable entities upon detection of error. 2) Whether the system can attempt to automatically recover after a system entity has been disabled (e.g., A system can attempt to bring up a physical interface which had been disabled earlier) 3) If error recovery is possible, then the time interval to wait before the system starts the recovery attempt.
MODULE-IDENTITY
.1.3.6.1.4.1.9.9.548
ciscoErrDisableMIBNotifs
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.0
cErrDisableNotificationsPrefix
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.0.1
cErrDisableInterfaceEventThe cErrDisableInterfaceEvent is generated when an interface or {interface, vlan} is error-disabled by the feature specified in cErrDisableIfStatusCause. cErrDisableInterfaceEvent is deprecated and replaced by cErrDisableInterfaceEventRev1.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.548.0.1.1
cErrDisableInterfaceEventRev1The cErrDisableInterfaceEventRev1 is generated when an interface or {interface, vlan} is error-disabled by the feature specified in cErrDisableIfStatusCause. cErrDisableInterfaceEventRev1 deprecates cErrDisableInterfaceEvent to make it RFC 2578 compliant. According to section 8.5 of RFC 2578, the next to last sub-identifier in the name of any newly-defined notification must have the value zero.
NOTIFICATION-TYPE
.1.3.6.1.4.1.9.9.548.0.2
ciscoErrDisableMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.1
cErrDisableGlobalObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.1.1
cErrDisableRecoveryIntervalThis object specifies the error-disable recovery time interval. When a system entity is operationally disabled upon detecting abnormal condition by a particular feature, the system waits for a period equal to this time interval, and then re-enable the entity if automatic recovery is enabled for the feature.rw
TimeIntervalSec (CISCO-TC)
.1.3.6.1.4.1.9.9.548.1.1.1
cErrDisableNotifEnableThis object specifies whether cErrDisableInterfaceEvent and cErrDisableInterfaceEventRev1 notifications should be generated when a system entity is error-disabled.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.548.1.1.2
cErrDisableNotifRateThe value of this object specifies the maximum number of error-disable notifications the device will generate per minute. A value of '0' specifies no limit and the device will generate a notification for each error-disable event.rw
Unsigned32 UNITS "Notification/Minute"
.1.3.6.1.4.1.9.9.548.1.1.3
cErrDisableFeatureObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.1.2
cErrDisableFeatureTableThis table contains the error-disable related info for each feature employing the error-disable feature.
SEQUENCE OF CErrDisableFeatureEntry
.1.3.6.1.4.1.9.9.548.1.2.1
cErrDisableFeatureEntryAn entry is created for each feature that employs the error-disable feature.
CErrDisableFeatureEntry
.1.3.6.1.4.1.9.9.548.1.2.1.1
cErrDisableFeatureIndexThis object uniquely identifies a feature that makes use of the error-disable feature.
CErrDisableFeatureID
.1.3.6.1.4.1.9.9.548.1.2.1.1.1
cErrDisableFeatureConfigurableThis object indicates whether the error-disable related configuration is configurable for this feature. If a bit is set to 1, then the corresponding error-disable configuration can be configured. 'detectionEnable' - indicates the error-disable detection can be enabled/disabled for this feature via cErrDisableFeatureDetectEnable. 'recoveryEnable' - indicates the error-disable recovery can be enabled/disabled for this feature via cErrDisableFeatureRecoveryEnable. 'recoveryInterval' - indicates the error-disable recovery Interval can be configured via cErrDisableFeatureRecoveryInterval. 'detectShutdownVlan' - indicates the error-disable detection shutdown vlan mode can be configured for this feature via cErrDisableFeatureDetectShutdownVlan. 'flapControl' - indicates the error-disable flap control can be configured via cErrDisableFeatureMaxFlapCount and cErrDisableFeatureFlapTimePeriod.ro
Bits
.1.3.6.1.4.1.9.9.548.1.2.1.1.2
cErrDisableFeatureDetectEnableThis object specifies whether the error-disable detection is enabled for the feature. Note: This object is read-write only for those features that are configurable, meaning: cErrDisableFeatureConfigurable.<featureIndex> has the first bit set to 1.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.548.1.2.1.1.3
cErrDisableFeatureRecoveryEnableThis object specifies whether the system can automatically recover a system entity that has been disabled by the feature.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.548.1.2.1.1.4
cErrDisableFeatureRecoveryIntervalThis object specifies the error-recovery time interval that will be used by the system for any system entity that is error-disabled by this particular feature. If the value of this object is '0', then the device will use the value specified by the global configuration object cErrDisableRecoveryInterval.rw
TimeIntervalSec (CISCO-TC)
.1.3.6.1.4.1.9.9.548.1.2.1.1.5
cErrDisableFeatureDetectShutdownVlanThis object specifies whether shutting down the violating VLAN on an interface is enabled or not. The value of 'true' indicates that shutting down the violating VLAN on an interface is enabled. The value of 'false' indicates that shutting down the violating VLAN on an interface is disabled.rw
TruthValue (SNMPv2-TC)
.1.3.6.1.4.1.9.9.548.1.2.1.1.6
cErrDisableFeatureMaxFlapCountThis object specifies the maximum number of flaps that are allowed to occur before setting to error disable state. A read-only value of zero indicates that no flap control is present.rw
Unsigned32
.1.3.6.1.4.1.9.9.548.1.2.1.1.7
cErrDisableFeatureFlapTimePeriodThis object specifies the period of time counting the number of flaps that are allowed before setting to error disable state. A read-only value of zero indicates that no flap control is present.rw
Unsigned32
.1.3.6.1.4.1.9.9.548.1.2.1.1.8
cErrDisableIfObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.1.3
cErrDisableIfStatusTableThis table provides interface (port) specific error-disable status information. Each conceptual row provides status information about a {interface, vlan} disabled by a feature. On a trunk or multi-vlan access interface, a given vlan on the interface can be error-disabled. In this case, the row is indexed by the ifIndex for the interface and the vlan index corresponding to the vlan in question. If the interface is carrying only 1 vlan or the entire trunk interface is error-disabled (due to link flaps, for example) then the vlan index portion of the row index is 0.
SEQUENCE OF CErrDisableIfStatusEntry
.1.3.6.1.4.1.9.9.548.1.3.1
cErrDisableIfStatusEntryA collection of objects that specify the status of an error-disabled Interface or {interface, vlan}.
CErrDisableIfStatusEntry
.1.3.6.1.4.1.9.9.548.1.3.1.1
cErrDisableIfStatusVlanIndexThis object specifies the vlan of the given interface that has been error-disabled. If the physical interface is error-disabled then the value of this object is 0.
VlanIndexOrZero
.1.3.6.1.4.1.9.9.548.1.3.1.1.1
cErrDisableIfStatusCauseThis object specifies the feature/event that caused the {interface, vlan} (or the entire interface) to be error-disabled.ro
CErrDisableFeatureID
.1.3.6.1.4.1.9.9.548.1.3.1.1.2
cErrDisableIfStatusTimeToRecoverTime left before the system attempts an automatic recovery of the interface or the vlan of the given interface. If no recovery is scheduled, then the value of this object is '0'.ro
TimeIntervalSec (CISCO-TC)
.1.3.6.1.4.1.9.9.548.1.3.1.1.3
ciscoErrDisableMIBConform
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.2
ciscoErrDisableMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.2.1
ciscoErrDisableMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.548.2.2
CISCO-ERR-DISABLE-MIB - SNMP MIB Reference | MIBs Explorer