Walkthrough: Upgrading to the latest version for Linux

Upgrading using the unified product installer

The unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server and the TFTP server in your environment. If you manually enabled the TrueSight Server Automation Console Upgrade Service, the console is also automatically upgraded; otherwise, you must manually upgrade it. The checklist below walks you through the process of upgrading Windows and Linux environments using the unified product installer.

Step 1: Review requirements and limitations

The first step is to review the following requirements and limitations when using the unified product installer for product upgrade.

Requirements

Limitations when using the unified product installer

Step 2: Prepare the environment for upgrade

Perform these tasks in order. Many steps are prerequisites for other steps that occur later in the process.

1. Back up the TrueSight Server Automation database. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state is from the backups.
2. Ensure that the following components are up and running:
   • All Application Servers
   • PXE Server
   • RSCD agents on Application Servers, PXE servers, and file servers.
   • RSCD agents installed with the –local option on Application Servers, PXE servers, and file servers.

3. Back up the installation directories for all Application Servers and PXE servers. The default installation locations are:

   • Application Server: /opt/bmc/bladelogic/NSH

   • PXE Server: /opt/bmc/bladelogic/NSH

     If you are upgrading the PXE server, follow the upgrade instructions for Windows or UNIX, to prevent loss of configuration settings.
     

   Note that the user who installed the earlier version of the product might have changed the installation directory from the default location, so ensure that you have the right location. If your current installation is already an upgrade from a previous version, the paths might be different, due to differences in these locations in earlier versions of TrueSight Server Automation. If you do not know the installation location for TrueSight Server Automation components view the contents of the /usr/lib/rsc/HOME file (on Linux or UNIX) or the %WINDIR%\rsc\HOME file (on Windows).

4. Back up the TrueSight Server Automation file server storage location. For example, copy the entire contents of the storage location to a directory other than the current storage location.
5. Ensure that there is an agent installed on the Application Server. For agent installation on Linux or UNIX, use the -local option (as discussed in Installing-components-in-non-default-installation-paths-using-the-local-flag). Similarly, if an RSCD agent and NSH are not already installed on the PXE server, install them now.

6. If you are not running the UPI/Application Server installer directly from a graphical desktop on the Application Server host, you must forward the X Window GUI to another system w/ an X Server or use silent mode to install the Application Server (Windows).  

   The most common method to set up forwarding in a secured environment is to tunnel the X Window connection over an SSH connect between the X Server (your system) and the X Client (the Application Server in this case). Review your SSH client’s documentation for specific instructions, but generally:

   1. Set up the SSH client to forward the remote display across the SSH connection.
   2. When you log on to the remote system, set the DISPLAY environment variable to ‘localhost:11.0’ (for example).
   3. Your system must run an X Server. For Windows, you can use MobaXterm (which is also an SSH client), Xming, Xmanager, Exceed, and so on. Linux supports X Server natively.
7. Ensure that the following 32-bit and 64-bit required package is installed:
   • For RHEL 7: libncurses 
   • For versions earlier than RHEL 7: libtermcap
8. Ensure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.

9. Ensure that you have disabled the NSH proxy on all Application Servers in the environment to avoid failure during upgrade. To disable the NSH proxy, run the following command on the NSH client:
   secadmin -m default -p 5 -T encryption_only -e tls -appserver_protocol clear
   This command temporarily removes the appserver_protocol=ssoproxy entry from the default line in the secure file (in the rsc folder).

   Note: After the upgrade completes, remember to add this entry back into the secure file. You can use the following command:
   secadmin -m default -p 5 -appserver_protocol ssoproxy 

10. To preserve the Live Reporting dashboard environment, back up the cacerts file (for example, /opt/bmc/bladelogic/appserver/NSH/br/java/lib/security/cacerts for Linux) to a separate safe location on the TrueSight Server Automation server. You must do this because the TrueSight Server Automation upgrade overwrites the existing cacerts.
11. If you have already enabled file server access restrictions when configuring the file server agent ACLs, then perform the following steps:

1. 
   
   1. Add the following entry to the exports file on the file server, before you upgrade TrueSight Server Automation using the Unified Product Installer (UPI):
      *   rw,user=root
   2. Remove the entry added in step a from the exports file on the file server, after the UPI upgrade process is complete. This is necessary for the file server access restrictions to work properly.

Related topics: (See these topics for additional upgrade considerations and supported upgrade paths)

Preparing-for-a-Linux-or-UNIX-upgrade-using-the-unified-product-installer

Minimum-software-requirements, especially Requirements for 32-bit and 64-bit libraries when installing on Red Hat Linux using UPI

Step 3: Download the files

Download and extract the installation files to a temporary location.

1. Download the TSSA<version>-LIN64.zip file (which contains the unified product installation program files) and the TSSA<version>-RSCDAgent.zip file (which contains the RSCD Agents for all supported platforms) to the host computer of the Application Server that was set up as a configuration server.
2. Extract the zip files. For example:
   unzip TSSA<version>-RSCDAgents.zip -d /tmp/TSSA<version>-RSCDAgents
   unzip TSSA<version>-LIN64.zip -d /tmp/TSSA<version>-LIN64 
3. Copy the rscd folder from inside /tmp/TSSA<version>-RSCDAgents to <temporary_location>/Disk1/files/installer/ before running the unified product installer. The unified product installer uses the RSCD installers while installing or upgrading TrueSight Server Automation in your environment.

Step 4: Run the unified product installer on the Application Server

Run the unified product installer on the Application Server. The unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server and TFTP server, and console in your environment, with certain exceptions. Before running the upgrade, back up your database and inform your users that TrueSight Server Automation will be unavailable during the upgrade.

1. Make sure that the RSCD Agent, Application Server, and PXE Server are running. 
2. Navigate to the temporary directory that contains the installation files. On a Linux machine, you must assign an executable permission to the installer file (setup.bin) by entering the following command:
   chmod +x -R <temporary directory>
3. Do one of the following:
   
   • Run the following command:
     setup.bin

   • (Optional) Provide the parameters with the command to upgrade all or any of the following artifacts: ZipKits, blconnect, compliance content, and quick start page
     The following table describes these parameters:

     Parameter name	Description
     -J IMPORT_ZIPKITS	ZipKit packages are used for operating systems and common enterprise applications and databases.
     -J IMPORT_BLCONTENT	The blconnect script is used to create groups, folders, and smart groups that are commonly used by organizations.
     -J CREATE_CONTAINER_COMPLIANCE_ARTIFACTS	SCAP container compliance jobs are created.
     -J ENABLE_QUICK_START_PAGE	The Quick Start page supports the common use cases of TrueSight Server Automation.

     Example: To upgrade all these artifacts, add these parameters with the command as follows:

     setup.bin -J IMPORT_ZIPKITS=true -J CREATE_CONTAINER_COMPLIANCE_ARTIFACTS =true -J ENABLE_QUICK_START_PAGE=true

     If you do not provide any of these parameters, these artifacts are not upgraded.

4. Select the language in which you want to run the installer and click OK. 
   Note: If problems arise during the upgrade, the on-screen error messages contain instructions and guidance to help you troubleshoot the problems, and further information is available in the log files.
5. Read through the basic information about the unified product installer and the types of nodes that are installed in the environment.
   
6. Click Next.
7. Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement, and then click Next. 
    
8. Read the copyright statement and select I agree to the terms of the license agreement, and then click Next. 
    
   
   
9. Enter your Authentication profile credentials to proceed with the upgrade procedure. The profile that you specify must be associated with the same Application Server where you are performing the upgrade. Note that only secure remote password (SRP), LDAP, or Domain Authentication type profiles can be used with the unified product installer. 
   
10. Click Next.

11. Review the TrueSight Server Automation infrastructure discovered in your environment. This includes the different types of servers that are present in the TrueSight Server Automation environment, their count, and their status.
    If the Application server and the PXE server share the same target server, the installer upgrades the PXE server automatically. 
    
    Review the TrueSight Server Automation infrastructure discovered in your environment. This includes the different types of servers that are present in the TrueSight Server Automation environment, their count, and their status.
    If your environment includes PXE servers, the installer upgrades the PXE server automatically, if it is up and running during the infrastructure discovery phase.
    If you are running one or more remote PXE servers (that is, on a different subnet than the Application Server), the installer detects and lists them as part of your infrastructure. The unified product installer upgrades the remote PXE servers as part of the upgrade process. The checkbox for the Remote Site field controls how the PXE server installer files are copied to the PXE server, as described in the table below.

    PXE upgrade option	Explanation
    Remote Site field selected (default)	Selecting the checkbox assumes that you have previously manually copied the PXE installer binary (../installers/appserver_64/TSSA<version>-LIN64.sh) to the PXE server prior to upgrading (for example, to the /tmp directory). The unified product installer validates the existence of the PXE installer binary under the expected location, and upgrades the PXE server during the upgrade process. For performance reasons, this option is strongly recommended for PXE servers that are on a different LAN/WAN than the Application Server.
    Remote Site field cleared (not selected)	Clearing the checkbox assumes that you want the installer to copy the ../installers/appserver_64/TSSA<version>-LIN64.sh script to the remote host, typically to the /tmp folder. De-select the Remote Site option if the PXE server is on the same LAN/WAN as the Application Server. However, note that clearing the checkbox is typically much slower if thePXE server is on a different LAN/WAN than the Application Server.

12. Click Next.
13. Preview the upgrade.
    
14. Select the I acknowledge that the installer will bring down the TrueSight Server Automation (TSA) environment for upgrade check box.
15. Click Install, and then Next to continue with the upgrade. 
16. (optional) When the upgrade is finished, click View Log and review the upgrade description. 
     
17. Click Done to exit the installer. 
     

Step 5: Uninstall the old console on the Application Server system

You cannot use a version of the TSSA Console that is incompatible with the connecting Application Server, as shown in the following screenshot. Therefore, uninstall the existing version of the TSSA Console before you upgrade the Application Server and the other components unless you absolutely need to create a ready-to-use test environment.

Before you uninstall the existing version of the console, note the following:

• You must have an X Window server installed and configured to uninstall using the User Interface. The X Window server is not required if you uninstall using silent mode. For more information on performing a silent install, see Using-silent-mode-to-uninstall-product-components.
• You must stop the RSCD agent. See Starting and stopping the RSCD agent.

To uninstall the console:

1. Log on as root.
2. Navigate to the directory in which TrueSight Server Automation components are installed. By default, this directory is /opt/bmc/bladelogic or /opt/bmc/bladelogic/appserver.
3. Navigate to the UninstallBMCClientInstaller subdirectory.
4. Invoke the installation script by entering the following command:
   ./uninstall.bin
   An X Window opens. The installation program displays a series of messages.
5. Select the language in which you want to run the installer and click OK.  
6. When the Welcome window opens, click Next.
   
   A window displays the components that you can uninstall.
7. Select the components, and then click Next.
   
   A window displays the components to be uninstalled.
8. Click Uninstall.
   
   A window displays the successful completion of uninstallation.
9. (optional) To view the uninstallation log, click View Log.
    
10. Click Done.
    Uninstallation is complete.

    NoteThe uninstallation process does not delete some log files that TrueSight Server Automation creates. If you plan to reinstall a later version of TrueSight Server Automation in the same location, be sure to completely remove all leftover files to avoid conflicts. The easiest way to do this is to delete all files in the installation directory (for example, <installDir>/CM/).

Step 6: Install the new console on a separate system

Because the unified product installer does not upgrade the console, you must manually upgrade the console to match the Application Server version so that the console functions correctly. 

Note the following, before you install:

• To install the TrueSight Server Automation Console, you can use the installation wizard in the user interface or silent mode. You cannot use console mode. To use the installation wizard, follow the steps below. To use silent mode, see Using-silent-mode-to-install-the-TrueSight-Server-Automation-Console-Linux-and-UNIX.
• You must have an X Window server installed and configured.
• You must have write access to the /tmp directory, as well as sufficient disk space. To review the hardware requirements for the console, see Minimum-hardware-requirements.
• Make sure that port 12333 (TCP) is not being used. Installation of the console requires use of this port; if it is already in use, the installation fails.
• Linux platforms on which you plan to install the TrueSight Server Automation Console (RCP client) or Network Shell must have the libtermcap.so.2 shared library installed. Install the shared library before installing these components. For more information, see Requirement for installing the Application Server, TrueSight Server Automation Console, or Network Shell on Linux.
• If the version of the RSCD Agent does not match the version of the console, uninstall the old RSCD Agent and install a new version that matches the console. Stop the RSCD Agent before you try to install the console.
• You must close all the NSH shell windows while installing TrueSight Server Automation Console.

To install the console on a separate system:

1. Navigate to the directory containing installation files and run the installation script for the TrueSight Server Automation Console. (Script names follow the convention: TSSACONSOLE<version>-<platformbit>, for example, TSSACONSOLE89-SP3-LIN64.bin) You must execute the installation from a root shell. Do not execute the installation script from a non-root account.
2. The TrueSight Server Automation Installation window opens.
3. Select a language, and then click OK.
   A series of messages indicate progress. This process might take several minutes. Then the Welcome window opens.
   
4. Click Next.
   The Review License Agreement page opens.
   
5. To accept the license agreement, select I agree to the terms of the license agreement, and then click Next.
   The User Inputs window opens.
   
6. (optional) Remove the check marks from any components that you do not want to install, and then click Next.
   A series of messages indicate progress.
   
7. (optional) Select Check to install the default .nsh resource files into /etc/skel.
   
8. Click Next.
   The Installing window previews the features to be installed.
   
9. To install, click Install. To change your selections, click Previous.
   A series of messages indicate progress. This process might take several minutes. Then the Installation Summary window opens, indicating successful installation.
   
10. (optional) Click View Log.
11. Click Done.
    The window closes. Installation is complete.
12. Start the RSCD Agent and then start the console (for example, /opt/bmc/BladeLogic/CM/rcp/launcher). To configure the console so that it connects to the default Application Server, click Options.
    
13. Click the Authentication Profiles tab and click Add. TrueSight Server Automation clients use authentication profiles to facilitate single sign-on feature. You must create an Authentication profile before you start using the Console. For more information about why we use Authentication Profiles, see System-capabilities-related-to-security.
    
14. Enter the following information.
    
    
    1. Assign a name to the authentication profile. For example, you could assign a name such as QATeam, DevTeam, or defaultProfile.
    2. Enter the name or IP address (IPv4 or IPv6) of the default Application Server to which the client should connect.
    3. Enter an Authentication Port number to which the client should connect. The same port is used for all TrueSight Server Automation authentication mechanisms. The default Port is 9840. For more information about Console ports, see TrueSight-Server-Automation-ports.

    4. Select any one authentication mechanism for the authentication profile:

       • Secure Remote Password.
       • AD/Kerberos Single Sign-on.
       • Domain Authentication.
       • LDAP.
       • RSA SecurID Authentication.
       • Public Key Infrastructure Authentication.

       In this walkthrough we will use the Secure Remote Password mechanism. For information about implementing the other authentication mechanisms, see Implementing-authentication. 

    5. Click OK.
15. Click Connect to log on the Application Server using the BLAdmin user that is created while installing the default Application Server node.
    
16. If you see a security alert that the certificate is not initially trusted, optionally, you can view the certificate. Or you can simply click Yes to proceed. 
    
17. The quick start page is the first page that is displayed once you log on the the Console. It introduces you to the main use cases of TrueSight Server Automation and allows you to execute them from a centralized UI immediately after installing the TrueSight Server Automation set up. For information about using the quick start page, see Quick-start-page. For general information about the UI of the TrueSight Server Automation Console, see Navigating-the-interface.
    

Step 7: Manually upgrade additional components

After the unified product installer completes the upgrade, manually upgrade any components that meet the following criteria. You can perform this step anytime after the upgrade.

• NSH clients on non-Application Server host computers - Use the instructions in Upgrading the Network Shell.
• PXE and TFTP servers that reside on separate host computers - When you upgrade a PXE server on a different subnet than the target server, you need to copy the installation files to the remote machine and upgrade the remaining servers manually, as described in Upgrading-a-PXE-server-on-Linux-or-UNIX.
  If the TFTP service is not started automatically after the upgrade, manually start it, as described in Starting-and-stopping-a-TFTP-server.
• Upgrade any agents that you may have that fall into the following categories.
  • Agent on an online or offline patch repository
  • Agent on a basic/standard repeater
  • Agent on a VMware vCenter server. You must upgrade the agent on the vCenter server before you try to use the vCenter integration or the updated VMware configuration object push. For more information, see Setting-up-a-VMware-vSphere-environment and Distributing-configuration-objects.

Related topic:

Upgrading-the-RSCD-agent-on-Linux-and-UNIX

Step 8: Perform additional post-upgrade tasks

At any time after the upgrade, complete the following tasks, if they apply to your environment:

Run the Update Model Objects Job

For custom configuration objects to work reliably, the version of the custom object should match the version of the agent. You can perform this step anytime after the upgrade.

1. Run an Update Server Properties Job on the agents you have upgraded. For more information, see Creating Update Server Properties Jobs.
2. If you are not upgrading all of your agents at this time, make copies of all component templates, BLPackages, Snapshot Jobs, and Audit Jobs that reference custom configuration objects that have dependencies on agents running earlier versions. You must maintain a version match between component templates, BLPackages, Snapshot Jobs, and Audit Jobs and custom configuration objects and agents. The objects that you copy in this step are the objects that you can use to maintain the version match.
3. If you upgrade to the latest version of TrueSight Server Automation and you are using TrueSight Server Automation for virtual environments, you must immediately update the RSCD agent on the system used for the integration and add the new configuration object version for the integration. For example, for the vCenter server, you must upgrade the RSCD agent on either the Windows vCenter server or the AMO proxy and add the new VMware configuration object to the vCenter server object in TrueSight Server Automation.
4. To ensure that all configuration-object-based assets within existing content are upgraded, run an Upgrade Model Objects Job that targets any component templates, BLPackages, Snapshot Jobs, or Audit jobs that you want to upgrade. For more information about the Upgrade Model Objects Job, see Creating-or-modifying-Upgrade-Model-Objects-Jobs.
   Note: Do not run the Upgrade Model Objects Job against the copies of objects that you created in step 3.
   If you open an existing component template, BLPackage, Snapshot Job, or Audit Job that references a custom configuration object and a later version of that custom configuration object exists, the system displays a message saying it will automatically upgrade the referenced custom configuration object. To maintain a version match with an earlier agent, close the component template, BLPackage, Snapshot Job, or Audit Job without saving.
5. After executing the Upgrade Model Objects Job, display the results of the job run to see which assets were successfully upgraded and which were not. If you find that certain assets were not automatically upgraded, you must upgrade them manually. Perform the following steps:
   1. Open the object (template, package, or job).
   2. Manually remove the asset of the earlier version and add the asset of the latest version.
   3. Save the object.

Related topics:

Upgrading-custom-configuration-objects

Creating-or-modifying-Upgrade-Model-Objects-Jobs

Upgrade Compliance Content add-ons

Perform an over-the-top upgrade of the new Compliance Content add-ons. You can perform this step anytime after the upgrade.

Related topic: Installing-and-configuring-Compliance-Content-add-ons

Update the sunpkcs11.cfg file for PKI authentication

If you are using PKI authentication, Starting from version 21.3, TrueSight Server Automation no longer support 32-bit DLLs when using ActivClient or 90meter for PKI authentication. Therefore, after you upgrade the TrueSight Server Automation console to 21.3 or later, update the sunpkcs11.cfg file to the store the path to the 64-bit DLLs. For instructions, see Implementing-PKI-authentication.

Related topics

Walkthrough-Upgrading-using-the-configurator-and-individual-component-installers

Walkthrough: Upgrading to the latest version on Microsoft Windows