Open topic with navigation

# Upgrading Deployed Capabilities

Note: Make sure you have completed the Checklist: Upgrading Your On-premises Environment process before proceeding with the steps listed here, to ensure a successful upgrade. As part of the process, you must upgrade your deployed capabilities using the OMT Management Portal.

- Verifying the Certificate Validation

- Considerations for Upgrading Intelligence

- Upgrading Deployed Capabilities

## Verifying the Certificate Validation

Verify that your certificate has been validated. Do the following:

1. On the OMT Management Portal, click DEPLOYMENT, and then select Deployments.
2. Click the Three Dots (Browse) on the far right and then choose Reconfigure.
Note: If you are unable to access the OMT Management Portal Reconfigure Page during the upgrade process, see the known issue Accessing the OMT Management Portal Reconfigure in the Release Notes for ArcSight Platform 23.3 for a workaround.
3. (Optional) Any new parameters for upgraded capabilities are presented. You can set values for them, if desired, or leave the defaults in place.
4. If your certificate has not yet been validated, you are prompted to accept the certificate. Do so now. If you are not prompted, then your certificate has already been validated and no action needs to be taken.

## Considerations for Upgrading Intelligence

If you have deployed Intelligence and are upgrading it, consider performing the following steps on the NFS before upgrading the deployed capability:

- Ensure that you move your SQL loader scripts from:
  `/<arcsight_nfs_vol_path>/interset/analytics/vertica_loader_sql/0/<existing_folder_name>` to
  `/<arcsight_nfs_vol_path>/interset/analytics/vertica_loader_sql/0/1.<existing_folder_name>`.

- If you are using custom data identifiers, ensure that you back up the `logstash-config-pipeline` config map that is accessible through the Kubernetes dashboard.

## Upgrading Deployed Capabilities

Important: DO NOT CLOSE YOUR BROWSER at any time during this process. If you inadvertently close the browser, use this method to recover.

1. (Conditional) Before upgrading Intelligence, review the section "Considerations for Upgrading Intelligence" discussed above.

Perform all of the following steps from the master node to which you downloaded the upgrade files.

1. Delete any pre-existing upgrade pods by running the following command from the master node:

       kubectl delete deployments suite-upgrade-pod-arcsight-installer -n $(kubectl get namespaces | grep arcsight-installer | awk ' {print $1} ')

   Note: The above command might return a spurious error message. It can be ignored and you can proceed to the next step.
2. Change to the following directory:

       cd ${K8S_HOME}/scripts

   where `{K8S_HOME}` has a format similar to: `/opt/arcsight/kubernetes/`

1. Run the following command to upload the images to the local Container Registry. Adjust the `-c 4` option up to half of your CPU cores in order to increase the speed of the upload.

    ./uploadimages.sh -c 4 -d {​​unzipped-installer-dir}​​/images

Note: You will be prompted for a password for the Container Registry-admin user. The registry-admin password is initially set to the same password as the admin user for the OMT Management Portal during installation when Configuring and Running the OMT Installer; however, later changing the OMT Management Portal admin password does not change the registry-admin password as it is managed separately.

Note: Make sure to copy the `arcsight-suite-metadata-x.x.x.x.tar` to the system where your web browser is running before performing the process below.
1. Browse to the management portal at https://<virtual_FQDN>:5443, or at https://<master_node1_FQDN>:5443.
   1. Click DEPLOYMENT>Metadata and click + Add.
   2. Select `arcsight-suite-metadata-x.x.x.x.tar` from your system. The new metadata is added to the system.
   Select the Overwrite box only if you are overwriting data that was not uploaded correctly, such as from a failed installation.

1. Start the upgrade process.
   1. Browse to DEPLOYMENT > Deployments. Notice the number 1 in the red circle in the Update column.
   Note: Minor version changes do not display like regular updates. (For example: 23.2.0.15 -> 23.2.0.16.)
   2. Click the red circle and select your recently added metadata to initiate the upgrade.
2. From the Update to page, click NEXT until you reach the Import suite images page. When prompted to download or transfer images, simply click Next to skip the steps, as you performed these steps earlier.
3. Ensure that the validation results of container images show a complete number of files.
Note: When you arrive at the Import suite images page, the images should already be imported, as you performed these steps earlier.
4. Click NEXT until you reach the Upgrade Complete page.

Note: In the rare event of upgrade failure, consult the log for errors at `/tmp/autoUpgrade/upgradeLog/upgrade-<timestamp>.log`.