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.

Junos ®<br />

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

Related<br />

Documentation<br />

•<br />

unit 0 {<br />

vlan-id 100;<br />

}<br />

}<br />

802.1Q VLANs Overview on page 53<br />

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

Guidelines for Configuring VLAN ID List-Bundled Logical <strong>Interfaces</strong> That Connect CCCs<br />

For MX Series routers, you can bind a list of VLAN IDs to a logical interface, configure a<br />

Layer 2 VPN routing instance or Layer 2 circuit on the logical interface, and then use the<br />

logical interface to configure a circuit cross-connect (CCC) to another Layer 2 VPN routing<br />

instance or Layer 2 circuit.<br />

A CCC allows you to configure transparent connections between two circuits so that<br />

packets from the source circuit are delivered to the destination circuit with, at most, the<br />

Layer 2 address being changed. You configure a CCC by connecting circuit interfaces of<br />

the same type. For more information, see Circuit and Translational Cross-Connects<br />

Overview.<br />

NOTE: The Junos <strong>OS</strong> supports binding of <strong>Ethernet</strong> logical interfaces to lists<br />

of VLAN IDs on MX Series routers only. For all other routers, you can bind an<br />

<strong>Ethernet</strong> logical interface to only a single VLAN ID or to a single range of VLAN<br />

IDs.<br />

The following configuration guidelines apply to bundling lists of VLAN IDs to <strong>Ethernet</strong><br />

logical interfaces used to configure CCCs:<br />

• Guidelines for Configuring Physical Link-Layer Encapsulation to Support<br />

CCCs on page 68<br />

• Guidelines for Configuring Logical Link-Layer Encapsulation to Support CCCs on page 69<br />

Guidelines for Configuring Physical Link-Layer Encapsulation to Support CCCs<br />

68<br />

To enable a physical interface to support VLAN-bundled logical interfaces that you will<br />

use to configure a CCC, you must specify one of the following physical link-layer<br />

encapsulation types as the value of the encapsulation statement at the [edit interfaces<br />

interface-name] hierarchy level:<br />

[edit interfaces interface-name]<br />

encapsulation (extended-vlan-ccc | flexible-ethernet-services);<br />

• extended-vlan-ccc—For <strong>Ethernet</strong> interfaces with standard TPID tagging.<br />

• flexible-ethernet-services—For supported Gigabit <strong>Ethernet</strong> interfaces for which you<br />

want to configure multiple per-unit <strong>Ethernet</strong> encapsulations.<br />

For more information about configuring the encapsulation on a physical interface, see<br />

Configuring Interface Encapsulation on Physical <strong>Interfaces</strong>.<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!