Single-level M-LAG
A server is often connected to a network through link aggregation. If the device connected to the server fails, services are interrupted. To prevent this problem, a server can connect to a network through M-LAG. That is, deploy M-LAG between SW1 and SW2 and connect the server to SW1 and SW2. SW1 and SW2 load balance traffic. When one device fails, traffic can be rapidly switched to the other device to ensure nonstop service transmission.
The virtual ip will be work as the gateway of the server.
Single-level M-LAG + VRRP configuration example （CE68 as example）
SW1:
stp mode rstp
stp v-stp enable
#
ip vpn-instance management
ipv4-family
route-distinguisher 100:1
vpn-target 111:1 both
#
interface Meth 0/0/0
ip binding vpn-instance management
ip address x.x.x.x x
#
dfs-group 1
source ip x.x.x.x //ip of the meth0/0/0
priority 150
#
interface eth-trunk 1 //connect to SW2
trunkport 10ge x/0/a to x/0/b
mode lacp-static
peer-link 1
#
vlan batch x //service vlan
#
interface eth-trunk 2 //connect to server
mode lacp-static
port link-type trunk
port trunk allow-pass vlan x
trunkport 10ge x/0/x
dfs-group 1 m-lag 1
#
interface vlanif x
ip address x.x.x.2 x
vrrp vrid 1 virtual-ip x.x.x.1
#
commit
SW2:
stp v-stp enable
#
ip vpn-instance management
ipv4-family
route-distinguisher 100:1
vpn-target 111:1 both
#
interface Meth 0/0/0
ip binding vpn-instance management
ip address x.x.x.x x
#
dfs-group 1
source ip x.x.x.x //ip of meth0/0/0
priority 120
#
interface eth-trunk 1 //connect to SW1
trunkport 10ge x/0/a to x/0/b
mode lacp-static
peer-link 1
#
vlan batch x //service vlan
#
interface eth-trunk 2
mode lacp-static
port link-type trunk
port trunk allow-pass vlan x
trunkport 10ge x/0/x
dfs-group 1 m-lag 1
#
interface vlanif x
ip address x.x.x.3 x
vrrp vrid 1 virtual-ip x.x.x.1
#
commit
