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.


NE20E-S V800R010C10SPC500 Feature Description - VPN 01

This is NE20E-S V800R010C10SPC500 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).
EVPN's Service Modes

EVPN's Service Modes

Multiple Ethernet VPN instances (EVIs) can be configured on PEs at the edge of an EVPN. Each EVI connects to one or more user networks. EVIs access user networks in various service modes:

Port-based Mode

In port-based mode, an interface is used to access a user service. Specifically, the physical interface connected to a user network is directly bound to a common EVI (neither an EVI in BD mode nor an EVI in VPWS mode) and has no sub-interfaces created. This service mode is used only to carry Layer 2 services.

VLAN-based Mode

On the network shown in Figure 12-29, in VLAN-based mode, the physical interfaces connected to user networks each have different sub-interfaces created. Each sub-interface is associated with a unique VLAN and added to a specific bridge domain (BD). Each BD is bound to a specific EVI. In this service mode, the sub-interface, VLAN, BD, and EVI are exclusive for a user to access a network, and a separate MAC forwarding table is used on the forwarding plane for each user. Therefore, this mode effectively ensures service isolation. However, an EVI is required per user, consuming numerous EVI resources. This service mode is used to carry Layer 2 or Layer 3 services.

Figure 12-29 VLAN-based mode

VLAN Bundle

On the network shown in Figure 12-30, in VLAN bundle mode, an EVI connects to multiple users, who are divided by VLAN, and the EVI is bound to a BD. In this service mode, the users connected to the same EVI share a MAC forwarding table, requiring each user on the network to have a unique MAC address. This service mode is used to carry Layer 2 or Layer 3 services.

Figure 12-30 VLAN-bundle mode

VLAN-Aware Bundle

On the network shown in Figure 12-31, in VLAN-aware bundle mode, an EVI connects to multiple users, who are divided by VLAN. Additionally, the EVI can be bound to multiple BDs, in which case, the EVI must have different BD tags configured. When EVPN peers send routes to each other, a BD tag is encapsulated into the Ethernet Tag ID field of an Ethernet auto-discovery route, MAC/IP advertisement route, and inclusive multicast route. In this service mode, users connected to the same EVI use separate forwarding entries. During traffic forwarding, the system uses the BD tag carried in user packets to locate the corresponding MAC forwarding table and searches the table for a forwarding entry based on a MAC address.

Figure 12-31 VLAN-aware bundle mode

Unlike the other service mode, in VLAN-aware bundle mode, load balancing, designated forwarder (DF), host migration, and route re-origination are implemented based on a BD:
  • Load balancing: In VLAN-aware bundle mode, load balancing can be implemented only if a MAC/IP advertisement route and Ethernet auto-discovery route have the same Ethernet segment identifier (ESI) and the same BD tag. If the BD tags are inconsistent, the routes belong to different BDs, preventing load balancing from being implemented.

  • DF election:
    • For interface-based DF election, the system chooses the first interface to go Up in a BD for DF election.

    • During DF election after an AC interface is enabled to influence DF election, a PE cannot participate in DF election if the system does not receive the Ethernet auto-discovery route advertised by the PE. If the VLAN-aware bundle mode is enabled in this scenario, an Ethernet auto-discovery route is generated for each BD tag. The PE can participate in DF election only if the system receives Ethernet auto-discovery routes in all BDs bound to a specified EVI.

  • Host migration: When the system generates a local MAC/IP advertisement route, the system checks whether it has received a MAC/IP advertisement route from the remote end. If the system has received such a route, the MAC address transfer attribute is added to the locally generated route, or the value of the sequence field in the MAC address transfer attribute is incremented by 1. In VLAN-aware bundle mode, a BD tag is the prefix key of a MAC/IP advertisement route. The system compares the BD tags carried in the received MAC/IP advertisement route and the locally generated one, preventing MAC address conflict between different BDs from causing a host migration failure.

  • Route re-origination: In the Data Center Interconnect (DCI) solution, a DCI-PE re-originates a MAC/IP advertisement route received from a peer device and then sends the new route to the peer device. When the VLAN-aware bundle mode is enabled on the DCI-PE, a MAC/IP advertisement route can be re-originated only if its Ethernet tag ID is consistent with the BD tag.

Updated: 2019-01-03

Document ID: EDOC1100055135

Views: 11421

Downloads: 23

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