stp compliance

Function

The stp compliance command configures a format for sent and received Multiple Spanning Tree Protocol (MSTP) BPDUs.

The undo stp compliance command restores the default format of sent and received MST BPDUs.

By default, the format of sent and received MST BPDUs is auto.

Format

stp compliance { auto | dot1s | legacy }

undo stp compliance

Parameters

Parameter	Description	Value
auto	Indicates that the MST BPDU format is self-adaptive.	-
dot1s	Indicates that the MST BPDU format is standard IEEE 802.1s.	-
legacy	Indicates that the MST BPDU format is proprietary.	-

Parameter

Description

Value

auto

Indicates that the MST BPDU format is self-adaptive.

dot1s

Indicates that the MST BPDU format is standard IEEE 802.1s.

legacy

Indicates that the MST BPDU format is proprietary.

Views

100GE interface view, 10GE interface view, 25GE interface view, 400GE interface view, 40GE interface view, 50GE interface view, Eth-Trunk interface view, GE optical interface view, GE electrical interface view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
mstp	write

Usage Guidelines

Usage Scenario

MST BPDUs have two formats: dot1s (IEEE 802.1s standard) and legacy (proprietary). To facilitate device communication, run the stp compliance command to set an MST BPDU format for a local device based on the format of MST BPDUs from the remote device.

To allow a port to automatically accommodate to the format of MST BPDUs sent by a remote device, configure the auto format.

Precautions

If you configure different MST BPDU formats on the same interface in the interface view, the latest configuration overrides the previous one.

Example

# Set the MST BPDU format on interface Eth-Trunk1 to IEEE 802.1s.

<HUAWEI> system-view
[~HUAWEI] interface eth-trunk 1
[*HUAWEI-Eth-Trunk1] portswitch
[*HUAWEI-Eth-Trunk1] stp compliance dot1s