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

AR500, AR510, and AR530 V200R007 CLI-based Configuration Guide - Ethernet Switching

This document describes the configuration of Ethernet services, including configuring transparent bridge, MAC table, link aggregation, VLANs, STP/RSTP/MSTP, and so on.The document provides the configuration procedures and configuration examples to illustrate the service configuration methods and application scenario.
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).
MST BPDUs

MST BPDUs

MSTP calculates spanning trees on the basis of Multiple Spanning Tree Bridge Protocol Data Units (MST BPDUs). By transmitting MST BPDUs, spanning tree topologies are computed, network topologies are maintained, and topology changes are conveyed.

Table 12-5 shows differences between TCN BPDUs, configuration BPDUs defined by STP, RST BPDUs defined by RSTP, and MST BPDUs defined by MSTP.

Table 12-5  Differences between BPDUs

Version

Type

Name

0

0x00

Configuration BPDU

0

0x80

TCN BPDU

2

0x02

RST BPDU

3

0x02

MST BPDU

MST BPDU Format

Figure 12-9 shows the MST BPDU format.

Figure 12-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 12-6 lists the major information carried in an MST BPDU.

Table 12-6  Major information carried in an MST BPDU

Field

Byte

Description

Protocol Identifier

2

Indicates the protocol identifier.

Protocol Version Identifier

1

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

BPDU Type

1

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

  • 0x80: TCN BPDU for STP

  • 0x02: RST BPDU or MST BPDU

CIST Flags

1

Indicates the CIST flags.

CIST Root Identifier

8

Indicates the CIST root switching device ID.

CIST External Path Cost

4

Indicates the total path costs 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

8

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

2

Indicates the ID of the designated port in the IST.

Message Age

2

Indicates the lifecycle of the BPDU.

Max Age

2

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

2

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

Forward Delay

2

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

Version 1 Length

1

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

Version 3 Length

2

Indicates the BPDUv3 length.

MST Configuration Identifier

51

Indicates the MST configuration identifier, which has four fields.

CIST Internal Root Path Cost

4

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

CIST Bridge Identifier

8

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

CIST Remaining Hops

1

Indicates the remaining hops of the BPDU in the CIST.

MSTI Configuration Messages(may be absent)

16

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

Configurable MST BPDU Format

Currently, there are two MST BPDU formats:

  • dot1s: BPDU format defined in IEEE 802.1s.

  • legacy: private BPDU format.

If a port transmits either dot1s or legacy BPDUs by default, the user needs to identify the format of BPDUs sent by the peer, and then runs a command to configure the port to support the peer BPDU format. Once the configuration is incorrect, a loop probably occurs due to incorrect MSTP calculation.

By using the stp compliance command, you can configure a port on a Huawei datacom device 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 datacom devices:

  • auto

  • dot1s

  • legacy

In addition to dot1s and legacy formats, the auto mode allows a port to automatically switch 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 keeps pace with 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 datacom 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.

Translation
Download
Updated: 2019-05-25

Document ID: EDOC1000097279

Views: 20295

Downloads: 64

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