Service Manual

Description Behavior at Peer Up Behavior During Run Time Action to Take
Unit ID mismatch
The VLT peer does not boot
up. The VLTi is forced to a
down state.
A syslog error message is
generated.
The VLT peer does not boot
up. The VLTi is forced to a
down state.
A syslog error message is
generated.
Verify the unit ID is correct on
both VLT peers. Unit ID
numbers must be sequential on
peer units; for example, if Peer
1 is unit ID “0”, Peer 2 unit ID
must be “1’.
Version ID mismatch A syslog error message and an
SNMP trap are generated.
A syslog error message and an
SNMP trap are generated.
Verify the Dell Networking OS
software versions on the VLT
peers is compatible. For more
information, refer to the
Release Notes for this release.
VLT LAG ID is not congured
on one VLT peer
A syslog error message is
generated. The peer with the
VLT congured remains active.
A syslog error message is
generated. The peer with the
VLT congured remains active.
Verify the VLT LAG ID is
congured correctly on both
VLT peers.
VLT LAG ID mismatch
The VLT port channel is
brought down.
A syslog error message is
generated.
The VLT port channel is
brought down.
A syslog error message is
generated.
Perform a mismatch check
after the VLT peer is
established.
Reconguring Stacked Switches as VLT
To convert switches that have been stacked to VLT peers, use the following procedure.
1. Remove the current conguration from the switches. You will need to split the conguration up for each switch.
2. Copy the les to the ash memory of the appropriate switch.
3. Copy the les on the ash drive to the startup-cong.
4. Reset the stacking ports to user ports for both switches.
5. Reload the stack and conrm the new congurations have been applied.
6. On the Secondary switch (stack-unit1), enter the command stack-unit1 renumber 0.
7. Conrm the reload query.
8. After reloading, conrm that VLT is enabled.
9. Conrm that the management ports are interconnected or connected to a switch that can transfer Heartbeat information.
Specifying VLT Nodes in a PVLAN
You can congure VLT peer nodes in a private VLAN (PVLAN). VLT enables redundancy without the implementation of Spanning
Tree Protocol (STP), and provides a loop-free network with optimal bandwidth utilization.
Because the VLT LAG interfaces are terminated on two dierent nodes, PVLAN conguration of VLT VLANs and VLT LAGs are
symmetrical and identical on both the VLT peers. PVLANs provide Layer 2 isolation between ports within the same VLAN. A PVLAN
partitions a traditional VLAN into sub-domains identied by a primary and secondary VLAN pair. With VLT being a Layer 2
redundancy mechanism, support for conguration of VLT nodes in a PVLAN enables Layer 2 security functionalities. To achieve
maximum VLT resiliency, you should congure the PVLAN IDs and mappings to be identical on both the VLT peer nodes.
The association of PVLAN with the VLT LAG must also be identical. After the VLT LAG is congured to be a member of either the
primary or secondary PVLAN (which is associated with the primary), ICL becomes an automatic member of that PVLAN on both
switches. This association helps the PVLAN data ow received on one VLT peer for a VLT LAG to be transmitted on that VLT LAG
from the peer.
Virtual Link Trunking (VLT)
829