· Attach singlehomed servers Server B and Server C to the M-LAG system. Server B is in the same subnet as Server A, and Server C is in a different subnet than Server A.

Establish network connections to meet the following requirements:

· Server A, Server B, and Server C have both IPv4 and IPv6 connectivity among them.

· Server A, Server B, and Server C have both IPv4 and IPv6 connectivity with Network.

· Service traffic is not interrupted when link failures occur on the M-LAG member devices.

Figure 1 Network diagram

Device	Interface	IP address	Peer device and interface
Device A	Loopback 0	3.3.3.3/32 2000::3:3:3:3/128	IP address of a loopback interface Router ID
	XGE 3/0/8	-	Server B
	XGE 3/0/5	-	Server A M-LAG group member interface
	XGE 3/0/4	32.1.1.1/24 32::1/64	Device C: XGE 3/0/4
	XGE 3/0/1	21.1.1.1/24	Device B: XGE 3/0/1 Keepalive interface
	XGE 3/0/2	-	Device B: XGE 3/0/2 Member port of the peer-link interface
	XGE 3/0/3	-	Device B: XGE 3/0/3 Member port of the peer-link interface
	VLAN 100	100.1.1.1/24 100::1/64	Dual-active VLAN interface
	VLAN 101	101.1.1.1/24 101::1/64	Used for setting up a Layer 3 link between the M-LAG member devices to forward east-west traffic or south-north failover traffic.
Device B	Loopback 0	4.4.4.4/32 2000::4:4:4:4/128	IP address of a loopback interface Router ID
	XGE 3/0/8	200.1.1.1/24 200::1/64	Server C
	XGE 3/0/5	-	Server A M-LAG group member interface
	XGE 3/0/4	33.1.1.1/24 33::1/64	Device C: XGE 3/0/5
	XGE 3/0/1	21.1.1.2/24	Device A: XGE 3/0/1 Keepalive interface
	XGE 3/0/2	-	Device A: XGE 3/0/2 Member port of the peer-link interface
	XGE 3/0/3	-	Device A: XGE 3/0/3 Member port of the peer-link interface
	VLAN 100	100.1.1.1/24 100::1/64	Dual-active VLAN interface
	VLAN 101	101.1.1.2/24 101::2/64	Used for setting up a Layer 3 link between the M-LAG member devices to forward east-west traffic or south-north failover traffic.
Device C	XGE 3/0/1	22.1.1.1/24 22::1/64	Network 1
	XGE 3/0/4	32.1.1.2/24 32::2/64	Device A: XGE 3/0/4
	XGE 3/0/5	33.1.1.2/24 33::2/64	Device B: XGE 3/0/4
Server A	-	100.1.1.11/24 100::11/64	Device A: XGE 3/0/5 Device B: XGE 3/0/5
Server B	-	100.1.1.12/24 100::12/64	Device A XGE 3/0/8
Server C	-	200.1.1.11/24 200::11/64	Device B: XGE 3/0/8
Network 1	-	22.1.1.11/24 22::11/64	Device C: XGE 3/0/1

Applicable product matrix

IMPORTANT:

In addition to running an applicable software version, you must also install the most recent patch, if any.

Device	Software version
S10500, S10500X, S7600, S7600-X, S7600E-X, S7500X, S7500E	R7625 and later
S12500G-AF (type T cards)	R7625 and later
S12500G-AF (type S cards)	R8054P04 and later
S10500X-G, S7500X-G	R7754P04 and later
S5590XP-HI-G, S6520X-EI-G, S6520XP-EI-G	R7754P04 and later
S6550XE-HI, S6525XE-HI	R8106P22 and later
S6520X-EI, S6520X-HI	F6628P11 and later
S5590-HI, S5590-EI, S6805-G, S6850-G, S6530X, S9850-G	R8307P08 and later
S5560X-HI	F6628P11 and later
S5560X-EI	F6628P11 and later

Analysis

· Configure VLAN interfaces on Device A and Device B to provide dual-active gateway services for Server A.

· Attach Server A with two links to the M-LAG system, and specify the IP address of VLAN-interface 100 as the gateway on Server A.

· Attach Server B with one link to the M-LAG system, and specify the IP address of VLAN-interface 100 as the gateway on Server B.

· Attach Server C with one link to the M-LAG system, and specify the IP address of VLAN-interface 200 as the gateway on Server C.

· Configure ECMP routes to Device C on Device A and Device B.

· Configure Device A and Device B as OSPF and OSPFv3 neighbors to each other for them to forward traffic of singlehomed servers and back up each other.

· Configure IPv4 and IPv6 dual stack.

Restrictions and guidelines

All parameters of the device are set to the factory default settings. If you have already configured the device, verify that the existing configuration does not conflict with the following settings.

Configuring the M-LAG system

Procedure summary

· Setting up the M-LAG system

· Configuring interconnect links between the M-LAG device and Server A

· Configuring Layer 3 interconnect links between the M-LAG member devices

· Configuring dual-active gateways

· Configuring the interconnect links between the M-LAG system and upstream Device C

· Configuring the interfaces facing singlehomed devices

Setting up the M-LAG system

Device A	Device B	Description	Remarks
m-lag system-mac 2-2-2	m-lag system-mac 2-2-2	Set the M-LAG system MAC address.	You must set the same M-LAG system MAC address for devices in the same M-LAG system.
m-lag system-number 1	m-lag system-number 2	Set the M-LAG system number.	You must set different M-LAG system numbers for devices in the same M-LAG system.
m-lag system-priority 123	m-lag system-priority 123	Set the M-LAG system priority.	You must set the same M-LAG system priority for devices in the same M-LAG system.
m-lag standalone enable	m-lag standalone enable	(Optional.) Enable M-LAG standalone mode.	The M-LAG member devices might both operate with the primary role to forward traffic after the M-LAG system splits. M-LAG standalone mode helps avoid traffic forwarding issues in this multi-active situation.
m-lag keepalive ip destination 21.1.1.2 source 21.1.1.1	m-lag keepalive ip destination 21.1.1.1 source 21.1.1.2	Configure the destination and source IP addresses of keepalive packets.	N/A
interface Ten-gigabitethernetE3/0/1	interface Ten-gigabitethernetE3/0/1	Enter the view of the keepalive interface.	N/A
port link-mode route	port link-mode route	Configure the keepalive interface to operate in Layer 3 mode.	N/A
ip address 21.1.1.1 24	ip address 21.1.1.2 24	Assign source IPv4 address of keepalive packets to the keepalive interface.	N/A
quit	quit	Return to system view.	N/A
m-lag mad exclude interface Ten-gigabitethernetE3/0/1	m-lag mad exclude interface Ten-gigabitethernetE3/0/1	Exclude the interface used for M-LAG keepalive detection from the shutdown action by M-LAG MAD.	N/A
interface bridge-aggregation 1	interface bridge-aggregation 1	Create the Layer 2 aggregate interface to be used as the peer-link interface and enter interface view.	N/A
link-aggregation mode dynamic	link-aggregation mode dynamic	Configure the aggregate interface to operate in dynamic mode.	N/A
quit	quit	Return to system view.	N/A
interface range Ten-gigabitethernetE 3/0/2 Ten-gigabitethernetE 3/0/3	interface range Ten-gigabitethernetE 3/0/2 Ten-gigabitethernetE 3/0/3	Enter the view of physical interfaces on the peer link.	N/A
port link-aggregation group 1	port link-aggregation group 1	Assign the physical interfaces on the peer link to the aggregation group for the peer link.	N/A
quit	quit	Return to system view.	N/A
interface bridge-aggregation 1	interface bridge-aggregation 1	Enter aggregate interface view.	N/A
port m-lag peer-link 1	port m-lag peer-link 1	Specify Bridge-Aggregation 1 as the peer-link interface.	N/A
undo mac-address static source-check enable	undo mac-address static source-check enable	Disable the static source check feature to avoid inter-peer link Layer 3 traffic forwarding failures.	N/A
quit	quit	Return to system view.	N/A

Configuring interconnect links between the M-LAG device and Server A

Device A	Device B	Description
interface bridge-aggregation 2	interface bridge-aggregation 2	Create an aggregate interface to connect to Server A.
link-aggregation mode dynamic	link-aggregation mode dynamic	Configure the aggregation group to operate in dynamic mode.
port m-lag group 1	port m-lag group 1	Assign Bridge-Aggregation 2 to M-LAG group 1.
port lacp system-priority 100	port lacp system-priority 101	Set the LACP system priority for the high-priority member port to be selected upon split brain.
quit	quit	Return to system view.
interface Ten-gigabitethernetE 3/0/5	interface Ten-gigabitethernetE 3/0/5	Enter the view of the physical interface facing Server A.
port link-aggregation group 2	port link-aggregation group 2	Assign the interface to an aggregation group.
quit	quit	Return to system view.

Configuring Layer 3 interconnect links between the M-LAG member devices

Device A	Device B	Description	Remarks
router id 3.3.3.3	router id 4.4.4.4	Configure a router ID.	N/A
ospf 1	ospf 1	Enable OSPF.	N/A
import-route direct	import-route direct	Redistribute direct routes..	N/A
area 0	area 0	Configure area 0.	N/A
quit	quit	Return to OSPF view.	N/A
quit	quit	Return to system view.	N/A
ospfv3 1	ospfv3 1	Enable OSPFv3.	N/A
router-id 3.3.3.3	router-id 4.4.4.4	Configure a router ID.	N/A
import-route direct	import-route direct	Redistribute direct routes..	N/A
area 0	area 0	Configure area 0.	N/A
quit	quit	Return to OSPFv3 view.	N/A
quit	quit	Return to system view.	N/A
interface Loopback 0	interface Loopback 0	Create a loopback interface.	N/A
ip address 3.3.3.3 255.255.255.255	ip address 4.4.4.4 255.255.255.255	Assign an IPv4 address to the loopback interface.	N/A
ospf 1 area 0.0.0.0	ospf 1 area 0.0.0.0	Enable OSPF on the loopback interface.	N/A
ipv6 address 2000::3:3:3:3/128	ipv6 address 2000::4:4:4:4/128	Assign an IPv6 address to the loopback interface.	N/A
ospfv3 1 area 0.0.0.0	ospfv3 1 area 0.0.0.0	Enable OSPFv3 on the loopback interface.	N/A
quit	quit	Return to system view.	N/A
vlan 101	vlan 101	Create VLAN 101.	N/A
quit	quit	Return to system view.	N/A
interface vlan-interface 101	interface vlan-interface 101	Create VLAN-interface 101.	Used for setting up a Layer 3 link between the M-LAG member devices to forward east-west traffic or south-north failover traffic.
ip address 101.1.1.1 255.255.255.0	ip address 101.1.1.2 255.255.255.0	Assign an IPv4 address to VLAN-interface 101.	N/A
ospf 1 area 0.0.0.0	ospf 1 area 0.0.0.0	Enable OSPF on the interface.	N/A
ipv6 address 101::1 64	ipv6 address 101::2 64	Assign an IPv6 address to VLAN-interface 101.	N/A
ospfv3 1 area 0.0.0.0	ospfv3 1 area 0.0.0.0	Enable OSPFv3 on the interface.	N/A
quit	quit	Return to system view.	N/A
m-lag mad exclude interface Vlan-interface 101	m-lag mad exclude interface Vlan-interface 101	Exclude the VLAN interface from the shutdown action by M-LAG MAD.	N/A

Configuring dual-active gateways

Device A	Device B	Description	Remarks
vlan 100	vlan 100	Create VLAN 100.	N/A
quit	quit	Return to system view.	N/A
interface bridge-aggregation 2	interface bridge-aggregation 2	Enter aggregate interface view.	N/A
port link-type trunk	port link-type trunk	Configure Bridge-Aggregation 2 as a trunk port.	N/A
port trunk permit vlan 100	port trunk permit vlan 100	Assign the interface to VLAN 100.	N/A
undo port trunk permit vlan 1	undo port trunk permit vlan 1	Remove the interface from VLAN 1.	N/A
quit	quit	Return to system view.	N/A
interface vlan-interface 100	interface vlan-interface 100	Create VLAN-interface 100.	N/A
ip address 100.1.1.1 24	ip address 100.1.1.1 24	Assign an IPv4 address to VLAN-interface 100.	The IP address is used as the IPv4 dual-active gateway.
ipv6 address 100::1 64	ipv6 address 100::1 64	Assign an IPv6 address to VLAN-interface 100.	The IP address is used as the IPv6 dual-active gateway.
mac-address 0002-2222-2222	mac-address 0002-2222-2222	Assign a MAC address to VLAN-interface 100.	N/A
quit	quit	Return to system view.	N/A
m-lag mad exclude interface Vlan-interface100	m-lag mad exclude interface Vlan-interface100	Exclude VLAN-interface 100 from the shutdown action by M-LAG MAD.	Excluded the VLAN interface of the VLAN accommodating M-LAG interfaces from the shutdown action by M-LAG MAD. This ensures correct ARP and ND entry synchronization via the VLAN interface.

Configuring the interconnect links between the M-LAG system and upstream Device C

Device A	Device B	Description
vlan 32	vlan 33	Create VLAN 33.
quit	quit	Return to system view.
interface Ten-gigabitethernetE 3/0/4	interface Ten-gigabitethernetE 3/0/4	Enter Ethernet interface view.
port access vlan 32	port access vlan 33	Assign the interface to VLAN 33.
quit	quit	Return to system view.
interface vlan-interface 32	interface vlan-interface 33	Create VLAN-interface 33.
ip address 32.1.1.1 24	ip address 33.1.1.1 24	Assign an IPv4 address to the VLAN interface.
ospf 1 area 0	ospf 1 area 0	Enable OSPF on the interface.
ipv6 address 32::1 64	ipv6 address 33::1 64	Assign an IPv6 address to the VLAN interface.
ospfv3 1 area 0	ospfv3 1 area 0	Enable OSPFv3 on the interface.
quit	quit	Return to system view.

Configuring the interfaces facing singlehomed devices

Device A	Device B	Description
-	vlan 200	Create VLAN 200.
-	quit	Return to system view.
interface ten-gigabitethernet 3/0/8	interface ten-gigabitethernet 3/0/8	Configure the interface to which Server B and Server C are singlehomed.
port access vlan 100	port access vlan 200	Assign the interface to VLAN 200.
quit	quit	Return to system view.
-	interface vlan-interface 200	Create VLAN-interface 200.
-	ip address 200.1.1.1 24	Assign an IPv4 address to the VLAN interface.
-	ipv6 address 200::1 64	Assign an IPv6 address to the VLAN interface.
-	quit	Return to system view.

Configuring upstream Device C

Procedure summary

· Configuring the interconnect links between upstream Device C and the M-LAG system

· Configuring the interconnect links between upstream Device C and Network

Configuring the interconnect links between upstream Device C and the M-LAG system

Device C	Description
undo stp global enable	Disable the spanning tree protocol globally.
vlan 32 33	Create VLANs.
interface Ten-gigabitethernetE 3/0/4	Enter Ethernet interface view.
port access vlan 32	Assign the interface facing Device A to VLAN 32.
quit	Return to system view.
interface Ten-gigabitethernetE 3/0/5	Enter Ethernet interface view.
port access vlan 33	Assign the interface facing Device B to VLAN 33.
quit	Return to system view.
router id 5.5.5.5	Configure a route ID.
ospf 1	Configure OSPF to establish IPv4 connectivity between the M-LAG member devices.
import-route direct	Redistribute direct routes..
area 0	Configure area 0.
quit	Return to OSPF view.
quit	Return to system view.
ospfv3 1	Enable OSPFv3.
router-id 5.5.5.5	Configure area 0.
import-route direct	Redistribute direct routes..
area 0	Configure area 0.
quit	Return to OSPFv3 view.
quit	Return to system view.
interface loopback 0	Create a loopback interface.
ip address 5.5.5.5 255.255.255.255	Assign an IPv4 address to the loopback interface.
ospf 1 area 0	Enable OSPF on the loopback interface.
ipv6 address 2000::5:5:5:5/128	Assign an IPv6 address to the loopback interface.
ospfv3 1 area 0	Enable OSPFv3 on the loopback interface.
quit	Return to system view.
interface vlan-interface 32	Create VLAN-interface 32.
ip address 32.1.1.2 24	Assign an IPv4 address to the VLAN interface.
ospf 1 area 0	Enable OSPF on the VLAN interface.
ipv6 address 32::2 64	Assign an IPv6 address to the VLAN interface.
ospfv3 1 area 0	Enable OSPFv3 on the VLAN interface.
quit	Return to system view.
interface vlan-interface 33	Create VLAN-interface 33.
ip address 33.1.1.2 24	Assign an IPv4 address to the VLAN interface.
ospf 1 area 0	Enable OSPF on the VLAN interface.
ipv6 address 33::2 64	Assign an IPv6 address to the VLAN interface.
ospfv3 1 area 0	Enable OSPFv3 on the VLAN interface.
quit	Return to system view.

Configuring the interconnect links between upstream Device C and Network

Device C	Description
vlan 22	Create VLAN 22.
quit	Return to system view.
interface Ten-gigabitethernetE 3/0/1	Enter Ethernet interface view.
port access vlan 22	Assign the interface facing the external network to VLAN 22.
quit	Return to system view.
interface vlan-interface 22	Create VLAN-interface 22.
ip address 22.1.1.1 24	Assign an IPv4 address to the VLAN interface.
ipv6 address 22::1 64	Assign an IPv6 address to the VLAN interface.
quit	Return to system view.

Traffic forwarding models

Overlay traffic characteristics

The forwarding model matrix provides the following characteristics of overlay traffic:

· No.—Traffic number in the O-X-XXX format:

¡ O—Overlay traffic.

¡ X—Protocol number, which can be 4 (IPv4) or 6 (IPv6).

¡ XXX—Traffic sequence number starting from 001.

· Traffic type—Type of overlay traffic, which can be IPv4 known unicast or IPv6 known unicast.

· Direction—Direction of overlay traffic. The value is south-north or east-west.

· Forwarding path—Nodes that overlay traffic traverses.

· Traffic simulation—Traffic simulation method. Typically, a tester is used to simulate server traffic.

· Load—Traffic size, which can be light (less than 1000 flows) and heavy (more than 1000 flows).

· Traffic direction to firewalls/LB—Configuration used to direct traffic to firewalls and load balancers, such as PBR, M-LAG, VRRP, static routes.

Forwarding models

No.	Traffic type	Direction	Forwarding path	Traffic simulation	Load	Traffic direction to firewalls/LB	Remarks
O-4-001	IPv4 known unicast	South-north	Server A > Device A&B > Device C > Network 1	Tester	Light	N/A	Traffic fails over via the Layer 3 link between the M-LAG member devices upon failure of an uplink interface.
O-4-002	IPv4 known unicast	South-north	Server B > Device A > Device C > Network 1	Tester	Light	N/A
O-4-003	IPv4 known unicast	South-north	Server C > Device B > Device C > Network 1	Tester	Light	N/A
O-4-004	IPv4 known unicast	East-west	Server A > Device A&B > Device A > Server B	Tester	Light	N/A	N/A
O-4-005	IPv4 known unicast	East-west	Server A > Device A&B > Device B > Server C	Tester	Light	N/A	N/A
O-4-006	IPv4 known unicast	East-west	Server B > Device A > Device B > Server C	Tester	Light	N/A	N/A
O-6-001	IPv6 known unicast	South-north	Server A > Device A&B > Device C > Network 1	Tester	Light	N/A	Traffic fails over via the Layer 3 link between the M-LAG member devices upon failure of an uplink interface.
O-6-002	IPv6 known unicast	South-north	Server B > Device A&B > Device C >	Tester	Light	N/A
O-6-003	IPv6 known unicast	South-north	Server C > Device A&B > Device C >	Tester	Light	N/A
O-6-004	IPv6 known unicast	East-west	Server A > Device A&B > Device A > Server B	Tester	Light	N/A	N/A
O-6-005	IPv6 known unicast	East-west	Server A > Device A&B > Device B > Server C	Tester	Light	N/A	N/A
O-6-006	IPv6 known unicast	East-west	Server B > Device A > Device B > Server C	Tester	Light	N/A	N/A

Testing network convergence upon single points of failure

Table 1 Network convergence upon single points of failure

Device	Failure type	Traffic interruption time	Remarks
Device A	Single point of failure on M-LAG member links	≤ 400 ms	N/A
	Single point of failure restored on M-LAG member links	≤ 100 ms	N/A
	Single point of failure on uplinks	≤ 400 ms	N/A
	Single point of failure restored on uplinks	≤ 100 ms	N/A
	Peer link failure	≤ 400 ms	Only M-LAG interfaces are paid attention. Availability of interfaces facing single-homed devices are not ensured.
	Peer link failure restored	≤ 400 ms	Only M-LAG interfaces are paid attention. Availability of interfaces facing single-homed devices are not ensured.
	Keepalive link failure	0 ms	N/A
	Keepalive link failure restored	0 ms	N/A
	Keepalive link and peer link failure	≤ 4000 ms	Only M-LAG interfaces are paid attention. Availability of interfaces facing single-homed devices are not ensured.
	Keepalive link and peer link restored	≤ 4000 ms	Only M-LAG interfaces are paid attention. Availability of interfaces facing single-homed devices are not ensured.
	M-LAG member device restart	≤ 100 ms	Only M-LAG interfaces are paid attention. Availability of interfaces facing single-homed devices are not ensured.
	M-LAG member device restored after restart	≤ 100 ms	Only M-LAG interfaces are paid attention. Availability of interfaces facing single-homed devices are not ensured.
	Switching fabric module failure	≤ 100 ms	N/A
	Switching fabric module failure restored	≤ 100 ms	N/A

Verifying the configuration

Verification commands

Device A	Device B	Description
display m-lag summary	display m-lag summary	Displays summary information about the peer-link interface and M-LAG interfaces.
display m-lag keepalive	display m-lag keepalive	Displays packet statistics about the M-LAG keepalive link.
display m-lag role	display m-lag role	Displays M-LAG role information.
display m-lag summary	display m-lag summary	Displays summary information about the peer-link interface and M-LAG interfaces.
display m-lag verbose	display m-lag verbose	Displays detailed information about the peer-link interface and M-LAG interfaces.

Procedure

Verifying that the M-LAG system is operating correctly

# Display M-LAG keepalive packet statistics and verify that the keepalive packet receive and send status is successful.

[DeviceA]disp m-lag keepalive

Neighbor keepalive link status (cause): Up

Neighbor is alive for: 244023 s 640 ms

Keepalive packet transmission status:

Sent: Successful

Received: Successful

Last received keepalive packet information:

Source IP address: 21.1.1.2

Time: 2020/05/12 10:21:12

Action: Accept

M-LAG keepalive parameters

Destination IP address: 21.1.1.2

Source IP address: 21.1.1.1

Keepalive UDP port : 6400

Keepalive VPN name : N/A

Keepalive interval : 1000 ms

Keepalive timeout : 5 sec

Keepalive hold time: 3 sec

[DeviceA]

[DeviceB]display m-lag keepalive

Neighbor keepalive link status (cause): Up

Neighbor is alive for: 244177 s 621 ms

Keepalive packet transmission status:

Sent: Successful

Received: Successful

Last received keepalive packet information:

Source IP address: 21.1.1.1

Time: 2020/05/11 10:23:47

Action: Accept

M-LAG keepalive parameters

Destination IP address: 21.1.1.1

Source IP address: 21.1.1.2

Keepalive UDP port : 6400

Keepalive VPN name : N/A

Keepalive interval : 1000 ms

Keepalive timeout : 5 sec

Keepalive hold time: 3 sec

# Display M-LAG role information.

[DeviceA]display m-lag role

Effective role information

Factors Local Peer

Effective role Primary Secondary

Initial role None None

MAD DOWN state Yes Yes

Health level 0 0

Role priority 32768 32768

Bridge MAC b0f9-63b6-4c00 b0f9-63b6-4c09

Effective role trigger: IPL calculation

Effective role reason: Bridge MAC

Configured role information

Factors Local Peer

Configured role Primary Secondary

Role priority 32768 32768

Bridge MAC b0f9-63b6-4c00 b0f9-63b6-4c09

[DeviceA]

[DeviceB]display m-lag role

Effective role information

Factors Local Peer

Effective role Secondary Primary

Initial role None None

MAD DOWN state Yes Yes

Health level 0 0

Role priority 32768 32768

Bridge MAC b0f9-63b6-4c09 b0f9-63b6-4c00

Effective role trigger: IPL calculation

Effective role reason: Bridge MAC

Configured role information

Factors Local Peer

Configured role Secondary Primary

Role priority 32768 32768

Bridge MAC b0f9-63b6-4c09 b0f9-63b6-4c00

# Display detailed information about the peer-link interface and M-LAG interfaces.

[DeviceA]display m-lag summary

Flags: A -- Aggregate interface down, B -- No peer M-LAG interface configured

C -- Configuration consistency check failed

PeerLink: BAGG1

PeerLink state (cause): UP

Keepalive link state (cause): UP

M-LAG interface information

M-LAG interface M-LAG group Local state (cause) Peer state Remaining down time(s)

BAGG2 1 UP UP -

[DeviceA]

[DeviceA]display m-lag verbose

Flags: A -- Home_Gateway, B -- Neighbor_Gateway, C -- Other_Gateway,

D -- PeerLink_Activity, E -- DRCP_Timeout, F -- Gateway_Sync,

G -- Port_Sync, H -- Expired

Peer-link interface/Peer-link interface ID: BAGG1/1

State: UP

Cause: -

Local DRCP flags/Peer DRCP flags: ABDFG/ABDFG

Local Selected ports (index): TE3/0/2 (2), TE3/0/3 (3)

Peer Selected ports indexes: 99, 100

Peer-link interface/Peer-link interface: BAGG2/1

Local M-LAG interface state: UP

Peer M-LAG interface state: UP

M-LAG group state: UP

Local M-LAG interface down cause: -

Remaining m-lag DOWN time: -

Local M-LAG interface LACP MAC: Config=N/A, Effective=0002-0002-0002

Peer M-LAG interface LACP MAC: Config=N/A, Effective=0002-0002-0002

Local M-LAG interface LACP priority: Config=32768, Effective=123

Peer M-LAG interface LACP priority: Config=32768, Effective=123

Local DRCP flags/Peer DRCP flags: ABDFG/ABDFG

Local Selected ports (index): TE3/0/5 (5)

Peer Selected ports indexes: 102

[DeviceB]display m-lag summary

Flags: A -- Aggregate interface down, B -- No peer M-LAG interface configured

C -- Configuration consistency check failed

Peer-link interface: BAGG1

Peer-link interface state (cause): UP

Keepalive link state (cause): UP

M-LAG interface information

M-LAG IF M-LAG group Local state (cause) Peer state Remaining down time(s)

BAGG2 1 UP UP -

[DeviceB]

[DeviceB]display m-lag verbose

Flags: A -- Home_Gateway, B -- Neighbor_Gateway, C -- Other_Gateway,

D -- PeerLink_Activity, E -- DRCP_Timeout, F -- Gateway_Sync,

G -- Port_Sync, H -- Expired

PeerLink interface/PeerLink interface ID: BAGG1/1

State: UP

Cause: -

Local DRCP flags/Peer DRCP flags: ABDFG/ABDFG

Local Selected ports (index): TE3/0/2 (99), TE3/0/3 (100)

Peer Selected ports indexes: 2, 3

PeerLink interface/PeerLink interface group ID: BAGG2/1

Local M-LAG interface state: UP

Peer M-LAG interface state: UP

M-LAG group state: UP

Local M-LAG interface down cause: -

Remaining M-LAG DOWN time: -

Local M-LAG interface LACP MAC: Config=N/A, Effective=0002-0002-0002

Peer M-LAG interface LACP MAC: Config=N/A, Effective=0002-0002-0002

Local M-LAG interface LACP priority: Config=32768, Effective=123

Peer M-LAG interface LACP priority: Config=32768, Effective=123

Local DRCP flags/Peer DRCP flags: ABDFG/ABDFG

Local Selected ports (index): TE3/0/5 (102)

Peer Selected ports indexes: 5

Verifying the routing protocols

# Display the OSPF neighbors of Device A.

[DeviceA]display ospf peer

OSPF Process 1 with Router ID 3.3.3.3

Neighbor Brief Information

Area: 0.0.0.0

Router ID Address Pri Dead-Time State Interface

4.4.4.4 101.1.1.2 1 32 Full/BDR Vlan101

5.5.5.5 32.1.1.2 1 38 Full/DR Vlan32

# Display the OSPFv3 neighbors of Device A.

[DeviceA]display ospfv3 peer

OSPFv3 Process 1 with Router ID 3.3.3.3

Area: 0.0.0.0

-------------------------------------------------------------------------

Router ID Pri State Dead-Time InstID Interface

4.4.4.4 1 Full/BDR 00:00:39 0 Vlan101

5.5.5.5 1 Full/BDR 00:00:40 0 Vlan32

# Display the OSPF neighbors of Device B.

[DeviceB]display ospf peer

OSPF Process 1 with Router ID 4.4.4.4

Neighbor Brief Information

Area: 0.0.0.0

Router ID Address Pri Dead-Time State Interface

3.3.3.3 101.1.1.1 1 33 Full/DR Vlan101

5.5.5.5 33.1.1.2 1 31 Full/DR Vlan33

# Display the OSPFv3 neighbors of Device B.

[DeviceB]display ospfv3 peer

OSPFv3 Process 1 with Router ID 4.4.4.4

Area: 0.0.0.0

-------------------------------------------------------------------------

Router ID Pri State Dead-Time InstID Interface

3.3.3.3 1 Full/DR 00:00:36 0 Vlan101

5.5.5.5 1 Full/BDR 00:00:39 0 Vlan33

# Display the OSPF neighbors of Device C.

[DeviceC]display ospf peer

OSPF Process 1 with Router ID 5.5.5.5

Neighbor Brief Information

Area: 0.0.0.0

Router ID Address Pri Dead-Time State Interface

3.3.3.3 32.1.1.1 1 35 Full/BDR Vlan32

4.4.4.4 33.1.1.1 1 35 Full/BDR Vlan33

# Display the OSPFv3 neighbors of Device C.

[DeviceC]display ospfv3 peer

OSPFv3 Process 1 with Router ID 5.5.5.5

Area: 0.0.0.0

-------------------------------------------------------------------------

Router ID Pri State Dead-Time InstID Interface

3.3.3.3 1 Full/DR 00:00:38 0 Vlan32

4.4.4.4 1 Full/DR 00:00:35 0 Vlan33

Verifying connectivity among the servers and between the servers and Network

Verify that Server A and Server B have IPv4 and IPv6 connectivity between them.

Verify that Server A and Server C have IPv4 and IPv6 connectivity between them.

Verify that Server A, Server B, and Server C have IPv4 and IPv6 connectivity with Network.

Verifying connectivity among the servers and between the servers and Network in case of downlink failure on Device A or Device B

Verify that Server A, Server B, and Server C have connectivity among them and with Network after the Device A is disconnected from Server A. Transient traffic loss occurs during traffic failover.

Verify that Server A, Server B, and Server C have connectivity among them and with Network after the Device B is disconnected from Server A. Transient traffic loss occurs during traffic failover.

Verifying connectivity among the servers and between the servers and Network in case of uplink failure on Device A or Device B

Verify that Server A, Server B, and Server C have connectivity among them and with Network after the Device A is disconnected from Device C. Transient traffic loss occurs during traffic failover.

Verify that Server A, Server B, and Server C have connectivity among them and with Network after the Device B is disconnected from Device C. Transient traffic loss occurs during traffic failover.

Upgrading the devices

Checking the environment

Execute the commands in "Verifying the configuration" and the following commands to verify that the devices are available for an upgrade.

Device A	Device B	Description
display device	display device	Displays device information.
display boot-loader	display boot-loader	Displays current software images and startup software images.
display version	display version	Displays system version information.

Upgrading the devices

Before you upgrade the device software, perform the following tasks:

1. Execute the display version command to view the current BootWare version and startup software version.

2. Use the release notes for the upgrade software version to evaluate the upgrade impact on your network and verify the following items:

¡ Software and hardware compatibility.

¡ Version and size of the upgrade software.

¡ Compatibility of the upgrade software with the current BootWare image and startup software image.

3. Use the release notes to verify whether the upgrade software images require a license. If licenses are required, check the system for availability of valid licenses. If no license exists on the device, first install a license. If you do not install a license, the software package will fail to be installed.

4. Use the dir command to verify that the device has sufficient storage space for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete command. Make sure that all MPUs in the system have sufficient storage space.

5. After Device A and Device B form an M-LAG system, perform the following tasks:

a. Check the LLDP neighbors of Device A to obtain the LLDP state information of all interfaces on Device A.

b. Manually shut down all interfaces connecting to the other devices (except the peer-link and keepalive interfaces) on Device A.

c. Switch all incoming and outgoing traffic of Device A to Device B.

6. Save the configuration on Device A, and use FTP or TFTP to transfer the upgrade image file to the root directory of a file system. Upgrade Device A and reboot it.

7. When Device A is being rebooted, manually shut down the interfaces connecting Device B to Device A, typically the peer-link and keepalive interfaces.

8. After Device A is rebooted, bring up the interfaces that have been shut down on Device B. Wait for M-LAG to restore between Device A and Device B.

9. After Device A and Device B form a new M-LAG system again, bring up the interfaces connecting to the other devices. Wait for the traffic to restore.

For the detailed upgrade guide, see H3C Switches M-LAG System Upgrade Guide.

No special requirements are imposed on the upgrade method. Upgrade the devices based on the environment.

Estimating upgrade downtime

See "Testing network convergence upon single points of failure." The upgrade downtime of each device contains the traffic downtime for restart of one M-LAG member device and recovery from M-LAG member device restart.

Verifying the upgrade result

Execute the commands in "Verifying the configuration" and the following commands to verify that the devices are upgraded successfully.

Device A	Device B	Description
display device	display device	Displays device information.
display boot-loader	display boot-loader	Displays current software images and startup software images.
display version	display version	Displays system version information.

Expanding the network

Checking the environment

Execute the commands in "Verifying the configuration" and the following commands to verify that the devices are available for an expansion.

Device A	Device B	Description
display device	display device	Displays device information.
display boot-loader	display boot-loader	Displays current software images and startup software images.
display version	display version	Displays system version information.

Adding a device to the network

1. Disconnect the device from network management systems.

2. Upgrade the software of the device as needed.

3. Preconfigure the device.

4. Connect the device to network management systems.

Estimating expansion downtime

N/A

Verifying the expansion result

Execute the following commands to verify that the device is added successfully.

Device A	Device B	Description
display device	display device	Displays device information.
display boot-loader	display boot-loader	Displays current software images and startup software images.
display version	display version	Displays system version information.

Replacing hardware

Replacing a service module

Checking the environment

Execute the commands in "Verifying the configuration" and the following commands to verify that the device is available for a replacement.

Device A	Device B	Description
display device	display device	Displays device information.
display boot-loader	display boot-loader	Displays current software images and startup software images.
display version	display version	Displays system version information.

Replacing hardware

Before you replace a service module, make sure the service and management traffic has switched over to other service modules that are operating correctly.

Replace the service modules online while the system is operating or power off the system before you do the replacement, depending on the evaluation of the conditions.

Estimating replacement downtime

See "Testing network convergence upon single points of failure." The replacement downtime of each device contains the downtime for single point of failure on M-LAG member links, single point of failure on uplinks, recovery from single point of failure on M-LAG member links, and recovery from single point of failure on uplinks.

Verifying the replacement result

See the commands used for environment check before the replacement.

Replacing a switching fabric module

Checking the environment

Execute the commands in "Verifying the configuration" and the following commands to verify that the device is available for a replacement.

Device A	Device B	Description
display device	display device	Displays device information.
display boot-loader	display boot-loader	Displays current software images and startup software images.
display version	display version	Displays system version information.

Replacing hardware

Replace the switching fabric modules online while the system is operating or power off the system before you do the replacement, depending on the evaluation of the conditions.

Estimating replacement downtime

See "Testing network convergence upon single points of failure." The replacement downtime of each device contains the downtime for switching fabric module failure and recovery from switching fabric module failure.

Verifying the replacement result

See the commands used for environment check before the replacement.

H3C Campus Switches M-LAG Configuration Guide-6W101

Example: Configuring dual-active VLAN gateways (campus)

Analysis

Setting up the M-LAG system

Configuring Layer 3 interconnect links between the M-LAG member devices

Forwarding models

Verifying that the M-LAG system is operating correctly

Verifying the routing protocols

Verifying connectivity among the servers and between the servers and Network

Verifying connectivity among the servers and between the servers and Network in case of downlink failure on Device A or Device B

Verifying connectivity among the servers and between the servers and Network in case of uplink failure on Device A or Device B

Upgrading the devices

Checking the environment

Adding a device to the network

Replacing hardware

Estimating replacement downtime

Verifying the replacement result

Replacing hardware

Estimating replacement downtime

Verifying the replacement result

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us