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 the Association Between STP/RSTP/MSTP and TRILL

Configuring the Association Between STP/RSTP/MSTP and TRILL

Context

The association between STP/RSTP/MSTP and TRILL enables an MSTP network to connect to a TRILL network through two uplinks, implementing seamless expansion of the original data center network.

As shown in Figure 1-25, TRILL is deployed on RB1, RB2, RB3, RB4, RB5, and RB6, and servers communicate over the TRILL network. MSTP is deployed on MS1, MS2, and MS3 to prevent traffic loops. Traffic loops will also occur among RB1, RB3, RB4, MS1, and MS2. However, MSTP cannot be deployed on RB1 to prevent traffic loops.

Figure 1-25 Networking diagram for configuring the association between STP/RSTP/MSTP and TRILL

To prevent traffic loops among RB1, RB3, RB4, MS1, and MS2, two methods are available. You can choose one to perform configurations.

  • Change the root bridge.

    Run MSTP on RB3 and RB4 and simulate RB3 and RB4 as one root bridge. That is, ensure that BPDUs sent by RB3 and RB4 carry the same bridge ID. MSTP then blocks one port after calculating the spanning tree, preventing traffic loops among RB1, RB3, RB4, MS1, and MS2. In most cases, however, each device has a different bridge MAC address and so has a different bridge ID. To ensure that RB3 and RB4 have the same bridge ID, you can configure the bridge MAC address used by the current device to participate in calculating the spanning tree.

    In Figure 1-26, MSTP blocks the MS3 interface connecting to MS2 and the MS2 interface connecting to MS1, and the transmission path for traffic from Server1 to Server3 is Server1 -> MS3 -> MS1 -> RB3 -> RB1 -> RB5 -> Server3.

    Figure 1-26 Networking of the association between STP/RSTP/MSTP and TRILL (changing the root bridge)

    In Figure 1-27, if the link between MS1 and MS3 fails, MSTP recalculates the spanning tree, blocks the MS3 interface connecting to MS1, and unblocks the MS3 interface connecting to MS2. All devices, including those on the TRILL network and connected networks, must be notified of the topology change and update their MAC address entries and ARP entries accordingly. However, devices on the TRILL network cannot process topology change (TC) packets generated by MSTP. To allow TRILL devices to process TC packets and ensure uninterrupted traffic forwarding, configure the association between MSTP and TRILL. In Figure 1-27, MSTP blocks the MS3 interface connecting to MS1, and the transmission path for traffic from Server1 to Server3 is Server1 -> MS3 -> MS2 -> RB4 -> RB1 -> RB5 -> Server3.

    Figure 1-27 Networking of the association between STP/RSTP/MSTP and TRILL (changing the root bridge in the case of a link fault)
  • Retain the root bridge.

    Configure the RB3 and RB4 interfaces connecting to the MSTP network to transparently transmit spanning tree packets in the TRILL network. Spanning tree packets are then transparently transmitted in the TRILL network. If the TRILL network receives topology change (TC) packets, the TRILL network updates MAC address entries in a timely manner. This configuration does not affect the existing configurations in the original MSTP network, and MS1 is still the root bridge.

    As shown in Figure 1-28, MSTP blocks the MS3 interface connecting to MS2, and the transmission path for traffic between Server1 and Server3 is Server1->MS3->MS1->RB3->RB1->RB5->Server3.

    Figure 1-28 Networking diagram for configuring the association between STP/RSTP/MSTP and TRILL (retaining the root bridge)

    As shown in Figure 1-29, if a fault occurs on the link between MS1 and MS3, MSTP recalculates the spanning tree, blocks the MS3 interface connecting to MS1, and unblocks the MS3 interface connecting to MS2. This topology change needs to be notified to all the devices using TC packets, including devices on the TRILL network and connected networks so that these devices can detect the topology change and update MAC address entries in a timely manner. The TRILL network, however, does not process the TC packets. To ensure uninterrupted service traffic forwarding in this situation, configure the transparent transmission of spanning tree packets in the TRILL network. Spanning tree packets are then transparently transmitted in the TRILL network. If the TRILL network receives TC packets, the TRILL network updates MAC address entries in a timely manner. As shown in Figure 1-29, MSTP blocks the MS3 interface connecting to MS1, and the transmission path for traffic between Server1 and Server3 becomes Server1->MS3->MS2->RB4->RB1->RB5->Server3.

    Figure 1-29 Networking diagram for configuring the association between STP/RSTP/MSTP and TRILL (retaining the root bridge in the case of a link fault)

Pre-configuration Tasks

Before configuring the association between STP/RSTP/MSTP and TRILL, complete the following tasks:

Procedure

  • Configure the association between STP/RSTP/MSTP and TRILL (changing the root bridge).
    1. Run system-view

      The system view is displayed.

    2. Run stp bridge-address mac-address

      The bridge MAC address for spanning tree calculation is configured on RB3 and RB4.

      By default, a device uses its MAC address as the bridge MAC address to calculate the spanning tree.

      NOTE:
      • A bridge ID identifies a device. If two devices send packets with the same bridge ID to another device, the packets are sent by one device. Exercise caution when you run the stp bridge-address command.

      • After you run the stp bridge-address command to configure the same bridge MAC address for two devices, to allow the devices to simulate the same root bridge, ensure that the devices have the same spanning tree protocol configurations, such as the device priority and timer settings.

    3. Run stp tc-notify trill vlan vlan-id

      The association between STP/RSTP/MSTP and TRILL is enabled on RB3 and RB4.

      By default, the association between STP/RSTP/MSTP and TRILL is disabled.

      vlan-id must be the ID of an admin VLAN on the TRILL network. A VLANIF interface must be configured for the admin VLAN.

      NOTE:

      Before the stp tc-notify trill vlan vlan-id command is configured on the device, the stp disable command must be configured on the interface configured with the trill enable port-mode { hybrid | p2p | trunk } command.

    4. Run commit

      The configuration is committed.

  • Configure the association between STP/RSTP/MSTP and TRILL (retaining the root bridge).
    1. Run system-view

      The system view is displayed.

    2. (CE switches excluding CE6870EI and CE6875EI) Run undo mac-address bpdu 0180-c200-0000

      The default BPDU MAC address on the switch is deleted.

    3. Run interface interface-type interface-number

      The interface view is displayed.

    4. Run stp disable

      STP/RSTP/MSTP is disabled on the interface.

      By default, STP/RSTP/MSTP is enabled on an interface.

    5. Run stp tc-snooping notify trill

      Transparent transmission of spanning tree packets is enabled in the TRILL network.

      By default, spanning tree packets are not transparently transmitted in a TRILL network.

      NOTE:

      To ensure that spanning tree packets are transparently transmitted in the TRILL network, ensure that:

      • An admin VLAN has been configured in the TRILL network and an IP address has been configured for the VLANIF interface of the admin VLAN.

      • The same PVID has been configured for the interfaces on which the stp tc-snooping notify trill command is executed, and the PVID is the ID of the admin VLAN of the TRILL network.

      • You are advised to run the stp edged-port disable command on the interfaces connecting the STP/RSTP/MSTP network to the TRILL network to configure the interfaces as non-edge ports.

      If the interface that connects the TRILL network to the MSTP network is faulty, MSTP cannot fast detect the fault, causing services to be interrupted for at least 48 seconds.

    6. Run commit

      The configuration is committed.

Verifying the Configuration

Run the display current-configuration command to check the association between STP/RSTP/MSTP and TRILL.

Translation
Download
Updated: 2019-05-08

Document ID: EDOC1100004349

Views: 30262

Downloads: 120

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