NOTE: You cannot configure both BGP signaling and LDP signaling for the
same VPLS routing instance. If you attempt to configure the statements that
enable BGP signaling for the VPLS routing instance (the site, site-identifier,
and site-range statements) and the statements that enable LDP signaling
for the same instance (the neighbor and vpls-id statements), the commit
operation fails.
NOTE: In the VPLS documentation, the word router in terms such as PE router
is used to refer to any device that provides routing functions.
Configure BGP signaling for the VPLS routing instance by completing the steps in the
following sections:
•
Configuring the VPLS Site Name and Site Identifier on page 1241
•
Configuring Automatic Site Identifiers for VPLS on page 1242
•
Configuring the Site Range on page 1243
•
Configuring the VPLS Site Interfaces on page 1245
•
Configuring the VPLS Site Preference on page 1245
Configuring the VPLS Site Name and Site Identifier
When you configure BGP signaling for the VPLS routing instance, on each PE router you
must configure each VPLS site that has a connection to the PE router. All the Layer 2
circuits provisioned for a VPLS site are listed as the set of logical interfaces (using the
interface statement) within the site statement.
You must configure a site name and site identifier for each VPLS site.
To configure the site name and the site identifier, include the site and the site-identifier
statements:
site site-name {
interface interface-name {
interface-mac-limit limit;
}
site-identifier identifier;
}
The numerical identifier can be any number from 1 through 65,534 that uniquely identifies
the local VPLS site.
You can include these statements at the following hierarchy levels:
•
[edit routing-instances routing-instance-name protocols vpls]
•
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols vpls]
1241Copyright © 2017, Juniper Networks, Inc.
Chapter 35: Configuring Virtual Private LAN Service
To Next Page
Loading...
Need help?
General
