最好的答案实际上
\n- \n
- Edit the value for \"InstantClone.Maintenance\" to 1 \n
- After a few minutes, vCenter and Horizon View will see that value, and shut down\/delete the cp-parent VMs on that host, and the value will change to 3 \n
- Once you see the cp-parent VMs are gone, you can go into Prism and go to LCM, once you have performed an inventory, you should be able to put a check next to the host you want to upgrade (ONLY CHECK THE HOST YOU WISH TO UPGRADE!). \n<\/ol>LCM will take care of the rest. It will invoke DRS (make sure HA Admission control is disabled or Nutanix will fail the process). It will migrate all workloads off the host, shut down the CVM, place the host into maintenance mode and begin the firmware upgrades. WHen the host comes back online, all your health checks are good, just change the value back to 0, and move some workloads back. When new VMs are needed in your instant clone pool, the cp-parent images will be spawned again. I would generally wait until the cp-parent images were re-spawned before moving to the second host. I only have 4 nodes in my instant clone cluster currently, so depending on how many firmware are needed bank on at least an hour per node I am on AOS 5.10.5 LTS, as there were some much needed improvements in LCM in the 5.10.x line up, so be sure you are on that build or higher.
\n
\nNOTE: if you have ANY nodes that require SATADOM upgrades, you HAVE to apply them on every node before any other firmware shows as available.
\n Let me know, i'm happy to answer any other questions!","className":"post__content__best_answer"}">
