This VPN configuration requires that the PE routers have IBGP sessions between them to exchange the VPN routing information. When configuring BGP on these routers, don't forget to define the ASN. This is done in the [edit routing-options] level of the hierarchy. It is also necessary to configure a local-address . The local-address is only relevant when peering from loopback interfaces; however, this is the normal method of peering when configuring IBGP. Since BGP should peer with the loopback interfaces, the BGP configuration will require the addition of configuration statements at both the [edit routing-options] and [edit protocols bgp] levels of the hierarchy. [edit routing-options] lab@Chicago# set autonomous-system as number [edit protocols bgp group internal] lab@Chicago# set local-address local-address Note The local-address defines the source address for establishing the BGP connection. For IBGP sessions, it is necessary to define the loopback0 IP address as the local-address . [edit protocols bgp] lab@Chicago# set group group name type [internalexternal] [edit protocols bgp] lab@Chicago# set group group name neighbor address [edit protocols bgp] lab@Chicago# set group group name family inet-vpn unicast The family inet-vpn statement is required to turn up MBGP advertisements of the correct address family Use the following commands to verify the BGP configuration: lab@Chicago> show bgp group MY-PE-IBGP-SESSION Group Type: Internal AS: 100 Local AS: 100 Name: MY-PE-IBGP-SESSION Total peers: 1 Established: 1 192.168.2.1+4827 Route Queue Timer: unset Route Queue: empty
|