04-22-2019 07:47 PM
Hi,
Good Day!
Is it possible forming a vPC connection between two Nk5 with different NX-OS version?
Network Device NX-OS Version
N5K-C5596UP = 5.2(1)N1(6
N5K-C5596UP = 7.3(5)N1(1)
Both appliances are not yet connected.
Thank you!
Solved! Go to Solution.
04-24-2019 12:01 AM
Hello,
Ok, so currently the second N5K is more a "spare" than a "backup"...
It is surprizing that you cannot afford an impact in your migration while your design currently includes a Single Point of Failure with only 1 N5K without resiliency mechanism.
The good news is then that you can establish VPC without impact, and you'll need to follow upgrade version path from 5.2(1)N1(6) to 7.3(5)N1(1).
- Downgrade "Backup" to 7.0(8)N1(1)
- Establish VPC peering
- Connect secondary links of surrounding devices onto Backup
- Upgrade Primary to 7.0(8)N1(1), then to 7.1(4)N1(1)
- Upgrade Backup to 7.1(4)N1(1), then to 7.3(5)N1(1)
- Upgrade Primary to 7.3(5)N1(1)
During failovers you still may encounter small cuts.
Remi Astruc
04-23-2019 01:16 AM
Hello Ejah,
The question is, what can be your requirement to have such similar switches (same HW, want to merge in VPC to act as a logical switch) having such different OS version...
I suggest you upgrade them into the same OS version, and avoid uncertain behavior with such inconsistency.
Remi Astruc
04-23-2019 02:34 AM
04-23-2019 03:33 AM
Hello,
That may not be a solution.
By itself, enabling VPC feature and configuring it on 2 switches will not impact existing traffic.
But if I understand that your 2 switches are already interconnected in traditional STP design with some Vlans, moving this interco into VPC Peer-Link with the production Vlans into it will impact these Vlans while you perform the change (and again, not confident about such OS version difference within a VPC).
Also, if you are not yet in VPC, it means your attached devices don't have Port-channel to the pair yet. To leverage VPC feature, you will need to reconfigure these devices from individual ports into Port-channel, which will have impact as well.
To summarize, moving into VPC will not avoid impact on your infra, and you can instead just move your active links towards the secondary Nexus with pretty similar impact.
Remi Astruc
04-23-2019 05:56 PM
Hi Remi,
Here is the current setup
And this is the propsed setup
04-24-2019 12:01 AM
Hello,
Ok, so currently the second N5K is more a "spare" than a "backup"...
It is surprizing that you cannot afford an impact in your migration while your design currently includes a Single Point of Failure with only 1 N5K without resiliency mechanism.
The good news is then that you can establish VPC without impact, and you'll need to follow upgrade version path from 5.2(1)N1(6) to 7.3(5)N1(1).
- Downgrade "Backup" to 7.0(8)N1(1)
- Establish VPC peering
- Connect secondary links of surrounding devices onto Backup
- Upgrade Primary to 7.0(8)N1(1), then to 7.1(4)N1(1)
- Upgrade Backup to 7.1(4)N1(1), then to 7.3(5)N1(1)
- Upgrade Primary to 7.3(5)N1(1)
During failovers you still may encounter small cuts.
Remi Astruc
04-25-2019 01:09 AM
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