The functioning of spanning tree protocol with virtual local area networks should collaborate because spanning tree protocol makes or designs the network topology to avoid loops in the bridged or switch topologies to expel the propagation of broadcast in the loop. When considering with the virtual Lan’s we have multiple broadcast domains to be added. So, each broadcast domain is a unique bridged internetwork that includes how the Spanning tree protocol works. We have a standard 802.1Q that defines us one spanning tree will be used by all Virtual LANS in the network. To know more about Per-VLAN Spanning Tree (PVST), Per-VLAN Spanning Tree Plus (PVST+), keep reading this article till the end.
Majorly Spanning tree works on native VLAN because in order to work on different compatible switches. Basically one spanning tree is regularly known as a common spanning tree or mono spanning tree.
Cisco introduced a protocol called per-VLAN spanning-tree plus (PVST+) which is compatible with common spanning-tree along with that it allows separate spanning trees to be constructed for VLAN but in the network of cisco, the paths can be different for each virtual local area networks.
Per VLAN spanning tree is a cisco protocol that makes the cisco devices to have different or multiple spanning trees. Devices can be interoperated with spanning trees on PVST and don’t operates on the 802.1Q devices but a standard of 802.1Q devices will allow all ports to run spanning trees.
PVST+ is an extension of PVST that makes or permits the devices to interoperate with devices that are running a single spanning tree. Common spanning trees and PVST regions cannot interoperate straightly but they can interoperate indirectly through PVST+ areas.
Also, read…
- What is EtherChannel PAgP and LACP Modes
- Difference between Spanning Tree Protocol (STP) and Rapid Spanning Tree Protocol (RSTP)
PVST Bridge port data units are tunneled through common spanning tree areas, while for VLAN1 are done by PVST+ areas. PVST improves the limitations of (STP) by aiding one separate instance for each VLAN, using ISL trunk only. PVST stills not operable with the devices only one (STP) instance. For PVST+ enhancing the tasks of PVST over 802.Q will leads to pvst+, the per-VLAN STP is always encapsulated with the help of multicast media access control and transferred over the channel.
PVST+ have two parts Tagged and Untagged, the native VLAN in the regions of PVST+ will communicate together over 802.1q but the complexity of the network only costs at the borders with the areas of PVST+ counts for native VLAN which interoperates with per VLAN spanning tree and the ISL instances are mapped to one-one with per VLAN spanning-tree plus instances.
Download Per-VLAN Spanning Tree (PVST) and Per-VLAN Spanning Tree Plus (PVST+) in pdf – Click here