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 Service PWs

Configuring Service PWs

Service PWs include common PWs and bypass PWs. If tunnels are configured on the public network for protection, there is no need to configure a bypass PW.

Context

Figure 7-20 shows the network on which PE1 is single-homed to the SPE. To implement multi-segment PW (MS-PW) redundancy, the following PWs must be configured:

  • Dynamic single-segment PW (SS-PW) between PE1 and the SPE

  • Dynamic MS-PWs in primary/secondary mode on the SPE

  • Bypass PW between PE2 and PE3

Figure 7-20 Configuring MS-PW redundancy when a PE is single-homed to an SPE

Procedure

  • Perform the following steps on PE1:
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The view of an AC interface is displayed.

    3. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name | [ control-word | no-control-word ] | [ raw | tagged ] | access-port | ignore-standby-state ] *

      A dynamic PW is configured to connect PE1 to the SPE.

      NOTE:
      • When creating a PW, you must specify the IP address and VC ID of the destination PE. The VC IDs at both ends must be consistent.

      • The default tunnel policy uses LSPs for dynamic PWs, and load balancing is not implemented. If you want to use a different type of tunnel, configure the tunnel-policy policy-name parameter for a dynamic PW to reference a specified tunnel policy. Before referencing a tunnel policy, Configuring a Tunnel Policy and Applying a Tunnel Policy to a VPN Service.

      • The encapsulation types at both ends of a PW must be the same.

    4. Run commit

      The configuration is committed.

  • Perform the following steps on the SPE:
    1. Run system-view

      The system view is displayed.

    2. Run mpls switch-l2vc [ instance-name instance-name ] ip-address vc-id [ tunnel-policy policy-name ] between ip-address vc-id [ tunnel-policy policy-name ] backup ip-address vc-id [ tunnel-policy policy-name ] encapsulation encapsulation-type [ control-word-transparent ]

      Dynamic MS-PWs in primary/secondary mode are created.

    3. (Optional) Run mpls switch-l2vc ip-address vc-id encapsulation encapsulation-type reroute { delay delay-time | immediately | never }

      A switchback policy is configured for the primary and secondary MS-PWs.

      By default, a primary/secondary PW switchback is performed after a delay of 30s.

    4. (Optional) Run mpls switch-l2vc ip-address vc-id encapsulation encapsulation-type switchover

      Service traffic is manually switched from the primary PW to the secondary PW.

      In normal cases, this command is not used. In commissioning or fault scenarios, if service traffic needs to be switched to the secondary PW temporarily or for a long time, run this command to trigger a forcible primary/secondary PW switchover.

    5. Run commit

      The configuration is committed.

  • Perform the following steps on each of PE2 and PE3:
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The service PW AC interface view is displayed.

    3. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ [ control-word | no-control-word ] | [ raw | tagged | ip-interworking | ip-layer2 ] | tunnel-policy policy-name | access-port | [ secondary ]

      Primary and secondary PWs are configured.

      • The primary PW must have the same encapsulation type as those of the secondary or bypass PWs.

      • The MTU and control word parameters on the AC interfaces of PE1, PE2, and PE3 must be the same. If the parameters on any PE are configured differently, the PWs may go Down, causing a traffic interruption and compromising services.

    4. Run mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ [ control-word | no-control-word ] | [ raw | tagged | ip-interworking | ip-layer2 ] | tunnel-policy policy-name | access-port | bypass

      A bypass PW is configured.

      The control word function must be enabled or disabled on both the bypass PW and primary PW.

    5. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 33014

Downloads: 59

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