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


To have a better experience, please upgrade your IE browser.


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


MSTP calculates spanning trees using Multiple Spanning Tree Bridge Protocol Data Units (MST BPDUs). MST BPDUs are transmitted to calculate spanning tree topologies, maintain network topologies, and convey topology changes.

Table 10-5 shows differences in the protocol version and type between TCN BPDUs, configuration BPDUs (defined by STP), RST BPDUs (defined by RSTP), and MST BPDUs (defined by MSTP).

Table 10-5 Differences between BPDUs

Protocol Version





Configuration BPDU











Figure 10-9 shows the MST BPDU format.

Figure 10-9 MST BPDU format

The first 36 bytes of an intra-region or inter-region MST BPDU are the same as those of an RST BPDU.

Fields from the 37th byte of an MST BPDU are MSTP-specific. The field MSTI Configuration Messages consists of configuration messages of multiple MSTIs.

Table 10-6 lists the major information carried in an MST BPDU.

Table 10-6 Major information carried in an MST BPDU




Protocol Identifier


Indicates the protocol identifier.

Protocol Version Identifier


Indicates the protocol version identifier. 0 indicates STP; 2 indicates RSTP; 3 indicates MSTP.



Indicates the BPDU type:
  • 0x00: Configuration BPDU for STP

  • 0x80: TCN BPDU for STP

  • 0x02: RST BPDU or MST BPDU

CIST Flags


Indicates the CIST flags.

CIST Root Identifier


Indicates the CIST root switching device ID.

CIST External Path Cost


Indicates the total path cost from the MST region where the switching device resides to the MST region where the CIST root switching device resides. This value is calculated based on link bandwidth.

CIST Regional Root Identifier


Indicates the ID of the regional root switching device on the CIST, that is, the IST master ID. If the root is in this region, the CIST Regional Root Identifier is the same as the CIST Root Identifier.

CIST Port Identifier


Indicates the ID of the designated port in the IST.

Message Age


Indicates the lifecycle of the BPDU.

Max Age


Indicates the maximum lifecycle of the BPDU. If the Max Age timer expires, it is considered that the link to the root fails.

Hello Time


Indicates the Hello timer value. The default value is 2 seconds.

Forward Delay


Indicates the forwarding delay timer. The default value is 15 seconds.

Version 1 Length


Indicates the BPDUv1 length, which has a fixed value of 0.

Version 3 Length


Indicates the BPDUv3 length.

MST Configuration Identifier


Indicates the MST configuration identifier, which has four fields.

CIST Internal Root Path Cost


Indicates the total path cost from the local port to the IST master. This value is calculated based on link bandwidth.

CIST Bridge Identifier


Indicates the ID of the designated switching device on the CIST.

CIST Remaining Hops


Indicates the remaining hops of the BPDU in the CIST.

MSTI Configuration Messages (may be absent)


Indicates an MSTI configuration message. Each MSTI configuration message occupies 16 bytes. If there are n MSTIs, MSTI configuration messages occupy n x 16 bytes.

Configurable MST BPDU Formats

Currently, devices of most vendors support two MST BPDU formats:

  • dot1s: BPDU format defined in IEEE 802.1s.

  • legacy: private BPDU format.

There is a possible issue if a port transmits either dot1s or legacy BPDUs by default. That is, the user needs to identify the format of BPDUs sent by the peer, and then run a command to configure the port to support the peer BPDU format. If the configuration is incorrect, a loop will likely occur due to incorrect MSTP calculation.

On Huawei network devices, this issue can be overcome by using the stp compliance command. This command configures a port to automatically adjust the MST BPDU format. With this function, the port automatically adopts the peer BPDU format. The following MST BPDU formats are supported by Huawei network devices:

  • auto

  • dot1s

  • legacy

In addition to dot1s and legacy formats, the auto mode allows a port to automatically change to the BPDU format used by the peer based on BPDUs received from the peer. In this manner, the two ports use the same BPDU format. In auto mode, a port uses the dot1s BPDU format by default, and changes format according to the peer after receiving BPDUs from the peer.

Configurable Maximum Number of BPDUs Sent by a Port at a Hello Interval

BPDUs are sent at Hello intervals to maintain the spanning tree. If a switching device does not receive any BPDU during a certain period of time, the spanning tree will be re-calculated.

After a switching device becomes the root, it sends BPDUs at Hello intervals. Non-root switching devices adopt the Hello Time value set for the root.

Huawei network devices allow the maximum number of BPDUs sent by a port at a Hello interval to be configured as needed.

The greater the Hello Time value, the more BPDUs sent at a Hello interval. Setting the Hello Time to a proper value limits the number of BPDUs sent by a port at a Hello interval. This helps prevent network topology flapping and avoid excessive use of bandwidth resources by BPDUs.

Updated: 2019-05-08

Document ID: EDOC1100004351

Views: 125105

Downloads: 295

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