Configuring MP-IBGP Between Hub-PE and Spoke-PE
By importing extended community attributes to BGP, MP-IBGP can advertise VPNv4 routes between PEs.
Context
The Hub-PE must set up the MP-IBGP peer with all the Spoke-PEs. Spoke-PEs do not need to set up the MP-IBGP peer between each other.
Perform the following steps on the Hub-PE and Spoke-PE.
Procedure
- Access the system view.
system-view
- Access the BGP view.
bgp { as-number-plain | as-number-dot }
- Specify the remote PE as the peer.
peer ipv4-address as-number { as-number-plain | as-number-dot }
- Specify the interface to set up the TCP connection.
peer ipv4-address connect-interface loopback interface-number
The 32-bit mask IP addresses of the loopback interfaces must be used to establish the MP-IBGP peer relationship between PEs. This can ensure that the tunnel can be iterated. The route destined to the loopback interface is advertised to the remote PE based on IGP on the MPLS backbone network.
- Access the BGP VPNv4 address family view.
ipv4-family vpnv4 [ unicast ]
- Exchange VPN IPv4 routing information between the peers.
peer ipv4-address enable