Upgrading ESA to v10.2.0 on

Upgrading ESA from v9.1.0.x

Mon, 01 Jan 0001 00:00:00 +0000

When ESA is upgraded from v9.1.0.x, then the process is completed over two phases.
During Phase 1, the Kernel, OS, and other components are upgraded. After the Phase 1 is completed, the system restarts automatically.

After the system restarts, Phase 2 begins automatically and the critical components of ESA are upgraded.

It is recommended to wait for a few minutes before logging in to the ESA using SSH, to view the upgrade progress.

Upgrading ESA from v9.2.0.x

Mon, 01 Jan 0001 00:00:00 +0000

When ESA is upgraded from v9.2.0.x, then the upgrade process happens in a single phase.

During the upgrade, the system displays the upgrade progress which appears on the ESA CLI Manager. After the upgrade is successful, the system restarts automatically.
After the system restarts, log in to the ESA using the CLI Manager or Web UI.

While upgrading the ESA from v9.2.0.x, the entire process takes approximately 30 minutes. A temporary downtime is expected, resulting in limited access or intermittent interruptions.
Additionally, the time taken for creating the backup depends on the actual size of the data which is being backed up. The time taken for the backup is excluded from the upgrade process.

Upgrading ESA from v10.0.x

Mon, 01 Jan 0001 00:00:00 +0000

When ESA is upgraded from v10.0.1 or v10.1.0, ensure to apply the hotfix patch before applying the v10.2.0 upgrade patch.

ESA Version	Hotfix to be applied
10.0.1	ESA_PAP-ALL-64_x86-64_10.0.2+HF.2451.pty
10.1.0	ESA_PAP-ALL-64_x86-64_10.1.1+HF.2473.pty

If upgrading ESA from v10.0.1 or v10.1.0, then the upgrade process happens in a single phase.

Verifying the ESA Patch Installation

Mon, 01 Jan 0001 00:00:00 +0000

Verifying the ESA version

Perform the following steps to verify the patch installation:

From the ESA Web UI, navigate to System > Information.
The current patch installed on the ESA is displayed.
Navigate to the About page to view the current version of the ESA.

The ESA is upgraded to v10.2.0.

Verifying Upgrade Logs

During the upgrade process, logs describing upgrade process are generated. The logs describe the services that are initiated, restarted, or the errors generated.

Verifying the health of Trusted Appliance Cluster

Mon, 01 Jan 0001 00:00:00 +0000

After upgrading all the ESAs in the Trusted Appliance Cluster to v10.2.0, ensure that all the nodes in the cluster are healthy.

Perform the following steps to verify health of ESAs in the TAC.

These steps must be performed individually on each ESA node in the Trusted Appliance Cluster.

From the ESA Web UI, navigate to System > Trusted Appliance Cluster.
Verify the details for each node in the TAC.
In the Status field, the ESA node must be Online.
In the Status Message field, no errors must be displayed.
In the Labels field, each node must be labeled as Consul Server or Consul Client.
If the label for any ESA node is not Consul Server or Consul Client, then refer Common ESA Errors.