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

Configuration Guide - Interface Management

CloudEngine 12800 and 12800E V200R003C00

This document describes the interface management configuration, including basic interface configuration, Ethernet interface configuration, and logical interface configuration.

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).
Configuring an Interface to Transit to the CRC Error-Down State When the Number of Received Error Packets Exceeds the Threshold

Configuring an Interface to Transit to the CRC Error-Down State When the Number of Received Error Packets Exceeds the Threshold

Context

The device records the status of an interface as Error-Down when it detects that a fault occurs. The interface in Error-Down state cannot receive or send packets and the interface indicator is off. Receiving excessive CRC error packets is one of the reasons that cause an interface to transit to the Error-Down state. When an Ethernet interface receives excessive CRC error packets, faults such as packet loss occur. Because the interface is still in Up state, traffic is still transmitted on the interface even if a backup link is configured. To avoid impact on services, you can configure the interface to change to the Error-Down state when it receives excessive CRC error packets. When the number of received CRC error packets on the interface exceeds the upper alarm threshold, the system disables the interface and records the interface status as ERROR DOWN(crc-statistics). Services are then switched to the backup link immediately.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run trap-threshold error-statistics threshold-value interval interval-value

    The alarm threshold of CRC error packets and the alarm interval are configured.

    By default, the alarm threshold of error packets is 3 and the alarm interval is 10 seconds.

  4. Run port crc-statistics trigger error-down

    The interface is configured to transit to the Error-Down state when the number of received CRC-error packets exceeds the threshold.

    By default, an interface does not transit to the Error-Down state when the number of received CRC-error packets exceeds the threshold.

  5. Run commit

    The configuration is committed.

Verifying the Configuration

Run the display error-down recovery [ interface interface-type interface-number ] command in any view to check information about the interfaces in Error-Down state.

Follow-up Procedure

If an interface is in Error-Down state, you are advised to find out the cause of the Error-Down event first. If the two connected interfaces are optical interfaces, check whether optical modules and fiber on the interfaces are securely installed or fail. If the two connected interfaces are electrical interfaces, check whether the network cable is securely connected to the interfaces or fails.

An interface in Error-Down state can be recovered using either of the following methods:
  • Manual recovery (after an Error-Down event occurs):

    If a few interfaces need to be recovered, run the shutdown and undo shutdown commands in the interface view. Alternatively, run the restart command in the interface view to restart the interfaces, or remove and reinstall the transmission medium on optical interfaces.

  • Automatic recovery (before an Error-Down event occurs):

    If a large number of interfaces need to be recovered, manual recovery is time consuming and some interfaces may be omitted. To avoid this problem, you can run the error-down auto-recovery cause crc-statistics interval command in the system view to enable automatic interface recovery and set the recovery delay time. You can run the display error-down recovery command to view information about automatic interface recovery.

    NOTE:

    This method does not take effect on interfaces that are already in Error-Down state. It takes effect only on interfaces that enter the Error-Down state after this configuration is complete.

Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004195

Views: 18881

Downloads: 37

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next