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
March 2014
January 2014
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:
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
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
Peer-Link
MLAG
MLAG domain
appears as a single
logical switch to
partner switches on
the network
Partner Switch
MLAG domain
Secondary MLAG peer
Partner Switch
MLAG
MLAG
Partner Switch
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.
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.
MLAG peer
peer
link
Link Aggregation
=
=
=
=
=
=
Spanning Tree
MLAG Port-channels
Interfaces
VLANs
Firmware
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
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
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
1
2
2 to 8
1 to 8
Limited only by number of ports available
1 or 2
Table 2
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
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.
(1/0/1)
Peer-Link
(48)
N3048
Partner Switch A
(47)
(11)
(12)
N3048
MLAG
MLAG
(27)
(29)
(28)
(30)
(1/0/1)
Partner Switch B
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)
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 30
switchport mode trunk
vpc 30
exit
interface port-channel 30
switchport mode trunk
vpc 30
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
feature vpc
vpc domain 1
peer-keepalive enable
exit
feature vpc
vpc domain 1
peer-keepalive enable
exit
Partner Switch A
Partner Switch B
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
interface port-channel 1
switchport mode trunk
exit
interface port-channel 1
switchport mode trunk
exit
interface gi1/0/27
channel-group 1 mode active
exit
interface gi1/0/29
channel-group 1 mode active
exit
interface gi1/0/28
channel-group 1 mode active
exit
interface gi1/0/30
channel-group 1 mode active
exit
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
To Switch / Port
To Switch / Port
Table 3
3. Run the show vpc brief command on either MLAG Peer to to display all information for both Peers.
11
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
Peer-link admin status......................... Enabled
Peer-link STP admin status................. Disabled
Configured VLANs................................. 1,30
Egress tagged VLANs............................ 30
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# 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+
(23)
(13-14)
1
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)
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.
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
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
interface port-channel 50
switchport mode trunk
vpc 50
exit
interface port-channel 50
switchport mode trunk
vpc 50
exit
15
feature vpc
vpc domain 1
peer-keepalive enable
exit
feature vpc
vpc domain 1
peer-keepalive enable
exit
MLAG Peer D
MLAG Peer E
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
interface port-channel 60
switchport mode trunk
vpc 60
exit
interface port-channel 60
switchport mode trunk
vpc 60
exit
feature vpc
feature vpc
vpc domain 2
peer-keepalive enable
exit
vpc domain 2
peer-keepalive enable
exit
BC and DE must be in
separate domains
Partner Switch A
Partner Switch F
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
interface port-channel 1
switchport mode trunk
exit
interface port-channel 1
switchport mode trunk
exit
interface gi1/0/13
channel-group 1 mode active
exit
interface gi1/0/13
channel-group 1 mode active
exit
interface gi1/0/14
channel-group 1 mode active
exit
interface gi1/0/14
channel-group 1 mode active
exit
interface gi1/0/23
switchport mode access
switchport access vlan 30
exit
interface gi1/0/24
switchport mode access
switchport access vlan 30
exit
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 Peer B
From Switch / Port
16
To Switch / Port
MLAG Peer C
From Switch / Port
To Switch / Port
MLAG Peer D
From Switch / Port
To Switch / Port
MLAG Peer E
From Switch / Port
MLAG Peer E / 1/0/13
Table 4
To Switch / Port
MLAG Partner F / 1/0/13
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
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
Peer-link admin status......................... Enabled
Peer-link STP admin status................. Disabled
Configured VLANs................................. 1,30
Egress tagged VLANs............................ 30
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
Configured VLANs............................... 1,30
VPC interface state............................. Active
VPC id# 40
----------Interface................................................ Po40
Configured VLANs............................... 1,30
VPC interface state............................. Active
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
Configured VLANs............................... 1,30
VPC interface state............................. Active
VPC id# 50
----------Interface................................................ Po50
Configured VLANs............................... 1,30
VPC interface state............................. Active
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
Ch-Type Hash Type Min-links Local Prf
------- ----------------------------- -------- --------- --------- ---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
MLAG peer
Peer-Link
X
Device B
Device A
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
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 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
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
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.
22
(23)
A.
= LAG
Stack No.
ACT
24 COMBO P
22
20
18
16
14
12
10
B.
(Te 1-2)
LNK
(22-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)
23
Description of commands
configure
protocol spanning-tree rstp
no disable
configure
protocol spanning-tree rstp
no disable
interface vlan 30
no shutdown
exit
interface vlan 30
no shutdown
exit
interface port-channel 1
description "VLT-Peer-Link"
no ip address
channel-member Fo 0/56
no shutdown
interface port-channel 1
description "VLT-Peer-Link"
no ip address
channel-member Fo 0/56
no shutdown
24
exit
exit
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
peer-link port-channel 1
back-up destination 172.25.194.25
primary-priority 2
system-mac mac-address
aa:bb:cc:dd:12:34
unit-id 1
exit
interface port-channel 40
no ip address
switchport
rate-interval 30
vlt-peer-lag port-channel 40
no shutdown
exit
interface port-channel 40
no ip address
switchport
rate-interval 30
vlt-peer-lag port-channel 40
no shutdown
exit
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
description Link to MLAG"
no ip address
port-channel-protocol LACP
port-channel 40 mode active
no shutdown
exit
interface Te 0/23
description Link to MLAG"
no ip address
port-channel-protocol LACP
port-channel 40 mode active
no shutdown
exit
interface Te 0/23
description Link to MLAG"
no ip address
port-channel-protocol LACP
port-channel 40 mode active
no shutdown
exit
interface port-channel 50
no ip address
switchport
rate-interval 30
no shutdown
vlt-peer-lag port-channel 50
exit
interface port-channel 50
no ip address
switchport
rate-interval 30
no shutdown
vlt-peer-lag port-channel 50
exit
interface vlan 30
tagged port-channel 40,50
exit
interface vlan 30
tagged port-channel 40,50
exit
interface Te 0/47
no ip address
port-channel-protocol LACP
port-channel 50 mode active
no shutdown
exit
exit
interface Te 0/47
no ip address
port-channel-protocol LACP
port-channel 50 mode active
no shutdown
exit
exit
25
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 1
description "MLAG-Peer-Link"
switchport mode trunk
vpc peer-link
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
interface port-channel 40
switchport mode trunk
vpc 40
exit
interface port-channel 60
switchport mode trunk
vpc 60
exit
interface port-channel 60
switchport mode trunk
vpc 60
exit
feature vpc
vpc domain 2
peer-keepalive enable
exi
exit
feature vpc
vpc domain 2
peer-keepalive enable
exit
exit
Partner Switch A
Partner Switch F
Description of commands
configure
vlan 30
exit
configure
vlan 30
exit
interface port-channel 1
switchport mode trunk
exit
interface port-channel 1
switchport mode trunk
exit
interface te1/0/1
channel-group 1 mode active
exit
interface te1/0/1
channel-group 1 mode active
exit
interface te1/0/2
channel-group 1 mode active
exit
interface te1/0/2
channel-group 1 mode active
exit
interface gi1/0/23
switchport mode access
switchport access vlan 30
exit
exit
interface gi1/0/24
switchport mode access
switchport access vlan 30
exit
exit
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
VLT Peer B
From Switch / Port
To Switch / Port
VLT Peer C
From Switch / Port
To Switch / Port
MLAG Peer D
26
To Switch / Port
MLAG Peer E
Table 5
To Switch / Port
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
Peer-Link details
----------------Interface.................................................. Po1
Peer-link admin status......................... Enabled
Peer-link STP admin status................. Enabled
Configured VLANs................................. 1,30
Egress tagged VLANs............................ 30
Peer-Link details
----------------Interface.................................................. Po1
Peer-link admin status......................... Enabled
Peer-link STP admin status................. Enabled
Configured VLANs................................. 1,30
Egress tagged VLANs............................ 30
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
Configured VLANs............................... 1,30
VPC interface state............................. Active
VPC id# 40
----------Interface................................................ Po40
Configured VLANs............................... 1,30
VPC interface state............................. Active
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
Configured VLANs............................... 1,30
VPC interface state............................. Active
VPC id# 60
----------Interface................................................ Po60
Configured VLANs............................... 1,30
VPC interface state............................. Active
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
Ch-Type Hash Type Min-links Local Prf
------- ----------------------------- -------- --------- --------- --------Po40
Active: Te1/0/1, Te1/0/2
Dynamic 7
1
Disabled
show interfaces port-channel 60
Channel Ports
Ch-Type Hash Type Min-links Local Prf
------- ----------------------------- -------- --------- --------- --------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
40
50
40
50
40
50
UP
UP
UP
UP
30
30
40
50
UP
UP
UP
UP
30
30
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
vlt domain 1
peer-link port-channel 1
back-up destination 172.25.194.25
primary-priority 2
system-mac mac-address aa:bb:cc:dd:12:34
unit-id 0
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
6.2.0.3
Dell S4810
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
32
N3048
Web: http://Support.Dell.com/
Telephone: USA: 1-800-945-3355
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