Performing the upgrade

During an upgrade, you only upgrade the application, which also upgrade the underlying database schema. 

Build numbers

You must provide the build number depending on the version that you want to upgrade to. 

To upgrade TrueSight Automation Console

1. Open a terminal and SSH into the host where you have set up the local registry, and run the following command to update the Stack Manager tool. 

   docker run -it --rm --network=host <hostname>:<port>/bmcsoftware/truesight-stack-manager:<version_number>.<build_number>
   

   Example

   docker run -it --rm --network=host 127.0.0.1:5000/bmcsoftware/truesight-stack-manager:23.3.00.2748
   

   Here, 127.0.0.1:5000 is the host:port of the local registry that contains the TrueSight Automation Console images.  
   You are prompted to specify a location to install the product.  

2. Enter a username with root permissions and a password. 
   The Stack Manager tool is updated at the specified location. 
3. Enter the location where the previous version is installed. 
   The following message is displayed: Stack Manager Launcher is already installed, do you want to overwrite it?y/(n)
4. Enter y.
   The Stack Manager tool is updated. 

5. On the host where the Stack Manager tool is installed, run any of the following commands to start upgrading the application.
   This command also upgrades the database schema. 

   <install_directory>/stackmanager install  --deployment tsac+
   

   <install_directory>/stackmanager install  --deployment=tsac+
   

   The existing installation and the END USER LICENSE AGREEMENT  is displayed. 

   [INFO] loading deployment registry from /opt/bmc/sm/registry/sm-deployment-registry.yml
   **************************************************
   TrueSight Stack Manager <version_number>.<build_number>
   **************************************************
   
   The following services are already installed:
   Deployment   Location
   ----------   --------
   application  /opt/bmc/truesight/application
   database     /opt/bmc/truesight/database
   
   [INFO] Start installation
   Press Enter to Read the License Agreement and enter the Appropriate Option
   END USER LICENSE AGREEMENT
   <Agreement Text>

6. Read, and type y to continue with the upgrade.
   If you are upgrading to 21.02.01 or later versions, the following message appears: Do you want to configure TSNA Connector [You may choose No now & configure it post upgrade] ([y]es/[n]o) ?
   

   Do I need to configure the TSNA connector during the upgrade?

   No. You can choose to skip it and continue with the upgrade. If you want to integrate with TrueSight Network Automation, you can configure the connector by using the Automation Console UI later.

7. (Optional) If you choose to configure the TrueSight Network Automation connector, type y and provide the values that match your environment:
   If you do not want to configure the connector, type n and skip to step number 8.

   Field	Description
   Host name of TrueSight Network Automation	Fully-qualified domain name or IP address of TrueSight Network Automation
   Port number of TrueSight Network Automation	Port number
   Protocol of TrueSight Network Automation	Default value: https
   Realm name of TrueSight Network Automation	Specify the realm name
   Service Account user name of TrueSight Network Automation	Specify the user name
   Password for the Service Account user of TrueSight Network Automation '<user name>'	Specify the password that matches the user name
   Realm name for the Service Account user of TrueSight Network Automation <Realm Name>	Specify the realm name of the service account user

8. TrueSight Automation Console upgrade is complete and the following status message appears.

   TrueSight Automation Console <build_number> can be accessed at: <URL>
   Installation is completed successfully.
   
   <For 21.02.01 or later versions>
   TrueSight Automation Console <version_number>.<build_number> can be accessed
   at: https://<hostname>:<portnumber>/services/#/account/tsna/login

9. Run the following command to verify whether the upgrade is successful: 

   To verify the status

   <install_directory>/stackmanager status  --deployment=application
   

   All the updated container names must display their status as running. 

10. (Optional) If you are using custom certificates, ensure that you have backed up the certificate files before the upgrade. After a successful upgrade, do these steps:
    1. 
       

       1. Run the following command to replace the new certificates (created during the upgrade) with the custom certificates copied earlier. 

          cp /opt/<backup_directory>/tsvmSslCertificate.crt <install_dir>/application/common/certs/
          cp /opt/<backup_directory>/tsvmSslCertificate.key <install_dir>/application/common/certs/

       2. Restart the application.

          <install_directory>/stackmanager restart  --deployment=application
          

Where to go next?

After a successful upgrade, the previously installed connectors do not need any update. If you want to configure any of the new/optional connectors, see Managing-connectors.