Currently only CE switches support M-LAG。
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.
