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 - Ethernet Switching

CloudEngine 8800, 7800, 6800, and 5800 V200R003C00

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, MUX VLAN, Voice VLAN, VLAN mapping, QinQ, GVRP, VCMP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, 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 (CE6870EI and CE6875EI)

(Optional) Configuring a Load Balancing Mode (CE6870EI and CE6875EI)

Context

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

Load balancing is valid only for outgoing traffic; therefore, interfaces at both ends of the link can use different load balancing modes.

Table 3-10 lists load balancing modes for different types of packets.

Table 3-10 Load balancing modes for different types of packets

Packet (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 controlled 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.

MPLS packets

top-label, fields in the inner IP header (src-ip and dst-ip or ipv6 src-ip and ipv6 dst-ip), and 2nd-label top-label, 2nd-label, and 3rd-label

VPLS packets

top-label, fields in the inner ETH header (src-mac,dst-mac, and ETH TYPE), and 2nd-label inner-sip and inner-dip

Layer 2 packets except IPv4, IPv6, and MPLS packets

src-mac, dst-mac and vlan src-mac, dst-mac, vlan, and eth-type

TRILL packets

Ingress node: src-mac, dst-mac, and vlan for Layer 2 packets; src-ip, dst-ip, l4-src-port, and l4-dst-port for Layer 3 packets

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

Transit node: src-mac, dst-mac, vlan, src-ip and dst-ip in the inner tag

src-mac, dst-mac, vlan, src-ip and dst-ip

Egress node: src-mac, dst-mac, vlan, src-ip and dst-ip in the inner tag

src-mac, dst-mac, vlan, src-ip and dst-ip

FCoE packets

dst-fcid and src-fcid dst-fcid, src-fcid
NOTE:

For MPLS packets, the load balancing mode based on fields in the inner IP header (src-ip and dst-ip or ipv6 src-ip and ipv6 dst-ip) and in the inner ETH header (src-mac, dst-mac, and ETH TYPE) does not need to be configured, and cannot be canceled.

For VPLS packets, the load balancing mode based on fields in the inner ETH header (src-mac, dst-mac, and ETH TYPE) does not need to be configured, and cannot be canceled.

Procedure

  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. profile-name specifies the name of the load balancing profile.

    By default, there is a load balancing profile named default.

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

    • Run l2 [ src-mac | dst-mac | vlan | eth-type ] *

      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 (src-mac), destination MAC address (dst-mac), and VLAN ID (vlan).

      NOTE:

      During Layer 2 forwarding, the switch load balances only IPv4, IPv6, 802.1ah, ARP and CFM packets based on eth-type.

      During Layer 2 forwarding, an Eth-Trunk configured with Dot1q tunnel, VLAN stacking, VLL, or VPLS cannot load balance packets based on the VLAN ID.

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

      A load balancing mode is configured for IPv4 packets.

      By default, the switch load balances IPv4 packets based on the source IP address (src-ip), destination IP address (dst-ip), transport-layer source port numbers (l4-src-port), and transport-layer destination port numbers (l4-dst-port).

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

      A load balancing mode is configured for IPv6 packets.

      By default, the switch load balances IPv6 packets based on the source IP address (src-ip), destination IP address (dst-ip), transport-layer source port numbers (l4-src-port), and transport-layer destination port numbers (l4-dst-port).

      NOTE:

      To load balance IPv6 packets based on the transport-layer source and destination port numbers, run the ip [ l4-src-port | l4-dst-port ] * command.

    • Run mpls [ 2nd-label | 3rd-label | top-label ] *

      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).

    • Run user-defined ethernet-over-mpls [ dot1q-tag tag-number ] { inner-sip sip-offset sip-nybble-number | inner-dip dip-offset dip-nybble-number } *

      An Eth-Trunk is configured to load balance VPLS packets based on the IP address in the inner tag.

    • Run fcoe { dst-fcid | src-fcid } *

      A load balancing mode is configured for FCoE packets.

      By default, the switch load balances FCoE packets based on the source FC_ID (src-fcid) and destination FC_ID (dst-fcid).

    • Run trill egress mode { l2 | ipv4 | ipv6 }

      An Eth-Trunk load balancing mode is configured on egress and transit nodes of the TRILL network.

      By default, the Eth-Trunk load balancing mode on egress and transit nodes of the TRILL network is ipv4.
      • l2: indicates load balancing based on the source MAC address, destination MAC address, and VLAN ID. The items used in load balancing depend on the l2 command.
      • ipv4: indicates load balancing based on the source MAC address, destination MAC address, source IPv4 address, destination IPv4 address, and VLAN ID. The items used in load balancing depend on the l2 and ip commands.
      • ipv6: indicates load balancing based on the source MAC address, destination MAC address, source IPv6 address, destination IPv6 address, and VLAN ID. The items used in load balancing depend on the l2 and ipv6 commands.
    • Run eth-trunk { src-interface | seed seed-data | universal-id universal-id | hash-mode hash-mode-id } *

      A load balancing mode is configured for a LAG.

      NOTE:

      Packets forwarded at Layer 3 cannot be load balanced based on destination MAC addresses, source MAC addresses, VLAN IDs, and Ethernet types.

      Link aggregation and ECMP on the device share the same load balancing profile. The load balancing mode configured by using the l2, ip, ipv6, or mpls command takes effect for both link aggregation and ECMP. The load balancing modes configured by using the eth-trunk (load-balance-profile view) and ecmp (load-balance-profile view) commands take effect for only link aggregation and ECMP respectively.

      When load balancing of the LAG and ECMP is uneven, change the value of universal-id or the hash mode.

    • Run mode symmetry

      A method is configured for an Eth-Trunk to hash a pair of flows to the same interface.

      By default, no method is configured for an Eth-Trunk to hash a pair of flows to the same interface.

  4. Run commit

    The configuration is committed.

Follow-up Procedure

  • Configure simulated calculation of an Eth-Trunk outbound interface.

    Run display load-balance forwarding-path unicast interface eth-trunk trunk-id src-interface interface-type interface-number { ethtype ethtype-number | vlan vlan-id | src-ip src-ip-data | dst-ip dst-ip-data | src-mac src-mac-data | dst-mac dst-mac-data | protocol { protocol-number | 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 Eth-Trunk outbound interface is configured after the 5-tuple information, source MAC address, and destination address are specified.

  • Verifying the Configuration

    Run display port forwarding-path { src-ip src-ip-data | dst-ip dst-ip-data | src-mac src-mac-data | dst-mac dst-mac-data | protocol { protocol-number | gre | icmp | igmp | ip | ipinip | 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 ] * } } * [ enhanced ]

    Verify the outbound interface of packets that contain specified 5-tuple information, source MAC address, and destination MAC address.

Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004351

Views: 126767

Downloads: 296

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