Dell PowerConnect B-RX - Configuration Rules

312 BigIron RX Series Configuration Guide
53-1002253-01
Configuring 802.1q tag-type translation
11
FIGURE 29 802.1q tag-type translation configuration example 2
As illustrated in 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).
For more information, refer to “Configuring 802.1q tag-type translation” on page 310.
Configuration rules
• 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 Edge Switch 3
Edge Switch 1
Core Switch 1 Core Switch 2
Edge Switch 4
8200 8200
8500
8500
8400
9100
9100
8400
8200
8300
8200
8300
T
T
T
T
U
T
T
T
U
T
T
Global 802.1Q
tag-type
8200
Global 802.1Q
tag-type
8200
Global 802.1Q
tag-type
8500
Multiple
802.1Q
tag-types
Multiple
802.1Q
tag-types
Global 802.1Q
tag-type
8500
Path A
Path B
Incoming Frame
on Core Switch 1
Outgoing Frame
on Core Switch 1
Outgoing Frame
on Core Switch 2
DA SA 8500
Customer
VLAN
DA SA 8200
Customer
VLAN
DA SA 9100
Provider
VLAN
DA SA 9100
Provider
VLAN
8500
DA SA 8500
Customer
VLAN
DA SA 8200
Customer
VLAN
T - Tagged port
U - Untagged port
DMA or port group
Path A
Path B
-
XXXX
Legend: