Dell PowerConnect B-RX BigIron RX Series Configuration Guide v02.8.00 - Page 387

Configuring 802.1q tag-type translation 11 FIGURE 28 802.1q tag-type translation configuration example 1 Network Core Customer Edge Switch 1 Provider Core Switch 1 Provider Core Switch 2 Customer Edge Switch 2 Tagged 8100 Tagged 9100 Tagged 8100 Tagged 8100 Tagged 9100 Tagged 8100 DA SA 8100 Customer VLAN DA SA 9100 Provider VLAN DA SA 8100 Customer VLAN As illustrated in Figure 28, the devices process the packet as follows: • Customer Edge Switch 1 sends a packet with an 802.1q tag-type of 8100 to Provider Core Switch 1. • Since the customer-facing interface on Provider Core Switch 1 has the same 802.1q tag-type as the incoming packet, it removes the 8100 tag-type and replaces (translates) it with the 9100 tag-type as it sends the packet to the uplink (Provider Core Switch 2). • The same process occurs between Provider Core Switch 2 and Customer Edge Switch 2. Figure 28 shows a simple application of the 802.1q tag-type translation in which all of the ports are tagged and the tag-types between devices match. In this example, each device performs the 802.1q tag-type translation as the packet traverses the network. Figure 29 shows a more complex example application in which some ports are untagged, not all tag-types between devices match, and the core devices have multiple tag-types. In this example, the tag-type translation feature integrates packets that have single and double tag-types. BigIron RX Series Configuration Guide 311 53-1002253-01