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 Mutual Protection Between an LDP VC and a CCC VC

Configuring Mutual Protection Between an LDP VC and a CCC VC

This section describes how to configure mutual protection between an LDP VC and a CCC VC. If a CCC VC (or LDP VC) functioning as the active path fails, traffic is switched to the LDP VC (CCC VC) functioning as the standby path so that they can protect each other, therefore improving reliability.

Usage Scenario

The use of Layer 2 virtual private network (L2VPN) technologies increases reliability requirements for L2VPNs. This is especially true of L2VPNs that provide real-time services such as VoIP and Internet Protocol television (IPTV).

To improve L2VPN service reliability, you can configure an LDP VC to protect a CCC VC. If the CCC VC functioning as the active path fails, traffic is switched to the LDP VC functioning as the standby path.

Similarly, you can also configure a CCC VC to protect an LDP VC. If the LDP VC functioning as the active path fails, traffic is switched to the CCC VC functioning as the standby path.

This configuration applies to the following scenarios:

  • Dual-homing to two PEs Figure 7-12 shows the following:

    • CE1 is dual-homed to PE1 and PE2 through an Eth-Trunk, with AC1 serving as the active path.
    • CE2 is dual-homed to PE1 and PE2 through another Eth-Trunk, with AC3 serving as the active path.
    • PW1 VC1 is deployed between PE1 and PE2 to protect AC3. If AC3 fails, CE1 accesses CE2 through the PW1 VC1 -> AC4 path.
    • PW2 VC1 is deployed between PE1 and PE2 to protect AC1. If AC1 fails, CE2 accesses CE1 through the PW2 VC1 -> AC2 path.

    Based on the preceding, CE1 and CE2 select AC1 and AC3 as the active paths, respectively. They select AC2 and AC4 as the standby paths, respectively. If the active paths fail, the standby paths take over service traffic.

    Figure 7-12 Mutual protection between an LDP VC and a CCC VC (dual-homing 2PE scenario)

  • Dual-homing to three PEs Figure 7-13 shows the following:

    • CE1 is dual-homed to PE1 and PE2 through an Eth-Trunk. AC1 serves as the active path, and AC2 serves as the standby path.
    • CE2 is dual-homed to PE2 and PE3 through another Eth-Trunk. AC3 serves as the active path, and AC4 serves as the standby path.
    • PW redundancy in Independent mode is configured on PE1, with PW1 VC1 being the active PW and PW2 VC1 being the standby PW.
    • PW redundancy in Independent mode is configured on PE3, with PW2 VC2 being the active PW and PW3 VC1 being the standby PW.

    The PW1 VC1 (active) and PW2 VC1 (standby) paths can be used to transmit traffic from AC1 to CE2. The AC3 (active) and PW3 VC2 (standby) paths can be used to transmit traffic from AC2 to CE2.

    Figure 7-13 LDP VC protecting CCC VC (dual-homing 3PE scenario)

Table 7-1 Mutual protection between a CCC VC and an LDP VC

Scenario

Key Configurations

Dual-homing 2PE scenario

An LDP VC protects a CCC VC.
  • Configure a primary CCC VC on PE1.
  • Configure a secondary (bypass) PW on PE1 to protect the CCC VC.
A CCC VC protects an LDP VC.
  • Configure a primary PW on PE1.
  • Configure a backup CCC VC on PE1 to protect the primary PW (LDP VC).

Dual-homing 3PE scenario

An LDP VC protects a CCC VC.
  • Configure a primary CCC VC connection on PE2.
  • Configure a secondary (bypass) PW on PE1 to protect the CCC VC.
  • Configure PW redundancy on PE1 and PE3.
A CCC VC protects an LDP VC.
  • Configure a primary PW on PE1.
  • Configure a secondary CCC VC connection on PE2 to protect the primary PW (LDP VC).
  • Configure PW redundancy on PE1 and PE3.

Pre-configuration Tasks

Before configuring mutual protection between an LDP VC and a CCC VC, complete the following tasks:
  • Configure PW status negotiation. You can configure an E-Trunk or VRRP to determine primary and secondary PWs.

  • Configure static routes or an IGP protocol on PEs and Ps on the MPLS backbone network to provide IP connectivity.

  • Configure basic MPLS functions on PEs and Ps on the MPLS backbone network.

  • Establish tunnels between PEs based on a tunnel policy. If no tunnel policy is configured, LDP tunnels are used by default.

Procedure

  1. Enable MPLS L2VPN.
    1. Run system-view

      The system view is displayed.

    2. Run mpls l2vpn

      MPLS L2VPN is enabled.

    3. Run quit

      Return to the system view.

  2. Create a CCC VC.
    1. Run interface interface-type interface-number [ .subinterface-number ]

      The AC interface view is displayed.

    2. Run either of the following commands:

      • To create a primary CCC VC, run the mpls ccc [ instance-name instance-name ] out-interface interface-type interface-number [ [ ip-interworking | ip-layer2 | raw | tagged ] | [ access-port ] * command.
      • To create a backup CCC VC, run the mpls ccc out-interface interface-type interface-number [ [ ip-interworking | ip-layer2 | raw | tagged ] | [ access-port ] * secondary command.

    NOTE:

    If you specify the secondary keyword, a secondary CCC VC is created. If you do not specify the keyword, a primary CCC VC is created.

  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 ] * | bypass

    A PW is created.

    NOTE:

    If you specify the secondary or bypass keyword, a secondary PW is created. If you do not specify the keyword, a primary PW is created.

  4. (Optional) Run mpls l2vpn pw ignore-ac-state [ secondary | bypass ]

    The AC interface is disabled from affecting the PW status when the AC interface changes.

    If an LDP-based bypass PW is required to ignore the status change of its AC interface, the bypass parameter must be specified.

    If an LDP-based secondary PW is required to ignore the status change of its AC interface, the secondary parameter must be specified.

    In the reliability scenario where an LDP VC is configured to protect a CCC VC, when an AC interface goes Down, the PW status also goes Down. When the AC interface goes Up, the PW has to negotiate the status and reestablish a connection. At this time, if an active/standby PW switchover is being performed, traffic is switched back to the active PW only after the PW negotiation is complete. As a result, the switchback performance deteriorates. To improve the switchback performance, run the mpls l2vpn pw ignore-ac-state command. With this configuration, when an AC interface goes Down, its connected PW remains Up; when the AC interface goes Up, the PW does not have to reestablish a connection.

  5. Run commit

    The configuration is committed.

Checking the Configurations

After configuring mutual protection between an LDP VC and a CCC VC, check the configurations:
  • Run the display mpls l2vpn vpws [ interface interface-type interface-number [ verbose ] ] command to check the PW information of the VPWS service.

Run the display mpls l2vpn vpws command to check the roles of the CCC VC and LDP VC. The command output shows that the CCC VC role is primary and the LDP VC role is bypass.

<HUAWEI> display mpls l2vpn vpws
Pri : Primary            Sec : Secondary            Byp : Bypass
PWb : PW-bypass          Acb : AC-bypass
Access Circuit                Virtual Circuit               States Active   Role
GE0/1/0                       GE0/1/1                       UP     Active   Pri
                              2.2.2.2:1                     UP    Inactive  Byp
Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 30002

Downloads: 54

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