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:
•
ethernet-vpls
•
extended-vlan-vpls
•
flexible-ethernet-services
•
vlan-vpls
NOTE: ACX Series routers do not support the extended-vlan-vpls and vlan-vpls
encapsulation types.
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
Ethernet Interfaces Feature Guide for Routing Devices.
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 {
1261Copyright © 2017, Juniper Networks, Inc.
Chapter 35: Configuring Virtual Private LAN Service