In inter-AS IPv6 VPN Option C, an inter-AS BGP LSP needs to be established on the backbone network, and BGP peers on the backbone network can exchange labeled IPv4 routes with each other.
Procedure
- Configure the PE.
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
- Run peer ipv4-address label-route-capability
The exchange of the labeled IPv4 routes with the ASBR in the same AS is enabled.
- Run commit
The configuration is committed.
- Configure the ASBR.
- Run system-view
The system view is displayed.
- Run interface interface-type interface-number
The view of the interface connected to the peer ASBR is displayed.
- Run ip address ip-address { mask | mask-length }
An IPv4 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-plain | as-number-dot }
The BGP view is displayed.
- Run peer ipv4-address label-route-capability
The capability of exchanging the labeled IPv4 routes with the PE of the same AS is enabled.
In the Option C solution, you must establish an inter-AS VPN LSP. The related PEs and the ASBRs exchange public network routes with the MPLS labels.
The ASBR establishes an EBGP peer relationship with the remote ASBR to switch labeled IPv4 routes.
The public network routes with the MPLS labels are advertised by the MP-BGP. According to relevant standards (Carrying Label Information in BGP-4), the label mapping information of a route is carried by advertising BGP updates. This feature is implemented through BGP extension attributes, which requires BGP peers to process the labeled IPv4 routes.
- Run peer ipv4-address as-number { as-number-plain | as-number-dot }
The peer ASBR is specified as the EBGP peer.
- Run peer ipv4-address label-route-capability
The exchange of the labeled IPv4 routes with the peer ASBR is enabled.
- Run commit
The configuration is committed.