No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
CloudEngine 12800 and 12800E V200R005C10 Configuration Guide - IP Unicast Routing

This document describes the configurations of IP Unicast Routing, including IP Routing, Static Route, RIP, RIPng, OSPF, OSPFv3, IPv4 IS-IS, IPv6 IS-IS, BGP, Routing Policy, and PBR.

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 the ECMP Load Balancing Mode

Configuring the ECMP Load Balancing Mode

Context

Equal-Cost Multi-Path (ECMP) implements load balancing and link backup. ECMP applies to the network where multiple links to the same destination are available. In the traditional routing technology, packets are forwarded to the destination through only one link; the other links are in backup or inactive state; traffic switching between these links takes some time when dynamic routes are used. Different from the traditional routing technology, ECMP can use multiple links to increase transmission bandwidth and transmit data on a faulty link without any delay or packet loss. ECMP is classified into per-flow load balancing and per-packet load balancing. Per-flow load balancing can ensure the packet sequence and ensure that the same data flow is forwarded using the same route and different data flows are forwarded using different routes. Per-packet load balancing can improve ECMP bandwidth efficiency to ensure even load balancing among equal-cost routes, but cannot prevent packet mis-sequencing. To ensure packet sequencing, confirm that the device or terminal that receives traffic supports packet reassembly in case of packet mis-sequencing.

In ECMP load balancing on a CE12800 series switch, on SD, FD (only the CE-L16CQ-FD), FD1, FG, and FG1 cards, the hash value is calculated based on the three packet headers starting with the forwarding byte. On the cards except SD, FD (only the CE-L16CQ-FD), FD1, FG, and FG1 cards, the hash value is calculated based on the first 128 bytes of the packet or based on the two packet headers starting with the forwarding byte.

Per-packet load balancing takes precedence over per-flow load balancing. When both of them are configured, per-packet load balancing takes effect.

In per-packet load balancing, devices support the following load balancing modes:
  • random mode: A route is randomly selected among multiple equal-cost routes to forward packets. When the IP address and MAC address of known unicast packets remain unchanged, configure random per-packet load balancing.
  • round-robin mode: Each equal-cost route, in turn, is used to forward packets. When known unicast packets have the similar length, configure round-robin per-packet load balancing.

The CE12800 and CE12800E that has ED-E, EG-E, and EGA-E series cards installed support only round-robin per-packet load balancing.

The CE12800E equipped with FD-X series cards supports random per-packet load balancing and round-robin per-packet load balancing.

In per-flow load balancing, devices support different load balancing modes for different packets, as listed in the following tables.

Table 1-5 Load balancing modes for different packets (CE12800)

Packets (on the Inbound Interface)

Default Load Balancing Mode

Configurable Load Balancing Mode

IPv4 packets

src-ip, dst-ip, l4-src-port, and l4-dst-port

src-ip, dst-ip, l4-src-port, l4-dst-port, and protocol

IPv6 packets

src-ip, dst-ip, l4-src-port, and l4-dst-port

src-ip, dst-ip, l4-src-port, l4-dst-port, and protocol

NOTE:

IPv6 packet load balancing modes, l4-src-port and l4-dst-port, are affected by the l4-src-port and l4-dst-port fields of IPv4 packets. That is, when the load balancing modes of IPv4 packets include l4-src-port or l4-dst-port, the l4-src-port or l4-dst-port field also participates in load balancing of IPv6 packets.

IPv4 over IPv4 packets

src-ip, dst-ip, and inner IP packet-based src-ip and dst-ip

src-ip, dst-ip, and inner IP packet-based src-ip and dst-ip

NOTE:

The ip [ dst-ip | l4-dst-port | l4-src-port | protocol | src-ip ] * command controls the load balancing modes of the src-ip and dst-ip fields in the inner and outer IPv4 headers. That is, when the load balancing mode of IPv4 packets is set to src-ip and dst-ip, the corresponding fields in the inner and outer IP headers of IPv4 over IPv4 packets will participate in hash calculation.

IPv4 over IPv6 packets

src-ip, dst-ip, and inner IPv4 packet-based src-ip and dst-ip

src-ip, dst-ip, and inner IPv4 packet-based src-ip and dst-ip

NOTE:
  • The ip [ dst-ip | l4-dst-port | l4-src-port | protocol | src-ip ] * command controls the load balancing modes of the src-ip and dst-ip fields in the inner IPv4 headers. That is, when the load balancing mode of IPv4 packets is set to src-ip and dst-ip, the corresponding fields in the inner IPv4 headers of IPv4 over IPv6 packets will participate in hash calculation.
  • The ipv6 [ dst-ip | protocol | src-ip ] * command controls the load balancing modes of the src-ip and dst-ip fields in the outer IPv6 headers. That is, when the load balancing mode of IPv6 packets is set to src-ip and dst-ip, the corresponding fields in the outer IPv6 headers of IPv4 over IPv6 packets will participate in hash calculation.

IPv6 over IPv4 packets

src-ip, dst-ip, and inner IPv6 packet-based src-ip and dst-ip

src-ip, dst-ip, and inner IPv6 packet-based src-ip and dst-ip

NOTE:
  • The ipv6 [ dst-ip | protocol | src-ip ] * command controls the load balancing modes of the src-ip and dst-ip fields in the inner IPv6 headers. That is, when the load balancing mode of IPv6 packets is set to src-ip and dst-ip, the corresponding fields in the inner and outer IPv6 headers of IPv6 over IPv4 packets will participate in hash calculation.
  • The ip [ dst-ip | l4-dst-port | l4-src-port | protocol | src-ip ] * command controls the load balancing modes of the src-ip and dst-ip fields in the outer IPv4 headers. That is, when the load balancing mode of IPv4 packets is set to src-ip and dst-ip, the corresponding fields in the outer IPv4 headers of IPv6 over IPv4 packets will participate in hash calculation.

IPv6 over IPv6 packets

src-ip, dst-ip, and inner IPv6 packet-based src-ip and dst-ip

src-ip, dst-ip, and inner IPv6 packet-based src-ip and dst-ip

NOTE:

The ipv6 [ dst-ip | protocol | src-ip ] * command controls the load balancing modes of the src-ip and dst-ip fields in the inner and outer IPv6 headers.

That is, when the load balancing mode of IPv6 packets is set to src-ip and dst-ip, the corresponding fields in the inner and outer IPv6 headers of IPv6 over IPv6 packets will participate in hash calculation.

TRILL packets

Ingress: Non-IP packets are load balanced based on the inner src-mac, vlan, and dst-mac. IP packets are load balanced based on src-ip, dst-ip, l4-src-port, and l4-dst-port.

src-ip, dst-ip, l4-src-port, l4-dst-port, protocol, vlan, and src-interface

Transit/Egress: Packets are load balanced based on the inner src-mac and dst-mac.

The load balancing mode cannot be configured.

MPLS packets

Transit: top-label, 2nd-label, and fields in the inner IP header (on SD, FD (only the CE-L16CQ-FD), FD1, FG, and FG1 cards, IPv4: src-ip, dst-ip, l4-src-port, and l4-dst-port or IPv6: src-ip, dst-ip, l4-src-port, and l4-dst-port; on cards except SD, FD (only the CE-L16CQ-FD), FD1, FG, and FG1 cards, IPv4: src-ip and dst-ip or IPv6: src-ip and dst-ip)

Egress: top-label, 2nd-label, and fields in the inner IP header (IPv4: src-ip, dst-ip, l4-src-port, and l4-dst-port or IPv6: src-ip, dst-ip, l4-src-port, and l4-dst-port)

top-label, 2nd-label, 3rd-label, src-ip, dst-ip, l4-src-port, and l4-dst-port

VPLS packets
Transit:
  • For FD, FDA, FG, FD1, FG1, and SD series cards: top-label, 2nd-label, and fields in the inner Ethernet header (src-mac and dst-mac)
  • For other cards: top-label, 2nd-label

inner-sip and inner-dip

NOTE:
  • The load balancing mode based on fields in the inner Ethernet header (src-mac and dst-mac) does not need to be configured, but the fields that participate in load balancing are affected by the load balancing mode configuration of the l2 [ src-mac | dst-mac | vlan | eth-type ] * command.
  • The load balancing mode based on top-label and 2nd-label is affected by the load balancing mode configuration of MPLS packets. In an inter-AS VPLS Option C scenario, after PHP is disabled, if packets carry three labels, packets can be load balanced based only on the top-label and 2nd-label fields of MPLS packets. If packets carry more than three labels, packets can be load balanced based only on the outer label.

VXLAN packets

l4-src-port

inner-src-mac, inner-dst-mac, inner-src-ip, inner-dst-ip, inner-l4-src-port, inner-l4-dst-port, inner-protocol, and l4-src-port
Table 1-6 Load balancing modes for different packets (on the CE12800E that has ED-E, EG-E, or EGA-E series cards installed)

Packets (on the Inbound Interface)

Default Load Balancing Mode

Configurable Load Balancing Mode

IP packets

src-ip, dst-ip, l4-src-port, and l4-dst-port

src-ip, dst-ip, l4-src-port, l4-dst-port, protocol, vlan, src-interface, dscp

GRE packets

Non-IP packets are load balanced based on the inner inner-src-ip, inner-dst-ip, inner-l4-dport, and inner-l4-sport. IP packets are load balanced based on src-ip, dst-ip, l4-src-port, and l4-dst-port.

inner-src-ip, inner-dst-ip, inner-l4-dport, and inner-l4-sport
Table 1-7 Load balancing modes for different packets (on the CE12800E that has FD-X series cards installed)

Packets (on the Inbound Interface)

Default Load Balancing Mode

Configurable Load Balancing Mode

IPv4 packets

src-ip, dst-ip, l4-src-port, and l4-dst-port

src-ip, dst-ip, l4-src-port, l4-dst-port, protocol, vlan, and src-interface

IPv6 packets

src-ipv6, dst-ipv6, l4-src-port, and l4-dst-port

src-ipv6, dst-ipv6, l4-src-port, l4-dst-port, protocol, vlan, and src-interface

Procedure

  • Configure ECMP load balancing on the CE12800.
    1. Run system-view

      The system view is displayed.

    2. Run load-balance profile profile-name

      A load balancing profile is configured and its view is displayed.

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

      • Run ip [ dst-ip | l4-dst-port | l4-src-port | protocol | src-ip ] *

        The load balancing mode of IPv4 packets is set in the load balancing profile.

      • Run ipv6 [ dst-ip | protocol | src-ip ] *

        The load balancing mode of IPv6 packets is set in the load balancing profile.

        IPv6 packet load balancing modes, l4-src-port and l4-dst-port, are affected by the l4-src-port and l4-dst-port fields of IPv4 packets. That is, when the load balancing modes of IPv4 packets include l4-src-port or l4-dst-port, the l4-src-port or l4-dst-port field also participates in load balancing of IPv6 packets.

      • Run mpls [ 2nd-label | 3rd-label | top-label ] * or mpls [ src-ip | dst-ip | l4-src-port | l4-dst-port ] *

        The load balancing mode of MPLS packets is set in the load balancing profile.

        By default, load balancing of MPLS packets is based on the two outer labels (top-label and 2nd-label) of each packet.

        On an IPv6 underlay network, if the IPv6 VXLAN function is enabled and the switch functions as a transit or egress node on the MPLS network, configurations related to the hash field in inner information in MPLS packets do not take effect in the load balancing profile. In this scenario, the mpls inner-type { ipv4 | ipv6 | l2 | any } command cannot be used to change the load balancing mode for MPLS packets in the load balancing profile. Instead, you can use the source and destination IP addresses in inner information in MPLS packets to configure a load balancing mode in the load balancing profile.

        • The mpls [ inner-ip | inner-ipv6 ] * command can be configured only when the IPv6 VXLAN function is enabled. In addition, this command cannot be used to configure a load balancing mode for VPLS packets. If the IPv6 VXLAN function is disabled, the switch automatically deletes the configurations related to the mpls [ inner-ip | inner-ipv6 ] * command.
        • For CE12800 series switches, if MPLS packets with four or more labels are received, Eth-Trunk or ECMP load balancing cannot be implemented based on the inner IP header. In V200R019C00 and later versions, after the assign forward segment-routing hash enhanced command is run, Eth-Trunk or ECMP load balancing can be implemented on MPLS packets with up to five labels.
        • For CE12800 series switches, if the implicit null label is disabled and the outer label is popped out (for example, ASBR in inter-AS VPN Option B and inter-AS VPN Option C networking), packets may be unable to be load balanced in the load balancing mode using ECMP or Eth-Trunk based on the inner field in MPLS packets.
        • The mpls [ inner-ip | inner-ipv6 ] * command takes effect only on SD, FD (only the CE-L16CQ-FD), FD1, FG, and FG1 series cards.
        • If EA, EC, ED, EF, EG, or BA series cards are used:
          • On an egress node, the load balancing mode based on fields in the inner IP header (IPv4: src-ip, dst-ip, l4-src-port, and l4-dst-port, or IPv6: ipv6 src-ip and ipv6 dst-ip) does not need to be configured, but the fields that participate in load balancing are affected by the load balancing mode configuration of IPv4 and IPv6 packets. If the l4-src-port and l4-dst-port fields are specified in the configured load balancing mode, packets may be unable to be load balanced in the configured load balancing mode. To prevent this problem, cancel the configuration of the l4-src-port and l4-dst-port fields in the load balancing mode of IPv4 packets.
          • On a transit node, the load balancing mode based on fields in the inner IP header (IPv4: src-ip and dst-ip or IPv6: src-ip and dst-ip) does not need to be configured, but the fields that participate in load balancing are affected by the load balancing mode configuration of IPv4 and IPv6 packets and the l4-src-port and l4-dst-port fields do not participate in load balancing of MPLS packets. The mpls [ src-ip | dst-ip | l4-src-port | l4-dst-port ] * command used to change the load balancing mode of MPLS packets does not take effect on EA, EC, ED, EF, EG, and BA series cards.
        • For FD and FDA series cards (excluding the CE-L16CQ-FD):
          • On an egress node, the load balancing mode based on fields in the inner IP header (IPv4: src-ip, dst-ip, l4-src-port, and l4-dst-port or IPv6: src-ip, dst-ip, l4-src-port, and l4-dst-port) does not need to be configured, but the fields that participate in load balancing are affected by the load balancing mode configuration of IPv4 and IPv6 packets. If the l4-src-port and l4-dst-port fields are specified in the configured load balancing mode, packets may be unable to be load balanced in the configured load balancing mode. To prevent this problem, cancel the configuration of the l4-src-port and l4-dst-port fields in the load balancing mode of IPv4 packets.
          • On a transit node, the load balancing mode based on fields in the inner IP header (IPv4: src-ip and dst-ip or IPv6: src-ip and dst-ip) does not need to be configured, but the fields that participate in load balancing are affected by the load balancing mode configuration of IPv4 and IPv6 packets. If the mpls [ src-ip | dst-ip | l4-src-port | l4-dst-port ] * command is executed to change the load balancing mode for MPLS packets and the l4-src-port and l4-dst-port fields are specified for load balancing, packets may be unable to be load balanced in the configured load balancing mode. To prevent this problem, run this command again without specifying the l4-src-port and l4-dst-port fields.
        • If FG, FD1, FG1, and SD series cards and CE-L16CQ-FD cards are used, the load balancing mode based on fields in the inner IP header (IPv4: src-ip, dst-ip, l4-src-port, and l4-dst-port or IPv6: src-ip, dst-ip, l4-src-port, and l4-dst-port) does not need to be configured, but the fields that participate in load balancing are affected by the load balancing mode configuration of IPv4 and IPv6 packets. If the l4-src-port and l4-dst-port fields are specified in the configured load balancing mode, packets may be unable to be load balanced in the configured load balancing mode. To prevent this problem, cancel the configuration of the l4-src-port and l4-dst-port fields in the load balancing mode of IPv4 and MPLS packets.

      • Run vxlan { inner-src-mac | inner-dst-mac | inner-src-ip | inner-dst-ip | inner-l4-src-port | inner-l4-dst-port | inner-protocol | l4-src-port | shift shift-data } *

        A load balancing mode is configured for VXLAN packets in the load balancing profile.

        By default, load balancing of VXLAN packets is based on l4-src-port of the outer UDP source port number.

        The command is not supported on the following cards: CE-L48GT-EA, CE-L48GT-EC, CE-L48GS-EA, CE-L48GS-EC, CE-L24XS-BA, CE-L24XS-EA, CE-L48XS-BA, CE-L48XS-EA and CE-L24LQ-EA. Do not use these cards together with the cards that support this command; otherwise, load balancing will become uneven.

    4. Run ecmp { src-interface | seed seed-data } *

      The ECMP load balancing mode is set in the enhanced load balancing profile.

      By default, the ECMP load balancing mode is seed.

    5. Run ecmp universal-id universal-id

      The hash algorithm offset of ECMP load balancing is set.

      By default, the hash algorithm offset of ECMP load balancing is 1.

      The default universal-id in ECMP load balancing is 11 in V100R005C00 and 1 in other versions. After an upgrade to V100R005C00, the default universal-id is changed from 1 to 11. After an upgrade from V100R005C00 to another version, the default universal-id is changed from 11 to 1. In V100R005C10 and later versions, you can run the ecmp universal-id universal-id command to change the hash algorithm offset. The default hash algorithm offset can ensure even load balancing in most scenarios. If uneven load balancing occurs, change the hash algorithm offset to adjust the forwarding path calculated using the hash algorithm.

    6. Run ecmp hash-mode hashmode-id

      The hash algorithm mode used in ECMP load balancing is configured.

      By default, the hash algorithm mode used in ECMP load balancing is 2. If the hash algorithm mode is set to 3, 4, or 5, the load balancing mode is per-packet load balancing.

    7. Run ecmp local-preference enable

      Local traffic preferential forwarding is enabled.

      By default, local traffic preferential forwarding is disabled.

    8. Run commit

      The configuration is committed.

  • Configure the ECMP load balancing mode (on the CE12800E that has the ED-E, EG-E, or EGA-E series cards installed).
    1. Run system-view

      The system view is displayed.

    2. Run load-balance ecmp

      The ECMP view is displayed.

    3. Run the following commands as required. You can configure a load balancing mode for IP packets.

      • Run ip { src-ip | dst-ip | vlan | l4-src-port | l4-dst-port | protocol | src-interface | dscp } *

        A load balancing mode is configured for IP packets.

        For the CE12800E with ED-E, EG-E, and EGA-E series cards installed, VXLAN packets are load balanced based on the IP packet type and based only on the outer source and destination IP addresses and the Layer 4 source and destination port numbers of the packets.

        For IPv4 over IPv4 packets, IPv4 over IPv6 packets, IPv6 over IPv4 packets, and IPv6 over IPv6 packets, if src-ip and dst-ip are configured for load balancing, the switch performs load balancing based on the source and destination IP addresses in the outer IP headers of IPinIP packets.

      • Run ip-tunnel { inner-src-ip | inner-dst-ip | inner-l4-sport | inner-l4-dport } *

        A load balancing mode is configured for GRE packets.

    4. Run hashmode hashmode-id

      The hash algorithm mode used in ECMP load balancing is configured.

      By default, the hash algorithm mode used in ECMP load balancing is 0. If the hash algorithm mode is set to 1, the load balancing mode is per-packet load balancing.

    5. Run local-preference enable

      Local traffic preferential forwarding is enabled.

      By default, local traffic preferential forwarding is disabled.

    6. Run commit

      The configuration is committed.

  • Configure ECMP load balancing (on the CE12800E that has the FD-X series cards installed).

    Per-flow load balancing:

    1. Run system-view

      The system view is displayed.

    2. Run load-balance ecmp

      The ECMP view is displayed.

    3. You can configure different load balancing modes for different packets. Perform the following operations according to network packet types.

      • Run ipv4 { src-ip | dst-ip | vlan | l4-src-port | l4-dst-port | protocol | src-interface } *

        A load balancing mode is configured for IPv4 packets.

      • Run ipv6 { src-ipv6 | dst-ipv6 | vlan | l4-src-port | l4-dst-port | protocol | src-interface } *

        A load balancing mode is configured for IPv6 packets.

      For IPv4 over IPv4 packets, IPv4 over IPv6 packets, IPv6 over IPv4 packets, and IPv6 over IPv6 packets, if src-ip, dst-ip, and src-ipv6 are configured for load balancing, the switch performs load balancing based on the source and destination IP addresses in the inner IP headers of IPinIP packets.

      If src-ipv6 and dst-ipv6 are specified for ECMP load balancing of IPv6 packets, the switch uses only the low-order 32 bits of the source and destination IPv6 addresses as the hash fields.

    4. Run hashmode hashmode-id

      The hash algorithm mode used in ECMP load balancing is configured.

      By default, the hash algorithm mode used in ECMP load balancing is 4.

    5. Run local-preference enable

      Local traffic preferential forwarding is enabled.

      By default, local traffic preferential forwarding is disabled.

    6. Run commit

      The configuration is committed.

    Per-packet load balancing:

    1. Run system-view

      The system view is displayed.

    2. Run load-balance ecmp

      The ECMP view is displayed.

    3. Run load-balance { random | round-robin }

      Random or round-robin per-packet load balancing is configured.

      If both per-packet load balancing and per-flow load balancing are configured in ECMP, per-packet load balancing takes effect.

    4. Run commit

      The configuration is committed.

  • Configure simulated calculation of an ECMP outbound interface.

    Run display load-balance forwarding-path unicast interface ecmp { vlan vlan-id | src-interface interface-type interface-number | vpn-instance vpn-instance-name | [ [ src-ip src-ip-data | dst-ip dst-ip-data ] * | [ src-ipv6 src-ipv6-data | dst-ipv6 dst-ipv6-data ] * ] | protocol { protocol-number [ l4-src-port src-port-data | l4-dst-port dst-port-data ] | icmp | igmp | ip | ospf | tcp [ l4-src-port src-port-data | l4-dst-port dst-port-data ] * | udp [ l4-src-port src-port-data | l4-dst-port dst-port-data ] * } } * slot slot-id

    Simulated calculation of an ECMP outbound interface is configured after the 5-tuple information, source MAC address, and destination address are specified.

Verifying the Configuration

  • Run the display load-balance forwarding-path unicast interface ecmp { vlan vlan-id | src-interface interface-type interface-number | vpn-instance vpn-instance-name | [ [ src-ip src-ip-data | dst-ip dst-ip-data ] * | [ src-ipv6 src-ipv6-data | dst-ipv6 dst-ipv6-data ] * ] | protocol { protocol-number [ l4-src-port src-port-data | l4-dst-port dst-port-data ] | icmp | igmp | ip | ospf | tcp [ l4-src-port src-port-data | l4-dst-port dst-port-data ] * | udp [ l4-src-port src-port-data | l4-dst-port dst-port-data ] * } } * slot slot-id command to configure simulated calculation of an ECMP outbound interface for IPv4 and IPv6 packets after the 5-tuple information, source MAC address, and destination address are specified.
Translation
简体中文
Download
Updated: 2021-09-17

Document ID: EDOC1100075354

Views: 418159

Downloads: 114

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :