Pls suggest me the configuration for two Nos of 4510R-E chassis with 2 nos of SUP V plus 2 10GE.
On both switches config must be same.
Config will include 1 backbone vlan and some static routes.
I want to implement redundancy of Backbone for distribution using HSRP and also SUP redundancy.
Also want to know the config for using 3 nos of link between two 4510R-E .
Pls give me the sample config....
it is nice to see this long thread has not been lost in the forum upgrade!
I answer to your questions:
1) Many of the Vlans Roots are selected randomly except Vlan 2 Backbone. Hence I need to tune STP so that for all Vlan Root will be the 3560 SW only for the perticular SWitch block except the backbone vlan.
â€¢ STP convergence time is more than expected.
yes for both the solution is to configure C3560 distribution nodes as the root bridge for all client vlans of the switch block
2) have seen Spaaningtree sumurry and it shows no of STP instances are around 300.
to limit number of running STP instances use switchport trun allowed vlan VTP pruning is NOT effective in this contrary to popular belief.
VTP pruning helps in limiting unnecessary traffic to be sent on L2 trunk ports. for a switch it is enough to have a vlan permitted on a single trunk to run an STP instance.
each C3560 distribution should run N+1 vlans if N are the client vlans.
Currently there is a risk that vlans extend in all campus. This has to be avoided
3) using a common native vlan on all trunks without IP services over it is recommended also for security reasons. I would do it
All these will provide improvements over current scenario. As I noted in previous posts if after all these changes you still see STP events it may be wise to open a service request
Hope to help
yes in the new config template root bridge is enforced for all Vlans with explicit command.
this is good.
About STP loop guard probably that is a possible explanation of why it is recommended to configure it on both ends of a link.
as explained in the documents in previous post you can use the command
spanning-tree loop guard default
However, I think it makes sense to use it only on inter-switches links not on access ports
So I would enabled it on a per port basis to have more control.
To be honest we cannot say that all these STP events will disappear.
Hope to help