Configuring MP-IBGP Between PEs and ASBRs in the Same AS

By importing extended community attributes to BGP, MP-IBGP can advertise VPNv4 routes between the PE and the ASBR.

Perform the following steps on the PE and ASBR in the same AS.

Specify the peer ASBR as the IBGP peer.

peer ipv4-address as-number { as-number-plain | as-number-dot }

Specify the loopback interface as the outgoing interface of the BGP session.
```
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 ]
```
Enable the exchange of IPv4 VPN routes between the PE and ASBR in the same AS.
```
peer ipv4-address enable
```
In the FW, an ASBR can change the next-hop address of a VPNv4 route to the ASBR's address before advertising the route to a PE.
(Optional) Configure a VPNv4 route to participate in route selection only when its next hop is iterated to a tunnel.
```
bestroute nexthop-resolved tunnel
```
If an ASBR receives a VPNv4 route from the local PE but there is only an IP link between the ASBR and PE, the ASBR cannot send the VPNv4 route to the peer ASBR. However, the ASBR still uses the VPNv4 route as the optimal route. This brings some difficulties in fault locating. After you configure the bestroute nexthop-resolved tunnel command, a VPNv4 route can participate in route selection only when its next hop is iterated to a tunnel. If a fault occurs, you can quickly locate the fault.