Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) - Manual (Page 218)

188 Multi-Service IronWare Switching Configuration Guide
53-1003036-02
Configuring 802.1q tag-type translation
7
FIGURE 16 802.1q Tag-type translation configuration example 1
As illustrated in Figure 16 , 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 16 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 17 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.