yeah that behaviour is normal & maximum of 30 seconds of delay you will get, but if you configure the given spantree command, it will might take less than 10 sec. or max. of 15 sec. reason of the delay is because it will find the root swtich. the command we are specify is to minimize that delay. it cannot be less than 2-3 sec.
Honestly, I could not guess the design of your network from your description;-) Do you have 3 switches and 2 routers, or are you considering two of your switches as routers (as you could indeed). Could you explain how they are connected together.
If I understand correctly, you put all the switches in the same vtp domain in transparent mode, and you are only using vlan 1 right?
At last, is your loss of connectivity temporary or permanent when you are connecting your new switch (and also, what is the new switch btw).
I would not blindly reduce STP timers to their minimum value without understanding the reason for your problem.
At this moment the 2980B and 3560A are NOT connected, and everything is ok. To achieve the STP redundancy the moment I connect 3560A with 2980B (Root Bridge) both the switches ie 2980A and 3560A become unaccessible.
Also in the config the HSRP is configured and the MPLS Router is the Active Router.
VTP is being used and the Root Bridge is VTP Server and rest of the switches are Clients.
The Gigports on all the Switches are in Trunk Mode.
Now, whenever the connection is made between 2980B and 3560A using the Gigports, I'm not able to ping from the MPLS Router to either the 2980A or 3560A.
Sorry for the late answer. I cannot find an obvious cause for your problem (there are too many possibilities in fact;-)).
STP has to block a port in your topology. It's very likely to be gi0/1 on the 3560. For some time, both uplinks on the 3560 could block (this depends also on your stp mode).
Is the connection permanently lost, or just for about 30 seconds or for about 300 seconds (one is 2xforward_delay, the other is the cam aging time)? Are you running MST? Do you have any feature configured (rootguard, bpduguard in particular)?
The simplest way to troubleshoot that is to inspect on the path between the two L3 devices that are trying to communicate the stp state of every switch involved. You can also check the consistency of the cam table for the mac address of the L3 devices along this path.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...