Perform reliability planning and configurations for server leaf nodes in M-LAG networking. For details, see Figure 2-4 and Table 2-4.
Figure 2-4 Common fault points of server leaf nodes![]()
Table 2-4 Impact analysis of common faults of server leaf nodes and recommended deployment solutionsNo.
|
Fault Scenario
|
Impact Analysis
|
Recommended Deployment Solution
|
|---|
1
|
Server leaf node
|
Device fault
|
- When Spine1 restarts, service traffic is quickly switched to Spine2.
- After Spine1 is restarted and re-connects to the network, M-LAG member interfaces go Up after a default delay of 240s. Peer-link interfaces go Up first and synchronize MAC address entries. After the uplink and downlink interfaces go Up, all the interfaces update the entries at the same time and switch back traffic.
|
- Configure M-LAG member interfaces to go Up after a delay of 240s and at an interval of 10s so that the interfaces go Up one by one and synchronize entries separately, improving convergence performance.
- Configure the peer-link interfaces to use Eth-Trunk 0 and the uplink interfaces to use Eth-Trunk 1, and configure the downlink interfaces to use an Eth-Trunk ID greater than 1 to allow the uplink interfaces to go Up first.
|
Card fault
|
When all the uplinks or downlinks go Down due to a card fault, traffic is forwarded through the peer-link. During this process, MAC address entries on the peer-link interfaces are cleared, and the interfaces need to learn MAC address entries again.
|
When multiple cards are installed and there are multiple links, deploy both uplinks and downlinks on different cards.
|
2
|
Link fault between Server Leaf1 and Spine1
|
- When the link between Server Leaf1 and Spine1 fails, traffic is switched to Spine2.
- When the links between Server Leaf1 and both spine nodes fail, traffic is forwarded through the peer-link.
|
-
|
3
|
Link fault between Server Leaf1 and Server
|
When the link between Server Leaf1 and Server fails, traffic from the spine nodes is forwarded through the peer-link, and traffic from Server is sent to Server Leaf2.
|
-
|
4
|
DAD link fault
|
The DAD link is used to determine whether the peer device or peer interface is faulty when a peer-link fails. In normal cases, the DAD link between the server leaf nodes does not carry traffic.
|
Configure the interfaces on the DAD link as reserved interfaces.
|
5
|
Peer-link down (all member links are faulty)
|
- If a peer-link fails and is detected by the DAD link, the uplink and downlink interfaces of the backup server leaf node in the DFS group enter the Error-Down state, and traffic is quickly switched to the other device in the group.
- After the peer-link fault is rectified, all Error-Down interfaces go Up after a delay of 240s. After the interfaces go Up, traffic is quickly switched back.
|
- Deploy the peer-link on different cards to improve reliability and reduce the occurrence of peer-link faults.
- When multiple cards are installed on the switch, at least one peer-link member interface should be deployed on a card different from that for deploying the DAD link.
|
