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.
|
ciscoErrDisableMIB1.3.6.1.4.1.9.9.548 |
| VlanIndexOrZero | CISCO-PRIVATE-VLAN-MIB |
| ciscoMgmt | CISCO-SMI |
| TimeIntervalSec | CISCO-TC |
| ifIndex | IF-MIB |
| MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | SNMPv2-CONF |
| MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32 | SNMPv2-SMI |
| TEXTUAL-CONVENTION, TruthValue | SNMPv2-TC |
| Name | Base Type | Values/Constraints |
|---|---|---|
| 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) |
![]() | .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 | |
![]() | .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 | |
![]() | .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 |
| Name | OID | Description |
|---|---|---|
| .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. |