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

Reminder

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

upgrade

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).
VPLS Multi-homing

VPLS Multi-homing

Background

To deliver high-reliability services over a VPLS network, carriers usually dual-home a CE to two PEs through redundant links. While providing link-level protection, the dual-homing mechanism also brings in the risk of routing loops. Currently, E-Trunk multi-homing or STP over VPLS is used to prevent routing loops. However, E-Trunk multi-homing is not widely supported by non-Huawei devices, and STP over VPLS introduces high routing costs during real-time loop detection. VPLS multi-homing adjusts link priorities to prevent routing loops. It ensures that one access link of a multi-homed CE is in the active state and the other access links are in the blocked state.

Related Concepts

VPLS multi-homing uses BGP to transmit multi-homing site information. It enhances standard BGP VPLS and improves reliability and applies to scenarios where a CE is multi-homed to PEs.

Table 10-9 VPLS multi-homing concepts

Concept

Description

MH-ID

A multi-homing ID that uniquely identifies a multi-homing site

Optimal site

Preferred multi-homing site used for PW establishment

Implementation

In VPLS multi-homing implementation, after a multi-homing site is configured on a PE accessed by a multi-homed CE, the PE advertises a BGP Update message carrying its multi-homing site information (including the MH-ID) to the other PEs in the VPLS domain. Upon receipt of the BGP Update message, PEs with the same MH-ID as that carried in the BGP Update message start an election process to determine which PE is the preferred one. After the preferred PE is elected, the access links between the multi-homed CE and the non-preferred PEs are blocked to prevent routing loops.

A multi-homed CE determines which PE to access based on link priorities. The link-priority-affecting factors are listed in descending order of influence as follows:
  1. AC status (ACS): For PEs with the same MH-ID, the ACS value may be either of the following:
    • 1: The AC between a multi-homed CE and a PE is Down.
    • 0: The AC between a multi-homed CE and a PE is Up.

    The link whose ACS is 0 has a higher priority than the link whose ACS is 1.

  2. Preference (PREF): A larger PREF value indicates a higher link priority. The value must be configured.
  3. PE's router ID (PE-ID): If no BGP router ID is configured, the system router ID is used by default. If a BGP router ID is configured, it is used as the PE-ID.

    A lower PE-ID indicates a higher link priority.

If a link between a multi-homed CE and a PE fails, the PE advertises a BGP Update message that carries ACS, PREF, and PE-ID information to the other PEs in the VPLS domain. Then, PEs with the same MH-ID as that carried in the BGP Update message start an election process to select a preferred link.

Figure 10-23 VPLS multi-homing networking

A PE assigns a multi-homing site and MH-ID to each accessed CE in a VSI, and shares a default multi-homing site with a single-homed CE. If a CE is dual-homed to PE1 and PE2, they must assign the same MH-ID to the CE. On the network shown in Figure 10-23, PE1 assigns a multi-homing site and MH-ID 1 to CE1, and PE3 assigns a multi-homing site and MH-ID 3 to CE3. CE2 is dual-homed to PE1 and PE2, which both assign MH-ID 2 to CE2. The following example uses PE1 to illustrate how to select an optimal site for PW establishment, with priority 100 for PE1's MH-ID 2 and priority 200 for PE2's MH-ID 2.
  1. Blocks the AC interface to prevent routing loops. After PE1 receives a BGP Update message from PE2, PE1 finds PE2's multi-homing site with the same MH-ID (2) as a multi-homing site on itself. Therefore, PE1 compares the ACS, PREF, and PE-ID values of the two sites. Because PE1's MH-ID 2 has a lower priority than PE2's MH-ID 2, PE1 blocks the AC interface of MH-ID 2. After PE2 receives a BGP Update message from PE1, PE2 also finds PE1's multi-homing site with MH-ID 2 and compares the ACS, PREF, and PE-ID values of the two sites. Because PE1's MH-ID 2 has a lower priority than PE2's MH-ID 2, PE2 does not take any action.
  2. PE1 selects MH-ID 1 as the optimal site, PE2 MH-ID 2, and PE3 MH-ID 3.
  3. Establishes PWs between the optimal sites.
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055135

Views: 10390

Downloads: 19

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