Overview
About This Document
This document describes how to prepare for an upgrade, upgrade a management node environment, upgrade a management node HA environment, perform checks and follow-up after the platform upgrade, and upgrade host virtualization components and the kernel as needed in a deployed ZSphere environment.
Intended Audience
This document is intended for administrators, implementation engineers, and operations engineers who upgrade and maintain ZSphere environments. Readers should understand the current deployment mode, management node access method, and basic Linux command-line operations.
Upgrade Paths
Select an upgrade path based on whether management node HA is configured in the current environment.
| Environment Type | Upgrade Path |
|---|---|
| ZSphere environment without management node HA | Prepare for the upgrade, upgrade the management node environment, and then perform checks and follow-up after the platform upgrade. |
| ZSphere environment with management node HA | Prepare for the upgrade, stop management services on both nodes, and upgrade the HA suite and management node on the management node where the VIP resides. After the platform upgrade succeeds, start management services on both nodes, and then perform checks and follow-up after the platform upgrade. |
After the platform upgrade is complete and the environment is running properly, you can upgrade host virtualization components such as QEMU and Libvirt and the host kernel independently as needed. A platform version upgrade does not automatically perform either type of upgrade. You can schedule these upgrades for separate maintenance windows based on business requirements.
