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

S9300, S9300E, and S9300X V200R012C00 Configuration Guide - Ethernet Switching

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, VLAN aggregation, MUX VLAN, VLAN termination, Voice VLAN, VLAN mapping, QinQ, GVRP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, HVRP, and Layer 2 protocol transparent transmission.
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 Load Balancing Mode

(Optional) Configuring a Load Balancing Mode

Context

An Eth-Trunk uses flow-based load balancing. Flow-based load balancing ensures that frames of the same data flow are forwarded on the same physical link and those of different data flows are forwarded on different physical links.

Common load balancing modes load balance packets according to their IP addresses or MAC addresses; enhanced load balancing load balances Layer 2 packets, IP packets, and MPLS packets according to VLAN IDs, protocols, and interface numbers.

Load balancing is valid only for outgoing traffic; therefore, the load balancing modes for the interfaces at both ends of the link can be different and do not affect each other.

When more than 128 Eth-Trunks or 16 member interfaces are configured using the assign trunk { trunk-group group-number | trunk-member member-number }* command, only the enhanced mode can be used for load balancing. If the enhanced mode is not used, problems such as packet loss and uneven load balancing may occur.

NOTE:

SA series cards do not support the enhanced load balancing mode. They still use the common load balancing mode even if enhanced load balancing is configured.

If an incorrect load balancing mode is configured, traffic will be unevenly load balanced among Eth-Trunk member interfaces. The following restrictions apply when configuring a load balancing mode:
  • In practical services, you need to configure a proper load balancing mode based on traffic characteristics. When a parameter of traffic changes frequently, you can set the load balancing mode based on this parameter to ensure that the traffic load is balanced evenly. For example, if IP addresses in packets change frequently, use the load balancing mode based on dst-ip, src-ip, or src-dst-ip so that traffic can be properly load balanced among physical links. If MAC addresses in packets change frequently and IP addresses are fixed, use the load balancing mode based on dst-mac, src-mac, or src-dst-mac so that traffic can be properly load balanced among physical links.

  • If the majority of service traffic are MPLS packets, you need to set the enhanced load balancing mode. You can run the mpls field command in the load balancing profile view to configure the load balancing mode of MPLS packets.

  • On a network where an Eth-Trunk and a CSS are configured, if the local-preference enable command is run to configure an Eth-Trunk interface to preferentially forward local traffic, traffic arriving at the local device is preferentially forwarded through Eth-Trunk member interfaces of the local device. If there is no Eth-Trunk member interface on the local device, traffic is forwarded through Eth-Trunk member interfaces on another device. This forwarding mode effectively saves bandwidth resources of member devices in the CSS and improves traffic forwarding efficiency.

Procedure

  • Configure a common load balancing mode.
    1. Run system-view

      The system view is displayed.

    2. Run interface eth-trunk trunk-id

      The Eth-Trunk interface view is displayed.

    3. Run load-balance { dst-ip | dst-mac | src-ip | src-mac | src-dst-ip | src-dst-mac }

      A common load balancing mode is configured for the Eth-Trunk.

      By default, the switch load balances packets based on the src-dst-ip information.

      NOTE:

      When the device is upgraded from an earlier version of V200R005C00 to V200R011C10 or later and the load balance command is used to set the load balancing mode to dst-dmac, src-smac, or src-dst-mac, information excluding inbound interface information is used for load balancing calculation of known unicast packets by default. You need to run the unicast load-balance sport command to configure the device to use inbound interface information for load balancing calculation of known unicast packets. The unicast load-balance sport command takes effect when the inbound interface of known unicast packets is located on the card excluding the X series and the load balance command is used to set the load balancing mode to dst-dmac, src-smac, or src-dst-mac on the Eth-Trunk in the outbound direction.

  • Configure an enhanced load balancing mode.
    1. Run system-view

      The system view is displayed.

    2. Run load-balance-profile profile-name

      A load balancing profile is created and its view is displayed. Only one load balancing profile can be created.

    3. Run the following commands as required. You can configure a load balancing mode for Layer 2 packets, IPv4 packets, IPv6 packets, and MPLS packets respectively.

      • Run l2 field [ dmac | l2-protocol | smac | sport | vlan ] *

        A load balancing mode is configured for Layer 2 packets.

        By default, the switch load balances Layer 2 packets based on the source MAC address (smac) and destination MAC address (dmac).

      • Run ipv4 field [ dip | l4-dport | l4-sport | protocol | sip | sport | vlan ] *

        A load balancing mode is configured for IPv4 packets.

        By default, the switch load balances IPv4 packets based on the source IP address (sip) and destination IP address (dip).

      • Run ipv6 field [ dip | l4-dport | l4-sport | protocol | sip | sport | vlan ] *

        A load balancing mode is configured for IPv6 packets.

        By default, the switch load balances IPv6 packets based on the source IP address (sip) and destination IP address (dip).

      • Run mpls field [ 2nd-label | 3rd-label | dip | dmac | sip | smac | sport | top-label | vlan ] *

        A load balancing mode is configured for MPLS packets.

        By default, the switch load balances MPLS packets based on the two outer labels (top-label and 2nd-label).

    4. Run quit

      Return to the system view.

    5. Run interface eth-trunk trunk-id

      The Eth-Trunk interface view is displayed.

    6. Run load-balance enhanced profile profile-name

      The load balancing profile is applied.

    NOTE:
    The preceding load balancing modes apply only to known unicast traffic. To configure a load balancing mode for unknown unicast traffic, run the unknown-unicast load-balance { dmac | smac | smacxordmac | enhanced | lbid } command in the system view.

    When the enhanced load balancing mode is used for unknown unicast traffic, specify the VLAN ID in the load balancing profile. When the outbound interface is an Eth-Trunk and is added to a user VLAN, multicast traffic on the device equipped with all LE1D2S04SEC0/LE1D2X32SEC0/LE1D2H02QEC0, or X series cards can be load balanced based on the user VLAN. If other cards are installed on the device, multicast traffic on the device cannot be load balanced based on the user VLAN.

Translation
Download
Updated: 2019-01-18

Document ID: EDOC1100038290

Views: 114041

Downloads: 24

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