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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Junos ®<br />

<strong>OS</strong> 12.3 <strong>Ethernet</strong> <strong>Interfaces</strong> <strong>Configuration</strong> Guide<br />

vlan-id number;<br />

}<br />

output-vlan-map {<br />

(pop | push | swap);<br />

tag-protocol-id tpid;<br />

vlan-id number;<br />

}<br />

You can include these statements at the following hierarchy levels:<br />

• [edit interfaces interface-name unit logical-unit-number]<br />

• [edit logical-systems logical-system-name interfaces interface-name unit<br />

logical-unit-number]<br />

The VLAN IDs you define in the input VLAN maps are stacked on top of the VLAN ID<br />

bound to the logical interface. For more information about binding a VLAN ID to the logical<br />

interface, see “802.1Q VLANs Overview” on page 53.<br />

All TPIDs you include in input and output VLAN maps must be among those you specify<br />

at the [edit interfaces interface-name gigether-options ethernet-switch-profile<br />

tag-protocol-id [ tpids ]] hierarchy level or [edit interfaces interface-name<br />

aggregated-ether-options ethernet-switch-profile tag-protocol-id [ tpids ]] hierarchy level.<br />

For more information, see “Configuring Frames with Particular TPIDs to Be Processed as<br />

Tagged Frames” on page 133.<br />

Table 10 on page 136 and Table 11 on page 137 specify when these statements are required.<br />

Table 10 on page 136 indicates valid statement combinations for rewrite operations for<br />

the input VLAN map. “No” means the statement must not be included in the input VLAN<br />

map for the rewrite operation. “Optional” means the statement may be optionally specified<br />

for the rewrite operation in the input VLAN map. “Any” means that you must include the<br />

vlan-id statement, tag-protocol-id statement, inner-vlan-id statement, or<br />

inner-tag-protocol-id statement.<br />

Table 10: Rewrite Operations and Statement Usage for Input VLAN Maps<br />

136<br />

Rewrite Operation<br />

push<br />

pop<br />

swap<br />

push-push<br />

swap-push<br />

swap-swap<br />

pop-swap<br />

Input VLAN Map Statements<br />

vlan-id<br />

Optional<br />

No<br />

Any<br />

Optional<br />

Optional<br />

Optional<br />

No<br />

tag-protocol-id<br />

Optional<br />

No<br />

Any<br />

Optional<br />

Optional<br />

Optional<br />

No<br />

inner-vlan-id<br />

No<br />

No<br />

No<br />

Optional<br />

Any<br />

Any<br />

Any<br />

inner-tag-protocol-id<br />

No<br />

No<br />

No<br />

optional<br />

Any<br />

Any<br />

Any<br />

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

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

Saved successfully!

Ooh no, something went wrong!