Configuring Spanning Tree Protocols; Restrictions And Guidelines: Spanning Tree Protocol Configuration; Restrictions: Compatibility With Other Features; Restrictions: Interface Configuration - H3C S6850 Series Configuration Manual

Configuring spanning tree protocols

Restrictions and guidelines: spanning tree
protocol configuration

Restrictions: Compatibility with other features

•
When the spanning tree protocol is enabled for a DR system, make sure the DR member
devices have the same spanning tree configuration, including:
Global spanning tree configuration.
Spanning tree configuration on the IPP.
Spanning tree configuration on DR interfaces.
Violation of this rule might cause network flapping. IPPs in the DR system do not participate in
spanning tree calculation. To view the spanning tree information of DR interfaces, use related
display commands on the primary DR device. For more information about the DR system,
DR interfaces, and IPPs, see "Configuring DRNI."
•
If both MVRP and a spanning tree protocol are enabled on a device, MVRP packets are
forwarded along MSTIs. To advertise a specific VLAN within the network through MVRP, make
sure this VLAN is mapped to an MSTI when you configure the VLAN-to-instance mapping table.
For more information about MVRP, see "Configuring MVRP."
•
The spanning tree configurations are mutually exclusive with any of the following features on a
port: service loopback group, RRPP, Smart Link, and L2PT.

Restrictions: Interface configuration

•
Some spanning tree features are supported in Layer 2 Ethernet interface view and Layer 2
aggregate interface view. Unless otherwise stated, these views are collectively referred to as
interface view in this document. BPDU drop can be configured only in Layer 2 Ethernet
interface view.
•
Configurations made in system view take effect globally. Configurations made in Layer 2
Ethernet interface view take effect only on the interface. Configurations made in Layer 2
aggregate interface view take effect only on the aggregate interface. Configurations made on
an aggregation member port can take effect only after the port is removed from the aggregation
group.
•
After you enable a spanning tree protocol on a Layer 2 aggregate interface, the system
performs spanning tree calculation on the Layer 2 aggregate interface. It does not perform
spanning tree calculation on the aggregation member ports. The spanning tree protocol enable
state and forwarding state of each selected member port are consistent with those of the
corresponding Layer 2 aggregate interface.
•
The member ports of an aggregation group do not participate in spanning tree calculation.
However, the ports still reserve their spanning tree configurations for participating in spanning
tree calculation after leaving the aggregation group.
23