Configuring IBGP Sessions Between PE Routers in VPNs on EX9200 Switches
You must configure an 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 as follows:
[edit protocols]
bgp {
group group-name {
type internal;
local-address ip-address;
family evpn {
signaling;
}
family (inet-vpn | inet6-vpn) {
unicast;
}
family l2vpn {
signaling;
}
neighbor ip-address;
}
}
The IP address in the local-address statement is
the address of the loopback interface on the local PE router. The
IBGP session for the VPN runs through the loopback address. (You must
also configure the loopback interface at the [edit interfaces] hierarchy level.)
The IP address in the neighbor statement is the loopback
address of the neighboring PE router.
The family statement allows you to configure
the IBGP session for Layer 2 VPNs, VPLS, EVPNs or for Layer 3
VPNs.
To configure an IBGP session for Layer 2 VPNs and VPLS, include the
signalingstatement at the[edit protocols bgp group group-name family l2vpn]hierarchy level:[edit protocols bgp group group-name family l2vpn] signaling;
To configure an IBGP session for EVPNs, include the
signalingstatement at the[edit protocols bgp group group-name family evpn]hierarchy level:[edit protocols bgp group group-name family evpn] signaling;
To configure an IPv4 IBGP session for Layer 3 VPNs, configure the
unicaststatement at the[edit protocols bgp group group-name family inet-vpn]hierarchy level:[edit protocols bgp group group-name family inet-vpn] unicast;
To configure an IPv6 IBGP session for Layer 3 VPNs, configure the
unicaststatement at the[edit protocols bgp group group-name family inet6-vpn]hierarchy level:[edit protocols bgp group group-name family inet6-vpn] unicast;
You can configure both family inet and family inet-vpn or both family inet6 and family
inet6-vpn within the same peer group. This allows you to enable
support for both IPv4 and IPv4 VPN routes or both IPv6 and IPv6 VPN
routes within the same peer group.