Configuring MP-EBGP Between ASBRs in Different ASs

After an MP-EBGP peer relationship is established between ASBRs, ASBRs can exchange VPNv4 routes.

Context

In inter-AS VPN Option B (ASBR also functioning as a PE), VPN instances also need to be created on ASBRs. The ASBR does not filter the VPNv4 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 commit
The configuration is committed.
Run quit
Return to the system view.
Run bgp as-number
The BGP view is displayed.
Run peer peer-address as-number as-number
The peer ASBR is specified as an EBGP peer.
Run ipv4-family vpnv4 [ unicast ]
The BGP-VPNv4 address family view is displayed.
Run peer peer-address enable
The function to exchange VPNv4 routes with the peer ASBR is enabled.
Run commit
The configuration is committed.