Configuring the VPLS 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 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.
To configure the encapsulation type on the physical interface, include the encapsulation
statement:
encapsulation (ethernet-vpls | ether-vpls-over-atm-llc |extended-vlan-vpls | vlan-vpls);
NOTE: ACX Series routers do not support the ether-vpls-over-atm-llc and
extended-vlan-vpls options for encapsulation.
You can include the encapsulation statement for physical interfaces 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 [edit logical-systems] hierarchy.
Copyright © 2017, Juniper Networks, Inc.1256
ACX Series Universal Access Router Configuration Guide
To Next Page
Loading...
Need help?
General
