304 BigIron RX Series Configuration Guide53-1001810-01Configuring 802.1q tag-type translation11Figure 29 shows a more complex example application in which some ports are untagged, not alltag-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.FIGURE 29 802.1q tag-type translation configuration example 2As 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 8500tag-type in the frame header (because the incoming port on Core Switch 1 is untagged) andadds the 9100 tag-type as it sends the packet to the uplink (Core Switch 2). In this case, thepacket 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 the8200 tag-type and replaces (translates) it with the 9100 tag-type as it sends the packet to theuplink (Core Switch 2).For more information, refer to “Configuring 802.1q tag-type translation” on page 302.Configuration rules• On the supported devices, you configure 802.1q tag-types per port region. Use the showrunning-config command at any level of the CLI to view port regions. Note that on GigabitEthernet modules, ports 1 and 2 belong to the same port region.Edge Switch 2 Edge Switch 3Edge Switch 1 Core Switch 1 Core Switch 2 Edge Switch 48200 82008500850084009100910084008200830082008300TTTTUTTT UTTGlobal 802.1Qtag-type8200Global 802.1Qtag-type8200Global 802.1Qtag-type8500Multiple802.1Qtag-typesMultiple802.1Qtag-typesGlobal 802.1Qtag-type8500Path APath BIncoming Frameon Core Switch 1Outgoing Frameon Core Switch 1Outgoing Frameon Core Switch 2DA SA 8500 CustomerVLANDA SA 8200 CustomerVLAN DA SA 9100 ProviderVLANDA SA 9100 ProviderVLAN8500 DA SA 8500 CustomerVLANDA SA 8200 CustomerVLANT - Tagged portU - Untagged portDMA or port groupPath APath B-XXXXLegend:
