Debugging VLAN Stacking
To debug VLAN stacking, use the following command.
• Debug the internal state and membership of a VLAN and its ports.
debug member
Example of Debugging a VLAN and its Ports
The port notations are as follows:
•
MT
— stacked trunk
•
MU
— stacked access port
•
T
— 802.1Q trunk port
•
U
— 802.1Q access port
•
NU
— Native VLAN (untagged)
Dell# debug member vlan 603
vlan id : 603
ports : Te 2/4 (MT), Te 3/1(MU), Te 3/25(MT), Te 3/26(MT), Te 3/27(MU)
Dell#debug member port tengigabitethernet 2/4
vlan id : 603 (MT), 100(T), 101(NU)
Dell#
VLAN Stacking in Multi-Vendor Networks
The first field in the VLAN tag is the tag protocol identifier (TPID), which is 2 bytes. In a VLAN-stacking
network, after the frame is double tagged, the outer tag TPID must match the TPID of the next-hop
system.
While 802.1Q requires that the inner tag TPID is 0x8100, it does not require a specific value for the outer
tag TPID. Systems may use any 2-byte value; Dell Networking OS uses 0x9100 (shown in the following)
while non-Dell Networking systems might use a different value.
If the next-hop system’s TPID does not match the outer-tag TPID of the incoming frame, the system
drops the frame. For example, as shown in the following, the frame originating from Building A is tagged
VLAN RED, and then double-tagged VLAN PURPLE on egress at R4. The TPID on the outer tag is 0x9100.
R2’s TPID must also be 0x9100, and it is, so R2 forwards the frame.
Given the matching-TPID requirement, there are limitations when you employ Dell Networking systems
at network edges, at which, frames are either double tagged on ingress (R4) or the outer tag is removed
on egress (R3).
VLAN Stacking
The default TPID for the outer VLAN tag is 0x9100. The system allows you to configure both bytes of the
2 byte TPID.
Previous versions allowed you to configure the first byte only, and thus, the systems did not differentiate
between TPIDs with a common first byte. For example, 0x8100 and any other TPID beginning with 0x81
were treated as the same TPID, as shown in the following illustration. Dell Networking OS Versions 8.2.1.0
and later differentiate between 0x9100 and 0x91XY, also shown in the following illustration.
Service Provider Bridging
903
Summary of Contents for S4820T
Page 1: ...Dell Configuration Guide for the S4820T System 9 8 0 0 ...
Page 282: ...Dell 282 Control Plane Policing CoPP ...
Page 622: ...Figure 81 Configuring Interfaces for MSDP 622 Multicast Source Discovery Protocol MSDP ...
Page 623: ...Figure 82 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 623 ...
Page 629: ...Figure 86 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 629 ...
Page 630: ...Figure 87 MSDP Default Peer Scenario 3 630 Multicast Source Discovery Protocol MSDP ...
Page 751: ...10 11 5 2 00 00 05 00 02 04 Member Ports Te 1 2 1 PIM Source Specific Mode PIM SSM 751 ...
Page 905: ...Figure 112 Single and Double Tag First byte TPID Match Service Provider Bridging 905 ...
Page 979: ...6 Member not present 7 Member not present Stacking 979 ...
Page 981: ...storm control Storm Control 981 ...
Page 1103: ...Figure 134 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 1103 ...