21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• For more information about binding a VLAN ID to the logical interface, see 802.1Q<br />

VLANs Overview on page 53.<br />

• For more information about the swap operation, see Examples: Stacking and Rewriting<br />

Gigabit <strong>Ethernet</strong> IQ VLAN Tags on page 147.<br />

• <strong>Junos®</strong> <strong>OS</strong> <strong>Ethernet</strong> <strong>Interfaces</strong><br />

Rewriting a VLAN Tag on Untagged Frames<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

On M320, M120, and MX Series routers with Gigabit <strong>Ethernet</strong> IQ, IQ2, and IQ2E PICs,<br />

10-Gigabit <strong>Ethernet</strong> IQ, IQ2, and IQ2E PICs, and on MX Series 40-port Gigabit <strong>Ethernet</strong><br />

R, 40-port Gigabit <strong>Ethernet</strong> R EQ, 4-port 10-Gigabit <strong>Ethernet</strong> R, and 4-port 10-Gigabit<br />

<strong>Ethernet</strong> R EQ DPCs, you can rewrite VLAN tags on untagged incoming and outgoing<br />

frames under ethernet-ccc and ethernet-vpls encapsulations. On MX Series routers with<br />

IQ2 and IQ2-E PICs, you can perform all rewrite VLAN tag operations. These features<br />

provide added flexibility.<br />

Consider a network where two provider edges (PE) are connected by a Layer 2 circuit.<br />

PE1 is receiving traffic on an untagged port while the corresponding port on PE2 is tagged.<br />

In the normal case, packets coming from PE1 will be dropped at PE2 because it is expecting<br />

tagged packets. However, if PE1 can push a VLAN tag on the incoming packet before<br />

sending it across to PE2, you can ensure that packets are not dropped. To make it work<br />

in both directions, PE1 must strip the VLAN tag from outgoing packets. Therefore, a push<br />

on the ingress side is always paired with a pop on the egress side.<br />

The rewrite operations represented by the following statement options are supported<br />

under ethernet-ccc and ethernet-vpls encapsulations:<br />

• push—A VLAN tag is added to the incoming untagged frame.<br />

• pop—VLAN tag is removed from the outgoing frame.<br />

• push-push—An outer and inner VLAN tag are added to the incoming untagged frame.<br />

• pop-pop—Both the outer and inner VLAN tags of the outgoing frame are removed.<br />

IQ2 and 10-Gigabit <strong>Ethernet</strong> PICs support all rewrite operations described above. Details<br />

on the possible combinations of usage are explained later in this section.<br />

NOTE: The push-push and pop-pop operations are not supported on the<br />

Gigabit <strong>Ethernet</strong> IQ PIC.<br />

For the input-vlan-map statement, only the push and push-push options are supported<br />

because it does not make sense to remove a VLAN tag from an incoming untagged frame.<br />

Similarly, only the pop and pop-pop options are supported for the output-vlan-map<br />

statement. Also, with the push and push-push options, the tag parameters have to be<br />

explicitly specified. Apart from this, the other rules for configuring the input-vlan-map<br />

and output-vlan-map statements are the same as for tagged frames. Table 12 on page 144<br />

through Table 14 on page 144 explain the rules in more detail.<br />

Chapter 5: Stacking and Rewriting Gigabit <strong>Ethernet</strong> VLAN Tags<br />

143

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!