Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ERROR-DOWN/4/hwErrordown_active
Message
ERROR-DOWN/4/hwErrordown_active: Error-down occurred. (Ifindex=[INTEGER], Ifname=[STRING], Cause=[STRING])
Parameters
| Parameter Name | Parameter Meaning |
|---|---|
Ifindex |
This object indicates the interface index. |
Ifname |
This object indicates the interface name. |
Cause |
This object indicates the Error-Down cause. |
Possible Causes
- auto-defend: The number of packets sent to the CPU for processing reaches the threshold.
- bpdu-protection: The STP edge interface receives BPDUs.
- crc-statistics: The number of CRC error packets exceeds the alarm threshold.
- dual-active: The stack is split and a dual-active fault occurs, and the service interfaces (except the reserved interfaces) on the switch that fails the competition enter the Error-Down state.
- forward-engine-buffer-failed: The interface buffer exception occurs.
- forward-engine-interface-failed: A fault occurs in the forwarding engine and the interface working status is unstable. As a result, packet loss may occur or traffic may fail to be forwarded. The interface changes to Error-Down state.
- link-flap: The interface frequently switches between Up and Down states due to link flapping.
- loopback-detect: Loops occur on the interface.
- m-lag: A dual-active split fault occurs.
- m-lag-consistency-check: Key configuration check of M-LAG master and slave devices fails.
- mac-address-flapping: MAC address floating occurs.
- monitor-link: The uplink link in the Monitor Link group is Down.
- portsec-reachedlimit: The number of secure MAC addresses learned on the interface reaches the upper limit.
- resource-mismatch: If a stack member switch that is starting uses a different resource mode than the master switch, or the port split configurations are inconsistent, all service ports except stack physical member ports will be set to Down. Resource modes include ARP resource allocation mode, Eth-Trunk quantity, tunnel mode, layer 3 resource allocation mode, large Layer 3 interface mode, and EEDB resource mode.
- spine-member-exceed-limit: The number of spine switches in an SVF exceeds the specification, and the service interfaces on the extra spine switches enter the Error-Down state.
- spine-type-unsupported: When the device that cannot function as a parent switch joins a stack set up by the parent switch of an SVF system, service ports of the device enter the Error-Down state.
- stack-config-conflict: During the setup of a stack, if the standby or slave switch has the stack configuration that conflicts with the master switch, the stack may fail to be set up, and service ports of the standby or slave switch will be set to Error-Down state.
- stack-member-exceed-limit: The number of member switches in a stack exceeds the specification, and the interfaces on the extra switches enter the Error-Down state.
- stack-packet-defensive: A physical member port receives a large number of stack protocol packets or stack error packets within a short period.
- storm-control: When the average rate of broadcast, unicast, or unknown unicast packets received on an interface exceeds the maximum threshold, the interface enters the Error-Down state.
- transceiver-power-low: The transceiver power on an interface is too low.
Procedure
- Cause: auto-defend
- Identify the attack source and prevent the attacks. After the fault is rectified, run the shutdown and undo shutdown commands in the interface view to restore the service interface state.
- Cause: bpdu-protection
- Cause: crc-statistics
- If optical interfaces are used, check whether the optical modules on the two ends are securely inserted to rectify the optical module or fiber fault. If electrical interfaces are used, check whether network cables are firmly connected or network cables fault.
- Cause: dual-active
- Rectify the link fault that results in stack splitting. After the fault is rectified, the split stack system is merged and the switch that fails competition automatically restarts. After the switch restarts, the Error-Down fault of the service interfaces is automatically rectified.
- Cause: forward-engine-buffer-failed
- Cause: forward-engine-interface-failed
- Collect alarm and configuration information, and contact technical support personnel.
- Cause: link-flap
- If optical interfaces are used, check whether the optical modules on the two ends are securely inserted to rectify the optical module or fiber fault. If electrical interfaces are used, check whether network cables are firmly connected.
- Cause: loopback-detect
- Cause: m-lag
- Cause: m-lag-consistency-check
- Run the display dfs-group consistency-check command to check the configuration of M-LAG master and backup devices. Modify the inconsistent common configuration.
- Cause: mac-address-flapping
- Cause: monitor-link
- Cause: portsec-reachedlimit
- Cause: resource-mismatch
- Save the configuration, and restart the device where the interface is in Error-Down state.
- Cause: spine-member-exceed-limit
- Cause: spine-type-unsupported
- Cause: stack-config-conflict
- Run the display stack troubleshooting command to check the conflicting configuration and then modify the configuration to meet service requirements. Subsequently, restart the switch to enable the stack to be set up again and recover the service ports from the Error-Down state.
- Cause: stack-member-exceed-limit
- Cause: stack-packet-defensive
- Cause: storm-control
- When there are attack packets, the average rate of broadcast, unicast, or unknown unicast packets received on the interface exceeds the maximum threshold. Identify the attack source and prevent the attacks. After the fault is rectified, run the shutdown and undo shutdown commands in the interface view to restore the service interface state.
- Cause: transceiver-power-low
