Configuration Rules - Dell PowerConnect B-RX Configuration Manual

11
Configuring 802.1q tag-type translation
FIGURE 29
Path A
Path B
As illustrated in
•
•
For more information, refer to

Configuration rules

•
•
312
802.1q tag-type translation configuration example 2
Global 802.1Q
T
tag-type
U
8500
Edge Switch 1
Incoming Frame
on Core Switch 1
DA SA 8500 Customer
VLAN
DA SA 8200 Customer
VLAN
Figure 29, the devices process the packets as follows:
Path A: When Core Switch 1 receives the tagged packet from Edge Switch 1, it keeps the 8500
tag-type in the frame header (because the incoming port on Core Switch 1 is untagged) and
adds the 9100 tag-type as it sends the packet to the uplink (Core Switch 2). In this case, the
packet is double-tagged as it travels between the core devices.
Path B: When Core Switch 1 receives the tagged packet from Edge Switch 2, it removes the
8200 tag-type and replaces (translates) it with the 9100 tag-type as it sends the packet to the
uplink (Core Switch 2).
On the supported devices, you configure 802.1q tag-types per port region. Use the show
running-config command at any level of the CLI to view port regions. Note that on Gigabit
Ethernet modules, ports 1 and 2 belong to the same port region.
Since the uplink (to the provider cloud) and the edge link (to the customer port) must have
different 802.1q tag-types, make sure the uplink and edge link are in different port regions.
Edge Switch 2
Global 802.1Q
tag-type
8200
8200
T
T
8200
Multiple
T
T
802.1Q
tag-types
T
8300
Core Switch 1
Outgoing Frame
on Core Switch 1
Provider
DA SA 9100 8500
VLAN
DA SA 9100 Provider
VLAN
"Configuring 802.1q tag-type translation"
Edge Switch 3
Global 802.1Q
tag-type
8200
8200
T
T
8200
Multiple
T
802.1Q
tag-types
U
8300
Core Switch 2
Outgoing Frame
on Core Switch 2
DA SA 8500 Customer
VLAN
DA SA 8200 Customer
VLAN
Legend:
T - Tagged port
U - Untagged port
-
XXXX
Path A
Path B
on page 310.
BigIron RX Series Configuration Guide
Global 802.1Q
tag-type
8500
Edge Switch 4
DMA or port group
53-1002253-01