I am migrating from a pair of 4510s to a pair of 6509s with as little disruption as possible. Any suggestions on how to do so when it comes to spanning tree?
The 4510s are configured as root at bridge priority 4096 and secondary at 8192. I was going to add in the 6509s as 12288 and 16384 and create a square design with all 4 switches. The access switches are a combination of 2950s, 3750s and 4948s with Etherchannel uplinks on some switches.
All access switches are configured with uplinkfast and the network is running PVST+ I'm trying to decide how to migrate the uplink ports on the access switches. I know I can move the blocking port to the new switches without disruption. I also know that I can move the root port and uplinkfast will fail to the other uplink subsecond. I also know that uplinkfast will wait 30-45 seconds to switch back from the "secondary" port to the root port, but what happens if the formerly root port is no longer in the root switch when it comes back up?
I realize there are many options so any input would be greatly appreciated.
Thanks for the advice, but I don't have that kind of window. Management would prefer I do it without even the 35-45 seconds of a recalc per access switch. My plan is to add the 6509s so I have 4 distribution switches, migrate all access switches to the 6509s and then shut down the 4510s. With no downtime.
I would suggest to make the new C6509 the new root bridges using base priority 0 and 1: after a recalculation you will have the final setup and then you move your access switches link by link to the new devices.
I would try to get from management a time window for doing this and then later you move each uplink
I wouldn't face the risk to have an access layer switch to have a chance to be elected root bridge even during a transition
With UplinkFast configured, the access switch will place blocked port (alternative link to a distribution switch) immediately into forwarding mode (less than one second)
*) For sake of stability:
- UplinkFast will move the returning root port immediately as soon as it is up, but the designated port in the other side of the uplink (to the root) will undertake the usual STP procedure (listening->learning) 2*ForwardDelay + 5sec = 35sec.
- To avoid flapping, uplinkFast will not allow another consecutive switchover to the backup uplink for 35 sec.
So you can take advantage of the very fast speed of UplinkFast recovery everytime an uplink failure occur(or a topology change) + 35 sec.
*) UplinkFast will make sure that the switch (access level) in which it is configured:
- have apriority of 49152 (you can can explicitly make it greater or make the priority on the root/backup very low).
- Set the port cost to 3000.
- Track alternate ports to distribution.
- instruct distribution switches to reset their CAM and then inform them about its local db (using dummy multicast): the availability of your network will be also limited by the speed at which CAM tables are updated and accurate, you can increse the frequency at which the access switch will send dummy packets.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...