All things considered — upgrade sequence and preaparation guidelines

  • 22 October 2019
  • 0 replies
  • 202 views

Userlevel 3
Badge +3
  • Nutanix Employee
  • 55 replies

Let’s face it, upgrades are daunting, and confusing, and frequent, and unavoidable, and, well, painful. Aiming to help with the preparation process and alleviate at least some of the worries Nutanix put together Acropolis upgrade (Upgrading AOS, Prism Central, Hypervisors, and Related Software Through The Web Console).

Recommended Upgrade Order:

  1. Prism Central (PC): Upgrade and run NCC on Prism Central.
  2. PC: Upgrade Prism Central.
  3. PC: Run NCC.
  4. Prism Element clusters (PE): Upgrade and run NCC.
  5. PE: Upgrade Foundation.
  6. PE: Run and upgrade Life Cycle Manager (LCM):
    • Perform an LCM inventory (also updates LCM framework). Do not upgrade any other software component except LCM in this step.
  7. PE: Upgrade AOS.
  8. PE: Run and upgrade Life Cycle Manager (LCM):
    • Perform an LCM inventory (also updates LCM framework).
    • Upgrade SATA DOM firmware (for hardware using SATA DOMs) as recommended by LCM.
    • Upgrade all other firmware as recommended by LCM (BIOS / BMC / other).
  9. PE: Upgrade AHV for AHV clusters.
  10. PE: Upgrade cluster hypervisor hosts other than AHV.
  11. PE: Run NCC.

 

Figure. Nutanix Upgrade Order 1 of 2: Prism Central and Prism Element Clusters

 

Figure. Nutanix Upgrade Order 2 of 2: Hypervisor Hosts

 

Nutanix recommends that you perform installation and upgrades during your scheduled maintenance window or outside your normal business hours. You can upgrade during these times, but your users might experience some latency during the upgrade process. This latency might be noticeable for clusters that use only 1GbE network uplinks due to the limited bandwidth available for this configuration.

Guest VMs might live migrate between hosts depending on the upgrade being performed with little to no impact to their services. Users can access to their VMs and be able to work as normal during the upgrade.

You might need to power down or adjust settings before upgrading for VMs that cannot live migrate, such as those with vGPUs or Affinity Rules. Typically this recommendation applies for any upgrade that requires a host reboot (like hypervisor upgrades). If you do not do this, an upgrade operation might stall when evacuating guest VMs.

 

:exclamation: Be sure to read Before You Begin, Upgrade Checklist as well as Reference and Resources (lists all compatibility matrices’ URLs) sections of the guide as a starting point.

May the Force be with you!:fingers_crossed:

 


0 replies

Be the first to reply!

Reply