Configuring Pe-To-Pe Lsps; Enabling Bgp Routing; Enabling Bgp Ecmp For Bgp/Mpls Vpns - Juniper JUNOSE 11.2.X BGP AND MPLS Configuration Manual

Configuring PE-to-PE LSPs

Enabling BGP Routing

router bgp

Enabling BGP ECMP for BGP/MPLS VPNs

Example 1
Copyright © 2010, Juniper Networks, Inc.
See "Configuring MPLS" on page 275, for information about configuring LSPs.
You must enable the BGP routing process on the router serving as the PE router.
Use to enable the BGP routing protocol and to specify the local AS—the AS to which
this BGP speaker belongs.
All subsequent BGP configuration commands are placed within the context of this
router and AS; you can have only a single BGP instance per virtual router.
Specify only one BGP AS per virtual router.
Example
host1:vr1(config)#router bgp 100
This command takes effect immediately.
Use the no version to remove the BGP process.
See router bgp.
Enabling ECMP support for BGP/MPLS VPNs allows multiple VPN routes to be included
in the list of available equal-cost paths. You can use the maximum-paths command
with the ibgp or eibgp keywords to enable ECMP support for BGP/MPLS VPNs.
The eibgp keyword specifies that the E Series router consider both external BGP (EBGP)
and internal BGP (IBGP) paths when determining the number of equal-cost paths to the
same destination that BGP can submit to the IP routing table. The ibgp keyword specifies
that the E Series router consider multiple internal IBGP paths, but not EBGP paths, when
determining the number of equal-cost paths.
You can create an ECMP environment in which multiple IBGP paths are selected as
multipaths and used for load balancing. In the example shown in Figure 93 on page 442,
the E Series router gives equal consideration to IBGP VPN routes learned from multiple
remote PE devices when determining load balancing.
Chapter 6: Configuring BGP-MPLS Applications
441