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

NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services 01

This is NE20E-S2 V800R010C10SPC500 Configuration Guide - IP Services

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).
Adjusting the Algorithm of Load Balancing

Adjusting the Algorithm of Load Balancing

NOTE:
For the default hash factors of hash algorithm in typical load balance scenarios, see the chapter Appendix: Default Hash Factors.

Configuring Hash Factors ( VLL or IP Forwarding Scenarios)

Configuration Guide

NOTE:

This configuration process is supported only on the Admin-VS.

View Command Format
Slot view load-balance hash-fields ip { l2 | l3 | l4 }
NOTE:
  • l2: indicates that hash factors are <source MAC, destination MAC>
  • l3: indicates that hash factors are <source IP, destination IP>
  • l4: indicates that hash factors are <source IP, destination IP, source port-number, destination port number, protocol number>

Suitable Scenarios

The command is used in VLL and IP forwarding scenarios, including
  • IPv4 unicast forwarding
  • L3VPN forwarding on ingress PE
  • VLL forwarding on ingress PE

In these scenarios:

  • IP carrying TCP/UDP packets: the default hash factors are <source IP, destination IP, source port-number, destination port number, protocol number>.
  • IP carrying non-TCP/non-UDP packets: the default hash factors are <source IP, destination IP>.
  • Ethernet carrying Non-IP packets: the default hash factors are <source MAC, destination MAC>

If the hash factors <source MAC, destination MAC> are hashable enough, try the l3 parameter. If the hash factors <source IP, destination IP> are hashable enough, try the l4 parameter.

Follow-up Procedure

If this command is configured but traffic load balancing cannot be performed well, you can try to modify hash-arithmetic. For detailed information, see Configuring Hash-arithmetic.

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.

Configuring Hash Factors (VPLS or Bridged Forwarding Scenarios)

Configuration Guide

NOTE:

This configuration process is supported only on the Admin-VS.

View Command Format
Slot view load-balance hash-fields mac { l2 | l3 | l4 | label-ip }
NOTE:
  • l2: Indicates that hash factors are <source MAC, destination MAC>
  • l3: Indicates that hash factors are <source IP, destination IP>
  • l4: Indicates that hash factors are <source IP, destination IP, source port-number, destination port number, protocol number>
  • label-ip:Indicates that hash factors are the MPLS labels. This means that the hash calculation is performed based on labels encapsulated into non-IP packets

Suitable Scenarios

The command is used in bridged forwarding scenarios, or in the ingress PE in VPLS scenarios. In these scenarios:

  • IP carrying TCP/UDP packets: the default hash factors are <source IP, destination IP, source port-number, destination port number, protocol number>.
  • IP carrying non-TCP/non-UDP packets: the default hash factors are <source IP, destination IP>.
  • Non-IP packets: the default hash factors are <source MAC, destination MAC>

If the hash factors <source MAC, destination MAC> are hashable enough, try the l3 parameter. If the hash factors <source IP, destination IP> are hashable enough, try the l4 parameter.

Follow-up Procedure

If this command is configured but traffic load balancing cannot be performed well, you can try to modify hash-arithmetic. For detailed information, see Configuring Hash-arithmetic.

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.

Configuring Hash Factors ( P nodes in MPLS Scenarios)

Configuration Guide

NOTE:

This configuration process is supported only on the Admin-VS.

Views Command Format
Slot view load-balance hash-fields mpls { payload-header | label | ip | mac }

Suitable Scenarios

The command is suitable on the P nodes of the L3VPN, VPLS, or the VLL homogenous transport.

This command is used to specify hash factors in MPLS forwarding. If MPLS labels are hashable, select the parameter label. If MPLS labels are not hashable and the labeled inner packets are IP packets, select the ip parameter. If MPLS labels are not hashable and the labeled inner packets are not IP packets, select the parameter payload-header.

Follow-up Procedure

If this command is configured but traffic load balancing cannot be performed well, you can try to modify hash-arithmetic. For detailed information, see Configuring Hash-arithmetic.

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.

Configuring Hash Factors ( Ingress PE in VLL Scenario)

Configuration Guide

NOTE:

This configuration process is supported only on the Admin-VS.

Views Command Format
Slot view load-balance hash-fields vll { l2 | l3 | l4 | label-ip }
NOTE:
  • l2: indicates that hash factors are <source MAC, destination MAC>
  • l3: indicates that hash factors are <source IP address, destination IP address>
  • l4: indicates that hash factors are <source IP address, destination IP address, source port number, destination port number, protocol number>
  • label-ip:
    Extends the l4 mode:
    • For IP packets, hash factors are the source and destination IP addresses, source and destination port numbers, and protocol number.

    • For non-IP packets, hash factors are MPLS labels. If the number of labels is less than or equal to five, all labels are used for hash calculation. If the number of labels is greater than five, five outermost labels are used for hash calculation.

Suitable Scenarios

Ingress PE in VLL Scenario.

  • IP carrying TCP/UDP: the default hash factors are <source IP address, destination IP address, source port number, destination port number, protocol number>
  • IP carrying non-TCP/non-UDP: the default hash factors are <source IP address, destination IP address>

Follow-up Procedure

If this command is configured but traffic load balancing cannot be performed well, you can try to modify hash-arithmetic. For detailed information, see Configuring Hash-arithmetic.

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.

Configuring Hash Factors ( L2/L3VPN Over L2VPN Scenarions)

Configuration Guide

NOTE:

This configuration process is supported only on the Admin-VS.

Views Command Format
Interface of Ethernet type, POS interface view load-balance hash-fields ip l3

Suitable Scenarios

Figure 10-1 L2/L3VPN Over L2VPN

As shown in Figure 10-1, in the L2/L3VPN Over L2VPN Scenarions, L2-PEs are the ingress of the L2VPN tunnel for MPLS L2/L3VPN packets. by default, L2-PEs balance traffic among member interfaces of the outbound Eth-Trunk interface based on MAC addresses carried in packets. Because packets transmitted over the same VPLS tunnel carry the same MAC address, traffic from the same site but different L3VPNs cannot be load-balanced among member interfaces of the Eth-Trunk interface. To solve this problem, you can run this command to configure backbone PEs to work in IP-address-based load-balancing mode, evenly distributing traffic from the same site but different L3VPNs among links between L2-PE1 and L2-P1.

Follow-up Procedure

If this command is configured but traffic load balancing cannot be performed well, you can try to modify hash-arithmetic. For detailed information, see Configuring Hash-arithmetic.

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.

Configuring Hash-arithmetic

NOTE:

This configuration process is supported only on the Admin-VS.

If proper hash factors are selected but traffic load balancing still cannot be performed well, the following method can be used to makes hash factors more hashable.

Configuring Hash-arithmetic

Views Command Format
Slot view load-balance hash-arithmetic { arithmetic1 | arithmetic2 | arithmetic3 | arithmetic4 | arithmetic5 | random }
NOTE:
Parameter description:
  • arithmetic1: specifies the hash algorithm as CRC32.
  • arithmetic2: specifies the hash algorithm as ETH-CRC32.
  • arithmetic3: specifies the hash algorithm as XOR, The hash algorithm CRC253 is used for packets with the TTL fields being even values, and the hash algorithm CRC21b is used for packets with the TTL fields being odd values.
  • arithmetic4: specifies the hash algorithm as CRC32c.
  • arithmetic5: specifies the hash algorithm as 8-bit XOR.
  • random: specifies the hash algorithm as S second-level load balancing algorithm.

In one-level load balancing, the hash algorithm of XOR is preferred in the small hash factor transition scenario.

In two-level load balancing, hash algorithms cannot be configured the same for the first- and second-level load balancing on the router. If they are configured the same, the second-level load balancing does not take effect.

The load balancing effects of hash algorithms vary with different network traffic models. If the load balancing effect of one hash algorithm is not satisfying, use another hash algorithm.

Follow-up Procedure

Run the save command to save the current configuration to the configuration file when a set of configuration is finished and the expected functions have been achieved.

Configuring Dynamic Load Balancing

If existing load balancing configurations do not meet actual needs, configure dynamic load balancing.

Usage Scenario

The router supports multiple load balancing configurations, including IP packet, VPLS, VLL, and trunk member interface-based load balancing configurations. If these configurations do not meet actual needs, configure dynamic load balancing to enable the router to dynamically adjust load balancing.

NOTE:

This configuration process is supported only on the Admin-VS.

Procedure

  1. Configure dynamic load balancing adjustment for a trunk.
    1. Run system-view

      The system view is displayed.

    2. Run load-balance dynamic-adjust trunk enable

      Dynamic load balancing adjustment is enabled for a trunk.

    3. Run commit

      The configuration is committed.

      NOTE:
      To modify key parameters for dynamic load balancing adjustment of a trunk, perform the following optional steps.

    4. (Optional) Run slot slot-id

      The slot view is displayed.

    5. (Optional) Run load-balance dynamic-adjust trunk

      Key parameters are configured for dynamic load balancing adjustment of a trunk.

    6. (Optional) Run commit

      The configuration is committed.

  2. Configure dynamic load balancing.
    1. Run slot slot-id

      The slot view is displayed.

    2. Run load-balance dynamic-adjust enable

      Dynamic load balancing is enabled.

    3. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-02

Document ID: EDOC1100055376

Views: 21447

Downloads: 48

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next