Configuring MP-EBGP for PEs and ASBRs in Different ASs
By introducing extended community attributes into BGP, MP-EBGP can advertise VPNv4 routes between PEs. And after an MP-EBGP peer relationship is established between ASBRs in different ASs, an ASBR can advertise the VPNv4 routes of its AS to the other ASBR.
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 peer ASBR is specified as an EBGP peer.
- Run peer peer-address connect-interface loopback interface-number
A loopback interface is specified as the outbound interface for BGP sessions.
- Run peer ipv4-address ebgp-max-hop [ hop-count ]
The maximum number of hops between PEs for which an EBGP peer relationship is to be configured is specified.
PEs of different ASs are generally not directly connected. To set up the EBGP peer relationship between PEs of different ASs, configure the maximum number of hops between PEs and ensure that PEs are reachable.
- Run ipv4-family unicast
The unicast IPv4 address family view is displayed.
- Run peer peer-address enable
The function to exchange IPv4 routes is enabled.
- (On PEs) Run quit
The BGP view is displayed.
- (On PEs) Run ipv4-family vpnv4 [ unicast ]
The BGP-VPNv4 address family view is displayed.
When the NetEngine 8000 F functioning as an ASBR advertises VPNv4 routes to a PE, the NetEngine 8000 F can automatically change the next hop of the routes to its own IP address.
- (On PEs) Run peer peer-address enable
The capability to exchange VPNv4 routes is enabled.
- (On PEs) Run policy vpn-target
The VPN-Target filter function is enabled on PEs.
- Run commit
The configuration is committed.