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

Configuration Guide - VPN 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - 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).
Configuring PW Redundancy

Configuring PW Redundancy

To build a virtual leased line from a BTS to a BSC, you can configure single-segments PWs or multi-segment PWs between CSGs and RSGs.

Usage Scenario

Network deployment imposes high requirements for VPN services. There are many fast fault detection and protection switching mechanisms such as bidirectional forwarding detection (BFD), operation, administration and maintenance (OAM), and fast reroute (FRR). These mechanisms, however, address only link or node failures within a packet switched network (PSN), but not PE failures or attachment circuit (AC) failures between PEs and CEs.

On the network shown in Figure 7-11 multi-segment PW services have been deployed between PE1 and PE2. To improve network reliability, configure PW redundancy on the SPE or PE1.

Figure 7-11 Networking diagram of configuring PW redundancy scenario
NOTE:
  • Only PWE3 VPWS supports PW redundancy. After the mpls l2vpn default martini command is run, VPWS does not support PW redundancy any longer.
  • When configuring PW redundancy, be sure to configure the primary, secondary, and bypass PW parameters consistently. Otherwise, the secondary or bypass PW may fail to take over services when the primary PW fails.

After configuring the primary and secondary PWs on a PE, you can specify the PW redundancy mode. The following PW redundancy modes are supported:

  • FRR mode: The FRR mode is the default PW redundancy mode and does not need to be configured.

  • Negotiation: is configured by using the mpls l2vpn redundancy command.

    • Master/slave mode: The primary and secondary PWs are manually specified on the master device, and then the local device notifies the remote device of information about the primary and secondary PWs. PW redundancy in master/slave mode works with the bypass PW to prevent links on the network side and links on the AC side from sensing faults in each other. That is, the fault on the AC side will trigger only an AC switchover and the fault on the public network will trigger only a PW switchover.

    • Independent mode: The primary and secondary PWs are determined by means of negotiation. Two PWs are configured on one PE to connect to two peer PEs, with both PWs being in the primary state on the local device. The peer PEs determine the primary and secondary PWs by means of E-Trunk or mVRRP, with one PW in the primary state and the other in the secondary state. The PEs on both ends negotiate and finally determine the primary PW. The independent mode applies to scenarios where PW redundancy is associated with E-Trunk. PW redundancy in independent mode, together with the bypass PW, can prevent links on the AC side from sensing faults on the network side but cannot prevent links on the network side from sensing faults on the AC side. That is, the fault on the public network will trigger only a PW switchover but not an AC link switchover whereas the fault on the AC side will trigger both an AC switchover and a PW switchover.

Pre-configuration Tasks

Before configuring PW redundancy, complete the following tasks:

  • Configuring IP addresses and an IGP on PEs

  • Configuring basic MPLS functions on the PEs

  • Establish a public network tunnel between PE1 and SPE and between the PE2 and the PE3. The public network tunnel can be LDP or TE.

Configuration Procedures

You can choose one of the following configuration tasks (excluding "Checking the Configurations") as required.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 30008

Downloads: 54

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