CISCO-ERR-DISABLE-MIB

        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.
    
Source file
CISCO-ERR-DISABLE-MIB
Last revised
Identity
ciscoErrDisableMIB
Base OID
1.3.6.1.4.1.9.9.548
Imported Objects
CISCO-PRIVATE-VLAN-MIB VlanIndexOrZero
CISCO-SMI ciscoMgmt
CISCO-TC TimeIntervalSec
IF-MIB ifIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-ERR-DISABLE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-ERR-DISABLE-MIB::ciscoErrDisableMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-ERR-DISABLE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-ERR-DISABLE-MIB::ciscoErrDisableMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (28)
.1.3.6.1.4.1.9.9.548
.1.3.6.1.4.1.9.9.548.0
.1.3.6.1.4.1.9.9.548.0.1
.1.3.6.1.4.1.9.9.548.1
.1.3.6.1.4.1.9.9.548.1.1
.1.3.6.1.4.1.9.9.548.1.1.1
.1.3.6.1.4.1.9.9.548.1.1.2
Notification/MinuteSNMPv2-SMIUnsigned32
.1.3.6.1.4.1.9.9.548.1.1.3
.1.3.6.1.4.1.9.9.548.1.2
.1.3.6.1.4.1.9.9.548.1.2.1
.1.3.6.1.4.1.9.9.548.1.2.1.1
.1.3.6.1.4.1.9.9.548.1.2.1.1.1
Bits
.1.3.6.1.4.1.9.9.548.1.2.1.1.2
.1.3.6.1.4.1.9.9.548.1.2.1.1.3
.1.3.6.1.4.1.9.9.548.1.2.1.1.4
.1.3.6.1.4.1.9.9.548.1.2.1.1.5
.1.3.6.1.4.1.9.9.548.1.2.1.1.6
.1.3.6.1.4.1.9.9.548.1.2.1.1.7
.1.3.6.1.4.1.9.9.548.1.2.1.1.8
.1.3.6.1.4.1.9.9.548.1.3
.1.3.6.1.4.1.9.9.548.1.3.1
.1.3.6.1.4.1.9.9.548.1.3.1.1
.1.3.6.1.4.1.9.9.548.1.3.1.1.1
.1.3.6.1.4.1.9.9.548.1.3.1.1.2
.1.3.6.1.4.1.9.9.548.1.3.1.1.3
.1.3.6.1.4.1.9.9.548.2
.1.3.6.1.4.1.9.9.548.2.1
.1.3.6.1.4.1.9.9.548.2.2
Dependencies (13) 7 direct · 6 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (1)
Enumeration
udld(1)
bpduGuard(2)
channelMisconfig(3)
pagpFlap(4)
dtpFlap(5)
linkFlap(6)
l2ptGuard(7)
dot1xSecurityViolation(8)
portSecurityViolation(9)
gbicInvalid(10)
dhcpRateLimit(11)
unicastFlood(12)
vmps(13)
stormControl(14)
inlinePower(15)
arpInspection(16)
portLoopback(17)
packetBuffer(18)
macLimit(19)
linkMonitorFailure(20)
oamRemoteFailure(21)
dot1adIncompEtype(22)
dot1adIncompTunnel(23)
sfpConfigMismatch(24)
communityLimit(25)
invalidPolicy(26)
lsGroup(27)
ekey(28)
portModeFailure(29)
pppoeIaRateLimit(30)
oamRemoteCriticalEvent(31)
oamRemoteDyingGasp(32)
oamRemoteLinkFault(33)
mvrp(34)
tranceiverIncomp(35)
other(36)
portReinitLimitReached(37)
adminRxBBCreditPerfBufIncomp(38)
ficonNotEnabled(39)
adminModeIncomp(40)
adminSpeedIncomp(41)
adminRxBBCreditIncomp(42)
adminRxBufSizeIncomp(43)
eppFailure(44)
osmEPortUp(45)
osmNonEPortUp(46)
udldUniDir(47)
udldTxRxLoop(48)
udldNeighbourMismatch(49)
udldEmptyEcho(50)
udldAggrasiveModeLinkFailed(51)
excessivePortInterrupts(52)
channelErrDisabled(53)
hwProgFailed(54)
internalHandshakeFailed(55)
stpInconsistencyOnVpcPeerLink(56)
stpPortStateFailure(57)
ipConflict(58)
multipleMSapIdsRcvd(59)
oneHundredPdusWithoutAck(60)
ipQosCompatCheckFailure(61)
loopDetect(62)
Conformance Groups (8)
A collection of objects to configure error-disable
functionality.
.1.3.6.1.4.1.9.9.548.2.2.1
A collection of objects to manage the configuration of
the error-disable feature.
.1.3.6.1.4.1.9.9.548.2.2.2
A collection of error-disable interface status objects.
.1.3.6.1.4.1.9.9.548.2.2.3
A collection of objects to configure error-disable
notifications.
.1.3.6.1.4.1.9.9.548.2.2.4
A collection of error-disable notification objects.
.1.3.6.1.4.1.9.9.548.2.2.5
A collection of error-disable notification objects.
.1.3.6.1.4.1.9.9.548.2.2.6
A collection of objects to manage the configuration of
error-disable detection shutdown vlan mode.
.1.3.6.1.4.1.9.9.548.2.2.7
A collection of objects to manage the configuration of
the error-disable flap control.
.1.3.6.1.4.1.9.9.548.2.2.8
Compliance Statements (3)

OID .1.3.6.1.4.1.9.9.548.2.1.1
The compliance statement for the cisco errdisable MIB.
Required groups
mandatory ciscoErrDisableGlobalCfgGroup
mandatory ciscoErrDisableFeatureCfgGroup
mandatory ciscoErrDisableIfStatusGroup
optional ciscoErrDisableNotifCfgGroup This group is mandatory if the managed system
supports notifications for error-disable events.
optional ciscoErrDisableNotifGroup This group is mandatory if the managed system
supports notifications for error-disable events.

OID .1.3.6.1.4.1.9.9.548.2.1.2
The compliance statement for the cisco errdisable MIB.
Required groups
mandatory ciscoErrDisableGlobalCfgGroup
mandatory ciscoErrDisableFeatureCfgGroup
mandatory ciscoErrDisableIfStatusGroup
optional ciscoErrDisableNotifCfgGroup This group is mandatory if the managed system
supports notifications for error-disable events.
optional ciscoErrDisableNotifGroupRev1 This group is mandatory if the managed system
supports notifications for error-disable events.
optional ciscoErrDisableShutdownVlanGroup This group is mandatory if the managed system
supports the configuration on error-disable
detection shutdown vlan mode.
Object refinements
ObjectAccessSyntaxDescription
cErrDisableRecoveryInterval readonly
Write access is not required.
cErrDisableNotifEnable readonly
Write access is not required.
cErrDisableNotifRate readonly
Write access is not required.
cErrDisableFeatureDetectEnable readonly
Write access is not required.
cErrDisableFeatureRecoveryEnable readonly
Write access is not required.
cErrDisableFeatureRecoveryInterval readonly
Write access is not required.
cErrDisableFeatureDetectShutdownVlan readonly
Write access is not required.

OID .1.3.6.1.4.1.9.9.548.2.1.3
The compliance statement for the cisco errdisable MIB.
Required groups
mandatory ciscoErrDisableGlobalCfgGroup
mandatory ciscoErrDisableFeatureCfgGroup
mandatory ciscoErrDisableIfStatusGroup
optional ciscoErrDisableNotifCfgGroup This group is mandatory if the managed system
supports notifications for error-disable events.
optional ciscoErrDisableNotifGroupRev1 This group is mandatory if the managed system
supports notifications for error-disable events.
optional ciscoErrDisableShutdownVlanGroup This group is mandatory if the managed system
supports the configuration on error-disable
detection shutdown vlan mode.
optional ciscoErrDisableFeatureFlapGroup This group is mandatory if the managed system
supports the configuration on error-disable
flap control.
Object refinements
ObjectAccessSyntaxDescription
cErrDisableRecoveryInterval readonly
Write access is not required.
cErrDisableNotifEnable readonly
Write access is not required.
cErrDisableNotifRate readonly
Write access is not required.
cErrDisableFeatureDetectEnable readonly
Write access is not required.
cErrDisableFeatureRecoveryEnable readonly
Write access is not required.
cErrDisableFeatureRecoveryInterval readonly
Write access is not required.
cErrDisableFeatureDetectShutdownVlan readonly
Write access is not required.
cErrDisableFeatureMaxFlapCount readonly
Write access is not required.
cErrDisableFeatureFlapTimePeriod readonly
Write access is not required.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.9.548.0.1.1
The 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.
.1.3.6.1.4.1.9.9.548.0.2
The 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.