We have a pair of Force 10 Core/Distribution switches, which is going to be migrated with a Cisco 6807-XL switch designed for VSS. This is a swap migration, ie - the F10 Core1 switch will be shutdown, and the 6807-1 will be placed in the same rack, since we dont have additional rack space to accomodate for parallel migration.
When we put 6807-1, the Force 10 -2 switch will still be active passing traffic. My question is:
1) can I put the 6807-1 with VSS preconfigured, so that when I replace Force10-2 switch with the 6807 pair, it automatically forms VSS neighborship, and is a part of the cluster ?
2) the above question is crucial, since we have VRRP running on F10, and we plan to do just L3 SVI's (and not HSRP) since the 6807s are in VSS pair.
3) If I cant put a standalone switch on VSS, the only option is to migrate to HSRP , by shutting down VRRP SVI's and bringing UP the HSRP SVI's in Cisco 6807.
I know STP is another mess during this migration, but Ill worry about it later :)
1. Build both the switches for VSS in the lab/work bench. Make sure VSS pairing is formed. Power them off. Then just rack the primary switch and move across SVIs. When you are ready to mount the second switch, just plug the VSL cables according to the configuration and ensure the secondary switch joins the VSS. This would be my prefered way.
2. Configure only one switch as VSS and migrate SVIs across. Then when you are ready to mount the second switch, just configure it, plus everything proprely and ensure VSS comes up.
Thanks for the reply. Id probably go with option 1.. are there any gotchas with option 1 ? when breaking the VSS, are there any limits/or timelines when the 1st switch can run without its VSS pair ? I know there isnt any, but have you seen any practical scenarios where are there issues with such migration ?
Thanks again for the points.. very useful... 5 points for sure.. :)
You can run the VSS switch without its pair indefinitely. You can look under "Failed Chassis Recover" under the document I mentioned in the first post. It advises the same thing.
Make sure that the switch priority is configured correctly and the you put your Primary VSS in production first. This is not a restriction or limitation, but just a safe practice. Also, make sure you dont power on the secondary switch without connecting the VSL to primary first. This step is to mainly ensure that you dont run into Dual-Active scenario.
Please mark this question as answered so that others can benefit from this discussion.
What is AppQoE?
AppQoE is a WAN optimization stack and optimizes WAN traffic for different use cases for applications that are deployed on-prem or in cloud.
What are the benefits of using AppQoE?
AppQoE improves application experience by d...
The application delivery challenges have been the enemy of network since the advent of Internet. So, what are these application delivery challenges that can bring down a network to its heels?
Above are some of the common problems faced not only by tradit...
It is our pleasure to officially announce the finalists in the 2021 IT Blog Awards. Now we are looking to YOU, our amazing tech community, to weigh in. Check out the amazing educational content we've uncovered and vote for your favorites before Friday, Fe...
SD-WAN Advanced Deployment What is SD-WAN? SD-WAN is Software define wide area network and SD-WAN is key part of the technology of software-defined networking . SDN is a centralized approach to network management which abstract...