Feature Requirements |
Series |
Models |
|---|---|---|
RSTP applies a single spanning tree instance to the entire switching network. It cannot solve the problem of performance deterioration caused by the increase of the network scale. Therefore, the network diameter cannot exceed 7. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
BPDU protection takes effect only on manually configured edge ports. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Loop protection and root protection cannot be configured on the same port. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When MSTP multi-instance is configured, the length of a protocol packet increases with the number of instances. MSTP sends MSTP packets in each process independently. When MSTP multi-process is configured, the number of sent MSTP packets increases. In multi-process and multi-instance scenarios, the default CPCAR value of STP cannot meet protocol requirements. You need to manually increase the CPCAR value of STP. Otherwise, protocol packets may be discarded by CAR. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
MSTP supports a maximum of 48 x 12 x 4 valid ports |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
To prevent traffic looping on the access ring after the link between the UPEs fails, it is advised to configure priorities and root protection for MSTP multi-processes. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
PW interfaces do not support multip-instances computation. They use the forwarding status of instance 0. Loops may occur when the status of MSTP instances on PW interfaces is inconsistent. Configure the network properly to ensure that the status of MSTP instances is consistent. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |