No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Feature Description - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Feature Description - VPN
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Inter-AS EVPN Option C

Inter-AS EVPN Option C

Inter-AS EVPN Option C implements Layer 2 interconnection between networks in different ASs.


With the wide application of MPLS VPN solutions, different MANs of a service provider or collaborative backbone networks of different service providers often span multiple ASs. Similar to L3VPN services, EVPN services running on an MPLS network must also have the capability of spanning ASs.


By advertisement of labeled routes between PEs, end-to-end BGP LSPs can be established to carry Layer 2 traffic in BGP ASs (including inter-IGP areas) and inter-BGP ASs that only support Option C.

In Option C mode, an autonomous system boundary router (ASBR) does not maintain or advertise EVPN routes. Instead, PEs exchange EVPN routes directly. EVPN routes include the following:
  • Ethernet auto-discovery routes
  • MAC and IP routes
  • Inclusive multicast routes
  • Ethernet segment routes
  • ASBRs advertise labeled IPv4 routes to PEs in their respective ASs through MP-IBGP, and advertise labeled IPv4 routes received on PEs in the local AS to the ASBR peers in other ASs. ASBRs in the transit AS also advertise labeled IPv4 routes. Therefore, a BGP LSP can be established between the ingress PE and egress PE.
  • PEs in different ASs establish multi-hop EBGP connections with each other and exchange EVPN routes.
  • ASBRs do not store EVPN routes or advertise EVPN routes to each other.
Figure 10-35 Inter-AS EVPN Option C networking where PEs advertise labeled EVPN routes

To improve expansibility, you can specify a route reflector (RR) in each AS. An RR stores all EVPN routes and exchanges EVPN routes with PEs in the AS. RRs in two ASs establish MP-EBGP connections with each other and advertise EVPN routes.

Figure 10-36 Inter-AS EVPN Option C networking with RRs
Inter-AS EVPN Option C can be implemented using the following solutions:
  • A local ASBR learns a labeled public network BGP route from the peer ASBR, assigns a label to this route based on a matching policy, and advertises this route to its IBGP peer. Then, a complete public network LSP is established.
  • The IBGP peer relationship between a PE and ASBR in the same AS is not required. In this solution, a local ASBR learns a labeled public network BGP route from the peer ASBR and imports this route to an IGP to trigger LDP LSP establishment. Then, a complete LSP is established between the ingress and egress on the public network.


  • EVPN routes are directly exchanged between an ingress PE and egress PE. The routes do not have to be stored and forwarded by intermediate devices.

  • Only PEs exchange EVPN routing information. Ps and ASBRs forward packets only. The intermediate devices need to support only MPLS forwarding rather than MPLS VPN services. In such a case, ASBRs are no longer the performance bottlenecks. Inter-AS EVPN Option C, therefore, is suitable for an EVPN that spans multiple ASs.

Updated: 2019-01-14

Document ID: EDOC1100058940

Views: 18974

Downloads: 34

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next