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

Multi-Service IronWare Switching Configuration Guide 189
53-1003036-02
Configuring 802.1q tag-type translation
7
FIGURE 17 802.1q Tag-type translation configuration example 2
As illustrated in Figure 17 , 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).
Configuration rules
Configuration of tag-type ports on the Brocade device are on a per-port basis and follow the same
rules as described in
“Configuration rules” .