The following table lists the precautions for M-LAG networking planning on spine nodes, server leaf nodes, and DCI leaf nodes.
Table 2-1 M-LAG planning precautionsItem
|
Spine Node
|
Server Leaf Node
|
DCI Leaf Node
|
|---|
Peer-link
|
- Multi-card/subcard scenario requirement: inter-card/subcard deployment
- Single-card scenario requirement: At least two links should be deployed.
- Bandwidth requirement: When a large number of devices use the single-homed access mode, the bandwidth should be the same as the uplink bandwidth of a single device.
|
- The precautions and suggestions are the same as those for spine nodes.
- Focus on peer-link bandwidth planning when a large number of servers are connected in active/standby mode.
|
The precautions and suggestions are the same as those for spine nodes.
|
DAD
|
Deploy DAD on an independent Layer 3 link, which is deployed on the same physical link as the Layer 3 backup link of the uplink. The peer-link cannot be used as the DAD link.
|
Deploy DAD on an independent Layer 3 link. The peer-link cannot be used as the DAD link.
|
Use the underlay Layer 3 bypass link as the DAD link.
|
Uplink interface
|
- Connect to PEs in square-looped mode.
- Connect to PEs in dual-homed mode and connect to spine nodes through Layer 3 backup links.
|
Connect to spine nodes in dual-homed mode.
|
Connect to upstream devices in dual-homed mode.
|
Downlink interface
|
Connect to server leaf nodes in dual-homed mode.
|
Servers connect to server leaf nodes in active/standby or load sharing mode.
|
Connect to spine nodes in dual-homed mode. When the DCI traffic is small, the square-looped mode can be used.
|
Eth-Trunk/M-LAG ID
|
- Plan Eth-Trunk IDs in the following sequence:
- Configure the smallest Eth-Trunk ID (for example, Eth-Trunk 0) for the peer-link.
- Configure the second smallest Eth-Trunk ID for the uplink interface and the third smallest Eth-Trunk ID for the downlink interface.
- The M-LAG ID should be the same as the Eth-Trunk ID.
|
- Plan Eth-Trunk IDs in the following sequence:
- Configure the smallest Eth-Trunk ID (for example, Eth-Trunk 0) for the peer-link.
- Configure the second smallest Eth-Trunk ID for the uplink interface and the third smallest Eth-Trunk ID for the downlink interface.
- The M-LAG ID should be the same as the Eth-Trunk ID.
|
The precautions and suggestions are the same as those for server leaf nodes.
|
