Configuring Interfaces for VPLS Routing

On each PE router and for each VPLS routing instance, specify which interfaces are intended for the VPLS traffic traveling between PE and CE routers. To specify the interface for VPLS traffic, include the interface statement in the routing instance configuration:

interface interface-name;

You can include this statement at the following hierarchy levels:

You must also define each interface by including the following statements:

vlan-tagging;encapsulation encapsulation-type;unit logical-unit-number {vlan-id vlan-id-number;family vpls;}

You can include these statements at the following hierarchy levels:

The following sections provide enough information to enable you to configure interfaces for VPLS routing. For detailed information about configuring interfaces and the statements at the [edit interfaces] hierarchy level, see the Junos Network Interfaces Configuration Guide.

To configure an interface for VPLS, you perform the steps in the following sections:

Configuring the Interface Name

Specify both the physical and logical portions of the interface name, in the following format:

physical.logical

For example, in ge-1/2/1.2, ge-1/2/1 is the physical portion of the interface name and 2 is the logical portion. If you do not specify the logical portion of the interface name, 0 is set by default.

A logical interface can be associated with only one routing instance.

If you enable a routing protocol on all instances by specifying interfaces all when configuring the master instance of the protocol at the [edit protocols] hierarchy level, and you configure a specific interface for VPLS routing at the [edit routing-instances routing-instance-name] hierarchy level, the latter interface statement takes precedence and the interface is used exclusively for VPLS.

If you explicitly configure the same interface name at both the [edit protocols] and [edit routing-instances routing-instance-name] hierarchy levels and then attempt to commit the configuration, the commit operation fails.

Configuring the VPLS Interface Encapsulation

You need to specify an encapsulation type for each PE-router-to-CE-router interface configured for VPLS. This section describes the encapsulation statement configuration options available for VPLS. For a full description of all of the options available for this statement, see the Junos Network Interfaces Configuration Guide.

To configure the encapsulation type on the physical interface, include the encapsulation statement:

encapsulation (ethernet-vpls | extended-vlan-vpls | vlan-vpls);

You can include the encapsulation statement for physical interfaces at the following hierarchy levels:

You can configure the following physical interface encapsulations for VPLS routing instances:

To configure the encapsulation type for logical interfaces, include the encapsulation statement:

encapsulation (ether-vpls-over-atm-llc | vlan-vpls);

You can include the encapsulation statement for logical interfaces at the following hierarchy levels:

You can configure the following logical interface encapsulations for VPLS routing instances:

When you configure the physical interface encapsulation as vlan-vpls, you also need to configure the same interface encapsulation for the logical interface. You need to configure the vlan-vpls encapsulation on the logical interface because the vlan-vpls encapsulation allows you to configure a mixed mode, where some of the logical interfaces use regular Ethernet encapsulation (the default for logical interfaces) and some use vlan-vpls. For more information, see the Junos Network Interfaces Configuration Guide.

Enabling VLAN Tagging

The Junos OS supports receiving and forwarding routed Ethernet frames with 802.1Q virtual local area network (VLAN) tags and running Virtual Router Redundancy Protocol (VRRP) over 802.1Q-tagged interfaces. For VPLS to function properly, configure the router to receive and forward frames with 802.1Q VLAN tags by including the vlan-tagging statement at the [edit interfaces interface-name] hierarchy level:

[edit interfaces interface-name]vlan-tagging;

Gigabit Ethernet interfaces can be partitioned; you can assign up to 4095 different logical interfaces, one for each VLAN, but you are limited to a maximum of 1024 VLANs on any single Gigabit Ethernet or 10-Gigabit Ethernet port. Fast Ethernet interfaces can also be partitioned, with a maximum of 1024 logical interfaces for the 4-port FE PIC and 16 logical interfaces for the M40e router. Table 10 lists VLAN ID range by interface type.

Table 10: VLAN ID Range by Interface Type

Interface Type

VLAN ID Range

Fast Ethernet

512 through 1023

Gigabit Ethernet

512 through 4094

Configuring VLAN IDs for Logical Interfaces

You can configure a logical interface to forward packets and learn MAC addresses within each VPLS routing instance configured with a VLAN ID. To bind a VLAN ID to a logical interface, include the vlan-id statement:

vlan-id number;

You can include this statement at the following hierarchy levels:

You can also configure a logical interface to forward packets and learn MAC addresses within each VPLS routing instance configured with a VLAN ID that matches a VLAN ID specified in a list using the vlan-id-list statement. VLAN IDs can be entered individually using a space to separate each ID, entered as an inclusive list separating the starting VLAN ID and ending VLAN ID with a hyphen, or a combination of both.

For example, to configure the VLAN IDs 20 and 45 and the range of VLAN IDs between 30 and 40, issue the following command from the CLI:

set interfaces ge-1/0/1 unit 1 vlan-id-list [20 30-40 45];

To configure a list of VLAN IDs for a logical interface, include the vlan-id-list statement:

vlan-id-list list-of-vlan-ids;

You can include this statement at the following hierarchy levels:

For more information about how to configure VLANs, see the Junos Network Interfaces Configuration Guide. For detailed information about how VLAN identifiers in a VPLS routing instance are processed and translated, see the MX Series Layer 2 Configuration Guide.

Configuring Aggregated Ethernet Interfaces for VPLS

You can configure aggregated Ethernet interfaces between CE devices and PE routers for VPLS routing instances. Traffic is load-balanced across all of the links in the aggregated interface. If one or more links in the aggregated interface fails, the traffic is switched to the remaining links.

For more information about how aggregated Ethernet interfaces function in the context of VPLS, see VPLS and Aggregated Ethernet Interfaces.

To configure aggregated Ethernet interfaces for VPLS, configure the interface for the VPLS routing instance as follows:

interfaces aex {vlan-tagging;encapsulation encapsulation-type;unit logical-unit-number {vlan-id number;}}

You can configure the following physical link-layer encapsulation types for the VPLS aggregated Ethernet interface:

For the interface configuration statement, in aex, the x represents the interface instance number to complete the link association; x can be from 0 through 127, for a total of 128 aggregated interfaces.

For more information about how to configure aggregated Ethernet interfaces, see the Junos Network Interfaces Configuration Guide.

The aggregated Ethernet interface must also be configured for the VPLS routing instance as shown in the following example:

[edit]routing-instances {green {instance-type vpls;interface ae0.0;route-distinguisher 10.255.234.34:1;vrf-target target:11111:1;protocols {vpls {site-range 10;site green3 {site-identifier 3;}}}}}

Interface ae0.0 represents the aggregated Ethernet interface in the routing instance configuration. The VPLS routing instance configuration is otherwise standard.

Copyright© 1999-2010 Juniper Networks, Inc. All rights reserved.