There are some few constraints introduced by the interaction MST/PVST. It is generally simpler and more efficient to have an MST core with PVST access switches connected to it. I would thus rather recommend you start migrating to Rapid-PVST from the edge.
That's just a recommendation either way should work.
In any case, the CIST in the MST region must:
-have better information than any other vlan instance in the PVST region
-worse information than any other vlan instance in the PVST region
I think there is a quick explanation about that in the document that Prashanth referred to.
If the root for the PVST vlans are in the MST region, you can keep vlan load balancing and fast switchover between uplinks in case of failure.
Yes, interaction between MST and Rapid-PVST is supported.
Note that when MST talk to Rapid-PVST, there is no proposal agreement mechanism between them. The reason is that MST only runs a single instance while RPVST runs several instances. MST cannot generate a specific agreement on a per-vlan basis. Actually, it could because of a recent change in RSTP/MST, but it is not implemented (probably not worth it). To sum this up, MST will interoperate with Rapid-PVST, but at the same speed as it would with plain PVST.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...