To Next Page

To Previous Page

•

If you configure an MTU for an ATM cell relay interface on an ATM II PIC, the configured

MTU is used to compute the cell bundle size advertised for that Layer 2 circuit, instead

of the default interface MTU.

•

A configured MTU is used only in the control plane. It is not enforced in the data plane.

You need to ensure that the CE device for a given Layer 2 circuit uses the correct MTU

for data transmission.

To configure the MTU for a Layer 2 circuit, include the mtu statement at the [edit protocols

l2circuit neighbor address interface interface-name] hierarchy level.

mtu mtu-number;

Documentation

Configuring Interfaces for Layer 2 Circuits Overview on page 774•

• Enabling the Layer 2 Circuit When the MTU Does Not Match on page 780

• Configure the Layer 2 Circuit on page 196

Configuring the Protect Interface

You can configure a protect interface for the logical interface linking a virtual circuit to

its destination, whether the destination is remote or local. A protect interface provides

a backup for the protected interface in case of failure. Network traffic uses the primary

interface only so long as the primary interface functions. If the primary interface fails,

traffic is switched to the protect interface. The protect interface is optional.

To configure the protect interface, include the protect-interface statement:

protect-interface interface-name;

For a list of hierarchy levels at which you can include this statement, see the statement

summary section for this statement.

Documentation

Example: Configuring Layer 2 Circuit Protect Interfaces•

Configuring the Virtual Circuit ID

You configure a virtual circuit ID on each interface. Each virtual circuit ID uniquely identifies

the Layer 2 circuit among all the Layer 2 circuits to a specific neighbor. The key to

identifying a particular Layer 2 circuit on a PE router is the neighbor address and the virtual

circuit ID. An LDP-FEC-to-label binding is associated with a Layer 2 circuit based on the

virtual circuit ID in the FEC and the neighbor that sent this binding. The LDP-FEC-to-label

binding enables the dissemination of the VPN label used for sending traffic on that Layer 2

circuit to the remote CE device. When an LDP peer sends a Label Withdraw message for

a Layer 2 circuit FEC with a non zero group ID, the Junos OS software sends the Label

Release message with the group ID for the Layer 2 circuit associated with the FEC.

You also configure a virtual circuit ID for each redundant pseudowire. A redundant

pseudowire is identified by the backup neighbor address and the virtual circuit ID.

ACX Series Universal Access Router Configuration Guide

Juniper ACX2000 Configuration Guide

Other manuals for Juniper ACX2000