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.

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.5.25.257.2.1	Warning	communicationsAlarm(2)

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

After the errordown event occurs, traffic cannot be forwarded on relevant interfaces and services are interrupted.

The faults detected by service modules triggered errordown events. The possible causes are as follows:

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 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.
Check whether the interface is specified as an edge port.
- If the interface is not specified as an edge port, go to Step 3.
- If the interface is specified as an edge port, go to Step 4.
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 4.
Collect alarm information and configuration information, and then contact technical support personnel.