Doubts on PVSTP, RPVSTP and MST

Hello Valentina

Many of the answers to your questions are found within the STP lessons on the site, however, I will attempt to answer your questions specifically, or refer to you the appropriate lesson…

Yes. All interfaces that are up begin sending BPDUs and are in the listening state to listen for BPDUs from other devices. Only if a superior BPDU is received, only then will it considere itself not the root bridge.

For normal STP, BPDUs are generated by the root bridge every hello interval, which by default is 2 seconds, and each downstream switch that receives a BPDU on its root port will relay it to downstream switches. However, RSTP works differently, as all switches generate BPDUs.

In PVSTP, each VLAN has its own STP topology, and each one has its own root bridge. The root bridge of each VLAN sends out BPDUs. Assuming VLAN 1 is the native VAN on all trunks, then VLAN1 PVST+ BPDU is sent untagged while other VLANs PVST+ BPDUs are sent tagged with their appropriate VLAN.

Take a look at this post: Spanning Tree Topology Change Notification (TCN) - #24 by andrew

Take a look at the Discarding state in the following lesson:

Correct.

In the MST and PVST Interoperability lesson, it states:

Deciding the port role on the boundary interface for all VLANs is risky…after all, it means that we assume that all VLANs use the same root bridge, root ports, etc. We don’t know if the PVST+ domain agrees on the port role for all VLANs that we select on our MST boundary interface. There are, however, some simple checks that MST can use to figure out if PVST+ agrees on the port roles. Let’s take a look at each possible port role.

Those checks can be further understood from the lesson itself.

I hope this has been helpful!

Laz