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 - DCN and Server Management

CloudEngine 8800, 7800, 6800, and 5800 V200R003C00

This document describes the configurations of Trill, FCoE, DCB, and NLB Server Cluster Association.
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 TRILL Route Selection

Adjusting TRILL Route Selection

Pre-configuration Task

Before adjusting TRILL route selection, complete the following task:

Configuration Procedure

You can choose one or more configuration tasks as required.

Specifying a DVLAN

Context

To combine or separate TRILL networks, configure multiple carrier VLANs in a TRILL network. However, only one carrier VLAN is responsible for forwarding TRILL data packets. Therefore, a VLAN must be selected from these carrier VLANs to forward TRILL data packets. The DRB can specify a carrier VLAN as the designated VLAN (DVLAN), but the specified VLAN may not meet the network planning requirement. In this case, you can specify the DVLAN based on the network requirement. Only the DVLAN is responsible for forwarding TRILL data.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run interface interface-type interface-number

    The interface view is displayed.

  3. Run trill designated-vlan vlan-id

    A DVLAN is specified.

    NOTE:

    Make sure that the specified DVLAN is a TRILL carrier VLAN.

  4. Run commit

    The configuration is committed.

Configuring TRILL Load Balancing

Context

On large-scale TRILL networks, multiple equal-cost routes destined for the same node may exist. In this situation, traffic is forwarded randomly, which may result in traffic imbalance and poor traffic management. To resolve this issue, enable the equal-cost routes to load-balance the traffic, which can improve link utilization and prevent congestion.

Load balancing can be configured for a TRILL process or interface, and the load balancing configured for an interface takes precedence over that configured for a process.
  • To configure load balancing for a TRILL process, you need to specify the maximum number of equal-cost routes for load balancing.
    NOTE:

    For the load balancing modes of TRILL packets in Eth-Trunk, see "Link Aggregation Configuration" in the CloudEngine 8800, 7800, 6800, and 5800 Series switch Configuration Guide - Ethernet Switching.

    For TRILL ECMP load balancing modes, see "IP Routing Table Management" in the CloudEngine 8800, 7800, 6800, and 5800 Series switch Configuration Guide - IP Unicast Routing.

  • To configure load balancing for a TRILL interface, you can designate an RB as an AF for a VLAN or VLANs. After an RB is designated as an AF for a VLAN or VLANs, the RB is always used as an AF by the VLAN or VLANs, and all the RBs in other VLANs are designated as AFs based on the AF priority in order for load balancing.

Procedure

  • Configure load balancing for a TRILL process.
    1. Run system-view

      The system view is displayed.

    2. Run trill

      The TRILL view is displayed.

    3. Run maximum load-balance number

      The maximum number of equal-cost routes for load balancing is configured.

      After the command is run, traffic is load-balanced among a maximum of the configured number of equal-cost routes.

      NOTE:

      By default, TRILL supports load balancing, and the maximum number of equal-cost routes for load balancing is 16(CE switches excluding CE6870EI and CE6875EI) or 32(CE6870EI and CE6875EI).

      If equal-cost routes available outnumber number specified in the command, TRILL selects number equal-cost routes in the following sequence:
      • Routes with smaller outbound interface indexes
      • Routes whose next hop RBs have smaller system IDs

    4. Run commit

      The configuration is committed.

  • Configure load balancing for a TRILL interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run trill load-balance systemid vlan { vlan-id1 [ to vlan-id2 ] }&<1–10>

      The RB whose system ID is the specified systemid is designated as an AF for the specified VLAN or VLANs.

      NOTE:

      The value of vlan-id2 must be greater than that of vlan-id1.

    4. Run commit

      The configuration is committed.

Configuring Load Balancing Based on TRILL Inner Packets

Context

You can run the trill (load balancing profile view) command to configure a switch to perform load balancing based on TRILL inner packets.

You can also run the trill egress mode command to achieve this purpose. However, the following limitations exist:
  • The trill egress mode command supports only load balancing based on IP address, MAC address, and VLAN ID.
  • The trill egress mode command takes effect only for Eth-Trunk load balancing instead of ECMP load balancing. The trill (load balancing profile view) command takes effect for both Eth-Trunk load balancing and ECMP load balancing.
  • The two commands can be configured together to take effect simultaneously. Either of the two commands can be configured to enable a switch to perform load balancing based on TRILL inner packets.
NOTE:

Only CE6870EI and CE6875EI support this command.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run load-balance profile profile-name

    The global load balancing profile is configured and the profile view is displayed. profile-name specifies a profile name.

    By default, the load balancing profile is named default.

  3. Run trill { inner-src-mac | inner-dst-mac | inner-vlan | inner-src-ip | inner-dst-ip | inner-l4-src-port | inner-l4-dst-port | inner-protocol | inner-eth-type | shift shift-data } *

    The switch is configured to perform load balancing based on TRILL inner packets.

    By default, the CE6870EI does not perform load balancing based on TRILL inner packets, but the CE6875EI performs load balancing based on TRILL inner packets. By default, on the ingress node, load balancing factors include all factors; on the transit node, load balancing factors are inner-src-mac, inner-dst-mac, and inner-vlan.

    NOTE:
    • If configured hash factors include an inner VLAN ID, packets can be forwarded along the same path only when their inner VLAN IDs and inner VLAN priorities are the same.

    • Load balancing based on TRILL inner packets do not take effect on the CE6875EI.

  4. Run commit

    The configuration is committed.

Configuring an Overload Bit for an RB

Context

If an RB on a TRILL network fails or needs to be upgraded or maintained, you can configure an overload bit for it. After an overload bit is configured for the RB, the RB is isolated from the TRILL network temporarily so that other devices no longer forward traffic to the RB, which prevents traffic interruptions.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run trill

    The TRILL view is displayed.

  3. Run set-overload [ on-startup [ timeout1 ] [ send-sa-bit [ timeout2 ] ] ] max-reachable-cost

    The RB is enabled to send LSPs whose overload bit is 1 and routes whose cost is the maximum link cost allowed (16777214).

    NOTE:

    timeout1 specifies the period during which the RB stays in the overload state. The default value is 600s.

    If send-sa-bit is specified in the command, the SA bit carried in Hello packets sent by the RB is 1 so that neighbors of the RB will not advertise the neighbor relationship with the RB to others after receiving the Hello packets. timeout2 specifies the period during which the SA bit carried in Hello packets sent by the RB stays at 1. The default value is 30s.

  4. Run commit

    The configuration is committed.

Enabling TRILL Multicast Group-based Pruning

Context

On a TRILL network, an RB calculates a multicast distribution tree (MDT) to forward multicast or broadcast traffic. If the MDT has more than one next hop, the RB replicates the traffic and forwards one copy to each next hop. As a result, each next hop needs to process the traffic on receiving it, wasting bandwidth and forwarding resources.

To address this issue, TRILL provides multicast group-based pruning to ensure that an RB forwards traffic only to the next hop in the same multicast group. This function improves bandwidth efficiency.
NOTE:

After devices on a TRILL network are configured to perform pruning based on multicast groups, multicast data within the TRILL network can only be forwarded based on MAC addresses. Multiple IPv4 multicast addresses may be mapped to the same IPv4 multicast MAC address according to the multicast IP-and-MAC address mapping mechanism. When multicast data is forwarded based on MAC addresses and a group IP address for receivers and the multicast IP address reserved for a protocol are mapped to the same IP multicast MAC address, the protocol cannot run normally. For example, IP multicast address 224.0.0.5 is reserved for the OSPF protocol. If a multicast group uses IP multicast address 225.0.0.5, the two IP multicast addresses are both mapped to IP multicast MAC address 01-00-5E-00-00-05. In this case, the OSPF protocol cannot run normally. Therefore, a proper IP multicast address plan must be made to prevent this problem.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run trill

    The TRILL view is displayed.

  3. Run multicast-group prune enable

    TRILL multicast group-based pruning is enabled.

  4. Run commit

    The configuration is committed.

Adjusting Multicast Distribution Trees

Multicast distribution trees (MDTs) can be adjusted for flexible TRILL configuration.

Context

On a TRILL network, either of the following ways can be used to adjust MDTs:
  • Configure a specific number of MDTs: By default, an RB calculates two MDTs for load balancing. However, configuring an RB to calculate only one MDT in the following scenarios is recommended:
    • One of the two RBs that function as Spine nodes fails, but you do not want other non-Spine-node RBs to be selected as MDT roots.
    • The network is simple or forwarding resources are limited.
  • Configure TRILL to calculate MDTs in compliance with RFC 7180: By default, TRILL calculates MDTs in compliance with RFC 6325. To allow devices following RFC 6325 to interoperate with devices following RFC 7180, run the rfc7180 compatible command to configure TRILL to calculate MDTs in compliance with RFC 7180.

Procedure

  • Configure a specific number of MDTs.
    1. Run system-view

      The system view is displayed.

    2. Run trill

      TRILL is enabled globally, and the TRILL view is displayed.

    3. Run tree-number compute compute-number

      The number of MDTs to be calculated by an RB is configured.

    4. Run commit

      The configuration is committed.

  • Configure TRILL to calculate MDTs in compliance with RFC 7180.
    1. Run system-view

      The system view is displayed.

    2. Run trill

      TRILL is enabled globally, and the TRILL view is displayed.

    3. Run rfc7180 compatible

      TRILL is configured to calculate MDTs in compliance with RFC 7180.

    4. Run commit

      The configuration is committed.

Verifying the TRILL Route Selection Configuration

Procedure

  • Run the display trill interface [ interface-type interface-number | verbose ] command to view information about TRILL interfaces.
  • Run the display trill route [ nickname ] [ verbose ] command to view information about TRILL unicast routes.
Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004349

Views: 30133

Downloads: 120

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