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


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


Log Reference

AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.

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).



ERRDOWN/4/ERRDOWN_DOWNNOTIFY: Notify interface to change status to error-down. (InterfaceName=[STRING], Cause=[STRING])


After an error-down event occurred on an interface, the log was displayed, indicating the interface name and the error down cause.


Parameter Name Parameter Meaning
InterfaceName Interface name
Cause Cause of the errordown event

Possible Causes

The faults detected by service modules triggered errordown events. The possible causes are as follows:
  • 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.


  1. 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.

  2. Perform the following steps.

    • Run:

      interfaceinterface-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.

  3. Collect log information and configuration information, and then contact technical support personnel.
Updated: 2019-05-29

Document ID: EDOC1000097209

Views: 133998

Downloads: 189

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next