Configuring Interfaces for VPLS Routing in ACX Series
Copyright © 2017, Juniper Networks, Inc.
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 interface-name;
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name]
[edit logical-systems logical-system-name routing-instances routing-instance-name]
NOTE:
ACX Series routers do not support the
You must also define each interface by including the following statements:
vlan-tagging;
encapsulation encapsulation-type;
unit logical-unit-number {
family vpls;
vlan-id vlan-id-number;
}
You can include these statements at the following hierarchy levels:
[edit interfaces interface-name]
[edit logical-systems logical-system-name interfaces interface-name]
NOTE:
ACX Series routers do not support the
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
hierarchy level, see the Junos OS Network Interfaces Library for
[edit interfaces]
Routing Devices.
Configuring the VPLS Interface Name on page 1256
Configuring VPLS Interface Encapsulation on page 1256
Enabling Flexible VLAN Tagging on page 1258
Configuring VLAN IDs for Logical Interfaces on page 1259
Sample Scenario of Hierarchical Virtual Private LAN Service on Logical Tunnel
Interface on page 1259
Configuring Aggregated Ethernet Interfaces for VPLS on page 1261
Chapter 35: Configuring Virtual Private LAN Service
statement in the routing instance configuration:
interface
hierarchy.
[edit logical-systems]
hierarchy.
[edit logical-systems]
1255