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 a PW Protection Group

Configuring a PW Protection Group

In a PW APS scenario, a PW protection group consists of a primary PW and a secondary PW. The primary or secondary PW can be either a single-segment or a multi-segment PW.

Context

In the PW APS scenarios shown in Figure 7-16 and Figure 7-17, a PW protection group consisting of the primary and secondary PWs needs to be configured on PE1 and PE2. The primary or secondary PW can be either a single-segment or a multi-segment PW. When configuring PW redundancy, consider the following advice:

Determine whether to use single-segment or multi-segment PWs based on the following principles:
  • If the bearer network where PE1 and PE2 reside is small or PE1 and PE2 belong to a carrier other than the bearer network carrier, configure single-segment PWs.
  • If PE1 and PE2 belong to different ASs on a large bearer network and a tunnel or signaling connection cannot be directly established between them, configure multi-segment PWs.
Determine whether to use static or dynamic PWs based on the following principles:
  • Dynamic PWs use LDP signaling to transmit VC labels and are easy to configure. The network scalability is high.
  • Static PWs use manually configured VC labels and are complex to configure. The network scalability is low but the network controllability is high.
NOTE:
  • A static or hybrid multi-segment PW cannot obtain the TTL value by dynamic negotiation. To ensure the correct forwarding of PW APS negotiation packets between the endpoint PEs of a multi-segment PW, run the mpls l2vpn pw-ttl ttl-value [ secondary | bypass ] command to configure a TTL value, so that the PW APS mechanism knows the specific number of PW segments.

  • In the case of single-segment PWs, configure the primary and secondary PWs on the endpoint PEs.

  • In the case of multi-segment PWs, configure the primary and secondary PWs on the endpoint PEs and configure switched PWs on the SPEs.

  • The types of PWs within the same protection group must be the same, and the PW types on the two endpoints of a PW segment must also be the same.

  • When you configure a PW protection group, configure the same parameters for the primary and secondary PWs. A parameter inconsistency causes the secondary PW to fail to take over traffic if the primary PW fails.

Configure a PW protection group consisting of the primary and secondary PWs on PE1 and PE2. If the PWs are multi-segment PWs, you also need to configure switched PWs on SPE1 and SPE2.

Procedure

  • Configure a PW protection group that consists of the static primary and secondary PWs.

    Perform the following steps on PE1 and PE2.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The AC interface view is displayed.

    3. The static primary PW is configured.

      Run either of the following commands based on AC interface types:
      • For an Ethernet AC interface, run:

        mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-value receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name | access-port | [ control-word | no-control-word ] | [ raw | tagged ] ] *
      • For an ATM AC interface, run:

        mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-value receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name | access-port | [ control-word | no-control-word ] | [ max-atm-cells cells-value ] | [ atm-pack-overtime time ] ] *
      • For a TDM AC interface, run:

        mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-value  receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name | access-port | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ] | [ rtp-header ] ] *

    4. Configure the static secondary PW.

      Run either of the following commands based on AC interface types:
      • For an Ethernet AC interface, run:

        mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-value receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name | access-port | [ control-word | no-control-word ] | [ raw | tagged ] ] * secondary
      • For an ATM AC interface, run:

        mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-value receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name | access-port | [ control-word | no-control-word ] | [ max-atm-cells cells-value ] | [ atm-pack-overtime time ] ] * secondary
      • For a TDM AC interface, run:

        mpls static-l2vc { { destination ip-address | pw-template pw-template-name vc-id } * | destination ip-address [ vc-id ] } transmit-vpn-label transmit-label-value receive-vpn-label receive-label-value [ tunnel-policy tnl-policy-name | access-port | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ] | [ rtp-header ] ] * secondary

    5. Run quit

      Return to the system view.

    6. Run commit

      The configuration is committed.

  • Configure a PW protection group that consists of the dynamic primary and secondary PWs.

    Perform the following steps on PE1 and PE2:

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The AC interface view is displayed.

    3. Configure the dynamic primary PW.

      Run either of the following commands based on AC interface types:
      • For an Ethernet AC interface, 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 ] *
      • For an ATM AC interface, run:

        mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name | [ control-word | no-control-word ] | [ max-atm-cells cells-value ] | [ atm-pack-overtime time ] | ignore-standby-state ] *
      • For a TDM AC interface, run:

        mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ | tunnel-policy policy-name | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ] | rtp-header | ignore-standby-state ] *

    4. Configure the secondary dynamic PW.

      Run either of the following commands based on AC interface types:
      • For an Ethernet AC interface, run:

        mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ access-port | [ control-word | no-control-word ] | ignore-standby-state | raw | tagged ] | tunnel-policy policy-name ] * secondary
      • For an ATM AC interface, run:

        mpls l2vc{ ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name | [ control-word [ seq-number ] | no-control-word ] | max-atm-cells cells-value | atm-pack-overtime atm-pack-overtime | transmit-atm-cells transmit-atm-cell-value ignore-standby-state ] * secondary
      • For a TDM AC interface, run:

        mpls l2vc { ip-address | pw-template pw-template-name } * vc-id [ tunnel-policy policy-name | [ control-word | no-control-word ] | [ jitter-buffer depth ] | [ tdm-encapsulation-number number ] | [ tdm-sequence-number ] | [ idle-code idle-code-value ]
        | [ rtp-header ] | [ ignore-standby-state ] ] * secondary

    5. Run quit

      Return to the system view.

    6. Run commit

      The configuration is committed.

  • (Optional) Configure switched PWs.

    If the PWs are multi-segment PWs, perform the following steps on SPEs.

    1. Run system-view

      The system view is displayed.

    2. Run either of the following commands based on PW types on the endpoint PEs:

      • If PW types on the endpoint PEs are both dynamic, run the following command to configure a dynamic switched PW:

        mpls switch-l2vc 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 ] [ stream-dual-receiving ] [ independent ] ] encapsulation encapsulation-type [ control-word-transparent ]
      • If PW types on the endpoint PEs are both static, run the following command to configure a static switched PW:

        mpls switch-l2vc ip-address vc-id trans trans-label recv received-label [ tunnel-policy policy-name ] between ip-address vc-id trans trans-label recv received-label [ tunnel-policy policy-name ] encapsulation encapsulation-type [ control-word | no-control-word ] [ control-word-transparent ]
      • If PW types on the endpoint PEs are static and dynamic respectively, run the following command to configure a hybrid switched PW:

        mpls switch-l2vc ip-address vc-id [ tunnel-policy policy-name ] between ip-address vc-id trans trans-label recv received-label [ tunnel-policy policy-name ] encapsulation encapsulation-type [ mtu mtu-value ] [ control-word | no-control-word ] [ rtp-header ] [ timeslotnum timeslotnum ] [ tdm-encapsulation number ]

    3. Run quit

      Return to the system view.

    4. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 30041

Downloads: 54

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