Using MLAG in Dell Networks v1.3

Using MLAG in Dell Networks
A deployment guide for Dell Networking switches (version 1.3)

Dell Engineering
February 2015
January 2014
A Dell Deployment and Configuration Guide
Revisions
Date
Description
Author
February 2015
1.3 contains full-mesh support with VLT, new method to singlehome devices to one Peer, and improvements on show
reporting from the secondary Peer.
Victor Teeter
August 2014
1.2 clarifies native VLAN assignment on the Peer-Link; solutions

for single-homing a Partner device to one Peer.
March 2014
1.1 includes changes to full-mesh support with VLT, limitation

of Partner switches, and added clarification of ports that can be
used in Peer-Links.
January 2014
1.0 Initial Release.
2015 Dell Inc., All rights reserved.

Except as stated below, no part of this document may be reproduced, distributed or transmitted in any form or by any
means, without express permission of Dell.
You may distribute this document within your company or organization only, without alteration of its contents.
THIS DOCUMENT IS PROVIDED AS-IS, AND WITHOUT ANY WARRANTY, EXPRESS OR IMPLIED. IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE SPECIFICALLY DISCLAIMED.
PRODUCT WARRANTIES APPLICABLE TO THE DELL PRODUCTS DESCRIBED IN THIS DOCUMENT MAY BE FOUND
AT: http://www.dell.com/learn/us/en/19/terms-of-sale-commercial-and-public-sector Performance of network
reference architectures discussed in this document may vary with differing deployment conditions, network loads, and
the like. Third party products may be included in reference architectures for the convenience of the reader. Inclusion
of such third party products does not necessarily constitute Dells recommendation of those products. Please consult
your Dell representative for additional information.
Trademarks used in this text:
Dell, the Dell logo, Dell Precision ,OptiPlex, Latitude, PowerEdge, PowerVault, PowerConnect,
OpenManage, and Force10 are trademarks of Dell Inc. Other Dell trademarks may be used in this document.
Cisco Nexus, Cisco MDS, Cisco NX-0S, and other Cisco Catalyst are registered trademarks of Cisco System Inc.
Microsoft, Windows, Windows Server, Internet Explorer, MS-DOS, Windows Vista and Active Directory are
either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red
Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and/or other
countries. Novell and SUSE are registered trademarks of Novell Inc. in the United States and other countries.
VMware, Virtual SMP, vMotion, vCenter and vSphere are registered trademarks or trademarks of VMware, Inc.
in the United States or other countries. IBM is a registered trademark of International Business Machines
Corporation. Broadcom and NetXtreme are registered trademarks of Broadcom Corporation. Qlogic is a registered
trademark of QLogic Corporation. Other trademarks and trade names may be used in this document to refer to either
the entities claiming the marks and/or names or their products and are the property of their respective owners. Dell
disclaims proprietary interest in the marks and names of others.
Using MLAG in Dell Networks v 1.3
Contents
1 Introduction.........................................................................................................................5
2 Caveats for Enabling MLAG ............................................................................................. 6
3 Supported Topologies ...................................................................................................... 8
4 Single-Tier Example .......................................................................................................... 9
5 Two-Tier Example ............................................................................................................13
6 Connecting Single-homed Partners ........................................................................... 19
7 MLAG with VLT ................................................................................................................ 22
8 Additional Resources .......................................................................................................31
Appendix ................................................................................................................................ 32
Support and Feedback ........................................................................................................ 33
About Dell .............................................................................................................................. 33
Executive Summary
Multi-switch Link Aggregation or MLAG is a feature that allows two Dell Networking switches to act as a
single switch, providing multiple paths across the network and offering benefits such as:
Failover in cases of failed cables or switches

Increased bandwidth of up to double the bandwidth of a single switch
Elimination of port blocking and reconvergence delays of spanning tree
An MLAG domain is created by connecting a Dell Networking switch to another Dell Networking switch
through Peer-Link ports to create MLAG Peers (the two connected switches). Other switches directly
connected to the MLAG Peers are unaware that they are connecting to two switches, which appear as a
single switch on the network.
All links in the MLAG can carry data traffic across many physically diverse topologies. In the case of a link
or switch failure, traffic continues to flow with minimal disruption. MLAG optimizes availability and
bandwidth between attached devices in Dells Datacenter and Campus networking solutions.
The following Dell Networking N-series switches support MLAG and may be used in building the
configurations in this guide:
N2024
N3024
N4032
N2024P
N3024P
N4032F
N2048
N3024F
N4064
N2048P
N3048
N4064F
N3048P
Note: Dell N15xx Series switches do not support MLAG.
Introduction
MLAGs provide an active-active split aggregation deployment across two switches acting as one,
creating a more resilient network with higher bandwidth capabilities. This guide discusses MLAGs,
how and when they are used, caveats to look out for, and instructions on how to implement MLAG
into your network.
Figure 1 shows two very basic examples of MLAG domains. In both examples, Peer switches are linked
together with a special LAG (one or more cables as denoted by red lines in the pictures below), called a
Peer-Link. Any non-management port on the switch can be used in the Peer-Link. With the Peer-Link
configured, the two switches appear as a single switch to Partner switches upstream and downstream.
Each Partner switch contains MLAGs that are simply LAGs (Link Aggregation Groups) whose cables are
split between the two Peers. Primary and secondary Peer roles are automatically assigned by the switch
firmware when MLAG is enabled.
Simple L2 MLAG
MLAG domain
Secondary MLAG peer
Primary MLAG peer
Peer-Link
MLAG
MLAG domain
appears as a single
logical switch to
partner switches on
the network
Partner Switch
L3 MLAG with mulitple

partner switches
MLAG domain
Secondary MLAG peer
Primary MLAG peer

Peer-Link
Partner Switch
MLAG
MLAG
Two examples of a single-tier MLAG topology
Partner Switch
Caveats for Enabling MLAG

Here are a few requirements when implementing MLAGs:
Same series switch models are required to create MLAG Peers. This means any N2000 Series can
only be peered with another N2000 Series, an N3000 Series with another N3000 Series, and an
N4000 Series with another N4000 Series.
Peer devices must use the same expansion module type if ports from the expansion module are to
be part of the MLAG interface.
Neither of the two switches used as MLAG Peers may be stacked with other switches.
See the switch User Guide for additional information.
Spanning Tree
Examples shown in this paper are running Spanning Tree protocol RSTP. MLAG supports MSTP as well but
does not support RPVST. Be sure all devices have the appropriate configuration regarding the spanning
tree protocol used.
Consistency of MLAG Peers

As mentioned above, the two switches used as MLAG Peers must be of the same switch series, along with
any expansion modules that may be used in the MLAG Peer-Link setup. There are also six areas in the
software configuration that must be given special attention to ensure they contain identical information
prior to enabling the MLAG. These areas are reflected in Figure 2.
MLAG peer
peer
link
Link Aggregation
=
=
=
=
=
=
Spanning Tree
MLAG Port-channels
Interfaces
VLANs
Firmware
Consistent MLAG Peer configurations
MLAG peer
Link Aggregation
Spanning Tree
MLAG Port-channels
Interfaces
VLANs
Firmware
When changing settings in any of the areas listed below in Table 1, it is required that the settings be
modified on both MLAG Peer switches. Enable MLAG only after configuring the settings on both Peer
switches. Failure to make these areas identical may cause sporadic traffic issues on the network which are
difficult to troubleshoot.
It is recommended that MLAG be temporarily disabled when making changes to these settings.
Caution: Failure to make these settings identical on both Peers may cause sporadic traffic issues on the
network which can be difficult to troubleshoot.
Note: Be sure to schedule down time if making changes that may impact traffic or cause data loss.
Option category
Settings that need to match on both MLAG Peers
Link Aggregation
Hashing mode
Minimum links
Static/dynamic LAG
LACP parameters
o Actor parameters
o Admin key
o Collector max-delay
o Partner parameters
Bpdufilter
Bpduflood
Auto-edge
TCN-guard
Cost
Edgeport
Root guard
Loop guard
STP Version
STP MST VLAN configuration
STP MST instance configuration (instance ID,
port priority, port cost/mode)
Port-channel mode
Link speed
Duplex mode
MTU
Bandwidth
VLAN configuration
PFC configuration
CoS queue assignments
MLAG VLANs must be configured on both
MLAG Peers, and connect to two Partner LAGs.
Both Peers require the same firmware version
to operate correctly.
FDB entry aging timers
Static MAC entries
ACL configuration
Spanning Tree
1.
MLAG Port-channels
Interfaces
VLANs
Firmware
Misc.
Table 1
Settings required to match between MLAG Peers
Supported Topologies
MLAG topologies offer several options. They can be a single layer (only one pair of MLAG Peer switches) or
two layers (two pair of MLAG Peer switches). The Peer-Link between Peers can have anywhere from 1 to 8
active interfaces to create the link. With these and other variables, there are dozens of ways to setup an
MLAG. 0 lists all supported topology options.
Topological parameter
Supported options
# of MLAG domains per switch

# of Peer switches per MLAG domain
# of interfaces per MLAG
# of interfaces per Peer-Link
# of MLAGs connecting to MLAG domain
# of layers
1
2
2 to 8
1 to 8
Limited only by number of ports available
1 or 2
Table 2
Parameters for an MLAG topology
Figure 3 shows just a few examples of MLAG topologies that can be built using the MLAG feature. The red
lines show the Peer-Links between the primary and secondary Peer switches. The blue line in the bottom
diagram shows compatibility with VLT in a 2-layer topology. VLT is a technology similar to MLAG that is
used with certain Dell switches like the S4810. See the User Guide for the S4810 and other Dell switches
that use VLT for guidance on implementing a VLT.
3 partner switches
1 partner switch
full mesh
2 partner switches
SYS MASTER
FAN PSU
Force10 S4810P
RS-232
52
10
12
14
16
18
20
22
24
26
28
30
32
34
36
SFP+
38
40
42
44
46
48
QSFP+
60
56
LNK
ETHERNET
ACT
VLTi
SYS MASTER
FAN PSU
Force10 S4810P
RS-232
52
10
12
14
16
18
20
22
24
SFP+
26
28
30
32
34
36
38
40
42
44
46
48
QSFP+
60
56
LNK
ETHERNET
ACT
MLAG and VLT

full mesh
Examples of MLAG topologies
Single-Tier Example
Figure 4 shows the configuration of the two MLAG Peers with two MLAG Partners. The default spanning
tree configuration is used and spanning tree is disabled on the Peer-Link.
Primary MLAG peer
(1/0/1)
Peer-Link
(48)
N3048
Partner Switch A
(47)
(11)
Secondary MLAG peer
(12)
N3048
MLAG
MLAG
(27)
(29)
(28)
(30)
(1/0/1)
Partner Switch B
Single-tier MLAG topology

To configure the two MLAG Peers in the basic configuration, follow the steps below:
1.
Enter the following commands on both Peer switches before enabling MLAG (using the feature vpc
command) on each one. Each configuration is also attached in the left attachment column (click the
paperclip icon) that can be used to cut and paste into a CLI session.
Primary MLAG Peer (N3048)
Secondary MLAG Peer (N3048)
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
Create a VLAN for MLAG and all

Partner traffic
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
vpc peer-link
exit
Configure the port channel for

the Peer-Link
- must be trunk mode
interface tengigabitethernet 1/0/1

channel-group 1 mode active
exit

exit
Identify and configure the

Peer-Link interface
-Peer-Link requires a native
VLAN (i.e. VLAN 1 or other
VLAN made native)
vpc 30
exit
vpc 30
exit
Create a LAG for Partner switch

A to pass traffic
Assign a unique id for Partner
switch A
vpc 40
exit
vpc 40
exit
Create a LAG (port-channel) for

Partner switch B to pass traffic
switch B
interface gigabitethernet 1/0/47

description "MLAG-Partner-link"
exit

description "MLAG-Partner-Link"
exit
Assign interfaces to connect to

Partner A LAG (channel-group)

exit

exit
Assign interfaces to connect to

Partner B LAG (channel-group)
feature vpc
vpc domain 1
peer-keepalive enable
exit
feature vpc
vpc domain 1
exit
Enable the MLAG
Partner Switch A
Partner Switch B
configure
vlan 30
exit
configure
vlan 30
exit
create same VLAN on Partners
exit
exit
interface gi1/0/27
exit
interface gi1/0/29
exit
Assign interfaces to MLAG

(channel-group)
interface gi1/0/28
exit
interface gi1/0/30
exit
Assign interfaces to MLAG

(channel-group)
interface range gi1/0/xx-yy

switchport mode access
switchport access vlan 30
exit
interface range gi1/0/xx-yy

exit
Assign additional ports to the

VLAN only for hosts that will be
using the MLAG
configure the port channel

trunk for the Partner link
The Peer-Link requires a native VLAN to be configured. It can use VLAN 1 (the default native VLAN) or
another VLAN that has been set to native. This is a limitation of the Peer-Link keep alive protocol.
Interfaces used to connect each Peer to the Partner switch LAG do not need to match on each Peer.
For instance, in the example above, one Partner LAG interface connects to 1/0/47 on the primary Peer
while the other interface connects to 1/0/11 on the secondary Peer.
2. Connect all cables as shown in Figure 4, or use the checklist in Error! Reference source not found..
10
Primary MLAG Peer

From Switch / Port
To Switch / Port
Primary MLAG Peer / 1/0/1
Secondary MLAG Peer / 1/0/1
Partner Switch A / 1/0/27
Partner Switch B / 1/0/30
Secondary MLAG Peer

From Switch / Port
To Switch / Port
Partner Switch A / 1/0/28
Partner Switch B / 1/0/29
Table 3
Cabling checklist for the single tier example
3. Run the show vpc brief command on either MLAG Peer to to display all information for both Peers.
11
Primary MLAG Peer
Secondary MLAG Peer
show vpc brief
show vpc brief
VPC domain ID.................................... 1

VPC admin status............................... Enabled
Keep-alive admin status................... Enabled
VPC operational status..................... Enabled
Self role................................................ Primary
Peer role.............................................. Secondary
Peer detection admin status........... Disabled
Operational VPC MAC...................... ECF4.BBF5.2502
Operational VPC system priority. 32767
VPC domain ID........................................ 1

VPC admin status................................... Enabled
Keep-alive admin status....................... Enabled
VPC operational status......................... Enabled
Self role.................................................. Secondary
Peer role................................................ Primary
Peer detection admin status............... Disabled
Operational VPC MAC.......................... ECF4.BBF5.2502
Operational VPC system priority.. 32767
Peer-Link details
----------------Interface.................................................. Po1
Peer-link admin status......................... Enabled
Peer-link STP admin status................. Disabled
Configured VLANs................................. 1,30
Egress tagged VLANs............................ 30
Peer-Link details
----------------Interface.................................................. Po1
VPC Details
----------Number of VPCs configured...................... 2
Number of VPCs operational..................... 2
VPC Details
VPC id# 30
----------Interface.................................................... Po30
Configured VLANs.................................. 1,30
VPC interface state................................. Active
VPC id# 30
----------Interface.................................................... Po30
Configured VLANs.................................. 1,30
VPC interface state................................. Active
Local Members
----------------Gi1/0/47
Status
-----Up
Local Members
----------------Gi1/0/11
Status
-----Up
Peer Members
---------------Gi1/0/11
Status
-----Up
Peer Members
---------------Gi1/0/47
Status
-----Up
VPC id# 40
----------Interface.............................................. Po40
Configured VLANs............................ 1,30
VPC interface state........................... Active
VPC id# 40
----------Interface............................................ Po40
Configured VLANs.......................... 1,30
VPC interface state......................... Active
Local Members
----------------Gi1/0/48
Status
-----Up
Local Members
----------------Gi1/0/12
Status
-----Up
Peer Members
---------------Gi1/0/12
Status
-----Up
Peer Members
---------------Gi1/0/48
Status
-----Up
Results of the command should be the same as shown above. All member ports must show UP, and the
VPC interface state must show Active. When Partner switches are correctly configured with MLAGs and
connected to the MLAG Peers, the Number of VPCs operational in the show vpc brief command will
show 1 or more. A value of 0 indicates the Partner switches are not properly configured.
The show interface port-channel is another helpful tool to verify if the configured LAG ports are up and
running. This command can be run on both the primary and secondary Peers on a single layer MLAG
topology. If correctly configured, the port(s) in the LAG are listed with an Active status. If there are any
inactive ports, check for cabling or configuration issues.
Single-tier MLAG Peer
show interface port-channel 40
Channel Ports
Ch-Type Hash Type Min-links Local Prf
------- ----------------------------- -------- --------- --------- ---Po40
Active: Gi1/0/48
Dynamic 7
1
Disabled
Hash Algorithm Type
1 - Source MAC, VLAN, EtherType, source module and port Id
2 - Destination MAC, VLAN, EtherType, source module and port Id
3 - Source IP and source TCP/UDP port
4 - Destination IP and destination TCP/UDP port
5 - Source/Destination MAC, VLAN, EtherType, source MODID/port
6 - Source/Destination IP and source/destination TCP/UDP port
7 - Enhanced hashing mode
12
Two-Tier Example
Figure 5 shows a logical topology for a two-tier fully meshed MLAG, offering full redundancy across all
four MLAG Peers. Six Dell N3024s are used for the example, however the same principles apply and the
same commands can be used on the N2000 and N4000 series switches.
A.
11
13
15
17
19
10
12
14
16
18
20
21
LNK 23 ACT
Stack No.
LNK
22
ACT
24 COMBO P
SFP+
= MLAG
B.
1
11
13
15
17
19
10
12
14
16
18
20
21
LNK 23 ACT
Stack No.
LNK
22
ACT
24 COMBO P
SFP+
C.
Peer-Link
11
13
15
17
19
10
12
14
16
18
20
21
LNK 23 ACT
Stack No.
LNK
ACT
2
22
24 COMBO P
SFP+
2 tier
(2 layer, full mesh)
D.
1
11
13
15
17
19
10
12
14
16
18
20
21
LNK 23 ACT
Stack No.
LNK
F.
22
24 COMBO P
ACT
SFP+
E.
Peer-Link
11
13
15
17
19
10
12
14
16
18
20
21
LNK 23 ACT
Stack No.
LNK
ACT
11
13
15
17
19
10
12
14
16
18
20
21
24 COMBO P
SFP+
LNK 23 ACT
Stack No.
LNK
22
22
ACT
24 COMBO P
SFP+
Logical topology of a two-tier full mesh configuration

Figure 6 shows the physical layout of the same topology as it might appear in a rack, including cabling and
attached hosts that need to communicate across the MLAG. The same color scheme is used for the cables
in Figure 6 that was used to show logical connections in Figure 5.
(23)
(13-14)
1
Ports are denoted by the

port # in parenthesis.
Example:
gigabitethernet 1/0/23
is shown as (23)
11
13
15
17
19
21
LNK 23 ACT
A.
Stack No.
LNK
10
12
11
14
16
18
20
13
15
17
19
22
ACT
24 COMBO P
SFP+
(1-2)
1
21
LNK 23 ACT
(14)
B.
2
10
12
16
18
20
22
ACT
24 COMBO P
SFP+
Server
(Te 1)
(13)
(1-2)
C.
14
Stack No.
LNK
11
13
15
17
19
10
12
14
16
18
20
13
15
17
19
21
LNK 23 ACT
Stack No.
LNK
22
ACT
24 COMBO P
SFP+
(Te 1)
D.
11
LNK 23 ACT
(14)
(1-2)
4
10
12
11
16
18
20
15
17
19
22
13
Stack No.
10
12
14
16
18
20
22
11
13
ACT
24 COMBO P
SFP+
(Te 1)
15
17
19
21
LNK 23 ACT
Stack No.
LNK
10
12
14
16
18
20
22
24 COMBO P
(24)
Physical cabling of a two-tier full mesh configuration
LNK 23 ACT
(13-14)
13
SFP+
(Te 1)
21
LNK
F.
ACT
24 COMBO P
(13)
(1-2)
1
14
Stack No.
LNK
E.
21
ACT
SFP+
PC
In a full mesh, all eight ports joined together in the MLAG (four blue cables) are in the same port channel
to achieve maximum redundancy.
To configure the two-tier in a full mesh configuration, follow the steps below:
1.
Enter the commands below for each corresponding switch in the topology.
2. Cable the configuration as shown in Figure 6 or use the checklist in Table 4.

3. Enable MLAG (using the feature vpc command) on each switch.
Similar commands are performed on all four MLAG Peer switches. MLAG Peers B and C are required to be
consistent in their configurations following the guidelines set above in the
Consistency of MLAG
Peers section. MLAG Peers D and E also follow consistency requirements. Though MLAG Partner switches
A and F may have similar configurations in this particular scenario, they have no such consistency
requirements to each other or to the Peer switches.
Each configuration below is also attached in the left attachment column (click the paperclip icon) that
can be used to cut and paste into a CLI session. Command sections are color-coded for easier reading.
14
MLAG Peer B
MLAG Peer C
configure
vlan 30
exit
configure
vlan 30
exit
Create a VLAN for MLAG and

all Partner traffic
vpc peer-link
exit
vpc peer-link
exit

the BC peer link

exit

exit
Identify and configure the BC

peer link interfaces
vpc 40
exit
vpc 40
exit
Create a LAG (port-channel)

for Partner switch DE to pass
traffic
vpc 50
exit
vpc 50
exit

for Partner switch A to pass
traffic

exit

exit
Assign interfaces to connect

to Partner Es half of full mesh
LAG

exit

exit

to Partner Ds half of full mesh
LAG
15

switchport trunk allowed vlan 30
exit

exit
Assign interfaces to VLAN that

will connect to Partner As LAG
-put both 13 and 14 into same
LAG 50
feature vpc
vpc domain 1
exit
feature vpc
vpc domain 1
exit
Enable the MLAG

BC and DE must be in
separate domains
MLAG Peer D
MLAG Peer E
configure
vlan 30
exit
configure
vlan 30
exit

all Partner traffic
vpc peer-link
exit
vpc peer-link
exit

the DE peer link

exit

exit
Identify and configure the DE

vpc 40
exit
vpc 40
exit

for Partner switch BC to pass
traffic
vpc 60
exit
vpc 60
exit

for Partner switch F to pass traffic

exit

exit

to Partner B s half of full mesh
MLAG

exit

exit

to Partner C s half of full mesh
LAG

exit

exit

will connect to Partner Fs LAG
feature vpc
feature vpc
Enable the MLAG
-put both 13 and 14 into same

LAG 60
vpc domain 2
exit
vpc domain 2
exit
BC and DE must be in
separate domains
Partner Switch A
Partner Switch F
configure
vlan 30
exit
configure
vlan 30
exit
exit
exit

trunks for the Partner links
interface gi1/0/13
exit
interface gi1/0/13
exit
Assign first interface to LAG

(channel-group)
interface gi1/0/14
exit
interface gi1/0/14
exit
Assign second interface to

LAG (channel-group)
interface gi1/0/23
exit
interface gi1/0/24
exit

using the MLAG
Connect all cables as shown in Figure 6 on page 13 or use the checklist below in Table 4. Port 23 in switch
A connects to the Server, and port 24 in switch F connects to the PC client.
Note: Peers B and C are in their own MLAG domain. Peers D and E are also in their own MLAG
domain. Each domain views the other as a partner.
MLAG Peer A
From Switch / Port
To Switch / Port
MLAG Partner A 1/0/13
MLAG Peer C 1/0/13
MLAG Partner A 1/0/14
MLAG Peer B 1/0/14
MLAG Peer B
From Switch / Port
16
To Switch / Port
MLAG Peer B Te/0/1
MLAG Peer C Te/0/1
MLAG Peer B 1/0/1
MLAG Peer E 1/0/1
MLAG Peer B 1/0/2
MLAG Peer D 1/0/1
MLAG Peer C
From Switch / Port
To Switch / Port
MLAG Peer C 1/0/1
MLAG Peer E 1/0/2
MLAG Peer C 1/0/2
MLAG Peer D 1/0/2
MLAG Peer D
From Switch / Port
To Switch / Port
MLAG Peer D / Te0/1
MLAG Peer E / Te0/1
MLAG Peer D / 1/0/14
MLAG Partner F / 1/0/14
MLAG Peer E
From Switch / Port
MLAG Peer E / 1/0/13
Table 4
To Switch / Port
MLAG Partner F / 1/0/13
Cabling checklist for the two-tier example
4. Run the show vpc brief command on either MLAG Peer to display information for both Peers.
Note: Interfaces used to connect each Peer to the Partner switch LAG are not required to match on each
Peer. For instance, in the example above, one Partner LAG interface connects to 1/0/47 on the primary
Peer while the other interface connects to 1/0/11 on the secondary Peer. It is not required that both
Peers use port 1/0/47 or port 1/0/11.
Note: The Partner switches must be configured with LAGs and be connected to the MLAG Peers, or the
Number of VPCs operational in the show vpc brief command will show 0.
17
MLAG Peer B (Primary Peer)
MLAG Peer C (Secondary Peer)
show vpc brief
show vpc brief
VPC domain ID...................................... 1

Self role................................................ Primary
Peer role.............................................. Secondary
VPC domain ID...................................... 1

Self role................................................ Secondary
Peer role.............................................. Primary
Peer-Link details
----------------Interface.................................................. Po1
Configured VLANs................................ 1,30
Peer-Link details
----------------Interface.................................................. Po1
VPC Details
VPC Details
VPC id# 40
----------Interface................................................ Po40
Configured VLANs............................... 1,30
VPC interface state............................. Active
VPC id# 40
----------Interface................................................ Po40
Local Members
Status
----------------- -----Gi1/0/1
Up
Gi1/0/2
Up
Local Members
Status
----------------- -----Gi1/0/1
Up
Gi1/0/2
Up
Peer Members
---------------Gi1/0/1
Gi1/0/2
Peer Members
---------------Gi1/0/1
Gi1/0/2
Status
-----Up
Up
Status
-----Up
Up
VPC id# 50
----------Interface................................................ Po50
VPC id# 50
----------Interface................................................ Po50
Local Members
Status
----------------- -----Gi1/0/14
Up
Local Members
Status
----------------- -----Gi1/0/13
Up
Peer Members
---------------Gi1/0/13
Peer Members
---------------Gi1/0/14
Status
-----Up
Status
-----Up
All member ports must show UP, and the VPC interface state must show Active.
The show interface port-channel is another helpful tool to let you know if the configured LAGs are up and
running. When correctly configured, ports in the LAG are listed with an Active status. Inactive ports are
usually a sign of a cabling or configuration issue.
MLAG Peers
show interface port-channel 40
Channel Ports
------- ----------------------------- -------- --------- --------- ---Po40
Active: Gi1/0/1, Gi1/0/2
Dynamic 7
1
Disabled
Hash Algorithm Type
1 - Source MAC, VLAN, EtherType, source module and port Id
2 - Destination MAC, VLAN, EtherType, source module and port Id
3 - Source IP and source TCP/UDP port
4 - Destination IP and destination TCP/UDP port
5 - Source/Destination MAC, VLAN, EtherType, source MODID/port
6 - Source/Destination IP and source/destination TCP/UDP port
7 - Enhanced hashing mode
18
Connecting Single-homed Partners

Single-homing a device by attaching it to only one Peer does not actually create an MLAG Partner.
When configuring an MLAG topology, Partner devices (switches, servers, storage, or other) must use an
MLAG link aggregation that spans both MLAG Peers in order to be a Partner. Using only one cable or portchannel going into only one of the MLAG Peers (Figure 7) does not take advantage of the multiple path
MLAG and can lead to data loss.
MLAG peer
MLAG peer
Peer-Link
X
Device B
Device A
Unsupported single-homed Partner devices

Traffic to and from non-redundant ports is filtered and never crosses the MLAG Peer-Link. Such
ports/VLANs need to obtain connectivity via an alternative to the MLAG-connected ports/VLANs. There are
three ways to circumvent the problem of a singled-homed device that allows it to attach and pass traffic
through the MLAG topology.
Solution 1
The first solution, as shown in Figure 8, shows single-homed devices attaching to only one MLAG Peer.
An extra port-channel connection between the MLAG Peers allows for non-MLAG VLAN traffic from the
single-homed devices to cross from one Peer to the other. This can only be run in an MSTP environment
and is not supported when running RSTP. For this example, VLANs 1-39 are used in the MLAG, with VLAN
40 dedicated to be used only by devices with non-redundant links. No MLAG benefits are achieved for
these attached devices when using this method.
VLAN 40
MLAG peer
MLAG peer
Peer-Link
VLAN 40
MSTP
Environment
VLAN 40
VLANs 1-39
MLAG
Device
Partner
Solution 1 - Adding a VLAN link between the MLAG Peers
19
Device
MLAG interfaces and non-redundant ports cannot be members of the same VLAN, i.e. a VLAN may contain
MLAG interfaces or a VLAN may contain non-redundant ports, but not both.
Note: Solution 1 can be ran in an MSTP environment only. The MSTP domain should always be named
in order for the peer-link to remain unblocked.
Solution 2
As shown in Figure 9, the second solution is to configure one or more MLAG Partner switches between
the MLAG Peers and the devices that require a single link. The single-homed devices (e.g. A, B, C, and D)
can then pass traffic across the MLAG domain.
MLAG peer
MLAG peer
Peer-Link
ML
AG
Partner Y
Device A
AG
ML
Partner Z
Connecting single-homed
devices to Partner devices
already configured for MLAG
Device B
Device C
Device D
Solution 2 - Connecting devices to a Partner switch
Solution 3
A third solution, as shown in Figure 10, is achieved through multi-homing the Partner device, and thereby
creating an MLAG. By adding one or more cables to the device, creating a LAG, and splitting the LAG with
half of the cables going to one MLAG Peer, and half going to the other MLAG Peer, the redundant multipath advantage is attained. Attaching to a minimum of two Partner devices is mandatory in order to take
advantage of MLAG.
MLAG peer
MLAG peer
Peer-Link
ML
AG
AG
ML
Partner B
Partner A
Solution 3 Muli-homed, Multi-switch LAG (MLAG)

20
Explaining the MLAG method (solution 3) is the primary purpose of this guide, and a complete explanation
including N-Series switch configurations for this topology are found in the
Single-Tier Example on page 9. To configure link aggregation for servers, storage, or other devices,
consult the User Guides for the NICs being used in those devices.
21
MLAG with VLT

MLAG can also be used in combination with Virtual Link Trunking (VLT). VLT is the technology similar to
MLAG that can be implemented on certain Dell switches like the S4810. Figure 11 shows MLAG Peers on
one layer and VLT Peers on the second layer, with a full-mesh LAG. The orange line shows the VLTi (VLT
interconnect) for the VLT domain and the red line shows the Peer-Link for the MLAG domain. The top and
bottom partner switches (labeled A and F ) may be any switch model.
A.
LAG
S4810
B.
TER
SYS MAS FAN PSU
Force10 S4810P
RS-232
52
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
SFP+
44
46
48
QSFP+
60
56
LNK
ETHERNET
VLTi
C.
S4810
TER
SYS MAS FAN PSU
Force10 S4810P
ACT
RS-232
52
10
12
14
16
18
20
22
24
26
28
30
32
34
36
38
40
42
44
46
48
QSFP+
60
56
SFP+
LNK
ETHERNET
ACT
LAG
full
D.
N4032
1
11
13
15
17
19
21
LNK 23 ACT
10
12
14
16
18
20
22
24
mesh
Peer-Link
E.
N4032
1
11
13
15
17
19
21
LNK 23 ACT
10
12
14
16
18
20
22
24
MLAG
F.
Mixed full-mesh LAG using MLAG and VLT

This topology is similar to the one shown in Figure 5 on page 13 but replaces B and C with S4810 switches,
and D and E with N4032 switches in order to illustrate compatibility of VLT with MLAG protocols. This
particular scenario also provides a full-mesh 10 GbE solution. 40 GbE interfaces will be used for the VLTi
and Peer-Link connections.
Note: Other 10 GbE solutions include using all N4000 Series switches (MLAG only) or all S4810 switches
(VLT only) for BCDE.
Figure 12 shows the physical layout of the same topology as it might appear in a rack, including cabling
and attached hosts that need to communicate across the MLAG/VLT. The same color scheme is used for
the cables in Figure 12 that was used to show logical connections in Figure 11.
22
(23)
A.
= LAG
Stack No.
ACT
24 COMBO P
22
20
18
16
14
12
10
B.
(Te 1-2)
LNK
(22-23)
Ports are denoted by

the port # in
parenthesis.
Example:
port 1/0/23
is shown as (23)
LNK 23 ACT
21
19
17
15
13
11
(47)
Force10 S4810P
ER
ST N
U
S
SY MA FA PS
RS-232
52
10
12
14
16
18
20
22
SFP+
24
26
28
30
32
34
36
38
40
42
44
46
QSFP+
48
60
LNK
56
ETHERNET
SFP+
C.
(47)
Force10 S4810P
10
12
14
16
18
RS-232
QSFP+
60
LNK
56
48
46
44
42
40
38
36
34
32
30
28
26
24
22
20
Server
ER
ST N
U
S
SY MA FA PS
52
ACT
(56)
(22-23)
ETHERNET
ACT
SFP+
(56)
D.
11
13
15
17
19
10
12
14
16
18
20
22
24
LNK
ACT
11
13
15
17
19
21
(Fo 2)
LNK 23 ACT
(Fo 2)
LNK
10
12
14
16
18
20
ACT
QSFP+ MODULE
(24)
22
ACT
24
PC
LNK
ACT
QSFP+ MODULE
(24)
(1-2)
F.
LNK 23 ACT
LNK
(1-2)
E.
21
(1-2)
11
13
15
17
19
21
LNK 23 ACT
Stack No.
LNK
10
12
14
16
18
20
22
24 COMBO P
(24)
ACT
SFP+
(Te 1-2)
Physical cabling of a two-tier MLAG/VLT full-mesh configuration
The configurations below are used in configuring this example.

Note: In a full mesh of MLAG-only peer switches (as shown in the two-tier example in Figure 5), each
peer pair must be in it's own MLAG domain. However, with a full mesh of one MLAG peer pair and one
VLT peer pair, each pair is already in their own domain within its protocol. For this reason, both peer
pairs may use the same domain number if desired.
Enter the commands for each corresponding switch in the topology, then cable the configuration as
shown in the above figure.
Configurations are also attached in the left attachment column that can be used to cut and paste into a
CLI session. Click the paperclip icon to expose the list of attachments. Command sections are colorcoded for easier reading.
23
VLT Peer B (S4810)
VLT Peer C (S4810)
configure
protocol spanning-tree rstp
no disable
configure
protocol spanning-tree rstp
no disable
Enable spanning tree, which is

disabled by default on the S4810
interface vlan 30
no shutdown
exit
interface vlan 30
no shutdown
exit
Create one or more VLANs for

Partner traffic
description "VLT-Peer-Link"
no ip address
channel-member Fo 0/56
no shutdown
description "VLT-Peer-Link"
no ip address
channel-member Fo 0/56
no shutdown

the peer link
- can be different than DE
port channel
Assign the peer link interfaces
24
exit
exit
interface forty 0/56

no shutdown
exit
interface forty 0/56

no shutdown
exit
Bring up the peer interfaces
vlt domain 1
peer-link port-channel 1
back-up destination 172.25.194.24
primary-priority 1
system-mac mac-address
aa:bb:cc:dd:12:34
unit-id 0
exit
vlt domain 1
primary-priority 2
system-mac mac-address
aa:bb:cc:dd:12:34
unit-id 1
exit
Setup the VLT domain
no ip address
switchport
rate-interval 30
vlt-peer-lag port-channel 40
no shutdown
exit
no ip address
switchport
rate-interval 30
no shutdown
exit

for Partner switch DE
-put into L2 mode
-set rate interval
-port channel of peer (same
here for ease of remembering)
interface Te 0/22
description Link to MLAG"
no ip address
port-channel-protocol LACP
port-channel 40 mode active
no shutdown
exit
interface Te 0/22
no ip address
no shutdown
exit

to Partner Ds half of full mesh
LAG
interface Te 0/23
no ip address
no shutdown
exit
interface Te 0/23
no ip address
no shutdown
exit

to Partner Es half of full mesh
LAG
no ip address
switchport
rate-interval 30
no shutdown
exit
no ip address
switchport
rate-interval 30
no shutdown
exit

for Partner switch A to pass
traffic
-put into L2 mode
-set rate interval
-port channel of peer (same
here for ease of remembering
interface vlan 30
tagged port-channel 40,50
exit
interface vlan 30
tagged port-channel 40,50
exit
Add the port-channels to

VLAN 30
interface Te 0/47
no ip address
no shutdown
exit
exit
interface Te 0/47
no ip address
no shutdown
exit
exit

will connect to Partner As LAG
-identify a port channel

-provide the management
address of the other peer
-lower priority will be primary
-provide a MAC for the pair
-provide correct unit-id (0-1)
-put both into same LAG 50
25
MLAG Peer D (N4032F)
MLAG Peer E (N4032F)
configure
vlan 30
exit
configure
vlan 30
exit

all Partner traffic
vpc peer-link
exit
vpc peer-link
exit

the DE peer link
interface forty 1/1/2

exit
interface forty 1/1/2

exit
Identify and configure the DE

vpc 40
exit
vpc 40
exit

for Partner switch BC traffic
switch BC
interface ten 1/0/1

exit
interface ten 1/0/1

exit

to B s half of full mesh LAG
interface ten 1/0/2

exit
interface ten 1/0/2

exit

to C s half of full mesh LAG
vpc 60
exit
vpc 60
exit

for Partner switch F to pass traffic
switch F
interface ten 1/0/24

exit
interface ten 1/0/24

exit

will connect to Partner Fs LAG
-put both into same LAG 60
feature vpc
vpc domain 2
exi
exit
feature vpc
vpc domain 2
exit
exit
Enable the MLAG
Partner Switch A
Partner Switch F
configure
vlan 30
exit
configure
vlan 30
exit
exit
exit

trunks for the Partner links
interface te1/0/1
exit
interface te1/0/1
exit
Assign first interface to LAG

(channel-group)
interface te1/0/2
exit
interface te1/0/2
exit
Assign second interface to

LAG (channel-group)
interface gi1/0/23
exit
exit
interface gi1/0/24
exit
exit

using the MLAG
Connect all cables as shown in Figure 12 on page 23 or use the checklist below in Table 5. Port 23 in
switch A connects to the Server, and port 24 in switch F connects to the PC client.
Partner Switch A
From Switch / Port
To Switch / Port
Partner Switch A / Te0/1
VLT Peer B / 1/0/47
Partner Switch A / Te0/2
VLT Peer C / 1/0/47
VLT Peer B
From Switch / Port
To Switch / Port
VLT Peer B / 1/0/56
VLT Peer C / 1/0/56
VLT Peer B / 1/0/22
MLAG Peer E / 1/0/1
VLT Peer B / 1/0/23
MLAG Peer D / 1/0/1
VLT Peer C
From Switch / Port
To Switch / Port
VLT Peer C / 1/0/23
MLAG Peer E / 1/0/2
VLT Peer C / 1/0/22
MLAG Peer D / 1/0/2
MLAG Peer D
26
From Switch / Port
To Switch / Port
MLAG Peer D / Fo0/2
MLAG Peer E / Fo0/2
MLAG Peer D / 1/0/24
Partner Switch F / Te0/2
MLAG Peer E
Table 5
From Switch / Port
To Switch / Port
MLAG Peer E / 1/0/24
Partner Switch F / Te0/1
Cabling checklist for the MLAG with VLT example
Run the show vpc brief command on one of the MLAG Peers to display information for the MLAG Peers.
Note: Interfaces used to connect each Peer to the Partner switch LAG are not required to match on each
Peer. For instance, in the example above, one Partner LAG interface connects to 1/0/47 on the primary
Peer while the other interface connects to 1/0/11 on the secondary Peer. It is not required that both
Peers use port 1/0/47 or port 1/0/11.
Note: The Partner switches must be configured with LAGs and be connected to the MLAG Peers, or the
Number of VPCs operational in the show vlt brief command will show 0.
27
MLAG Peer D (N4032F)
MLAG Peer E (N4032F)
show vpc brief
show vpc brief
VPC domain ID........................................ 2

Self role.................................................... Primary
Peer role.................................................. Secondary
Operational VPC MAC.................... ECF4.BBF4.2402
Operational VPC system priority........ 32767
VPC domain ID........................................ 2

Self role.................................................... Secondary
Peer role.................................................. Primary
Operational VPC MAC........................ ECF4.BBF4.2402
Operational VPC system priority........ 32767
Peer-Link details
----------------Interface.................................................. Po1
Peer-link STP admin status................. Enabled
Peer-Link details
----------------Interface.................................................. Po1
Peer-link STP admin status................. Enabled
VPC Details
----------Number of VPCs configured................. 2
Number of VPCs operational................ 2
VPC Details
----------Number of VPCs configured................. 2
Number of VPCs operational................ 2
VPC id# 40
----------Interface................................................ Po40
VPC id# 40
----------Interface................................................ Po40
Local Members
Status
----------------- -----Te1/0/1
Up
Te1/0/2
Up
Local Members
Status
----------------- -----Te1/0/1
Up
Te1/0/2
Up
Peer Members
---------------Te1/0/1
Te1/0/2
Peer Members
---------------Te1/0/1
Te1/0/2
Status
-----Up
Up
Status
-----Up
Up
VPC id# 60
----------Interface................................................ Po60
VPC id# 60
----------Interface................................................ Po60
Local Members
Status
----------------- -----Te1/0/24
Up
Local Members
Status
----------------- -----Te1/0/24
Up
Peer Members
---------------Te1/0/24
Peer Members
---------------Te1/0/24
Status
-----Up
Status
-----Up
Results of the command should be the same as shown above. All member ports must show Up, and the
VPC interface state must show Active.
The show interface port-channel is another helpful tool to let you know if the configured LAGs are up and
running. If correctly configured, ports in the primary LAG are listed with an Active status. Inactive ports are
usually a sign of a cabling or configuration issue.
MLAG Peers
show interfaces port-channel 40
Channel Ports
------- ----------------------------- -------- --------- --------- --------Po40
Active: Te1/0/1, Te1/0/2
Dynamic 7
1
Disabled
show interfaces port-channel 60
Channel Ports
------- ----------------------------- -------- --------- --------- --------Po60
Active: Te1/0/24
Dynamic 7
1
Disabled
Run show vlt brief and other commands on one of the VLT Peers to display information for the VLT Peers.
ICL Link, Heartbeat, and VLT Peer Status should all show Up.
28
29
VLT Peer B (Primary Peer)
VLT Peer C (Secondary Peer)
show vlt brief
show vlt brief
VLT Domain Brief

-----------------Domain ID:
1
Role:
Primary
Role Priority:
1
ICL Link Status:
Up
HeartBeat Status:
Up
VLT Peer Status:
Up
Local Unit Id:
0
Version:
6(4)
Local System MAC address:
00:01:e8:8b:36:0e
Remote System MAC address:
00:01:e8:8b:3b:6f
Configured System MAC address:
aa:bb:cc:dd:12:34
Remote system version:
6(4)
Delay-Restore timer:
90 seconds
Delay-Restore Abort Threshold: 60 seconds
Peer-Routing :
Disabled
Peer-Routing-Timeout timer:
0 seconds
Multicast peer-routing timeout: 150 seconds
VLT Domain Brief

-----------------Domain ID:
1
Role:
Secondary
Role Priority:
2
ICL Link Status:
Up
HeartBeat Status:
Up
VLT Peer Status:
Up
Local Unit Id:
1
Version:
6(4)
Local System MAC address:
00:01:e8:8b:3b:6f
Remote System MAC address:
00:01:e8:8b:36:0e
Configured System MAC address:
aa:bb:cc:dd:12:34
Remote system version:
6(4)
Delay-Restore timer:
90 seconds
Delay-Restore Abort Threshold: 60 seconds
Peer-Routing :
Disabled
Peer-Routing-Timeout timer:
0 seconds
Multicast peer-routing timeout: 150 seconds
show vlt detail
show vlt detail
Local LAG Id Peer LAG Id Local Peer VLANs
Local LAG Id Peer LAG Id Local Peer VLANs
-------------- --------------- ------- ------- ---------
-------------- --------------- ------- ------- ---------
40
50
40
50
40
50
UP
UP
UP
UP
30
30
40
50
UP
UP
UP
UP
30
30
show running-config vlt
show running-config vlt
vlt domain 1
primary-priority 1
system-mac mac-address aa:bb:cc:dd:12:34
unit-id 0
vlt domain 1
primary-priority 2
system-mac mac-address aa:bb:cc:dd:12:34
unit-id 0
show vlt backup-link

VLT Backup Link
----------------Destination:
Peer HeartBeat status:
Destination VRF:
HeartBeat Timer Interval:
show vlt backup-link

VLT Backup Link
----------------Destination:
Peer HeartBeat status:
Destination VRF:
HeartBeat Timer Interval:
172.25.194.24
Up
default
1
172.25.194.25
Up
default
1
HeartBeat Timeout:
UDP Port:
HeartBeat Messages Sent:
HeartBeat Messages Received:
3
34998
257900
257868
HeartBeat Timeout:
UDP Port:
HeartBeat Messages Sent:
HeartBeat Messages Received:
3
34998
257877
257879
Results of the command should be in proximity to those above. The Destination should show the
management IP address of the peer switch, and the Peer HeartBeat status should be Up.
Consult the S4810 User Guide or VLT Deployment Guide for additional information on implementing VLT.
30
Additional Resources
Support.dell.com is focused on meeting your needs with proven services and support.
DellTechCenter.com is an IT Community where you can connect with Dell Customers and Dell
employees for the purpose of sharing knowledge, best practices, and information about Dell products and
installations.
Referenced or recommended Dell publications:
Dell Networking Support
- http://www.dell.com/support
Dell TechCenter (community forums and blogs for Dell customers)
- http://delltechcenter.com
Dell Networking Whitepapers
- http://en.community.dell.com/techcenter/networking/p/guides
Dell Networking N2000/N3000/N4000 User Guides and Firmware downloads
- http://en.community.dell.com/techcenter/networking/p/guides#N-series
Configuration Details
This paper was compiled using the following components and versions.
31
Component
Revision
Dell N2000, N3000, N4000
6.2.0.3
Dell S4810
Dell Application Software (Firmware) Version 9.6
Appendix
Unsupported Configurations
The configurations and topologies found in this guide are supported. A few configuration models that are
not supported are discussed below.
Using different types of expansion modules in a Peer-Link is not supported. Peer devices must use the
same type of expansion module if ports from the expansion modules are to be part of the MLAG interface.
Stacking of either MLAG peer is not supported. Neither switch used as MLAG Peers may be stacked with
other switches.
Using two different series switch models as MLAG peers is not supported. Same series switch models are
required to create MLAG Peers. This means any N2000 Series can only be peered with another N2000
Series, an N3000 Series with another N3000 Series, and an N4000 Series with another N4000 Series.
Figure 13 shows another example of an unsupported configuration, attempting to connect an MLAG Peer
with a non-MLAG Peer, such as a VLTi (shown) or Cisco vPC/VSS Peer. These type of mixed protocol
scenarios are not supported with MLAG.
S4810
ER
SYS MAST FAN PSU
Force10 S4810P
RS-232
52
10
12
14
16
18
20
22
24
SFP+
26
28
30
32
34
36
38
40
42
44
46
48
QSFP+
60
56
LNK
ETHERNET
ACT
VLTi
XPeer-Link
LAG
Unsupported Peer configuration
32
N3048
Support and Feedback

Contacting Technical Support
Support Contact Information
Web: http://Support.Dell.com/
Telephone: USA: 1-800-945-3355
Feedback for this document

We encourage readers of this publication to provide feedback on the quality and usefulness of this
document by sending an email to Using MLAG in Dell Networks Feedback
About Dell
Dell is a worldwide leader in data center and campus solutions which includes the manufacturing and
distribution of servers, network switches, storage devices, personal computers, and related hardware and
software. For more information on these and other products, please visit the Dell website at
http://www.dell.com
33

Using MLAG in Dell Networks v1.3

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Using MLAG in Dell Networks v1.3

Hochgeladen von

Copyright:

Verfügbare Formate

Using MLAG in Dell Networks

A deployment guide for Dell Networking switches (version 1.3)

A Dell Deployment and Configuration Guide

1.2 clarifies native VLAN assignment on the Peer-Link; solutions

1.1 includes changes to full-mesh support with VLT, limitation

1.0 Initial Release.

2015 Dell Inc., All rights reserved.

Using MLAG in Dell Networks v 1.3

Using MLAG in Dell Networks v 1.3

Failover in cases of failed cables or switches

Note: Dell N15xx Series switches do not support MLAG.

Using MLAG in Dell Networks v 1.3

Primary MLAG peer

L3 MLAG with mulitple

Primary MLAG peer

Two examples of a single-tier MLAG topology

Using MLAG in Dell Networks v 1.3

Caveats for Enabling MLAG

See the switch User Guide for additional information.

Consistency of MLAG Peers

Consistent MLAG Peer configurations

Using MLAG in Dell Networks v 1.3

Settings that need to match on both MLAG Peers

Settings required to match between MLAG Peers

Using MLAG in Dell Networks v 1.3

# of MLAG domains per switch

Parameters for an MLAG topology

MLAG and VLT

Examples of MLAG topologies

Using MLAG in Dell Networks v 1.3

Primary MLAG peer

Secondary MLAG peer

Single-tier MLAG topology

Secondary MLAG Peer (N3048)

Create a VLAN for MLAG and all

Configure the port channel for

interface tengigabitethernet 1/0/1

interface tengigabitethernet 1/0/1

Identify and configure the

Create a LAG for Partner switch

Using MLAG in Dell Networks v 1.3

Create a LAG (port-channel) for

interface gigabitethernet 1/0/47

interface gigabitethernet 1/0/11

Assign interfaces to connect to

interface gigabitethernet 1/0/48

interface gigabitethernet 1/0/12

Assign interfaces to connect to

Enable the MLAG

create same VLAN on Partners

Assign interfaces to MLAG

Assign interfaces to MLAG

interface range gi1/0/xx-yy

interface range gi1/0/xx-yy

Assign additional ports to the

configure the port channel

Using MLAG in Dell Networks v 1.3

Primary MLAG Peer

Primary MLAG Peer / 1/0/1

Secondary MLAG Peer / 1/0/1

Primary MLAG Peer / 1/0/47

Partner Switch A / 1/0/27

Primary MLAG Peer / 1/0/48

Partner Switch B / 1/0/30