Configuring an IBGP Session Between PE Routers
You must configure an internal Border Gateway Protocol (IBGP) session between the PE routers to allow the PE routers to exchange information about routes originating and terminating in the VPN. The PE routers rely on this information to determine which labels to use for traffic destined for remote sites.
Configure an IBGP session for the VPN at the
[edit protocols bgp groupgroup-name]hierarchy level as follows:[edit protocols]bgp {groupgroup-name{type internal;local-addressip-address;family (inet-vpn | inet6-vpn) {unicast;}family l2vpn {signaling;}neighborip-address;}}The IP address in the
local-addressstatement is the address of the loopback interface (lo0) on the local PE router. The IBGP session for the VPN runs through the loopback address. (You must also configure thelo0interface at the[edit interfaces]hierarchy level.)The IP address in the
neighborstatement is the loopback address of the neighboring PE router. If you are using RSVP signaling, this IP address is the same address you specify in thetostatement at the[edit mpls label-switched-pathlsp-path-name]hierarchy level when you configure the MPLS LSP.The family statement allows you to configure the IBGP session for either Layer 2 VPNs and VPLS or for Layer 3 VPNs. To configure an IBGP session for Layer 2 VPNs and VPLS, include the
signalingstatement at the[edit protocols bgp groupgroup-namefamily l2vpn]hierarchy level:[edit protocols bgp groupgroup-namefamily l2vpn]signaling;To configure an IPv4 IBGP session for Layer 3 VPNs, configure the
unicaststatement at the[edit protocols bgp groupgroup-namefamily inet-vpn]hierarchy level:[edit protocols bgp groupgroup-namefamily inet-vpn]unicast;To configure an IPv6 IBGP session for Layer 3 VPNs, configure the
unicaststatement at the[edit protocols bgp groupgroup-namefamily inet6-vpn]hierarchy level:[edit protocols bgp groupgroup-namefamily inet6-vpn]unicast;