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).
Configuring TRILL Network Dual-Homing Through an M-LAG

Configuring TRILL Network Dual-Homing Through an M-LAG

Pre-configuration Tasks

Before configuring TRILL network dual-homing through an M-LAG, Configuring Basic TRILL Functions.

Configuring a DFS Group

Context

A DFS group is used to pair devices. To exchange heartbeat packets, a DFS group must be bound to a nickname, which is used to communicate with the peer end.

In a TRILL active-active scenario, configure a pseudo nickname for a DFS group. Two devices dual-homed to the TRILL network must have the same pseudo nickname. In this way, the peer end considers the two devices a logical device on the TRILL network and does not need to reconstruct the network topology.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run dfs-group dfs-group-id

    A DFS group is created and its view is displayed, or the view of an existing DFS group is displayed.

  3. Run source nickname nickname-value

    The DFS group is bound to a nickname.

  4. Run pseudo-nickname nickname-value1 [ priority priority ]

    A pseudo nickname is configured for the DFS group.

  5. (Optional) Run priority priority

    The priority of the DFS group is set.

    The priority of a DFS group is used for master/backup negotiation between two devices. The device with a higher priority is the master, and a larger priority value indicates a higher priority.

    If the priorities of the two devices are the same, the device with a smaller system MAC address is the master.

    By default, the priority of a DFS group is 100.

  6. Run commit

    The configuration is committed.

Configuring an Interface as a Peer-link Interface

Context

A peer-link is a direct aggregated link between two devices configured with M-LAG. The peer-link is used to transmit negotiation packets and some traffic. The two devices exchange protocol packets over the peer-link to ensure normal running of M-LAG.

Prerequisites

The direct link between two devices configured with M-LAG has been configured as an aggregated link.

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 { lacp-static | lacp-dynamic }

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

    By default, an Eth-Trunk works in manual load balancing mode. To ensure M-LAG reliability, you must configure the Eth-Trunk to work in LACP mode.

  4. Run undo stp enable

    STP is disabled on the interface.

    NOTE:

    STP needs to be disabled because two devices need to be simulated into one STP root bridge and the directly connected interface cannot be blocked.

    When V-STP needs to be configured, you do not need to perform this operation.

  5. Run peer-link peer-link-id

    The interface is configured as a peer-link interface.

    • An interface configured as a peer-link interface joins all VLANs by default.

    • If the ERPS control VLAN, TRILL Carrier VLAN, or FCoE VLAN needs to be configured, perform 6 to remove the peer-link interface from the control VLAN, Carrier VLAN, or FCoE VLAN. Otherwise, the control VLAN, Carrier VLAN, or FCoE VLAN cannot be configured.

    • If the network-side VLANIF interface is configured, you are advised to perform 6 to remove the peer-link interface from the VLAN. Otherwise, exceptions may occur. For example, heartbeat detection becomes ineffective.

  6. (Optional) Run port vlan exclude { { vlan-id1 [ to vlan-id2 ] } &<1-10> }

    The VLANs not allowed by the peer-link interface are specified.

  7. Run commit

    The configuration is committed.

Binding an Interface to a DFS Group

Prerequisites

The links between a server and two upstream devices configured with M-LAG have been configured as aggregated links. To improve reliability, configure link aggregation in LACP mode.

Procedure

  • When the Eth-Trunk works in manual load balancing mode, perform the following operations.
    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 dfs-group dfs-group-id m-lag m-lag-id

      The Eth-Trunk is bound to a DFS group.

      NOTE:

      The two devices configured with M-LAG must use the same M-LAG ID.

    4. Run commit

      The configuration is committed.

  • When the Eth-Trunk works in LACP mode, perform the following operations.
    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 { lacp-static | lacp-dynamic }

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

    4. Run dfs-group dfs-group-id m-lag m-lag-id

      The Eth-Trunk is bound to a DFS group.

      NOTE:

      The two devices configured with M-LAG must use the same M-LAG ID.

    5. Run lacp m-lag priority priority

      The LACP M-LAG system priority is configured.

      • Eth-Trunks on both devices configured with M-LAG must use the same LACP M-LAG system priority.
      • The LACP M-LAG system priority configured in the system view takes effect for all Eth-Trunks. The LACP M-LAG system priority configured in the Eth-Trunk interface view takes effect for only the specified Eth-Trunk. If the lacp m-lag priority command is configured in the system view and Eth-Trunk interface view, the LACP M-LAG system priority configured in the Eth-Trunk interface view takes effect.
      • When multiple M-LAGs are configured on the device, different Eth-Trunks can use different system priorities. In this case, you need to set the LACP M-LAG system priority in the Eth-Trunk interface view.
      • The LACP M-LAG system priority is valid for the M-LAG composed of an Eth-Trunk in LACP mode, whereas the LACP system priority configured by the lacp priority command is valid for an Eth-Trunk in LACP mode.

        If both the LACP M-LAG system priority and LACP system priority are configured, the Eth-Trunk in LACP mode that joins an M-LAG uses the LACP M-LAG system priority but not the LACP system priority.

    6. Run lacp m-lag system-id mac-address

      The LACP M-LAG system ID is configured.

      • Eth-Trunks on both devices configured with M-LAG must use the same LACP M-LAG system ID.
      • The LACP M-LAG system ID configured in the system view takes effect on all Eth-Trunks. The LACP M-LAG system ID configured in the Eth-Trunk interface view takes effect for only the specified Eth-Trunk. If the lacp m-lag system-id command is configured in the system view and Eth-Trunk interface view, the LACP M-LAG system ID configured in the Eth-Trunk interface view takes effect.
      • When multiple M-LAGs are configured on the device, different Eth-Trunks can use different system IDs. In this case, you need to set the system ID of an LACP M-LAG in the Eth-Trunk interface view.
      • The LACP M-LAG system ID is valid for the M-LAG composed of an Eth-Trunk in LACP mode, whereas the LACP system ID is valid for an Eth-Trunk in LACP mode. The LACP system ID is the MAC address of an Ethernet interface on the MPU and cannot be changed.

    7. Run commit

      The configuration is committed.

Verifying the Configuration

Procedure

  • Run the display dfs-group dfs-group-id [ node node-id m-lag [ brief ] | peer-link ] command to check M-LAG information.
  • Run the display stp v-stp command to check the V-STP status and statistics.
  • Run the display dfs-group m-lag check stp command to check whether the STP configurations on both ends of the M-LAG are consistent.

Follow-up Procedure

After M-LAG is configured, if the peer-link is faulty but the heartbeat status is normal, some interfaces on the standby devices will enter the Error-Down state. The device records the status of an interface as Error-Down when it detects that a fault occurs. The interface in Error-Down state cannot receive or send packets and the interface indicator is off. You can run the display error-down recovery command to check information about all interfaces in Error-Down state on the device.

  • When M-LAG is used for dual-homing to a TRILL network and the peer-link fails but the heartbeat is normal, the M-LAG interface on the backup device will enter the error-down state. When the peer-link recovers, the M-LAG interface in Error-Down state becomes Up after 2 minutes by default, and the physical interfaces in Error-Down state are restored to be Up.

  • When M-LAG is used for dual-homing to an Ethernet, VXLAN network, or IP network and the peer-link fails but the heartbeat is normal, all physical interfaces except the management interface, peer-link interface, and stack interface on the backup device will enter the error-down state. When the peer-link recovers, the M-LAG interface in Error-Down state becomes Up after 2 minutes by default, and the physical interfaces in Error-Down state are restored to be Up.

When the interface enters the Error-Down state, locate the cause. You are not advised to manually restore the interface or run the error-down auto-recovery cause m-lag interval interval-value command in the system view to enable the interface to go Up automatically. Otherwise, extra packets, packet loss or forwarding failure may occur. Exercise caution when you perform the preceding operation.

Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004349

Views: 30254

Downloads: 120

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