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

Alarm Handling

S600-E V200R010C00

This document provides the explanations, causes, and recommended actions of alarms 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).
ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.1 hwErrordown

ERRDOWN_1.3.6.1.4.1.2011.5.25.257.2.1 hwErrordown

Description

ERRDOWN/4/ErrordownOccur: OID [oid] Error-down occured. (Ifindex=[INTEGER], Ifname=[STRING], Cause=[STRING])

An error-down 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.
IfIndex Indicates the interface index.
Ifname Indicates the interface name.
Cause Indicates the cause of the error-down event.

Impact on the System

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

Possible Causes

The faults detected by service modules triggered error-down events. The possible causes are as follows:
  • EFM detected a link fault, which could 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 reached the maximum value, the interface received 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.

Procedure

  1. Locate the fault based on the value of Cause in the alarm.

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

  3. Perform the following steps.

    1. Run the interface interface-type interface-num command to enter the interface view.
    2. Run the undo stp edged-port command to delete the edge port configuration and run the undo shutdown command to restart the interface. Check whether the log still exists. If the log still exists, go to Step 5.

  4. Collect log information and contact technical support personnel.
Translation
Download
Updated: 2019-09-24

Document ID: EDOC1000141873

Views: 155043

Downloads: 15

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