Recommended Device Models and Versions
Table 2-7 lists the recommended device models and versions for M-LAG networking.
Device Role |
Usage Scenario |
Recommended Device Model |
Recommended Version |
|---|---|---|---|
Spine |
Medium- and large-scale network |
CE12800 |
V200R005C10 |
CE16800 |
V200R019C10 |
||
Small-scale network |
CE8861 |
V200R005C10 |
|
Server leaf |
GE access |
CE5855 (10GE/40GE uplink) |
V200R005C10 |
10GE access |
CE6857 (40GE/100GE uplink) |
V200R005C10 |
|
CE6881 (40GE/100GE uplink) |
V200R019C10 |
||
25GE access |
CE6865 (40GE/100GE uplink) |
V200R005C10 |
|
CE6863 (40GE/100GE uplink) |
V200R019C10 |
||
40GE access |
CE8861 (40GE/100GE uplink) |
V200R005C10 |
|
100GE access |
CE8861 (100GE uplink) |
V200R005C10 |
|
DCI leaf |
Small-scale DCI interconnection |
Same as that for server leaf nodes (excluding CE5855) |
Same as that for server leaf nodes (excluding CE5855) |
Large-scale DCI interconnection |
Same as that for spine nodes |
Same as that for spine nodes |
- M-LAG interfaces do not support dynamic routing protocols. For example, OSPF, Intermediate System to Intermediate System (IS-IS), and BGP cannot be used to establish neighbor relationships between the active-active gateways on the spine nodes and the servers, or between the gateways and the firewalls and LBs that are dual-homed through Eth-Trunk interfaces.
- You are not advised to use VSs to deploy M-LAG, because convergence is slow when a VS is reset or a peer-link fails.
- The two devices that set up an M-LAG cannot be configured with DHCP snooping.
- To enable the DHCP relay function, the function must be configured on both devices that set up an M-LAG.
- You are advised to deploy the DHCP server and NTP server on dedicated servers instead of on switches, because switches have limited CPU computing performance and high protocol running pressure.
