RPVST with VSX guidelines

  • Path cost is not allowed to be configured on the ISL port.

  • Do not configure port-specific spanning tree configurations on the ISL.

  • Do not have redundant links to the ISL.

  • Topology changes for VSX LAGs are accounted on the active multichassis LAG role only.

  • RPVST is supported in both VSX and non-VSX environments.

  • The common bridge ID continues to be used even after the VSX split brain scenario is identified.

  • STP configurations on VSX LAG ports must be the same on VSX switches.

  • To find the maximum supported RPVST instances that can be configured, enter the following command: show capacities rpvst