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 Flow Label-based Load Balancing

(Optional) Configuring Flow Label-based Load Balancing

Flow label-based load balancing enables L2VPN data flows on a PW to be load-balanced over tunnels between P devices based on flow labels, improving forwarding efficiency.

Context

When multiple links exist between P devices, configure flow label-based load balancing to improve L2VPN traffic forwarding efficiency. After flow label-based load balancing is enabled on a PE, the PE adds different labels for different L2VPN data flows to distinguish them one from the other. After a P device receives a data packet carrying a flow label, it performs the Hash calculation and selects a forwarding path based on the flow label in the data packet. This processing implements load balancing. To enable flow label-based load balancing for PWs, run the flow-label command.

NOTE:

Currently, only LDP VPWS, LDP VPLS, and static VPWS and VPLS support flow label-based load balancing.

Procedure

  1. Run system-view

    The system view is displayed.

  2. (Optional) Run flow-label hash-fields { l2 | l3 | l4 }

    A hash element is configured for flow label load balancing.

    This command takes effect only after the PW L2VPN flow label function is enabled in the interface view.

  3. Run interface interface-type interface-number

    The AC interface view is displayed.

  4. Run mpls l2vpn flow-label { both | send | receive } [ secondary ] [ static ]

    Flow label-based load balancing is enabled for PWs on the interface.

    By default, flow label-based load balancing of PWs is disabled on an interface.

    NOTE:
    • Flow label-based load balancing can be enabled only when any of the following conditions is met:
      • The receive parameter is configured on the local PE, and the send parameter is configured on the remote PE.
      • The send parameter is configured on the local PE, and the receive parameter is configured on the remote PE.
      • Both the send and receive parameters are configured on the local and remote PEs.
    • If secondary is configured, the flow label-based load balancing capability takes effect only for the secondary PW on the interface. If secondary is not configured, the flow label-based load balancing capability takes effect only for the primary PW on the interface.

    • If static is configured, the flow label-based load balancing capability is statically configured. The end PEs deliver the flow label-based load balancing capability, irrespective of whether the other end has the capability enabled. For dynamic PWs, if static is not configured, the flow label-based load balancing capability of the local end is negotiated by the remote end. For static PWs, the flow label-based load balancing capability is statically configured, irrespective of whether static is configured.

      If the static flow label-based load balancing configuration does not match on both ends, the device discards packets carrying a flow label, causing packet loss.

  5. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 27808

Downloads: 53

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