Walkthrough: Upgrading to the latest version for Linux
The topic includes the following sections:
- Upgrading using the unified product installer
- Step 1: Review requirements and limitations
- Step 2: Prepare the environment for upgrade
- Step 3: Download the files
- Step 4: Run the unified product installer on the Application Server
- Step 5: Manually upgrade additional components
- Step 6: Perform additional post-upgrade tasks
- Related topics
The video at right provides helpful tips on how to upgrade your Application Server running on Linux.
The [embed] macro is a standalone macro and it cannot be used inline. Click on this message for details.
https://youtu.be/6oce5bNZHZY
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
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.
- 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.
- 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 - 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.
- Make sure that the RSCD Agent, Application Server, and PXE Server are running.
- 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> - 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 .
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
- Run the following command:
- 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. - Read through the basic information about the unified product installer and the types of nodes that are installed in the environment.
- Click Next.
- Read the End User License Agreement (EULA) and select I agree to the terms of the license agreement, and then click Next.
- Read the copyright statement and select I agree to the terms of the license agreement, and then click Next.
- 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.
- Click Next.
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.
- Click Next.
- Preview the upgrade.
- Select the I acknowledge that the installer will bring down the TrueSight Server Automation (TSA) environment for upgrade check box.
- Click Install, and then Next to continue with the upgrade.
- (optional) When the upgrade is finished, click View Log and review the upgrade description.
- Click Done to exit the installer.
Step 5: 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 6: Perform additional post-upgrade tasks
At any time after the upgrade, complete the following tasks, if they apply to your environment:
Task | Steps |
---|---|
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. Related topics: |
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 | Starting from version 21.3, if you are using PKI authentication, no longer support 32-bit DLLs when using ActivClient or 90meter for PKI authentication. Therefore, after you upgrade the 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. |
Improve security for RMI interfaces by using SSL to encrypt connections to the Application Server and PXE server | Set the value of UseSSLSockets and RequireClientAuthentication Application Server parameters to true as shown here. Related topic: Managing-the-Application-Server. |
Related topics
Walkthrough-Upgrading-using-the-configurator-and-individual-component-installers
Walkthrough: Upgrading to the latest version on Microsoft Windows