Hey If you're willing to do a little bit more work upfront and have an easier life later, I'd go with MST. While PVST (pvst+) adopted fast-convergence properties introduced by IEEE RSTP protocol, the core feature of keeping a separate copy of STP per VLAN did not change. Ie it still remained a challenge. Seeing the problems associated with PVST approach, Cisco came with idea of decoupling the concepts of STP instances and VLANs. MST. The initial implementation was called MISTP (Multiple Instances Spanning Tree) and later evolved into IEEE 802.1s standard called MSTP (Multiple Spanning Trees Protocol). Pvst can also be tuned to achieve faster convergence. Have a look at the design guides below. http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configurati... http://standards.ieee.org/getieee802/802.1.html http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configurati... Gitau Sent from my iPad On 24 Feb 2012, at 16:17, TheMburu George <themburu@gmail.com> wrote:
Hey skunks
I need to implement fastest convergence on VLAN's. One way is implementing PVST (Per VLAN STP) and have preset root bridges, now the question which among the following facilitate faster root bridge election and hence quicker convergence #spanning-tree vlan vlan_no. priority value #spanning-tree vlan vlan_no. root {primary |secondary}
The second way is implement Multiple Spanning Tree (MST), though I havent implemented it and dont know the shortcoming but seems faster and lighter than PVST. Question is how is the experience to those who have implemented it and speed of convergence and fault tolerance
./TheMburu -- Conservatism is the adherence to the old tried against the new untried. _______________________________________________ Skunkworks mailing list Skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks ------------
Skunkworks Rules http://my.co.ke/phpbb/viewtopic.php?f=24&t=94 ------------ Other services @ http://my.co.ke