[Contents] [Prev] [Next] [Index] [Report an Error]

Understanding VPLS Routing Instances

To configure VPLS functionality, you must enable VPLS support on the PE router. You must also configure PE routers to distribute routing information to the other PE routers in the VPLS and configure the circuits between the PE routers and the CE devices.

You create a VPLS routing instance on each PE router that is participating in the VPLS. The routing instance has the same name on each PE router. To configure the VPLS routing instance, you specify the following:

Route distinguisher—Helps BGP distinguish between potentially identical network layer reachability information (NLRI) messages received from different VPLS instances. Each routing instance that you configure on a PE router must have a unique route distinguisher.
Route target—Defines which route is part of a VPLS. A unique route target helps distinguish between different VPLS services on the same router.
Site name—Provides unique name for the VPLS site.
Site identifier—Provides unique numerical identifier for the VPLS site.
Site range—Specifies total number of sites in the VPLS. The site range must be greater than the site identifier.
Interface to the CE router—Specifies the physical interface to the CE router that carries VPLS traffic. The interface must be configured for a VPLS encapsulation type.

Note: In addition to the VPLS routing instance, you must configure MPLS label-switched paths (LSPs) between the PE routers, internal BGP (IBGP) sessions between the PE routers, and an interior gateway protocol (IGP) on the PE routers.

Caution: MPLS is disabled by default on J-series Services Routers and you must explicitly configure your router to allow MPLS traffic. However, when MPLS is enabled, all flow-based security features are deactivated and the router performs packet-based processing. Flow-based services such as security policies, zones, NAT, ALGs, chassis clustering, screens, firewall authentication, and IPSec VPNs are unavailable on the router. For more information on flow-based and packet-based processing, see the JUNOS Software Security Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]