Upgrade Prerequisites

Verify the following before performing the upgrade :

• The packages for upgrade have been downloaded following this procedure:

  • To identify the files to download to your secure network location, see Downloading the files in the Release Notes for ArcSight Platform.

  • From a secure network location, download the installation packages for the OMT Installer and the products of your choice from the Software Licenses and Downloads portal.

  This secure network location must be able to access your instance of AWS.

• Root access to the bastion VM is granted

• The kubernetes command line tool kubectl is installed on your bastion and connected to your cluster

• Any existing suite-upgrade-pod-arcsight-installer deployment has been deleted using this command:

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

  The command will return an error if no upgrade has been done previously

• Check that your EFS throughput configuration is the correct one to manage the amount of data going through. See EFS Throughput modes for more information. Making sure your configuration is correct will also prevent environment performance issues during regular operation.

• (Conditional) If you are using custom data identifiers for Intelligence, ensure that you back up the logstash-config-pipeline config map that is accessible through the Kubernetes dashboard.

• (Conditional) If you have deployed the Intelligence capability, and are using custom SQL scripts, then perform Step 1 of the workaround described in the known issue Analytics Does Not Detect the Custom SQL Loader Scripts After the Intelligence Upgrade in the Release Notes for Arcsight Platform 23.1.

• All pods are running, verify with this command:

  kubectl get pods -A

Next Step: Stopping Event Ingestion for the ArcSight Database