No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
MENU
Support Documentation

Log Reference

CloudEngine 8800, 7800, 6800, and 5800 V200R005C00

This document provides the explanations, causes, and recommended actions of logs on the product.
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

ERROR-DOWN/4/hwErrordown_active

Message

ERROR-DOWN/4/hwErrordown_active: Error-down occurred. (Ifindex=[INTEGER], Ifname=[STRING], Cause=[STRING])

Description

An Error-Down event occurred.

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
    1. 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
    1. Check whether the interface should be specified as an edge interface.

      • If not, go to step 2.

      • If so, go to step 3.

    2. Perform the following steps:

      • Run the interface interface-type interface-num command to enter the interface view.

      • Run the undo stp edged-port and restart commands to delete the edge interface configuration. Then check whether the log persists. If the log persists, go to step 3.

    3. Collect the alarm information and contact technical support personnel.
  • Cause: crc-statistics
    1. 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
    1. 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
    1. Run the display interface command in the user view to check the total number and total bytes of sent packets on an interface.

      If the number of packets discarded by the interface during physical layer detection due to queue congestion keep rising, run both the shutdown and undo shutdown commands or run the restart command in the interface view to restart the interface.

    2. If the fault is not rectified, check the links.
  • Cause: forward-engine-interface-failed
    1. Collect alarm and configuration information, and contact technical support personnel.
  • Cause: link-flap
    1. 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
    1. Check the network configuration and whether loops occur in cable connections.

      • If so, correct the connections.
      • If not, go to step 2.

    2. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause: m-lag
    1. Check whether the peer link is faulty.

      • If so, rectify the peer link fault.
      • If not, go to step 2.

    2. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause: m-lag-consistency-check
    1. 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
    1. Check the network configuration and whether loops occur in cable connections.

      • If so, correct the connections.
      • If not, go to step 2.

    2. Collect trap, log, and configuration information, and contact technical support personnel.
  • Cause: monitor-link
    1. The upstream link state of the Monitor Link group is Down. To rectify the fault, see IFNET_1.3.6.1.6.3.1.1.5.3 linkdown.

  • Cause: portsec-reachedlimit
    1. Check whether the MAC address in the FEI_COMM_1.3.6.1.4.1.2011.5.25.315.3.2 hwPortSecRcvIllegalMacAlarm alarm is valid.

      • If so, go to step 2.
      • If not, go to step 3.

    2. Run the port-security max-mac-num max-number command to increase the maximum number of MAC address learning so that valid MAC addresses can be learned. Check whether the alarm is cleared.

      • If so, go to step 4.
      • If not, go to step 3.

    3. Collect trap, log, and configuration information, and contact technical support personnel.
    4. End.
  • Cause: resource-mismatch
    1. Save the configuration, and restart the device where the interface is in Error-Down state.
  • Cause: spine-member-exceed-limit
    1. Modify the configuration or cable connection, and remove extra spine switches. After the fault is rectified, restore the interface status of these spine switches using either of the following methods:

      • Run the shutdown and undo shutdown commands in the interface view, or run the restart command to restart the interface.

      • Run the reboot command to restart extra devices so that the Error-Down fault on all interfaces is rectified.

  • Cause: spine-type-unsupported
    1. Remove the cable between the device and SVF system. After the fault is rectified, use either of the following methods to restore the interface status of the parent switch:

      • Run the shutdown and undo shutdown commands in the interface view, or run the restart command to restart the interface.

      • Run the reboot command to restart extra devices so that the Error-Down fault on all interfaces is rectified.

  • Cause: stack-config-conflict
    1. 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
    1. Modify the configuration or cable connection, and remove extra stack devices. After the fault is rectified, restore the interface status of these devices using either of the following methods:

      • Run the shutdown and undo shutdown commands in the interface view, or run the restart command to restart the interface.

      • Run the reboot command to restart extra devices so that the Error-Down fault on all interfaces is rectified.

  • Cause: stack-packet-defensive
    1. Check whether the network connection is incorrect. If the network connection is correct, run both the shutdown and undo shutdown commands or run the restart command in the interface view to restart the interface.

  • Cause: storm-control
    1. 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
    1. Run the display interface transceiver command in the user view to check the transmit and receive optical power of the current interface.

      • If the transmit optical power is too low, you are advised to replace the local optical module.

      • If the receive optical power is too low, you are advised to replace the peer optical module.

    2. If the fault is not rectified, check the links.
Translation
简体中文
Download
Updated: 2019-04-20

Document ID: EDOC1100039602

Views: 115458

Downloads: 85

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next
Enterprise APP

Copyright © 2019 Huawei Technologies Co., Ltd. All rights reserved.