Smartfabric Os10 Virtual Link Trunking Ra

Dell EMC SmartFabric OS10 - Virtual Link
Trunking
Reference Architecture
Abstract
This reference architecture details VLT configuration and best practices within the Dell EMC
SmartFabric OS10 operating system.
Dell Technologies Networking Infrastructure Solutions
Part Number: H18362
June 2020
Notes, cautions, and warnings
NOTE: A NOTE indicates important information that helps you make better use of your product.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
© 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other
trademarks may be trademarks of their respective owners.
Contents
1 Introduction................................................................................................................................. 4
Virtual link trunking overview............................................................................................................................................... 4
VLT operation.........................................................................................................................................................................4
VLT architecture....................................................................................................................................................................5
VLT interconnect...................................................................................................................................................................5
Dell Technologies vision........................................................................................................................................................ 5
Typographical conventions...................................................................................................................................................5
2 VLT Functionality......................................................................................................................... 6
Peer routing............................................................................................................................................................................ 7
Peer routing timeout..............................................................................................................................................................7
VLT unicast routing............................................................................................................................................................... 8
VRRP in VLT...........................................................................................................................................................................8
eVLT in SmartFabric OS10................................................................................................................................................... 8
Split control scenario.............................................................................................................................................................9
Spanning tree protocol with VLT....................................................................................................................................... 10
Spanning tree configuration................................................................................................................................................10
LACP fallback in VLT........................................................................................................................................................... 12
Best practices for VLT deployment................................................................................................................................... 13
3 VLT Configuration.......................................................................................................................15
VLT configuration procedure..............................................................................................................................................15
FSB configuration on VLT network - example................................................................................................................ 26
FC switch configuration on VLT network........................................................................................................................ 28
4 VLT Validation............................................................................................................................30
show vlt 1..............................................................................................................................................................................30
show vlt 1 role....................................................................................................................................................................... 31
show vlt 1 backup-link..........................................................................................................................................................31
show vlt 1 vlt-port detail......................................................................................................................................................31
show interface brief............................................................................................................................................................. 31
A Technical Resources...................................................................................................................32
Dell Technologies Networking Guides...............................................................................................................................32
Support and feedback.........................................................................................................................................................32
Technical support.......................................................................................................................................................... 32
Feedback for this document........................................................................................................................................ 32
Terminology..........................................................................................................................................................................32
Contents 3
1
Introduction
Virtual link trunking, or VLT, enables networks with high availability and resiliency. VLT has been deployed at various locations, and
customers are satisfied with its seamless functionality for the traffic flow and their business needs.
This document explains the dual-node VLT deployment strategies with its associated network reference architecture. Various VLT
deployment topologies are described in this document with an emphasis on best practices and references for network scenarios. This
document also covers the configuration and troubleshooting of VLT using relevant show commands and different outputs.
Topics:
• Virtual link trunking overview
• VLT operation
• VLT architecture
• VLT interconnect
• Dell Technologies vision
• Typographical conventions
Virtual link trunking overview

VLT configured in the SmartFabric OS10 operating system offers an efficient and seamless traffic flow by aggregating two identical
physical switches to form one single logical switch.
This single logical switch keeps both switches' data and control plans isolated and eases maintenance at the physical switch level.
Implementing VLT enables multiple parallel paths between nodes without loops and includes traffic load balancing when alternate paths
exist. The outcome is high availability and high resilience for connected access, core switches, and clients during switch firmware
upgrades.
With the mandatory need for high availability in modern data centers and enterprise networks, VLT plays a vital role connecting to all its
access nodes with rapid convergence, seamless traffic flow, efficient load balancing, and loop-free mechanics.
VLT provides the following benefits:
• Provides node-level redundancy and load sharing by using the same port channel terminating on multiple upstream nodes.
• Provides a loop-free topology.
• Eliminates STP-blocked ports.
• Optimizes bandwidth utilization by using all available uplink bandwidth.
• Guarantees fast convergence if either a link or device fails.
• Enhances optimized forwarding with Virtual Router Redundancy Protocol (VRRP).
• Optimizes routing with VLT peer routing for Layer 3 VLANs.
• Enables Layer 3 routing protocol support in VLT LAGs with scaled Layer 3 VLAN support.
• Provides link-level resiliency.
• Assures high availability without taking the network offline during firmware upgrades.
VLT operation
Both the VLT nodes of a domain always continue to forward data plane traffic in Active-Active mode. With the instantaneous
synchronization of MAC and ARP entries, both the nodes remain Active-Active and continue to forward the data traffic seamlessly.
The VLT implementation in SmartFabric OS10 has been modified for the optimal operation that is based on the internal architecture and
the base operating system.
4 Introduction
VLT architecture
This section describes how SmartFabric OS10 implements core VLT functionality. The VLT-Fabric Manager (VLT- FM) module implements
the core VLT protocol functionalities and VLT fabric orchestration. Other modules in the system use the services of VLT-FM to achieve
the complete VLT solution.
The VLT fabric consists of two nodes providing a logical single switch view to the connected devices. However, each of the VLT peers
maintains separate control and data planes and can be configured individually for a port, protocol, and management behaviors.
The VLT design architecture is based on the VLT fabric manager process, controlling the VLT neighbor, and overall fabric orchestration.
The protocol used to communicate between VLT peers is defined as VLT Control Protocol (VLT-CP). The Node Discovery Service
module, or NDS, handles the topology discovery and management. On receiving the topology update message, VLT-FM builds raw
topology and initiates a loop-prevention algorithm to construct the overlay topology.
The VLT application elects the primary node that is based on the lower MAC address; however, with primary-priority command, the node
with the least primary priority becomes the primary node. This election is not preempted, which means that whenever there is a change in
priority, the primary role does not change until the nodes are rebooted or the VLT process is restarted.
The VLT-related information between the nodes is exchanged through the specific reserved VLAN (VLAN 4094). The VLT database (VLT
DB) is used to store the VLT control information to be exchanged between the VLT nodes. The local database (Local DB) stores the MAC
and ARP table entries.
The design and operation of internal communication details and failure handling is beyond the scope of this document.
VLT interconnect
A VLT interconnect (VLTi) synchronizes states between VLT peers. SmartFabric OS10 automatically adds VLTi ports to VLANs spanned
across VLT peers, but does not add VLTi ports to VLANs configured on only one peer.
• The VLTi synchronizes Layer 2 and Layer 3 control-plane information across the two nodes. The VLTi is used for data traffic only
when there is a link failure that requires VLTi to reach the final destination.
• LLDP, flow control, port monitoring, and jumbo frame features are supported on a VLTi. By default, VLTi ports are set to the maximum
supported MTU value.
• MAC, ARP, IPv6 neighbors that are learnt over VLANs on VLT peer nodes synchronize using the VLTi.
Dell Technologies vision

The vision at Dell Technologies is to be the essential technology company for the data era. Dell Technologies ensures modernization for
today's applications and the emerging cloud-native world. Our Networking team is committed to disrupting the fundamental economics of
the market with an open strategy that gives you the freedom of choice for networking operating systems and top-tier merchant silicon.
The Dell Technologies strategy enables business transformations that maximize the benefits of collaborative software and standards-
based hardware, including lowered costs, flexibility, freedom, and security. Dell Technologies provides further customer enablement
through validated deployment guides that demonstrate these benefits while maintaining a high standard of quality, consistency, and
support.
Typographical conventions
The CLI and GUI examples in this document use the following conventions:
Monospace text CLI examples

Underlined monospace text CLI examples that wrap the page
Italic monospace text Variables in CLI examples
Bold text within monospace text Commands entered at the CLI prompt, or to highlight information in
CLI output
Bold text GUI fields and information entered in the GUI
Introduction 5
2
VLT Functionality
The same VLT domain-id should be configured on both VLT nodes. The unit-id 1 and 2 for the nodes is configured automatically. For rapid
convergence and optimal service, the same VLT MAC address should be configured on both the nodes using the vlt-mac command
(optional). In the absence of vlt-mac configuration, if the primary VLT node goes down, the VLT port channel on the secondary node
flaps, causing slight traffic disruption. The priority of the primary node election is based on the lower system mac-address of the switch;
however, with the primary-priority command, the VLT node with the least configured priority takes over as the primary node. This election
will not be preempted. For example, when the primary node is reloaded, it is assigned the secondary role. The role change avoids
disruptions in traffic flow due to the election process.
The election happens only during the initial configuration or when VLT is initially launched. The VLT role election has no significance for the
data traffic flowing through the VLT domain. It is only for the control protocol exchange and handles potential split-control failure
scenarios.
VLAN ID 4094 is assigned automatically and internally reserved as a control VLAN for the exchange of VLT-related information between
the nodes. The IPv6 address that is automatically assigned within the reserved range is mapped for VLAN 4094 for reachability between
the VLT nodes.
For the VLT interconnect (VLTi) link, once the discovery interfaces are configured on both of the nodes, port channel 1000 is
automatically configured, mapping the physical discovery interfaces. The ports should be configured as no switchport from the default
Layer 2 mode while configuring the discovery interfaces.
Every thirty seconds, heartbeat messages are sent between the VLT nodes to check the liveliness of the peers and to handle the VLTi
failure scenario. The heartbeat interval value is configurable and reaches the peer through the backup destination. Similarly, keep-alive
messages (non-configurable) are sent through the VLTi port channel.
For VLT port channels, the user should explicitly assign the vlt-port-channel id to the configured port channel on both of the nodes. This
port-channel identifier should be the same for both of the nodes.
NOTE: Customers should ensure that they do not use VLAN 4094 for their services. This cannot be configured locally.
Similarly, the port-channel interface 1000 cannot be configured locally.
Important points to remember:

• VLT port channel interfaces must be switch ports.
• Dell EMC strongly recommends that the VLTi (VLT interconnect) be a static LAG and that you disable LACP on the VLTi.
• If you include RSTP/PVST, and it must be configured before VLT is configured.
• VLT Heartbeat is supported only on default VRFs.
• If you enable IGMP snooping on the VLT peers, ensure the value of the delay-restore command is not less than the query interval.
• Ensure that the spanning tree root bridge is at the Aggregation layer.
• VLT interconnect over 1G ports is not supported.
• Each VLT domain has a unique MAC address that you create.
• In a VLT domain, the peer switches must run the same Dell Networking OS software version.
• If you replace a VLT peer node, preconfigure the switch with the VLT system MAC address, unit-id, and other VLT parameters before
connecting it to the existing VLT peer switch using the VLTi connection.
Topics:
• Peer routing
• Peer routing timeout
• VLT unicast routing
• VRRP in VLT
• eVLT in SmartFabric OS10
• Split control scenario
• Spanning tree protocol with VLT
• Spanning tree configuration
• LACP fallback in VLT
• Best practices for VLT deployment
6 VLT Functionality
Peer routing
VLT peer routing enables optimized routing where packets destined for the Layer 3 endpoint of the VLT peer are locally routed. VLT
supports unicast routing of both IPv4 and IPv6 traffic.
To enable VLT unicast routing, both VLT peers must be in Layer 3 mode. The VLAN configuration must be symmetrical on both peers.
Users cannot configure the same VLAN as Layer 2 on one node and as Layer 3 on the other node.
IPv4 routing provides forwarding of packets to a destination IP address, based on a routing table. This routing table defines how packets
are routed (dynamically, broadcasted directly, or using proxy ARP), as well as what type of information is included with the packets.
Peer routing is not restricted for a VLAN with routing protocols. Instead, it is enabled domain wide. Peer routing ensures active-active
routing for the traffic path. To route traffic on behalf of other VLT peers, enable peer routing on both nodes. Peer routing synchronizes
the router MAC address (local destination MAC address) within the VLT domain and ensures seamless routing by the peer node.
Peer routing timeout

In the event of peer-node failure, the peer-routing-timeout command enables the availability of peer-routing features and retains the
corresponding local destination MAC address until the timer expires. For customers who would like to be aware of the node failure and its
associated traffic, this command would cease routing on behalf of the peer after the expiration of the timer. This timer does not need to
be configured for standard, high-availability requirement deployments.
Figure 1. Peer routing
The delay-restore timer command has a default value of 90 seconds. After a VLTi flap or node reboot, the VLT port channel is
held in a down state in the secondary VLT node until the delay-restore time has passed. This function allows the MAC and ARP address
table synchronization to complete between the nodes and the control protocols to converge before reinstating the VLT port channel for
forwarding the traffic. When the VLT port channel is brought to a working state, the forwarding tables are populated in the hardware,
which allows traffic to flow without disruption. In a highly scaled setup, it is recommended that the timer is increased to ensure that all of
the tables are synchronized, and that the protocol converges before opening the VLT port channel, as to avoid traffic issues.
VLT Functionality 7
VLT unicast routing
VLT unicast routing requires that both VLT peers be in Layer 3 mode. Static route and routing protocols such as RIP, OSPF, ISIS, and BGP
are supported. To enable VLT unicast, the VLAN configuration must be symmetrical on both peers. You cannot configure the same VLAN
as Layer 2 on one node and as Layer 3 on the other node. Configuration mismatches are logged in the syslog and display in the show vlt
mismatch command output.
VRRP in VLT
With VRRP configured in both of the VLT nodes, active-active mode is internally enabled by default, which ensures seamless traffic flow.
The active-active mode is activated when the VLT VLANs are configured with a VRRP group. For practical purposes, VRRP offers a single
virtual IP as a default gateway for its access clients.
VRRP should be enabled on host-facing VLANs. The gateway for the hosts should be the virtual IP of the respective VRRP group. Traffic
from the hosts is routed by either of the VLT nodes, since VRRP establishes active-active mode in VLT.
eVLT in SmartFabric OS10

Data Center Interconnect (DCI) between VLT domains is supported in SmartFabric OS10 with the VRRP feature across the VLT domains
(eVLT). With SmartFabric OS10, VRRP can be configured for dual VLT domains to form an eVLT topology, as shown in the following
figure. The same VRRP group-id enables a common virtual IP address across both the VLT domains. Therefore, any VM migration from
DC-1 to DC-2 can be initiated without any dependency while retaining the VM IP address and gateway IP address.
The VRRP group for the configured VLANs should be the same VRRP group id in both VLT domains. With this implementation, only one of
the nodes is selected as the VRRP Master, where the other three nodes each act as a standby for that VRRP group. For example, the
virtual IP address 192.168.1.254 is retained across both of the DCs. In the case that a VM with a default gateway of 192.168.1.254 is
migrated from DC-1 to DC-2, the VM can retain its IP address and continue to forward and receive traffic without changes.
8 VLT Functionality
Figure 2. DCI using eVLT with VRRP
Upstream devices from the VLT domains can have static routing, or any other dynamic routing protocols, to support the N-S traffic. The
host can still be reached if the traffic to the VM host lands at any upstream DC, which ensures high availability for the application and
services.
Split control scenario

If the VLTi links (Po-1000) go down with the backup link status in an Up state, the secondary VLT node automatically shuts down the VLT
port channels. This ensures that the traffic only flows through the primary VLT node. In another scenario, where the backup link is also
down and with the complete isolation between VLT nodes, the secondary node changes its role to Primary node without receiving any
keep alive and heartbeat messages from the peer.
VLT Functionality 9
Figure 3. Split control scenarios
MAC/ARP addresses that are learned in both switches are retained for the traffic flow. However, any new MAC/ARP addresses that are
learned from the access nodes are not synchronized. In both the cases, the orphan ports (or non-VLT ports) continue to function without
any change in the port state.
Spanning tree protocol with VLT

Rapid spanning tree protocol (RSTP) and rapid per-VLAN spanning tree+ (RPVST+) modes of spanning tree protocol in VLT are
supported. Currently, multiple spanning tree protocol (MSTP) is not supported. Depending on the network topology, the primary node of
the VLT domain can be designated as the root bridge. Bridge Protocol Data Units (BPDUs) are processed only in the primary node.
NOTE: Dell Technologies recommends that you enable spanning tree (RSTP or RPVST+) before enabling VLT to avoid
unintentional loops in the network.
Spanning tree configuration

About this task
Perform the following steps to configure spanning tree.
Steps
1. RPVST+ is enabled by default in SmartFabric OS10. There is no need to configure RPVST+ unless the default spanning-tree mode is
changed.
OS10-VLT-Peer1(config)# spanning-tree mode rapid-pvst

OS10-VLT-Peer2(config)# spanning-tree mode rapid-pvst
10 VLT Functionality
2. RSTP is enabled by changing the mode to RSTP using the following commands:
OS10-VLT-Peer1(config)# spanning-tree mode rstp

OS10-VLT-Peer2(config)# spanning-tree mode rstp
3. Based on the customer design solution and existing STP mode, if you plan to deploy VLT nodes as the root bridge, assign the bridge
priority value to both nodes so that both of the VLT nodes have lesser priority in the network. This assignment ensures that no other
access switch becomes the root bridge when one VLT node goes down, and it avoids unintended topology changes.
a. Configuring RPVST+:
OS10-VLT-Peer1(config)# spanning-tree vlan 2 priority 4096


b. Configuring RSTP:
OS10-VLT-Peer1(config)# spanning-tree rstp priority 4096

OS10-VLT-Peer2(config)# spanning-tree rstp priority 8192
4. The STP state of the VLTi link is always placed in the forward (FWD) state. Run the show spanning-tree virtual-
interface command to verify the spanning tree status of VLTi.
OS10-VLT-Peer1# show spanning-tree virtual-interface VFP(VirtualFabricPort) of RSTP 1 is

Designated Forwarding Edge port: No (default)
Link type: point-to-point (auto)
Boundary: No, Bpdu-filter: Disable, Bpdu-Guard: Disable, Shutdown-on-Bpdu- Guard-
violation: No
Root-Guard: Disable, Loop-Guard: Disable
Bpdus (MRecords) Sent: 1083, Received: 3 Interface

Designated
Name PortID Prio Cost Sts C
ost Bridge ID PortID
VFP(VirtualFabricPort) 0.1 0 1 FWD 0

4096 3417.eb3a.ef80 0.1
OS10-VLT-Peer1#
OS10-VLT-Peer2# show spanning-tree virtual-interface

VFP(VirtualFabricPort) of vlan 1 is Root
Forwarding Edge port: No (default)
Boundary: No, Bpdu-filter: Disable, Bpdu-Guard: Disable, Shutdown-on-Bpdu- Guard-
violation: No
Root-Guard: Disable,
Loop-Guard: Disable Bpdus (MRecords) Sent: 22, Received: 271 Interface
Designated
Name PortID Prio Cost Sts C
ost Bridge ID PortID
VFP(VirtualFabricPort) 0.1 0 1 FWD 0

4097 3417.eb3a.ef80 0.1
OS10-VLT-Peer2#
5. Configure orphan ports (non-VLT ports) connected to end hosts (not connected to switches) as edge-ports to avoid any topology
change when the link state changes.
OS10-VLT-Peer1(conf-if-eth1/1/45)# spanning-tree port type edge OS10-VLT-Peer2(conf-if-

eth1/1/45)# spanning-tree port type edge
6. Apply the edge-port configuration on the VLT port channel if the VLT port channel is connected directly to the end host.
7. Replicate spanning-tree configurations applied on the VLT port channel (such as cost, priority, and edge port) on both VLT peers.
8. The primary VLT node controls all the VLT port channel interfaces within the VLT domain. The primary VLT node synchronizes the
calculated spanning-tree role and state with the secondary VLT node. When a BPDU is received on the VLT port channel:
a. The BPDU is consumed for internal processing if the node is primary.
VLT Functionality 11
b. If the node is secondary, the BPDU is redirected to the primary node for processing.
NOTE: The processing of the BPDU is done only by the VLT primary node.
9. Use the same command for VLT and standalone nodes to check the spanning-tree states. For example:
OS10-VLT-Peer1# show spanning-tree active

Spanning tree enabled protocol rstp with force-version rstp
Executing IEEE compatible Spanning Tree Protocol
Root ID Priority 4096,
Address 3417.eb3a.ef80
Root Bridge hello time 2, max age 20,
forward delay 15
Bridge ID Priority 4096,
Address 3417.eb3a.ef80
We are the root
Configured hello time 2,
max age 20,
forward delay 15
Flush Interval 200 centi-sec,
Flush Invocations 69
Flush Indication threshold 0 (MAC flush optimization is disabled)
Interface Designated
Name PortID Prio Cost Sts Cost Brid ge ID PortID

port-channel1 128.2517 128 1000 FWD 0 4096 3417.eb3a.ef80 128.2517
port-channel2 128.2518 128 1000 FWD 0 4096 3417.eb3a.ef80
128.2518
Interface
Name Role PortID Prio Cost Sts Cost Link-type Edge
port-channel1 Desg 128.2517 128 1000 FWD 0 A UTO No
OS10-VLT-Peer1#
OS10-VLT-Peer2# show spanning-tree active

Spanning tree enabled protocol rstp with force-version rstp Executing IEEE compatible
Spanning Tree Protocol
Root ID Priority 4096, Address 3417.eb3a.ef80
Root Bridge hello time 2, max age 20, forward delay 15 Bridge ID Priority 8192, Address
3417.eb3a.f480 Configured hello time 2, max age 20,
forward delay 15
Flush Interval 200 centi-sec,
Flush Invocations 67
Flush Indication threshold 0 (MAC flush optimization is disabled) Interface Designated
Name PortID Prio Cost Sts Cost Brid ge ID PortID
port-channel1 128.2517 128 1000 FWD 1 8192 3417.eb3a.f480 128.2517
port-channel2 128.2518 128 1000 FWD 1 8192 3417.eb3a.f480
128.2518
Interface Name Role PortID Prio Cost Sts Cost Link-type Edge
OS10-VLT-Peer2#
LACP fallback in VLT

LACP fallback in a VLT configuration allows VLT peers the ability to control member ports of a port channel. It includes the following
characteristics:
• The LACP fallback feature is applied to support PXE boot from servers with NIC teaming or bonding.
• Use the lacp fallback enable command on the VLT port channels on both of the VLT nodes that are connected to servers.
• A member port in the VLT port channel is made active if the LACP PDUs are not received from the server within the LACP fallback
timeout period, which by default is set to 15 seconds.
• LACP fallback in VLT allows the PXE boot server to establish a connection over a single port, download the boot image, and continue
the boot process.
• After the server boots, it establishes the LACP port channel, which allows the VLT port channels to function like a regular VLT port
channel after the LACP PDUs are received.
• PXE boot uses untagged packets. Therefore, configure the VLT port channel as an untagged member in the respective VLAN to reach
the PXE/DHCP server.
• During LACP fallback, one VLT port channel member port is kept active, while other ports are kept in an inactive state.
The active port is selected based on the following order:
1. The port with the lowest LACP port priority is kept active.
2. The lowest port number is kept active if the port priority is the same or if it is the default port.
3. The port on the VLT node with the lowest system MAC address is kept active if the port numbers are the same in both VLT nodes.
Figure 4. LACP fallback
Best practices for VLT deployment

When deploying VLT, consider the following best practices:
• Both VLT peers require the same SmartFabric OS10 version within the production environment; however, a mismatch in versions is
acceptable during the upgrade procedure.
• Backup destination, or heartbeat connectivity, is recommended through the management network.
• Enable spanning tree to avoid unintentional loops in the network.
• Configure identical vlt-mac on both VLT peers to avoid VLT port channel flap during failure scenarios, such as VLTi flap and node
reboot.
• Increase the delay restore timer in a scaled VLAN configuration.
VLT Functionality 13
• Always deploy more than one link for VLTi port channel.
• Implement dynamic LACP for VLT port channels.
• Implement VLT nodes as the root bridge and the backup root bridge.
• Use the default active-active VRRP mode in VLT-VLANs.
• Configure symmetrical configurations on VLT port channels and VLT-VLANs on both VLT nodes.
• Identify and correct any mismatches reported by the show vlt mismatch command.
• For high availability, connect VLT port channels to the access nodes. Orphan ports that are connected directly to servers or switches
will fail if the connected node goes down.
3
VLT Configuration
The 1/1/9 and 1/1/10 interfaces form the discovery interface/VLTi (Po-1000) on the VLT Peer1. Similarly, the 1/1/1 and 1/1/2 interfaces
form the discovery interface on VLT Peer2. The VLT backup destination is mapped to the remote node management IP address. Port
channel 1 is configured on both VLT nodes as interface 1/1/21 and 1/1/13. VLAN 101-110 is mapped to port channel 1, with the VRRP group
1 configured for VLAN 101 using the virtual IP 101.1.1.254. Peer-routing is enabled on both VLT nodes.
Figure 5. VLT configuration
Topics:
• VLT configuration procedure
• FSB configuration on VLT network - example
• FC switch configuration on VLT network
VLT configuration procedure

About this task
Perform the following steps to configure VLT.
Steps
1. Use the no switchport command to configure the discovery-interfaces:
VLT Peer1 configuration
OS10-VLT-Peer1# configure terminal

OS10-VLT-Peer1(config)# interface ethernet 1/1/9
OS10-VLT-Peer1(conf-if-eth1/1/9)# no shutdown
OS10-VLT-Peer1(conf-if-eth1/1/9)# no switchport
OS10-VLT-Peer1(conf-if-eth1/1/9)# exit

OS10-VLT-Peer1(conf-if-eth1/1/10)#
VLT Configuration 15
OS10-VLT-Peer2# configure terminal

OS10-VLT-Peer2(conf-if-eth1/1/1)# exit

2. Configure the same VLT domain ID on both VLT peers.

OS10-VLT-Peer1(config)# vlt-domain 1
OS10-VLT-Peer1(conf-vlt-1)#
OS10-VLT-Peer2(config)# vlt-domain 1
3. Optionally, configure the primary priority to influence the primary election.

NOTE: The lower priority becomes the primary.
OS10-VLT-Peer1(conf-vlt-1)# primary-priority 1
OS10-VLT-Peer2(conf-vlt-1)# primary-priority 65535

4. Configure the same vlt-mac on both VLT peers:

OS10-VLT-Peer1(conf-vlt-1)# vlt-mac de:11:de:11:de:11

OS10-VLT-Peer2(conf-vlt-1)# vlt-mac de:11:de:11:de:11

5. Configure the VLTi links as discovery interfaces in both nodes:

OS10-VLT-Peer1(conf-vlt-1)# discovery-interface ethernet 1/1/9


6. Configure peer routing to make both VLT peers route traffic on behalf of each other.
NOTE: The configuration of peer-routing on both VLT peers is recommended for Layer 3 deployment.
16 VLT Configuration
OS10-VLT-Peer1(conf-vlt-1)# peer-routing
OS10-VLT-Peer2(conf-vlt-1)# peer-routing
7. Configure the backup destination on each VLT node as the IP address of the other peer.
NOTE: The configuration of the peer node management interface IP address is recommended.
OS10-VLT-Peer1(conf-vlt-1)# backup destination 10.16.208.184

OS10-VLT-Peer2(conf-vlt-1)# backup destination 10.16.208.181

8. Enter the following commands to check the status of both VLT nodes:
VLT Peer1 output
OS10-VLT-Peer1# show vlt 1

Domain ID : 1
Unit ID : 1
Role : primary
Version : 2.0
Local System MAC address : 14:18:77:98:48:f4
Role priority : 1
VLT MAC address : de:11:de:11:de:11
IP address : fda5:74c8:b79e:1::1
Delay-Restore timer : 90 seconds
Peer-Routing : Enabled
Peer-Routing-Timeout timer : 0 seconds VLTi Link Status
port-channel1000 : up
VLT Peer Unit ID System MAC Address Status IP Address version

14:18:77:98:3d:f4 up fda5:74c8:b79e:1::2 2.0
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1

Domain ID : 1
Unit ID : 2
Role : secondary
Version : 2.0
Local System MAC address : 14:18:77:98:3d:f4
Role priority : 65535
VLT MAC address : de:11:de:11:de:11
Peer-Routing : Enabled
Peer-Routing-Timeout timer : 0 seconds VLTi Link Status
port-
channel1000
: up
VLT Peer Unit ID System MAC Address Status IP Address Version

1 14:18:77:98:48:f4 up fda5:74c8:b79e:1::1 2.0 OS10-VLT-Peer2#
9. Check the VLTi link detail and status:
VLT Peer1 output
OS10-VLT-Peer1# show topology-map

TOPOLOGY MAP
Topology ID : 1
Topology Pattern : chain
Topology User : VLT
Local Unit ID : 1
Master Unit ID : 1
From-Interface|From-Interface|To-Interface|To-Interface |Link-Speed|Link-Status|
Unit ID | | Unit ID | | (Gb/s)
| |
1 |ethernet1/1/9 |2 |ethernet1/1/1 |10 |
up |
1 |ethernet1/1/10|2 |ethernet1/1/2 |10 |
up |
2 |ethernet1/1/1 |1 |ethernet1/1/9 |- |- |
2 |ethernet1/1/2 |1 |ethernet1/1/10|-
|- |
VLT Peer2 output
OS10-VLT-Peer2# show topology-map

TOPOLOGY MAP
Topology ID : 1
Topology Pattern : chain
Topology User : VLT
Local Unit ID : 2
Master Unit ID : 1
From-Interface|From-Interface|To-Interface|To-Interface |Link-Speed|Link-Status|
Unit ID | | Unit ID | | (Gb/s)
| |
1 |ethernet1/1/9 |2 |ethernet1/1/1 |-
|- |
1 |ethernet1/1/10|2 |ethernet1/1/2 |-
|- |
2 |ethernet1/1/1 |1 |ethernet1/1/9 |10 |
up |
2 |ethernet1/1/2 |1 |ethernet1/1/10|10 |
up |
10. Check the backup link status:

VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 backup-link VLT Backup Link

Destination : 10.16.208.184
Peer Heartbeat status : Up
Heartbeat interval : 30
Heartbeat timeout : 90 OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 backup-link VLT Backup Link

Heartbeat timeout : 90 OS10-VLT-Peer2#
11. Check the VLT role:

VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 role

VLT Unit ID Role
*1 primary
2 secondary
OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 role

VLT Unit ID Role
1 primary
*2 secondary
OS10-VLT-Peer2#
12. Configure the VLT port channel:

OS10-VLT-Peer1(config)# interface port-channel 1

OS10-VLT-Peer1(conf-if-po-1)# vlt-port-channel 1
OS10-VLT-Peer1(conf-if-po-1)#

OS10-VLT-Peer2(conf-if-po-1)# vlt-port-channel 1
13. Configure members to the VLT port channel:


OS10-VLT-Peer1(conf-if-eth1/1/21)# channel-group 1 mode active

OS10-VLT-Peer2(conf-if-eth1/1/13)# channel-group 1 mode active
14. Configure the VLT LAG status:

VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 vlt-port-detail vlt-port-channel ID : 1

VLT Unit ID Port-Channel Status Configured ports Active ports
* 1 port-channel1 up 1 1
2 port-channel1 up 1 1
OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 vlt-port-detail vlt-port-channel ID : 1

VLT Peer1 output
OS10-VLT-Peer1# show interface port-channel summary

LAG Mode Status Uptime Ports
1 L2-HYBRID up 00:10:36 Eth 1/1/21 (Up)
VLT Peer2 output
OS10-VLT-Peer2# show interface port-channel summary

LAG Mode Status Uptime Ports
1 L2-HYBRID up 00:10:00 Eth 1/1/13 (Up) OS10-VLT-Peer2#
15. Use the running-configuration command to check the VLT configuration:
VLT Peer1 output
OS10-VLT-Peer1# show running-configuration vlt

!
vlt-domain 1
backup destination 10.16.208.184 discovery-interface ethernet1/1/9-1/1/10 peer-routing
primary-priority 1
vlt-mac de:11:de:11:de:11
!
interface port-channel1 vlt-port-Phannel 1
VLT Peer2 output
OS10-VLT-Peer2# show running-configuration vlt

!
vlt-domain 1
backup destination 10.16.208.181 discovery-interface ethernet1/1/1-1/1/2 peer-routing
primary-priority 65535 vlt-mac de:11:de:11:de:11
!
interface port-channel1 vlt-port-channel 1
OS10-VLT-Peer2#
NOTE: As an option, you can use the following commands to delay the restore timer or to set the peer-routing
timeout:
OS10-VLT-Peer1(conf-vlt-1)# delay-restore 120

OS10-VLT-Peer1(conf-vlt-1)# peer-routing-timeout 240
OS10-VLT-Peer2(conf-vlt-1)# delay-restore 120

OS10-VLT-Peer2(conf-vlt-1)# peer-routing-timeout 240
OS10-VLT-Peer2(conf-vlt-1)
16. Enter the following commands to configure the VLAN on both VLT peers:
OS10-VLT-Peer1(config)# interface range vlan 101-110

OS10-VLT-Peer1(conf-range-vl-101-110)#
OS10-VLT-Peer2(config)# interface range vlan 101-110

OS10-VLT-Peer2(conf-range-vl-101-110)#
17. Use the following commands to add the VLT port channel to each VLAN:

OS10-VLT-Peer1(conf-if-po-1)# switchport mode trunk
OS10-VLT-Peer1(conf-if-po-1)# switchport trunk allowed vlan 101-110

OS10-VLT-Peer2(conf-if-po-1)# switchport mode trunk
OS10-VLT-Peer2(conf-if-po-1)# switchport trunk allowed vlan 101-110
18. Check the VLAN membership:
VLT Peer1 output
OS10-VLT-Peer1# show vlan

Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs
Q: A - Access (Untagged), T - Tagged
NUM Status Description Q Ports
1 Active A Eth1/1/1-
1/1/8,1/1/11-1/1/20,1/1/22-1/1/54
A Po1,1000
101 Active T Po1,1000

4094Active T Po1000
OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlan

Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs
Q: A - Access (Untagged), T - Tagged
NUM Status Description Q Ports
1 Active A Eth1/1/3-
1/1/12,1/1/14-1/1/54
A Po1,1000
4094Active T Po1000
OS10-VLT-Peer2#
19. Configure the IPv4 address for Layer 3 VLAN with VRRP:
OS10-VLT-Peer1(config)# interface vlan 101

OS10-VLT-Peer1(conf-if-vl-101)# ip address 101.1.1.1/24
OS10-VLT-Peer1(conf-if-vl-101)# vrrp-group 1
OS10-VLT-Peer1(conf-vlan101-vrid-1)# virtual-address 101.1.1.254
OS10-VLT-Peer1(conf-vlan101-vrid-1)#

OS10-VLT-Peer2(conf-if-vl-101)# ip address 101.1.1.2/24
OS10-VLT-Peer2(conf-if-vl-101)# vrrp-group 1
OS10-VLT-Peer2(conf-vlan101-vrid-1)# virtual-address 101.1.1.254
OS10-VLT-Peer2(conf-vlan101-vrid-1)#
20. Configure the IPv6 address for Layer 3 VLAN with VRRP:
OS10-VLT-Peer1(config)# vrrp version 3

OS10-VLT-Peer1(conf-if-vl-102)# ipv6 address 2001:102:1:1::1/64
OS10-VLT-Peer1(conf-if-vl-102)# vrrp-ipv6-group 1
OS10-VLT-Peer1(conf-vlan102-vrid-v6-1)# virtual-address fe80::102
OS10-VLT-Peer1(conf-vlan102-vrid-v6-1)# virtual-address 2001:102:1:1::ffff
OS10-VLT-Peer1(conf-vlan102-vrid-v6-1)#
OS10-VLT-Peer2(config)# vrrp version 3

OS10-VLT-Peer2(conf-if-vl-102)# ipv6 address 2001:102:1:1::2/64
OS10-VLT-Peer2(conf-if-vl-102)# vrrp-ipv6-group 1
OS10-VLT-Peer2(conf-vlan102-vrid-v6-1)# virtual-address fe80::102
OS10-VLT-Peer2(conf-vlan102-vrid-v6-1)# virtual-address 2001:102:1:1::ffff
OS10-VLT-Peer2(conf-vlan102-vrid-v6-1)#
21. Check for a VLT VLAN mismatch, which occurs when the VLT port-channel VLAN membership is different in both nodes:
VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 mismatch vlt-vlan

VLT VLAN mismatch:
vlt-port-channel ID : 1
VLT Unit ID Mismatch VLAN List
* 1 101
2 -
OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 mismatch vlt-vlan

VLT VLAN mismatch:
1 101
* 2 -
OS10-VLT-Peer2#
22. Check for a VLAN mismatch, which occurs in non-VLT or non-spanned VLANs when the VLAN does not exist in peer node:
VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 mismatch vlan

VLAN mismatch:
* 1 -
2 111
OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 mismatch vlan

VLAN mismatch:
1 -
* 2 111
OS10-VLT-Peer2#
23. Check for a VLT MAC mismatch, which occurs when vlt-mac is not identical or not configured in one node:
VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 mismatch vlt-mac

VLT-MAC mismatch:
VLT Unit ID vlt-mac
* 1 00:00:00:00:00:00
2 de:11:de:11:de:11 OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 mismatch vlt-mac

VLT-MAC mismatch:
VLT Unit ID vlt-mac
1 00:00:00:00:00:00
* 2 de:11:de:11:de:11 OS10-VLT-Peer2#
24. Check the peer routing configuration for a mismatch, which occurs when peer routing is configured only in one node:
VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 mismatch peer-routing

Peer-routing mismatch:
VLT Unit ID Peer-routing
* 1 Disabled
2 Enabled
OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 mismatch peer-routing

VLT Unit ID Peer-routing
1 Disabled
* 2 Enabled
OS10-VLT-Peer2#
25. Check for MAC inconsistency, which occurs when the MAC address is missing in one node, or points to a different port in each VLT
node:
VLT Peer1 output
OS10-VLT-Peer1# show vlt mac-inconsistency
Fetching MACs from unit 2

Identifying inconsistencies ..
VLAN 110
MAC 14:18:77:98:48:f4 destination port mismatch
At Node 1, MAC points to VLT Port 2
OS10-VLT-Peer1#
VLT Peer2 output

VLAN 110
MAC 14:18:77:98:48:f4 destination port mismatch
OS10-VLT-Peer2#
26. Enter the following commands to resolve a No Mismatch output from a normal functional state:
VLT Peer1 output
OS10-VLT-Peer1# show vlt 1 mismatch

VLT-MAC mismatch:
No mismatch
No mismatch
VLAN mismatch:
No mismatch
VLT VLAN mismatch:
No mismatch
OS10-VLT-Peer1#
VLT Peer2 output
OS10-VLT-Peer2# show vlt 1 mismatch

VLT-MAC mismatch:
No mismatch
No mismatch
VLAN mismatch:
No mismatch
VLT VLAN mismatch:

No mismatch
OS10-VLT-Peer2#
27. Enter the following commands to resolve a no MAC address inconsistency output from a normal functional state:
VLT Peer1 output

No inconsistencies found
OS10-VLT-Peer1#
VLT Peer2 output

No inconsistencies found
S10-VLT-Peer2#
28. Verify that the VLTi link spanning tree status is set in a FWD state:
VLT Peer1 output

VFP(VirtualFabricPort) of vlan 1 is Root Forwarding
Edge port: No (default)
Boundary: No, Bpdu-filter: Disable, Bpdu-Guard: Disable, Shutdown-on-Bpdu-Guard-
violation: No
Root-Guard: Disable, Loop-Guard: Disable Bpdus (MRecords) Sent: 16, Received: 60
Interface
Designated
Name PortID Prio Cost Sts Cost Bridge ID PortID
VFP 0.1 0 1 FWD 0 32769 1418.7798.3df4 0.1

violation: No
Bpdus (MRecords) Sent: 6, Received: 30
Interface
Designated
VFP 0.1 0 1 FWD 0 32869 1418.7798.3df4 0.1
violation: No
--more--
VLT Peer2 output

VFP(VirtualFabricPort) of vlan 1 is Designated Forwarding
violation: No
Root-Guard: Disable, Loop-Guard: Disable Bpdus (MRecords) Sent: 116, Received: 8
Interface
Designated
VFP 0.1 0 1 FWD 0 32769 1418.7798.3df4 0.1

VFP(VirtualFabricPort) of vlan 101 is Designated Forwarding
violation: No
Bpdus (MRecords) Sent: 58, Received: 2
Interface
Designated
VFP 0.1 0 1 FWD 0 32869 1418.7798.3df4 0.1

VFP(VirtualFabricPort) of vlan 102 is Designated Forwarding <<SNIP>>
FSB configuration on VLT network - example
About this task
Figure 6. VLT network with FCoE traffic and pinned ports
An example VLT configuration with pinned ports is provided in the following steps.
Steps
1. Enable the FIP snooping feature globally.
OS10-VLT-PEER1(config)# feature fip-snooping
2. Create the FCoE VLAN.
OS10-VLT-PEER1(config)#interface vlan 1001

OS10-VLT-PEER1(conf-if-vl-1001)# fip-snooping enable
3. Configure the VLTi interface.
OS10-VLT-PEER1(config)# interface ethernet 1/1/27

OS10-VLT-PEER1(conf-if-eth1/1/27)# no shutdown
OS10-VLT-PEER1(conf-if-eth1/1/27)# no switchport
4. Configure the VLT.
OS10-VLT-PEER1(config)# vlt-domain 1
OS10-VLT-PEER1(conf-vlt-1)# backup destination 10.16.151.110 <<Enter the management IP
address of the VLT peer>>
OS10-VLT-PEER1(conf-vlt-1)# discovery-interface ethernet1/1/27
5. Enable DCBX.
OS10-VLT-PEER1(config)# dcbx enable
6. Enable the PFC parameters on the interfaces.
OS10-VLT-PEER1(config)# class-map type network-qos fcoematch

OS10-VLT-PEER1(config-cmap-nqos)# match qos-group 3
OS10-VLT-PEER1(config-cmap-nqos)# exit
302 Fibre Channel
OS10-VLT-PEER1(config)# policy-map type network-qos PFC
OS10-VLT-PEER1(config-pmap-network-qos)# class fcoematch
OS10-VLT-PEER1(config-pmap-c-nqos)# pause
OS10-VLT-PEER1(config-pmap-c-nqos)# pfc-cos 3
7. Create uplink and downlink port channels, and configure the FCF facing port.
OS10-VLT-PEER1(config)# interface port-channel 10

OS10-VLT-PEER1(conf-if-po-10)# description uplink_VLT_LAG
OS10-VLT-PEER1(conf-if-po-10)# no shutdown
OS10-VLT-PEER1(conf-if-po-10)# switchport mode trunk
OS10-VLT-PEER1(conf-if-po-10)# switchport access vlan 1
OS10-VLT-PEER1(conf-if-po-10)# switchport trunk allowed vlan 1001,10
OS10-VLT-PEER1(conf-if-po-10)# vlt-port-channel 1
OS10-VLT-PEER1(conf-if-po-10)# fip-snooping port-mode fcf

OS10-VLT-PEER1(conf-if-po-20)# description downlink_VLT_LAG
OS10-VLT-PEER1(conf-if-po-20)# switchport trunk allowed vlan 1001,10
8. Apply the PFC configuration on downlink and uplink interfaces. In addition, include the interfaces to the port channel and configure one
of the interfaces as pinned-port.

OS10-VLT-PEER1(conf-if-eth1/1/1)# description uplink_port_channel_member1
OS10-VLT-PEER1(conf-if-eth1/1/1)# channel-group 10 mode active
OS10-VLT-PEER1(conf-if-eth1/1/1)# fcoe-pinned-port
OS10-VLT-PEER1(conf-if-eth1/1/1)# service-policy input type network-qos PFC
OS10-VLT-PEER1(conf-if-eth1/1/1)# priority-flow-control mode on

OS10-VLT-PEER1(conf-if-eth1/1/2)# description uplink_port_channel_member2

OS10-VLT-PEER1(conf-if-eth1/1/3)# description downlink_port_channel_member1
OS10-VLT-PEER1(conf-if-eth1/1/3)# fcoe-pinned-port

FC switch configuration on VLT network

About this task
An example FC switch configuration with VLT is provided in the following steps.
Steps
1. Enable the F_PORT mode.
OS10-VLT-PEER1(config)# feature fc domain-id 1
2. Create the FC zones.
OS10-VLT-PEER1(config)# fc zone zoneA

OS10-VLT-PEER1(config-fc-zone-zoneA)# member wwn 10:00:00:90:fa:b8:22:19 <<Enter the WWN
of Initiator CNA>>
OS10-VLT-PEER1(config-fc-zone-zoneA)# member wwn 21:00:00:24:ff:7b:f5:c8 <<Enter the WWN
of Target>>
3. Create the FC zoneset.
OS10-VLT-PEER1(config)# fc zoneset zonesetA

OS10-VLT-PEER1(conf-fc-zoneset-zonesetA)# member zoneA
4. Create the vfabric VLAN.
OS10-VLT-PEER1(config)# interface vlan 1001
5. Create vfabric and activate the FC zoneset.
OS10-VLT-PEER1(config)# vfabric 1
OS10-VLT-PEER1(conf-vfabric-1)# vlan 1001
OS10-VLT-PEER1(conf-vfabric-1)# fcoe fcmap 0xEFC00
OS10-VLT-PEER1(conf-vfabric-1)# zoneset activate zonesetA
6. Configure the VLTi interface.

7. Configure the VLT.
OS10-VLT-PEER1(config)# vlt-domain 10
OS10-VLT-PEER1(conf-vlt-10)# backup destination 10.16.151.110
OS10-VLT-PEER1(conf-vlt-10)# discovery-interface ethernet1/1/27
8. Enable DCBX.
OS10-VLT-PEER1(config)# dcbx enable
9. Apply the vfabric on the interfaces.

OS10-VLT-PEER1(conf-if-po-10)# description downlink_VLT_LAG_to FSB
OS10-VLT-PEER1(conf-if-po-10)# switchport trunk allowed vlan 10
OS10-VLT-PEER1(conf-if-po-10)# vfabric 1
OS10-VLT-PEER1(config)# interface fibrechannel 1/1/26
OS10-VLT-PEER1(conf-if-fc1/1/26)# description target_connected_port
OS10-VLT-PEER1(conf-if-fc1/1/26)# no shutdown
OS10-VLT-PEER1(conf-if-fc1/1/26)# vfabric 1
10. Apply the PFC configuration on the downlink interfaces. Include the interfaces to the port channel and configure one of the interfaces
as pinned-port.

OS10-VLT-PEER1(conf-if-eth1/1/9)# fcoe-pinned-por

OS10-VLT-PEER1(conf-if-eth1/1/10)# priority-flow-control mode on Fibre Channel 305
4
VLT Validation
The following table describes the commands used to validate VLT, and code examples of each are shown in the sections that follow.
Table 1. VLT validation commands

Validation parameter Command Line Interface
Domain ID - Verify that the domain ID is the same for each pair show running-configuration vlt
of switches
Unit ID - Verify the unit IDs on each switch of the pair show vlt <VLT_ID> - Look for Unit ID
Primary Priority - Verify the configured priorities on each switch show vlt <VLT_ID> role - Look for Role Priority
of the pair
Peer IP - Verify that the peer IP is configured according to the show vlt <VLT_ID> backup-link
plan
System MAC - Verify that the system MAC is configured show vlt <VLT_ID> - Look for the VLT MAC address
ICL Link Status (peer link) - Verify that the link is up show vlt <VLT_ID> - Look for the VLTi link status
HeartBeat Status - Verify that the status is up show vlt <VLT_ID> backup-link - Look for the peer heartbeat
status
Peer Status - Verify that the status is up show vlt <VLT_ID> - Look for the peer status in the table at the
bottom
Topics:
• show vlt 1
• show vlt 1 role
• show vlt 1 backup-link
• show vlt 1 vlt-port detail
• show interface brief
show vlt 1
S1# show vlt 1
Domain ID : 1
UnitID : 1
Role : primary
Version : 2.0
Local System MAC address: 74:e6:e2:f8:17:80
Role priority : 4096
VLT MAC address : 00:11:22:33:44:55
Peer-Routing : Disabled
Peer-Routing-Timeout timer : 0 seconds
VLTi Link Status
port-channel1000 : up
VLT Peer Unit ID System MAC Address Status IP Address Version

-------------------------------------------------------------------------------------------
2 64:00:6a:e1:7c:a0 up fda5:74c8:b79e:1::2 2.0
30 VLT Validation
show vlt 1 role
S1# show vlt 1 role
VLT Unit ID Role
--------------------------------------------------------------------------------------------
* 1 primary
2 secondary
show vlt 1 backup-link

S1# show vlt 1 backup-link
VLT Backup Link
--------------------------------------------------------------------------------------------
Heartbeat timeout : 90
show vlt 1 vlt-port detail

S1# show vlt 1 vlt-port-detail
--------------------------------------------------------------------------------------------
show interface brief

S1# show ip interface brief
Interface Name IP-Address OK Method Status Protocol
---------------------------------------------------------------------------------------------
Ethernet 1/1/1 unassigned YES unset up up
---------------------------------------------------------------------------------------------
output abbreviated
---------------------------------------------------------------------------------------------
Ethernet 1/1/48 unassigned NO unset up down
Ethernet 1/1/49 144.254.32.1/30 YES manual up up
Ethernet 1/1/50 192.168.16.1/30 YES manual up up
Management 1/1/1 192.168.1.1/24 YES DHCP up up
Vlan 1 unassigned YES unset up up
Loopback 0 192.168.77.1/32 YES manual up up
VLT Validation 31
A
Technical Resources
Topics:
• Dell Technologies Networking Guides
• Support and feedback
• Terminology
Dell Technologies Networking Guides

For additional information, see the following documentation:
Dell EMC PowerSwitch Guides
Dell EMC Networking Layer 3 Leaf-Spine Deployment and Best Practices with SmartFabric OS10
Dell EMC Networking Virtualization Overlay with BGP EVPN
ONIE User Guide
Dell Digital Locker (for the latest SmartFabric OS10 version)
OS10 Demo and Labs
Support and feedback
Technical support
For technical support, visit http://www.dell.com/support or call (USA) 1-800-945-3355.
Feedback for this document

We encourage readers to provide feedback on the quality and usefulness of this publication by sending an email to
Dell_Networking_Solutions@Dell.com.
Terminology
VLT domain - The domain includes VLT peer devices, VLT interconnects, and all port channels in the VLT connected to the attached
devices. It is also the configuration mode that you must use to assign VLT global parameters.
VLT interconnect (VLTi) - The link between VLT peer switches used to synchronize operating states.
VLT peer device - A pair of devices connected using a dedicated port channel—the VLTi. You must configure VLT peers separately.
Discovery interface - Interfaces on VLT peers in the VLT interconnect (VLTi) link.
VLT MAC address - Unique MAC address that you assign to the VLT domain. A VLT MAC address is a common address in both VLT
peers. If you do not configure a VLT MAC address, the MAC address of the primary peer is used as the VLT MAC address across both
peers.
VLT node priority - The priority based on which the primary and secondary VLT nodes are determined. If priority is not configured, the
VLT node with the lowest MAC address is elected as the primary VLT node.
VLT port channel - A combined port channel between an attached device and VLT peer switches.
32 Technical Resources
VLT port channel ID - Groups port channel interfaces on VLT peers into a single virtual-link trunk connected to an attached device.
Assign the same port channel ID to port channel interfaces on both peers that you bundle together.
Orphan ports - Ports that are not part of the VLT port channel but members of the spanned VLANs. The term spanned VLAN refers to a
VLAN that is configured on both the VLT peers.
Technical Resources 33

Smartfabric Os10 Virtual Link Trunking Ra

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Smartfabric Os10 Virtual Link Trunking Ra

Uploaded by

Copyright:

Available Formats

Dell EMC SmartFabric OS10 - Virtual Link

Dell Technologies Networking Infrastructure Solutions

Part Number: H18362

Virtual link trunking overview

Dell Technologies vision

Monospace text CLI examples

Important points to remember:

Peer routing timeout

Figure 1. Peer routing

eVLT in SmartFabric OS10

Split control scenario

Spanning tree protocol with VLT

Spanning tree configuration

OS10-VLT-Peer1(config)# spanning-tree mode rapid-pvst

OS10-VLT-Peer1(config)# spanning-tree mode rstp

OS10-VLT-Peer1(config)# spanning-tree vlan 2 priority 4096

OS10-VLT-Peer2(config)# spanning-tree vlan 2 priority 8192

OS10-VLT-Peer1(config)# spanning-tree rstp priority 4096

OS10-VLT-Peer1# show spanning-tree virtual-interface VFP(VirtualFabricPort) of RSTP 1 is

Bpdus (MRecords) Sent: 1083, Received: 3 Interface

VFP(VirtualFabricPort) 0.1 0 1 FWD 0

OS10-VLT-Peer2# show spanning-tree virtual-interface

VFP(VirtualFabricPort) 0.1 0 1 FWD 0

OS10-VLT-Peer1(conf-if-eth1/1/45)# spanning-tree port type edge OS10-VLT-Peer2(conf-if-

OS10-VLT-Peer1# show spanning-tree active

Name PortID Prio Cost Sts Cost Brid ge ID PortID

OS10-VLT-Peer2# show spanning-tree active

LACP fallback in VLT

Figure 4. LACP fallback

Best practices for VLT deployment

Figure 5. VLT configuration

VLT configuration procedure

OS10-VLT-Peer1# configure terminal

OS10-VLT-Peer1(config)# interface ethernet 1/1/10

OS10-VLT-Peer2# configure terminal

OS10-VLT-Peer2(config)# interface ethernet 1/1/2

2. Configure the same VLT domain ID on both VLT peers.

VLT Peer2 configuration

3. Optionally, configure the primary priority to influence the primary election.

VLT Peer1 configuration

VLT Peer2 configuration

OS10-VLT-Peer2(conf-vlt-1)# primary-priority 65535

4. Configure the same vlt-mac on both VLT peers:

OS10-VLT-Peer1(conf-vlt-1)# vlt-mac de:11:de:11:de:11

VLT Peer2 configuration

OS10-VLT-Peer2(conf-vlt-1)# vlt-mac de:11:de:11:de:11

5. Configure the VLTi links as discovery interfaces in both nodes:

OS10-VLT-Peer1(conf-vlt-1)# discovery-interface ethernet 1/1/9

VLT Peer2 configuration

OS10-VLT-Peer2(conf-vlt-1)# discovery-interface ethernet 1/1/1

VLT Peer2 configuration

VLT Peer1 configuration

OS10-VLT-Peer1(conf-vlt-1)# backup destination 10.16.208.184

VLT Peer2 configuration

OS10-VLT-Peer2(conf-vlt-1)# backup destination 10.16.208.181

OS10-VLT-Peer1# show vlt 1

VLT Peer Unit ID System MAC Address Status IP Address version

VLT Peer2 output

OS10-VLT-Peer2# show vlt 1

VLT Peer Unit ID System MAC Address Status IP Address Version

9. Check the VLTi link detail and status:

OS10-VLT-Peer1# show topology-map

VLT Peer2 output