For M-LAG networking of CE series switches, how to prevent some ports on a slave switch from entering the Error-Down state upon peer-link failures

If M-LAG is used on an Ethernet, VXLAN, or IP network where a CE switch is dual-homed to two PEs, when the peer-link is faulty but the heartbeat status is normal, all interfaces except the management interface, peer-link interface, and stack interface on the slave device enter the Error-Down state. When the peer-link recovers, the M-LAG member interfaces in Error-Down state are restored to the Up state after 2 minutes by default. Other physical interfaces in Error-Down state are restored to the Up state automatically.
In actual networking, however, some uplink interfaces that run routing protocols or are used as DAD heartbeat interfaces do not need to enter the Error-Down state when the peer-link is faulty. You can configure the function on non-M-LAG member interfaces.
# Configure Eth-Trunk 2 on the slave switch to automatically enter the Error-Down state.
system-view
[~HUAWEI] interface eth-trunk 2
[*HUAWEI-Eth-Trunk2] m-lag unpaired-port suspend
[*HUAWEI-Eth-Trunk2] commit
- When the peer-link is faulty but the heartbeat status is normal, M-LAG member interfaces and only the interfaces having the m-lag unpaired-port suspend command configured enter the Error-Down state.
- M-LAG member interfaces do not support the m-lag unpaired-port suspend command, so you are advised to configure them on both master and slave switches.

Other related questions:
How to restore an interface in ERROR DOWN(link-flap) state to Up state on a CE series switch
If you have more questions, you can seek help from following ways:
To iKnow To Live Chat To Google
Scroll to top