08-01-2023 07:17 AM
Hello,
I have a pair of 9407R switches connected through a port channel and a few access swtiches with links to both of them like shown in the picture below.
The layer 3 services are configured using HSRP for each vlan.
I was requested to plan a migration to Stackwise virtual, so I have checked the following pre-requisites.
One of the requirements is to minimize as much as possible the downtime, so I thought of the following procedure.
My questions would be.
I much appreciate any guidance you can give me.
Thanks.
Solved! Go to Solution.
08-02-2023 08:30 AM
Hi Hugo,
Once you convert switch1 from a standalone switch to VSS, the switch will reboot, and at that time all the old config will be gone. The same thing will be repeated for switch 2. So, that is why you need to have a step-by-step plan and a long enough maintenance window to redo some or all of your configs and put the switches back in production. I recommend you make a good copy of the current config before you try anything and have a plan on how you want to prioritize what portion of the config needs to be in place first to put the switches back in production as fast as possible. I also think it is easier if you do everything in one larger maintenance window vs multiple short ones.
HTH
08-01-2023 05:07 PM
Please stop using 17.3.X and make plans to migrate to 17.9.3 (and later).
08-02-2023 06:31 AM
Hi Leo,
Thank you for your response. I will include the upgrade in the procedure.
Regards,
Hugo
08-02-2023 06:41 AM
08-02-2023 07:43 AM
Hi Reza,
Thank you for your response.
You said that the VSS will wipe out completely the config on the switch. Will it happens with the frist swtich in converted to the VSS as well? I mean, If I have switch1 and switch2 and I enable the VSS config on swtich1 and reload I assume that it'll be the first one in the stack and I wonder if that one will be also wiped out or would keep the config except for the interface name that will get an extra digit at the front.
I definetely will do all those changes in maintenance windows but I was wondering if I could split the work in two maintence window so I would haeverything working antested on one side of the new VSS before converting the other node.
08-02-2023 08:30 AM
Hi Hugo,
Once you convert switch1 from a standalone switch to VSS, the switch will reboot, and at that time all the old config will be gone. The same thing will be repeated for switch 2. So, that is why you need to have a step-by-step plan and a long enough maintenance window to redo some or all of your configs and put the switches back in production. I recommend you make a good copy of the current config before you try anything and have a plan on how you want to prioritize what portion of the config needs to be in place first to put the switches back in production as fast as possible. I also think it is easier if you do everything in one larger maintenance window vs multiple short ones.
HTH
08-14-2023 05:52 AM
Hi Reza,
Thank you for your response.
I will schedule the job in a large enough maintenance windows to do both switches but I am working for an institution that can allow me some outages but not all the network down for a large period of time. So I am hoping I can enable the Stackwise portal on one of the switches and have everything configured and tested before enabling the stackwise on the other switch including the SVL and DAD interfaces. it does not matter if both restart afterwards but there are a lot of systems to test to make sure the connections are working properly and I would prefer to do it half way in case we have to roll back for some reason.
Regards,
Hugo
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide