Configuring Route Exchange Between a Hub-PE and a Spoke-PE
By introducing extended community attributes into BGP, MP-IBGP can advertise VPNv4 routes between PEs.
Context
An MP-IBGP peer relationship needs to be established between the Hub-PE and each Spoke-PE. Spoke-PEs do not need to exchange routes directly and therefore they do not need to establish MP-IBGP peer relationships.
Perform the following steps on the Hub-PE and all the Spoke-PEs.
Procedure
- Run system-view
The system view is displayed.
- Run bgp as-number
The BGP view is displayed.
- Run peer peer-address as-number as-number
The remote PE is configured as a BGP peer.
- Run peer peer-address connect-interface loopback interface-number
The interface used to establish a TCP connection is specified.
PEs must use the loopback interface addresses with 32-bit masks to establish an MP-IBGP peer relationship so that routes can recurse to a tunnel. The route to the loopback interface is advertised to the peer PE through IGP on the MPLS backbone network.
- Run ipv4-family vpnv4 [ unicast ]
The BGP-VPNv4 address family view is displayed.
- Run peer peer-address enable
The capability of exchanging BGP VPNv4 routing information with the peer is enabled.
- Run commit
The configuration is committed.