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).
(Optional) Configuring a Secondary PW

(Optional) Configuring a Secondary PW

This section describes how to configure VLL Fast Re-route (FRR). After VLL FRR is configured, the VLL traffic is switched to the secondary path if the primary path fails. If the primary path recovers, the VLL traffic can be switched back to it according to the revertive switching policy.

Context

A secondary PW is mainly used in the following networking modes:

  • Symmetrically dual-homed CEs

    Two communication paths exist between the CEs on the two ends of the VC. One is the master path; the other is a backup path.

  • Asymmetrically connected CEs

    Figure 7-5 Asymmetrically connected CEs

    On the network shown in Figure 7-5 the primary and secondary PWs need to be configured on PE1. Only one PW is required on PE2 and PE3.

    On an inter-AS L2VPN and an MH PWE3, the ASBR and SPE do not distinguish the primary and secondary PWs.

    The CE on one end of the VC accesses the PE of higher reliability through a single reliable link. The CE on the other end is dual-homed to the PE of lower reliability. Therefore, two communication paths form between the CEs on the two ends of the VC. The path of higher reliability acts as the master path, and the path with the lower reliability acts as the backup path.

    The primary and secondary PWs must be of the same type.

    For asymmetrically connected CEs, the primary and secondary IP addresses need to be configured on the interface on the CE connected to the PE through a single link. When the master path is available, the CE uses the primary IP address to communicate with the remote CE. When a fault occurs on the master path, this CE communicates with the remote CE by using the secondary IP address.

    NOTE:

    To configure a PW for Point-to-Point Protocol (PPP) in VLL FRR, you must specify the parameter ip-interworking and enable the control word.

    If the IP addresses of the AC interfaces on the two CEs at both ends of the PW are not in the same network segment, the type of the AC links use PPP and the ppp peer hostroute-suppress command cannot be used.

    In the networking where CEs are asymmetrically connected to related PEs, the secondary PW cannot transmit data when the master path and backup path work normally. If the AC interface of the secondary PW borrows the IP address of the AC interface of the primary PW, the following situations occur:

    • Non revertive mode cannot be configured.

    • The local CE has two equal-cost and direct routes to the remote CE. The destination addresses and next hops of the two routes are the same. In fact, the route that passes through the secondary PW is invalid.

    • If CEs exchange routing information by using routing protocols, you need to modify the cost or metric of the AC interface of the backup path to be greater than that of the AC interface of the master path. The local CE cannot communicate with the peer CE, but can communicate with other user devices.

    • If CEs use static routes to exchange routing information, you need to modify the preference of the backup route to be lower than that of the primary route (the greater the value, the lower the preference) by using the ip route-static dest-ip-address mask out-interface preference preference-value command.

    Perform the following steps on the PE to which a CE is connected through only one link:

Procedure

  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.

  4. Run interface interface-type interface-number [ .subinterface-number ]

    The AC interface view is displayed.

  5. Run either of the following commands:

    • To establish a secondary VPWS PW using Ethernet, PPP, interfaces, 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
    • To establish a secondary VPWS PW using ATM interfaces, 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
    • To establish a secondary VPWS PW using Time Division Multiple (TDM) interfaces, 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

    When you configure a backup VPWS connection, configure the same parameters for the primary, secondary, and bypass PWs. A parameter inconsistency causes the secondary or bypass PW to fail to take over traffic if the primary PW fails.

    When the CE accesses the PE in asymmetrical mode through PPP,, the following situations occur:

    • Both the primary and secondary PWs need to be configured on the PE to which a CE is single-homed. Only the primary PW needs to be configured on the PE to which a CE is dual-homed.
    • The control word configuration on the primary and secondary PWs must be the same. Otherwise, lots of packets will be lost after the primary/secondary PW switchover.
    • When the CE accesses the PE through PPP,, the following situations occur:

      • A PE can only be configured with the heterogeneous transport.

      • The interface connecting CE1 to PE1 can be configured with the primary and secondary IP addresses. The primary PW forwards packets through the primary IP address, and the secondary PW forwards packets through the secondary IP address.
      • CEs can advertise routes to each other by using OSPF. OSPF, however, does not support the route advertised by the secondary IP address. If the device with the secondary IP address is connected to other devices, it cannot implement route forwarding.

    The VC IDs of VCs with the same encapsulation type must be unique on a PE.

  6. (Optional) Run undo interface-parameter-type vccv

    The VCCV byte (an interface parameter) is deleted in the Mapping packet.

    If LDP VPWS is configured for devices running VRP V800R005 or later to communicate with devices running VRP V300R001 or branch versions, configure this command.

  7. (Optional) Run mpls l2vpn service-name service-name

    The L2VPN service name is specified. Then, you can use an NMS to maintain the L2VPN service based on the service name.

  8. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 37238

Downloads: 61

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