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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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 Ethernet Link Aggregation

Configuring Ethernet Link Aggregation

This section describes the Etherent link aggregation configuration.

Configuring Link Aggregation in Manual Load Balancing Mode

Link aggregation implements load balancing, increases interface bandwidth, and improves transmission reliability.

(Optional) Flexibly Setting the Number of LAGs

Context

Generally, the number of LAGs supported by the device is fixed. You can run the assign forward eth-trunk mode command to flexibly set the number of LAGs supported by the device, implementing flexible networking and meeting diversified service requirements.

NOTE:

This command is supported by CX910/CX911/CX912/CX913 10GE switching planes and CX31x/CX710 switching planes.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    assign forward eth-trunk mode { 64 | 128 }

    The number of LAGs supported by the device is set.

    By default, the device supports 128 LAGs.

    NOTE:

    After the assign forward eth-trunk mode command is used to change the number of LAGs supported by the device, restart the device to make the configuration take effect.

  3. Run:

    commit

    The configuration is committed.

Creating an LAG

Context

Each LAG corresponds to a logical interface, that is, Eth-Trunk. Before configuring link aggregation, create an Eth-Trunk.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface eth-trunk trunk-id

    An Eth-Trunk is created and the Eth-Trunk interface view is displayed.

    trunk-id is the Eth-Trunk ID. The value range depends on the switch module type.
    • For CX110/CX111/CX915 switching planes, the trunk ID range is from 0 to 127.
    • For CX910/CX911/CX912/CX913 10GE switching planes and CX31x/CX710 switching planes, the trunk ID range depends on the command assign forward eth-trunk mode { 64 | 128 }.
      • When 64 is used in the command, the trunk ID range is from 0 to 63.
      • When 128 is used in the command, the trunk ID range is from 0 to 127.

    If the specified Eth-Trunk already exists, this command directly displays the Eth-Trunk interface view.

  3. Run:

    commit

    The configuration is committed.

Setting the Manual Load Balancing Mode

Context

Link aggregation can work in manual load balancing mode and LACP mode.

In manual load balancing mode, you must manually create an Eth-Trunk and add member interfaces into the Eth-Trunk. All active links forward data and evenly load balance traffic. The manual load balancing mode mode is used when the peer device does not support LACP.

Procedure

  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:

    mode manual [ load-balance ]

    The working mode of the Eth-Trunk is configured.

    By default, an Eth-Trunk works in manual load balancing mode.

    Before configuring an Eth-Trunk, ensure that both ends use the same working mode. If the local end works in manual load balancing mode, the peer end must use the manual load balancing mode.

  4. Run:

    commit

    The configuration is committed.

Adding Member Interfaces to an Eth-Trunk

Context

You can add member interfaces to an Eth-Trunk in the Eth-Trunk interface view or member interface view.

Figure 5-29 Recommended deployment mode (when the member interfaces of multiple Eth-Trunk interfaces are deployed on different boards)
Figure 5-30 Deployment mode that is not recommended (when the member interfaces of multiple Eth-Trunk interfaces are deployed on different boards)

Procedure

  • Adding member interfaces to an Eth-Trunk in the Eth-Trunk interface view
    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:

      trunkport interface-type { interface-number1 [ to interface-number2 ] } &<1-16>

      A member interface is added to the Eth-Trunk.

      NOTE:

      On the CX111&CX915 switch module GE switching plane, run the trunkport interface-type { interface-number1 [ to interface-number2 ] } &<1-8> command to add member interfaces.

      NOTE:

      When member interfaces are added to an Eth-Trunk in batches, if one interface cannot be added to the Eth-Trunk, all the interfaces cannot be added to the Eth-Trunk.

    4. Run:

      commit

      The configuration is committed.

  • Adding member interfaces to an Eth-Trunk in the member interface view
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The member interface view is displayed.

    3. Run:

      eth-trunk trunk-id

      The member interface is added to an Eth-Trunk.

    4. Run:

      commit

      The configuration is committed.

    When adding an interface to an Eth-Trunk, pay attention to the following points:

    • On CX110 switching plane, each Eth-Trunk contains a maximum of 16 member interfaces.
    • On CX111/CX915 switching planes, each Eth-Trunk contains a maximum of 8 member interfaces.
    • On CX910/CX911/CX912/CX913 10GE switching planes and CX31x/CX710 switching planes, the maximum number of member interfaces on each Eth-Trunk depends on the command assign forward eth-trunk mode { 64 | 128 }.
      • When 64 is used in the command, each Eth-Trunk contains a maximum of 32 member interfaces.
      • When 128 is used in the command, each Eth-Trunk contains a maximum of 16 member interfaces.
    • A member interface cannot be configured with some service or static MAC address.
    • When adding an interface to an Eth-Trunk, ensure that the link-type of the interface is default link-type.
    • An Eth-Trunk cannot be nested, that is, its member interfaces cannot be Eth-Trunk.
    • An Ethernet interface can be added to only one Eth-Trunk. To add the Ethernet interface to another Eth-Trunk, delete it from the Eth-Trunk first.
    • An Eth-trunk contains member interfaces of the same type.
    • The peer interfaces directly connected to the local Eth-Trunk member interfaces must also be bundled into an Eth-Trunk; otherwise, the two ends cannot communicate.
    • After interfaces are added to an Eth-Trunk, MAC addresses and ARP are learned on the Eth-Trunk but not the member interfaces.
    • The rates at both ends of the Eth-Trunk must be the same. It is recommended that the number of connected physical interfaces, and jumbo and flow control configuration at both ends of the Eth-Trunk be the same.
    • Before adding the Ethernet optical port on the CX311 panel to the Eth-trunk, delete the default ACL rules from the port. The default ACL rules can be added to the Eth-trunk.
    • In a stack scenario, it is recommended that the number of member interfaces added to an LAG be the nth power of 2. Otherwise, unknown unicast traffic may be unevenly load balanced.
    • When a compute node interface is added to Eth-Truck, run the undo stp disable command to delete the stp disable configuration.

(Optional) Setting the Lower Threshold for the Number of Active Interfaces

Context

The lower threshold for the number of active interfaces affects the status and bandwidth of the trunk interface. To ensure that the trunk interface functions properly and is less affected by changes in member link status, set the following thresholds.

When the number of active interfaces falls below this threshold, the Eth-Trunk goes Down. This ensures that the Eth-Trunk has a minimum available bandwidth.

NOTE:

The upper threshold for the number of active interfaces is inapplicable to the manual load balancing mode.

Procedure

  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:

    least active-linknumber link-number

    The lower threshold for the number of active interfaces is set.

    By default, the lower threshold for the number of active interfaces is 1.

    The lower threshold for the number of active interfaces on the local switch modules can be different from that on the remote switch modules. If the two values are different, the larger one is used.

  4. Run:

    commit

    The configuration is committed.

(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. Different data flows are forwarded on different physical links to implement load balancing.

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.

Table 5-11 describes load balancing modes for different types of packets.

Table 5-11 Load balancing modes for different types of packets

Packet (Inbound Interface)

Default Load Balancing Mode

Configurable Load Balancing Mode

Remarks

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

The load balancing mode is relevant to the packet type and irrelevant to the packet forwarding process.

For example, even if the system provides only Layer 2 forwarding for IPv4 packets, the IPv4 packets are load balanced according to the load balancing mode for IPv4 packets. When the system cannot identify IPv4, IPv6, or MPLS packets, the system load balances packets based on src-mac, dst-mac, src-interface, and eth-type for Layer 2 packets.

IPv6 packets

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

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

MPLS packets

top-label and 2nd-label

top-label, 2nd-label, dst-ip and src-ip

Layer 2 packets except IPv4, IPv6, and MPLS packets

src-mac and dst-mac

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

Trill packets

  • Ingress node: inner src-mac and dst-mac 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, src-interface, l4-src-port, l4-dst-port, protocol and eth-type

Trill packets can be load balanced on the transit and egress nodes only when the load-balance enhanced profile profile-name command is used.

Transit/Egress node: inner src-mac and dst-mac for Layer 2 packets; src-ip, dst-ip, l4-src-port, and l4-dst-port for Layer 3 packets

Non-configurable

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. (Optional) 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.

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

    • Run:

      l2 [ src-mac | dst-mac | src-interface | eth-type ] *

      The load balancing mode of Layer 2 packets (non-IP packets) is set.

      By default, load balancing of Layer 2 packets (non-IP packets) is based on the source MAC address (src-mac) and destination MAC address (dst-mac).

    • Run:

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

      The load balancing mode of IPv4 packets is set.

      By default, load balancing of IPv4 packets is 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 | l4-src-port | l4-dst-port ] *

      The load balancing mode of IPv6 packets is set.

      By default, load balancing of IPv6 packets is 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:

      mpls [ top-label | dst-ip | src-ip | 2nd-label ] *

      The load balancing mode of MPLS packets is set.

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

    • Run:

      eth-trunk { hash-mode hash-mode-id | universal-id universal-id } *

      A load balancing mode of an Eth-Trunk is set.

      By default, load balancing of an Eth-Trunk is based on hash-mode (1), universal-id (1).

  3. Run:

    quit

    Return to the system view.

  4. Run the following commands as required.

    • Configure a load balancing mode for known unicast traffic.

      1. Run:

        interface eth-trunk trunk-id

        The Eth-Trunk interface view is displayed.

      2. Run:

        load-balance { dst-ip | dst-mac | src-ip | src-mac | src-dst-ip | src-dst-mac | enhanced profile profile-name }

        A load balancing mode of the Eth-Trunk is set.

        By default, the load balancing mode of the Eth-Trunk is enhanced profile.

        • dst-ip: Load balancing is performed based on destination IP addresses.

        • dst-mac: Load balancing is performed based on destination MAC addresses.

        • src-ip: Load balancing is performed based on source IP addresses.

        • src-mac: Load balancing is performed based on source MAC addresses.

        • src-dst-ip: Load balancing is performed based on the Exclusive-Or result of source and destination IP addresses.

        • src-dst-mac: Load balancing is performed based on the Exclusive-Or result of source and destination MAC addresses.

        • enhanced profile: Load balancing is performed based on the fields in the global load balancing profile.

      3. Run:

        commit

        The configuration is committed.

    • Configure a load balancing mode for unknown unicast traffic.

      1. Run:

        load-balance unknown-unicast { mac | enhanced }

        A load balancing mode is configured.

        By default, the load balancing mode is enhanced.

      2. Run:

        commit

        The configuration is committed.

Checking the Configuration

Procedure

  • Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check the Eth-Trunk configuration.
  • Run the display eth-trunk membership trunk-id command to check information about member interfaces of the Eth-Trunk.
  • Run the display load-balance profile [ profile-name ] command to check details of a load balancing profile of the Eth-Trunk.

Configuring Link Aggregation in LACP Mode

Link aggregation implements load balancing, increases interface bandwidth, and improves transmission reliability.

(Optional) Flexibly Setting the Number of LAGs

Context

Generally, the number of LAGs supported by the device is fixed. You can run the assign forward eth-trunk mode command to flexibly set the number of LAGs supported by the device, implementing flexible networking and meeting diversified service requirements.

NOTE:

This command is supported by CX910/CX911/CX912/CX913 10GE switching planes and CX31x/CX710 switching planes.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    assign forward eth-trunk mode { 64 | 128 }

    The number of LAGs supported by the device is set.

    By default, the device supports 128 LAGs.

    NOTE:

    After the assign forward eth-trunk mode command is used to change the number of LAGs supported by the device, restart the device to make the configuration take effect.

  3. Run:

    commit

    The configuration is committed.

Creating an LAG

Context

Each LAG corresponds to a logical interface, that is, Eth-Trunk. Before configuring link aggregation, create an Eth-Trunk.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface eth-trunk trunk-id

    An Eth-Trunk is created and the Eth-Trunk interface view is displayed.

    trunk-id is the Eth-Trunk ID. The value range depends on the switch module type.
    • For CX110/CX111/CX915 switching planes, the trunk ID range is from 0 to 127.
    • For CX910/CX911/CX912/CX913 10GE switching planes and CX31x/CX710 switching planes, the trunk ID range depends on the command assign forward eth-trunk mode { 64 | 128 }.
      • When 64 is used in the command, the trunk ID range is from 0 to 63.
      • When 128 is used in the command, the trunk ID range is from 0 to 127.

    If the specified Eth-Trunk already exists, this command directly displays the Eth-Trunk interface view.

  3. Run:

    commit

    The configuration is committed.

Setting the LACP Mode

Context

Link aggregation can work in manual load balancing mode, static LACP mode and dynamic LACP mode.

In LACP mode, you must manually create an Eth-Trunk and add member interfaces to the Eth-Trunk. LACP determines active interfaces by negotiating parameters through LACPDUs.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface eth-trunk trunk-id

    The Eth-Trunk interface view is displayed.

  3. Configure the working mode of the Eth-Trunk.

    Select the static or dynamic LACP mode.

    • When the two directly connected devices support LACP, static LACP is recommended.

      Run:

      mode lacp-static

      The Eth-Trunk interface is configured to work in static LACP mode.

      Before configuring an Eth-Trunk, ensure that both ends use the same working mode. If the local end works in static LACP mode, the peer end must use the static LACP mode.

    • When a device is directly connected to a server, the dynamic LACP mode must be used.

      mode lacp-dynamic

      The Eth-Trunk interface is configured to work in dynamic LACP mode.

  4. Run:

    commit

    The configuration is committed.

Adding Member Interfaces to an Eth-Trunk

Context

You can add member interfaces to an Eth-Trunk in the Eth-Trunk interface view or member interface view.

Figure 5-31 Recommended deployment mode (when the member interfaces of multiple Eth-Trunk interfaces are deployed on different boards)
Figure 5-32 Deployment mode that is not recommended (when the member interfaces of multiple Eth-Trunk interfaces are deployed on different boards)

Procedure

  • Adding member interfaces to an Eth-Trunk in the Eth-Trunk interface view
    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:

      trunkport interface-type { interface-number1 [ to interface-number2 ] } &<1-16>

      A member interface is added to the Eth-Trunk.

      NOTE:

      On the CX111&CX915 switch module GE switching plane, run the trunkport interface-type { interface-number1 [ to interface-number2 ] } &<1-8> command to add member interfaces.

      NOTE:

      When member interfaces are added to an Eth-Trunk in batches, if one interface cannot be added to the Eth-Trunk, all the interfaces cannot be added to the Eth-Trunk.

    4. Run:

      commit

      The configuration is committed.

  • Adding member interfaces to an Eth-Trunk in the member interface view
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The member interface view is displayed.

    3. Run:

      eth-trunk trunk-id

      The member interface is added to an Eth-Trunk.

    4. Run:

      commit

      The configuration is committed.

    When adding an interface to an Eth-Trunk, pay attention to the following points:

    • On CX110 switching plane, each Eth-Trunk contains a maximum of 16 member interfaces.
    • On CX111/CX915 switching planes, each Eth-Trunk contains a maximum of 8 member interfaces.
    • On CX910/CX911/CX912/CX913 10GE switching planes and CX31x/CX710 switching planes, the maximum number of member interfaces on each Eth-Trunk depends on the command assign forward eth-trunk mode { 64 | 128 }.
      • When 64 is used in the command, each Eth-Trunk contains a maximum of 32 member interfaces.
      • When 128 is used in the command, each Eth-Trunk contains a maximum of 16 member interfaces.
    • A member interface cannot be configured with some service or static MAC address.
    • When adding an interface to an Eth-Trunk, ensure that the link-type of the interface is default link-type.
    • An Eth-Trunk cannot be nested, that is, its member interfaces cannot be Eth-Trunk.
    • An Ethernet interface can be added to only one Eth-Trunk. To add the Ethernet interface to another Eth-Trunk, delete it from the Eth-Trunk first.
    • An Eth-trunk contains member interfaces of the same type.
    • The peer interfaces directly connected to the local Eth-Trunk member interfaces must also be bundled into an Eth-Trunk; otherwise, the two ends cannot communicate.
    • After interfaces are added to an Eth-Trunk, MAC addresses and ARP are learned on the Eth-Trunk but not the member interfaces.
    • The rates at both ends of the Eth-Trunk must be the same. It is recommended that the number of connected physical interfaces, and jumbo and flow control configuration at both ends of the Eth-Trunk be the same.
    • Before adding the Ethernet optical port on the CX311 panel to the Eth-trunk, delete the default ACL rules from the port. The default ACL rules can be added to the Eth-trunk.
    • In a stack scenario, it is recommended that the number of member interfaces added to an LAG be the nth power of 2. Otherwise, unknown unicast traffic may be unevenly load balanced.
    • When a compute node interface is added to Eth-Truck, run the undo stp disable command to delete the stp disable configuration.

(Optional) Limiting the Number of Active Interfaces

Context

The number of Up member links affects the status and bandwidth of the trunk interface. To ensure that the trunk interface functions properly and is less affected by changes in member link status, set the following thresholds.

  • Lower threshold for the number of active interfaces: When the number of active interfaces falls below this threshold, the trunk interface goes Down. This guarantees the trunk interface a minimum available bandwidth.
  • Upper threshold for the number of active interfaces: It is used for improving network reliability with assured bandwidth. When the number of active interfaces reaches the threshold, you can add new member interfaces to the Eth-Trunk, but excess member interfaces enter the Down state.

Procedure

  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:

    least active-linknumber link-number

    The lower threshold for the number of active interfaces is set.

    By default, the minimum number of active interfaces is 1.

    The minimum number of active interfaces on the local switch modules can be different from that on the remote switch modules. If the two values are different, the larger one is used.

  4. Run:

    lacp max active-linknumber link-number

    The upper threshold for the number of active interfaces is set.

    By default, the maximum number of active interfaces is 8 on the CX111&CX915 switch module GE switching plane, the maximum number of active interfaces is 16 on other models.

    The maximum number of active interfaces on the local switch modules can be different from that on the remote switch modules. If the two values are different, the smaller one is used.

    NOTE:

    The upper threshold for the number of active interfaces must be greater than or equal to the lower threshold for the number of active interfaces.

  5. Run:

    commit

    The configuration is committed.

(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. Different data flows are forwarded on different physical links to implement load balancing.

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.

Table 5-12 describes load balancing modes for different types of packets.

Table 5-12 Load balancing modes for different types of packets

Packet (Inbound Interface)

Default Load Balancing Mode

Configurable Load Balancing Mode

Remarks

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

The load balancing mode is relevant to the packet type and irrelevant to the packet forwarding process.

For example, even if the system provides only Layer 2 forwarding for IPv4 packets, the IPv4 packets are load balanced according to the load balancing mode for IPv4 packets. When the system cannot identify IPv4, IPv6, or MPLS packets, the system load balances packets based on src-mac, dst-mac, src-interface, and eth-type for Layer 2 packets.

IPv6 packets

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

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

MPLS packets

top-label and 2nd-label

top-label, 2nd-label, dst-ip and src-ip

Layer 2 packets except IPv4, IPv6, and MPLS packets

src-mac and dst-mac

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

Trill packets

  • Ingress node: inner src-mac and dst-mac 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, src-interface, l4-src-port, l4-dst-port, protocol and eth-type

Trill packets can be load balanced on the transit and egress nodes only when the load-balance enhanced profile profile-name command is used.

Transit/Egress node: inner src-mac and dst-mac for Layer 2 packets; src-ip, dst-ip, l4-src-port, and l4-dst-port for Layer 3 packets

Non-configurable

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. (Optional) 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.

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

    • Run:

      l2 [ src-mac | dst-mac | src-interface | eth-type ] *

      The load balancing mode of Layer 2 packets (non-IP packets) is set.

      By default, load balancing of Layer 2 packets (non-IP packets) is based on the source MAC address (src-mac) and destination MAC address (dst-mac).

    • Run:

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

      The load balancing mode of IPv4 packets is set.

      By default, load balancing of IPv4 packets is 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 | l4-src-port | l4-dst-port ] *

      The load balancing mode of IPv6 packets is set.

      By default, load balancing of IPv6 packets is 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:

      mpls [ top-label | dst-ip | src-ip | 2nd-label ] *

      The load balancing mode of MPLS packets is set.

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

    • Run:

      eth-trunk { hash-mode hash-mode-id | universal-id universal-id } *

      A load balancing mode of an Eth-Trunk is set.

      By default, load balancing of an Eth-Trunk is based on hash-mode (1), universal-id (1).

  3. Run:

    quit

    Return to the system view.

  4. Run the following commands as required.

    • Configure a load balancing mode for known unicast traffic.

      1. Run:

        interface eth-trunk trunk-id

        The Eth-Trunk interface view is displayed.

      2. Run:

        load-balance { dst-ip | dst-mac | src-ip | src-mac | src-dst-ip | src-dst-mac | enhanced profile profile-name }

        A load balancing mode of the Eth-Trunk is set.

        By default, the load balancing mode of the Eth-Trunk is enhanced profile.

        • dst-ip: Load balancing is performed based on destination IP addresses.

        • dst-mac: Load balancing is performed based on destination MAC addresses.

        • src-ip: Load balancing is performed based on source IP addresses.

        • src-mac: Load balancing is performed based on source MAC addresses.

        • src-dst-ip: Load balancing is performed based on the Exclusive-Or result of source and destination IP addresses.

        • src-dst-mac: Load balancing is performed based on the Exclusive-Or result of source and destination MAC addresses.

        • enhanced profile: Load balancing is performed based on the fields in the global load balancing profile.

      3. Run:

        commit

        The configuration is committed.

    • Configure a load balancing mode for unknown unicast traffic.

      1. Run:

        load-balance unknown-unicast { mac | enhanced }

        A load balancing mode is configured.

        By default, the load balancing mode is enhanced.

      2. Run:

        commit

        The configuration is committed.

(Optional) Setting the LACP System Priority

Context

LACP system priority differentiates priorities of devices at both ends. In LACP mode, active interfaces selected by devices at both ends must be consistent; otherwise, the LAG cannot be set up. To keep active interfaces consistent at both ends, you can set the priority of one device to be higher than that of the other device so that the other device can select active interfaces according to those selected by the device with a higher priority.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lacp priority priority

    The LACP system priority is set.

    A smaller LACP priority value indicates a higher priority. By default, the LACP system priority is 32768.

    The end with a smaller priority value functions as the Actor. If the two ends have the same priority, the end with a smaller MAC address functions as the Actor.

  3. Run:

    commit

    The configuration is committed.

(Optional) Setting the LACP Priority for an Interface

Context

In LACP mode, LACP interface priorities are set to prioritize interfaces of the same device. Interfaces with higher priorities are selected as active interfaces.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The member interface view is displayed.

  3. Run:

    lacp priority priority

    The LACP priority of the member interface is configured.

    By default, the LACP interface priority is 32768. A smaller priority value indicates a higher LACP priority.

    NOTE:
    1. By default, the system selects active interfaces based on interface priorities. However, low-speed member interfaces may be selected as active interfaces because of their high priorities. To select high-speed member interfaces, run the lacp select { priority | speed } command to configure the system to select active interfaces based on the interface rate.
    2. To ensure the normal operation of an Eth-Trunk link, you are advised to configure the same method of selecting active interfaces at both ends of the Eth-Trunk link.

  4. Run:

    commit

    The configuration is committed.

(Optional) Configuring LACP Preemption

Context

The LACP preemption function ensures that the interface with the highest LACP priority always functions as an active interface. For example, when the interface with the highest priority becomes inactive due to a failure, the LACP preemption function enables the interface to become active again after it recovers. If the LACP preemption function is disabled, the interface cannot become an active interface again.

The LACP preemption delay is the period during which an inactive interface waits before it becomes active. The LACP preemption delay prevents instable data transmission on an Eth-Trunk link due to frequent status changes of some links.

Procedure

  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:

    lacp preempt enable

    The LACP preemption function is enabled.

    By default, the LACP preemption function is disabled.

    NOTE:

    To ensure normal running of an Eth-Trunk interface, enable or disable LACP preemption on both ends of the Eth-Trunk interface.

  4. Run:

    lacp preempt delay delay-time

    The LACP preemption delay is set.

    By default, the LACP preemption delay is 30 seconds.

  5. Run:

    commit

    The configuration is committed.

(Optional) Setting the Timeout Interval for Receiving LACPDUs

Context

If the Eth-Trunk on the local device cannot detect a self-loop or fault that occurred on a member interface in the LAG on the peer device, data on the local device is still load balanced among original active interfaces. As a result, data traffic on the faulty link is discarded.

After the timeout interval at which LACPDUs are received is set, if a local member interface does not receive any LACPDUs within the configured timeout interval, it becomes Down immediately and no longer forwards data.

Procedure

  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:

    lacp timeout { fast | slow }

    The timeout interval at which LACPDUs are received is set.

    By default, the timeout interval for an Eth-Trunk to receive packets is 90 seconds.

    NOTE:
    • After you run the lacp timeout command, the local end informs the peer end of the timeout interval through LACP packets. If the fast keyword is used, the interval for sending LACP packets is 1 second. If the slow keyword is used, the interval for sending LACP packets is 30 seconds.

    • The timeout interval for receiving LACP packets is three times the interval for sending LACP packets. In other words, when the fast keyword is used, the timeout interval for receiving LACP packets is 3 seconds. When the slow keyword is used, the timeout interval for receiving LACP packets is 90 seconds.

    • You can select different keywords on the two ends. However, it is recommended that you select the same keyword on both ends to facilitate the maintenance.

  4. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display eth-trunk [ trunk-id [ interface interface-type interface-number | verbose ] ] command to check the Eth-Trunk configuration.
  • Run the display eth-trunk membership trunk-id command to check information about member interfaces of the Eth-Trunk.
  • Run the display load-balance profile [ profile-name ] command to check details of a load balancing profile of the Eth-Trunk.

Configuring Forwarding Through Local Member Interfaces (in a Stack)

On a network where the stack and Eth-Trunk are used, configure the Eth-Trunk to preferentially forward local interface traffic to increase bandwidth use efficiency between stack devices and improves traffic forwarding efficiency.

Context

You can configure the Eth-Trunk to or not to preferentially forward local interface traffic in the following scenarios:

  • If active interfaces in the local Eth-Trunk have sufficient bandwidth to forward traffic on the local device, configure the Eth-Trunk to preferentially forward local interface traffic, which improves traffic forwarding efficiency and increases bandwidth use efficiency between stack devices.
  • If active interfaces in the local Eth-Trunk do not have sufficient bandwidth to forward traffic on the local device, configure the Eth-Trunk not to preferentially forward local interface traffic. Some traffic on the local device is forwarded through member interfaces of Eth-Trunk on another device. This prevents packet loss.
Pre-configuration Tasks

Before configuring an Eth-Trunk to preferentially forward local interface traffic, complete the following tasks:

  • Creating an Eth-Trunk and adding physical interfaces to the Eth-Trunk

  • Connecting devices correctly and completing stack configurations so that a stack can be established

  • Ensure that member interfaces of the local Eth-Trunk have sufficient bandwidth to forward local traffic; otherwise, traffic may be discarded.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface eth-trunk trunk-id

    The view of the Eth-Trunk that needs to be configured to preferentially forward local interface traffic is displayed.

  3. Run:

    undo local-preference disable

    The Eth-Trunk is configured to preferentially forward local interface traffic.

    By default, an inter-device Eth-Trunk forwards traffic preferentially through local member interfaces.

    NOTE:

    This function is only valid for known unicast packets, and is invalid for unknown unicast packets, broadcast packets and multicast packets.

  4. Run:

    commit

    The configuration is committed.

Configuring the Minimum Number of Local Links on the Eth-Trunk (in a Stack)

On a network where the stack and Eth-Trunk are used, configure the minimum number of local links on the Eth-Trunk for forwarding traffic over devices to increase traffic forwarding efficiency when the bandwidth for the device is lower than the minimum number of links.

Context

After the local-preference transmit mode of the Eth-Trunk is enabled, traffic on the local device is forwarded over member interfaces of the Eth-Trunk on the local or another device based on the number of member interfaces in the Eth-Trunk as follows:

  • If active interfaces in the local Eth-Trunk have sufficient bandwidth to forward traffic on the local device, and the local-preference transmit mode of the Eth-Trunk is enabled, traffic is preferentially forwarded on the local device, which maximizes traffic forwarding efficiency and bandwidth usage between stacking devices.
  • If active interfaces in the local Eth-Trunk do not have sufficient bandwidth to forward traffic on the local device, and the local-preference transmit mode of the Eth-trunk is enabled, the local-preference transmit mode of the Eth-Trunk is disabled automatically, and some traffic on the local device is forwarded over member interfaces of the Eth-Trunk on another device. This prevents packet loss.
NOTE:
  • The minimum number of local links on the Eth-Trunk takes effect only after the local-preference transmit mode of the Eth-trunk is configured.
  • After local-preference transmit mode of the Eth-trunk and the minimum number of local links on the Eth-Trunk are enabled at the same time, and the Eth-Trunk provides sufficient bandwidth for forwarding traffic on the local device, traffic is automatically forwarded over member interfaces of the Eth-Trunk on the local device or another device based on the minimum number of local links on the Eth-Trunk. This prevents packet loss.
Prerequisites

Before configuring the minimum number of local links on the Eth-Trunk, the following tasks are complete:

  • An Eth-Trunk has been created, and physical interfaces have been added to the Eth-Trunk.

  • The environment for stacking devices has been established.

  • The local-preference transmit mode of the Eth-trunk has been enabled.

Procedure

  1. Run system-view to go to the system view.
  2. Run interface eth-trunk trunk-id.

    The Eth-Trunk interface view is displayed for configuring the minimum number of local links.

  3. Run least local active-linknumber link-number to configure the minimum number of local links on the Eth-Trunk.

    The minimum number of local links on the Eth-Trunk is 1 by default.

  4. Run commit.
Checking the Configuration Result

In the Eth-Trunk interface view, run display this to check the Eth-Trunk configuration. If the command output contains least local active-linknumber, the minimum number of local links is successfully configured.

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59782

Downloads: 3623

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