ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.1 hwErrordown
Description
ERRDOWN/4/ErrordownOccur: OID [oid] Error-down occurred. (Ifindex=[INTEGER], Ifname=[STRING], Cause=[STRING])
The alarm was generated when an errordown event occurred.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.257.2.1 |
Warning |
communicationsAlarm(2) |
Parameters
| Name | Meaning |
|---|---|
oid |
Indicates the MIB object ID of the alarm. |
IfIndex |
Index of an interface. |
Ifname |
Interface name. |
Cause |
Cause of the errordown event. |
Impact on the System
After the errordown event occurs, traffic cannot be forwarded on relevant interfaces and services are interrupted.
Possible Causes
EFM detected a link fault, which can be a fault that occurred on the remote end or a threshold-crossing event.
The MSTP edge port received BPDU packets.
After the number of secure MAC addresses learned by an interface reaches the maximum value, the interface receives packets from another MAC address.
MAC address flapping occurred.
The number of CRC error packets received by the interface during the alarm interval reached the alarm threshold.
The number of link flappings during the link flapping period reached the alarm threshold.
The current optical power of the interface fell below the lower alarm threshold.
Attack packets occurred on the interface.
The number of Runts error packets received by the interface reached the alarm threshold.
Only the S5720-EI supports the alarm indicating that the number of received Runts error packets reaches the alarm threshold.
Procedure
- Locate the fault based on the value of the Cause field in the alarm.
If the value of the Cause field is bpdu-protection, go to Step 2.
If the value of the error-down cause field is port-security, rectify the fault according to the log L2IFPPI_1.3.6.1.4.1.2011.5.25.315.3.2 hwPortVlanSecureMacAlarm.
If the value of the error-down cause field is mac-address-flapping, rectify the fault according to the log L2IFPPI_1.3.6.1.4.1.2011.5.25.160.3.7 hwMflpVlanAlarm.
If the value of the Cause field is efm-threshold-event, rectify the fault according to the log EFM_1.3.6.1.4.1.2011.5.25.136.1.6.4 hwDot3ahEfmThresholdEvent.
If the value of the Cause field is efm-remote-failure, rectify the fault according to the log EFM_1.3.6.1.4.1.2011.5.25.136.1.6.5 hwDot3ahEfmNonThresholdEvent.
If the value of the error-down cause field is error-statistics, rectify the fault according to the log IFNET_1.3.6.1.4.1.2011.5.25.41.4.1 hwIfMonitorCrcErrorRising.
If the value of the error-down cause field is link-flap, rectify the fault according to the section An Ethernet Interface Frequently Alternates Between Up and Down States in "Ethernet Interface Configuration" in the S2720, S5700, and S6700 V200R019C10 Configuration Guide - Interface Management.
If the value of the error-down cause field is transceiver-power-low, rectify the fault according to the log ENTITYTRAP_1.3.6.1.4.1.2011.5.25.219.2.4.5 hwOpticalInvalid 136194.
If the value of the error-down cause field is auto-defend, rectify the fault according to the next log.
If the value of the Cause field is runts-error-statistics, go to step 4.
- Check whether the interface is specified as an edge port.
- Perform the following steps.
Run:
interface interface-type interface-num
The interface view is displayed.
Run:
undo stp edged-port and undo shutdown
The edge port configuration is removed. Check whether the log still exists. If the log still exists, go to Step 5.
- Perform the following steps.
- If the interface is an optical interface, check whether the optical fiber or optical module is removed and reinstalled. If the interface is an electrical interface, check whether the network cable is removed and reinstalled. If not, go to step b.
- Run the display history-command command to check whether the shutdown or undo shutdown command has been executed on the interface. If not, go to step c.
- Check whether the physical link is faulty. If not, the interface may be attacked using Runts error packets. Check the log to find out the attack source and take measures to defend against the attack. If the fault persists, go to step 5.
- Collect log messages and contact technical support personnel.