MVRP with Per-VLAN STP and Per-VLAN RSTP

Beginning with FastIron 08.0.95, MVRP is enhanced to support Per-VLAN Spanning Tree (PVST). By default, all the dynamic VLANs created by MVRP run spanning tree instances. On both Layer 2 switch images and router images, PVST is enabled by default on MVRP untagged VLANs. You can use the mvrp spanning-tree command to choose the type of spanning tree to be added to the dynamic VLANs.

MVRP messages are propagated only to the ports in the active topology which comprise a set of forwarding ports in the MVRP untagged VLAN. MVRP does not support multiple dynamic VLANs to converge with different active spanning-tree topologies. The new VLANs that are learned dynamically will have the same Layer 2 data path. If you want a different path to be established for a particular PVST instance, you must manually configure the VLANs and add ports and configure the appropriate spanning tree parameters.

If you do not want spanning tree instances enabled by default on dynamic VLANs, you must remove the MVRP configuration on all interfaces, configure the no mvrp spanning-tree command, and then reconfigure MVRP on those interfaces.

MVRP Untagged VLAN

The MVRP untagged VLAN is the first port's untagged VLAN. All other MVRP ports added afterwards must follow the same untagged VLAN membership. The MVRP untagged VLAN is the VLAN in which all MVRP-enabled ports are present.

All the MVRP-enabled ports must have the same untagged VLAN membership. Consequently, the untagged VLAN membership of MVRP-enabled ports cannot be changed during MVRP operation. Therefore, the following operations issue an error message:

  • Configuring an MVRP-enabled untagged port on a different VLAN
  • Removing an MVRP untagged VLAN
  • Enabling MVRP on a port with untagged membership of a different VLAN
Note: It is recommended to configure Per-VLAN STP/RSTP on the MVRP untagged VLAN prior to MVRP configuration on interfaces to avoid unnecessary VLAN registrations.