Configuring MP-EBGP Between ASBRs in Different ASs

Context

In inter-AS EVPN Option B, you do not need to create EVPN instances on ASBRs. The ASBR does not filter the EVPN routes received from the PE in the same AS based on VPN targets. Instead, it advertises the received routes to the peer ASBR through MP-EBGP.

Procedure

Run system-view
The system view is displayed.
Run interface interface-type interface-number
The interface view is displayed.
Run ip address ip-address { mask | mask-length }
An IP address is configured for the interface.
Run mpls
The MPLS capability is enabled.
Run quit
Return to the system view.
Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Run peer peer-address as-number as-number
The peer ASBR is specified as an EBGP peer.
Run peer ipv4-address enable
The function to exchange IPv4 routes with the peer ASBR is enabled.
Run ipv4-family unicast
The BGP-EVPN address family view is displayed.
Run peer ipv4-address enable
The function to exchange EVPN routes with the peer ASBR is enabled.
Run peer ipv4-address esad-route-compatible enable
Enable PE and ASBR to send ES AD routes in the standard format defined in relevant standards.
Run commit
The configuration is committed.