Solved

Replacing upcoming EOL hardware process

  • 9 March 2023
  • 3 replies
  • 236 views
J

My 3 node cluster consiting of 1065-G5 nodes is coming EOL this year.  I will be replacing the hardware with a NX-3360N-G8 cluster.  What is the recommended workflow for replacing the hardware?  One thing to note is the current cluster is licensed with Prism Pro and the new one will be licensed with Starter as I’m not using all the features in Prism Pro.

Is the replacement as easy as expanding the cluster one node at a time, migrating the workloads and then removing the old cluster?  Will there be any hiccups with difference in licensing?

icon

Best answer by Kcmount 9 March 2023, 20:18

View original
This topic has been closed for comments

3 replies

Kcmount
Userlevel 4
Badge +6

Hi there!

Take a look at this - https://portal.nutanix.com/page/documents/details?targetId=Hardware-Admin-Guide:har-product-mixing-restrictions-r.html

 

Nutanix happy to support G8s and G5’s together in a cluster. 

 

There’s some other bits to take into account about SSDs/HDDs so give that link a good check through.

 

Licensing wise I don’t personally think there will be a problem, it’ll moan about licensing being in violation during the replacement but should settle down afterwards. 

 

Cheers,

 

Kim

Moustafa Hindawi
Userlevel 5
Badge +6

Hello @JarvisMeier 

As Kim said you can mix G5 with G8 in one cluster, however, I guess the earliest way is to build new cluster with G8 to avoid matching hypervisor and AOS versions, then migrate VMs using Nutanix Move.

Moustafa Hindawi | Blogger | Nutanix Technology Champion | NCSE | NCM-MCI | VMCE | 2xVCAP-DTM & DCV | 2xVCP-NV & CMA | LinkedIn: https://www.linkedin.com/in/moustafaadelmoustafa/ | My Blog: https://cloudwhales.co.uk/author/mhindawi/
M
Userlevel 3
Badge +6

Hi,

I’ve done this months ago, and I’m glad to have migrated all VMs from G5 cluster to a separate, freshly imaged G7 cluster. This way we got rid of any legacy configurations (vswitch bridge naming convention, just to name one) that may have prevailed on G5 in the course of numerous AOS and AHV upgrades.

Move was not AHV-to-AHV capable at that time though, and I had to set up ansyc DR to migrate the VMs over. Using DR instead of Move may still be more straightforward, as I reckon in your case no conversion will have to be carried out on the VMs at all. 

Kind regards,

Peter

Terms & Conditions