Licensing Requirements and Limitations for MSTP
Involved Network Elements
Other network elements are not required.
Licensing Requirements
MSTP is a basic function of the switch, and as such is controlled by the license for basic software functions. The license for basic software functions has been loaded and activated before delivery. You do not need to manually activate it.
Version Requirements
Product |
Minimum Version Required |
|---|---|
CE12804/CE12808/CE12812 |
V100R001C00 |
CE12816 |
V100R003C00 |
CE12804S/CE12808S |
V100R005C00 |
CE12800E |
V200R002C50 |
For details about the mapping between software versions and switch models, see the Hardware Query Tool.
Software version evolution: V100R001C00 -> V100R002C00 -> V100R003C00 -> V100R003C10 -> V100R005C00 -> V100R005C10 -> V100R006C00 -> V200R001C00 -> V200R002C50 -> V200R003C00 -> V200R005C00 -> V200R005C10 -> V200R019C00 -> V200R019C10
Feature Limitations
On networks that run STP, RSTP, MSTP, or VLAN-based Spanning Tree (VBST), configure an optimal core switch as the root bridge to ensure stability of the STP Layer 2 network. Otherwise, new access devices may trigger an STP root bridge change, causing short service interruptions.
When MSTP is enabled on a ring network, MSTP immediately starts spanning tree calculation. Parameters such as the device priority and port priority affect spanning tree calculation, and changing these parameters may cause network flapping. To ensure fast and stable spanning tree calculation, perform basic configurations on the switch and interfaces before enabling MSTP.
When MSTP multi-instance is configured, more MSTIs indicate longer MSTP BPDUs. MSTP BPDUs are sent independently in each MSTP process. When MSTP multi-process is configured, the number of outgoing MSTP BPDUs increases. When MSTP multi-instance and multi-process are configured, the default CPCAR of STP cannot meet requirements. You need to increase the default CPCAR of STP. If the default CPCAR of STP is not increased, MSTP BPDUs may be discarded.
BPDU protection takes effect for only the manually configured edge ports.
Loop protection and root protection cannot be configured on the same interface together.
- In versions earlier than V200R001C00, STP cannot be configured on a user-side interface of a VXLAN tunnel. Starting from V200R001C00, STP can be configured on a user-side interface of a VXLAN tunnel that accesses the VXLAN as a VLAN. In V200R002C50 and later versions, STP can be configured on a user-side interface of a VXLAN tunnel when the device is deployed to provide VXLAN access through a Layer 2 sub-interface or to provide VLAN access.
- In V200R001C00, the bpdu bridge enable command is not supported on the VXLAN network. If this command is configured in a version earlier than V200R001C00, it will be deleted from the device configurations after an upgrade to V200R001C00. To enable BPDU packets to traverse the VXLAN network, run the undo mac-address bpdu [ mac-address [ mac-address-mask ] ] command in the system view. In this command, mac-address specifies the MAC address of BPDU packets that need to traverse the VXLAN network.
When the interoperability mode of cards on CE12800 series switches is enhanced, a maximum of 64 MSTIs are supported. When the card interoperability mode is non-enhanced, a maximum of 61 MSTIs are supported. When the undo set forward capability enhanced command is used to set the card interoperability mode to non-enhanced, it is recommended that a maximum of 61 MSTIs be used. ED-E/EG-E/EGA-E series cards of the CE12800E support a maximum of 128 MSTIs. FD-X series cards of the CE12800E support a maximum of 64 MSTIs.