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

Troubleshooting Guide

CloudEngine 16800, 12800, 12800E, 8800, 7800, 6800, and 5800 Series Switches

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).
How Are Some Interfaces Configured Not to Enter the Error-Down State When the Peer-link Fails on an M-LAG Network?

How Are Some Interfaces Configured Not to Enter the Error-Down State When the Peer-link Fails on an M-LAG Network?

On a dual-homing Ethernet, VXLAN, or IP network where M-LAG is deployed, when the peer-link fails but DAD detects that the heartbeat status is normal, interfaces except the management interface, peer-link interface, and stack interface on the backup device all enter the Error-Down state. When the faulty peer-link is restored, the M-LAG interface in Error-Down state goes Up after 2 minutes by default and other physical interfaces in Error-Down state go up automatically.

In practice, uplink interfaces running routing protocols or DAD-enabled heartbeat interfaces should not enter the Error-Down state. You can configure the interfaces that are not M-LAG member interfaces to enter the Error-Down state.

# Configure Eth-Trunk 2 on the backup device to enter the Error-Down state.

<HUAWEI> system-view
[~HUAWEI] interface eth-trunk 2
[*HUAWEI-Eth-Trunk2] m-lag unpaired-port suspend
[*HUAWEI-Eth-Trunk2] commit
  • When the peer-link fails but the heartbeat status is normal, only the interface where the m-lag unpaired-port suspend command is configured enters the Error-Down state in addition to the M-LAG interface in Error-Down state.
  • The m-lag unpaired-port suspend command cannot be configured on the M-LAG interface. It is recommended that this command be configured on both the M-LAG master and backup devices.
Translation
Download
Updated: 2020-01-07

Document ID: EDOC1000060766

Views: 610255

Downloads: 2956

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next