This topic describes how to use the unified product installer to interactively upgrade TrueSight Server Automation on 64-bit Linux platforms. It includes the following sections:
List of components that are upgraded by the unified product installer
The unified product installer upgrades the following product components that were installed as part of the previous 8.3.x, 8.5.x, or 8.6.x installation (click to expand):
| |
|---|
| The unified product installer upgrades the TrueSight Server Automation schema (not the database software) on the following supported platforms for Linux: - Oracle Express Edition
- Oracle Enterprise Edition
- Oracle Standard Edition
If you are running a "mixed" environment (for example, you installed Linux Application Server + Microsoft SQL Server database via their individual components), you can use the unified product installer to upgrade the environment. The UPI is agnostic about the database during the upgrade. |
| If the file server is separate from the Application Server, then it is upgraded only if it resides on a 64-bit platform. |
Components on the computer that hosts the Application Server: |
Application Server (including its profiles — such as configuration server, job server, or NSH proxy server) | Do not shut down Application Servers when upgrading using the unified product installer. Shutting down the Application Servers during the upgrade can cause the upgrade to fail. Configuration changes will not be applied on Application Server machines that are down during the upgrade. |
| Based on whether the host computer on which you are installing Network Shell has a supported version of Perl installed, either of the following is performed: - A supported version of Perl installed — The Network Shell installation automatically installs the Network Shell Perl module. For information about the Perl versions that TrueSight Server Automation supports, see Perl support.
- An unsupported version of Perl installed — The installer copies files that allow you to install the Perl module after you have installed the supported version of Perl.
|
| TrueSight Server Automation requires an RSCD Agent installed on each Application Server. Therefore, during the upgrade, the unified product installer automatically installs RSCD Agents on the Application Servers, if they are not already present on them. The unified product installer installs the RSCD Agent at the following location on the Application Server: Note that if an RSCD agent is already present on the Application Server, the unified product installer upgrades the RSCD agent automatically. |
PXE server and TFTP server | Only those PXE Servers that have a status of up and running in the Infrastructure Management Window are upgraded. You need to upgrade the remaining servers manually (as described in Upgrading-a-PXE-server-on-Linux-or-UNIX). |
List of components that are not upgraded by the unified product installer
The unified product installer does NOT upgrade the following components (click to expand):
| |
|---|
TrueSight Server Automation Console | After completing the upgrade using the unified product installer, you can attend to the upgrade of the console. Manually upgrade the Console by running its individual component installer, see Upgrading-the-TrueSight-Server-Automation-Console-on-Windows. You can choose not to upgrade certain consoles. Specifically, version 8.9 of the TrueSight Server Automation Application Server supports communication with TrueSight Server Automation Consoles of version 8.8. To enable this backward support for any specific Application Server, you must use the blasadmin command versioncompabilitycheck to turn off the version compatibility check that occurs whenever you access a Console. For more information, see To enable communication with clients of an earlier version of TrueSight Server Automation. |
RSCD Agents in certain scenarios | RSCD Agents in the following scenarios are not upgraded: - RSCD Agents not on target (managed) servers
- RSCD Agents on a separate file server running on Linux, with an Application Server running on Windows (applies only to version 8.6; this limitation was fixed in 8.6 SP1)
- RSCD Agent on an online or offline patch repository
- RSCD Agent on a basic/standard repeater
- RSCD Agent on an advanced file server
- RSCD Agent on a VMware vCenter server
|
Multiple RSCD agents running on a single host computer | Depending on which version of TrueSight Server Automation you are on, the unified product installer may or may not upgrade multiple RSCD agents that are installed on single machine. In TrueSight Server Automation 8.6 SP1 and later versions. The local RSCD agents (installed using the -local option) are automatically upgraded by the unified product installer. Note that the local RSCD agents must be running when the unified product installer is executed, so that it can detect and upgrade the local RSCD agents. |
NSH clients on non-Application Server host computers | |
Custom configuration objects | |
| |
A dual database used for provisioning | |
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. |
TrueSight Smart Reporting for Server Automation | For upgrade instructions, see the TrueSight Smart Reporting for Server Automation online documentation. |
| |
Before you begin
Ensure that your environment meets the requirements discussed in Preparing-for-a-Linux-or-UNIX-upgrade-using-the-unified-product-installer.
Note
The task of running SQL Update scripts, which was necessary in the past for any upgrade to a TrueSight Server Automation patch or service pack, is no longer required during an upgrade. The database upgrade is now handled internally by the unified product installer, which was introduced in version 8.6.
To upgrade TrueSight Server Automation using the unified product installer
Warning
Ensure that you use a fresh copy of the installation folder (and its contents), for each environment that the unified product installer is run in. The unified product installer saves environment-related information in the installation folder (Disk1), which will cause errors if the same copy is used for upgrading different environments.
Download and extract the installation package appropriate for the operating system level and hardware platform in a <temporary location>. The package follows the naming convention BSA<version>-<platform>.zip, and contains the unified product installation program files.
Download this package to the host computer of the Application Server that was set up as a configuration server (for more about this type of Application Server setup, see Application Server types). If this is a Linux computer, ensure that it has an RSCD agent installed and running.
Note
Ensure that the temporary location where you extract the installation package does not contain the string nsh in its path.
- Extract the BSA<version>RSCDAgents.zip file and copy the rscd folder to the following location before running the unified product installer (The unified product installer uses the RSCD installers while installing or upgrading TrueSight Server Automation in your environment):<temporary location>/Disk1/files/installers
If you are on a Linux machine, assign executable permission to the temporary directory by entering the following command:
chmod +x -R <temporary directory>
In addition, if the temporary directory is at the end of a path (that is, has at least one parent directory), assign read permission to the others class (which includes the bladmin system user) for all directories in the path. To do this, execute the following command on the top-level directory in the path:
chmod o+r -R <top-level directory>
Run the installation file for TrueSight Server Automation (setup.bin).
Note
For Linux, BMC recommends that you execute the installation from a root shell. Do not execute the installation file from a non-root account.
- Follow the instructions in the installation wizard and 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. For more information, on Authentication profile credentials, see Setting-up-an-authentication-profile and Implementing-authentication.
- The unified product installer program displays the different types of servers that are present in the TrueSight Server Automation environment and their count.
If the unified product installer was successful in connecting with all servers, you can proceed with the installation. Skip to step 8.
Otherwise, click Next to continue to step 7.
- If any of the remote servers do not have an RSCD Agent installed, the wizard displays a list of those servers. You can choose from the following options:
- Manually install an RSCD Agent on each of the listed remote servers, and then resume the installation through the unified product installer.
Authorize the unified product installer to install an RSCD Agent on each of the listed remote servers by providing the following information:
- The name of a local super user (root or root-equivalent user on Linux) to which the RSCD Agent should map incoming connections during the installation.
The default is root.
Note: The installer does not validate the specified user to ensure that it is present and has administrator privileges on each of the target machines. - Host name or IP address of the PSExec host computer.
- User credentials (user name and password) for establishing an SSH connection to the remote hosts.
If user credentials are the same on all remote servers, select the Use Common Credentials check box, and enter credentials in the fields below the check box. Otherwise, clear the check box and enter credentials for each of the servers directly into the table that lists the servers.
After entering the required information, click Next.
Click Install to proceed with the upgrade of all TrueSight Server Automation components that are present in your environment.
Notes
If product components are detected during the upgrade on remote Windows machines in the TrueSight Server Automation environment, installers are automatically copied to the C:\BSAInstallerDumpDir directory on the remote machines. These installers are used to automatically upgrade product components on those machines.
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.
After performing the recommended troubleshooting steps, you can return to the installer and safely resume the upgrade from the point where you left off. You might do this in one of the following ways:
- If the installation wizard is still open, click the Previous button. This takes you to a new Summary window, which now lists only those components and servers that have not yet been successfully upgraded. Click Accept to re-attempt the upgrade of those components.
- If you were forced to close the installation wizard (typically the case for longer troubleshooting procedures), you can re-launch the installer. After several initial windows, an updated Summary window lists only those components and servers that have not yet been successfully upgraded. Click Accept to re-attempt the upgrade of those components.
During the upgrade, the original Application Server deployments are backed up. The backup files are stored in <installation directory>/br.
Where to go from here
- The unified product installer automatically installs agent installer jobs and depot objects such as agent installers and agent bundles that can be used for installing or upgrading agents on servers in the environment. The agent installers, agent bundles, and agent installer jobs are present in the following locations:
Object | Depot Path | Can be used for |
|---|
Installers | /Depot/BMC Maintenance/Agent Installers/ | Agent install and upgrade |
Bundles | /Depot/BMC Maintenance/Agent Bundles/ | Agent upgrade |
Jobs | /BMC Maintenance/Agent Installer Jobs/ | Agent upgrade |
For more information about using these objects, see Installing one or more agents using the TrueSight Server Automation Console and Upgrading-the-RSCD-Agent-using-an-Agent-Installer-Job.WarningModifying the name or path of these depot objects may cause errors in the agent installation process.
- Upgrade any remaining product components that were not upgraded by the unified product installer.
- If you adjusted security settings before the upgrade, remember to re-adjust your security settings, based on your unique needs and the IT security policies at your organization.
Starting from version 22.2, Server Automation by default restricts access to the Application Server file system by using a low privilege user named bluser for executing external commands. After you upgrade to 22.2, you can allow unrestricted access by updating the BLASAdmin parameter, EnableLowPrivUser in the Appserver module. For more information, see Restricting-access-to-the-Application-Server-file-system.
Important (Windows)
Before you run the NSH Script Jobs, Compliance Jobs or External Commands, ensure the following:
- The bluser user has Deny log on locally and Log on as a batch job User Rights, and no other rights.
- If the Deny log on locally and Log on as a batch job User Rights are managed via a GPO, then ensure to update the GPO so that bluser user has these rights in the GPO.
- Ensure that any groups bluser user belongs to, does not have the Deny log on as a batch job right.
When you upgrade to version 23.1, by default, the existing bladelogic.keystore file is not updated with the new cipher suits. If you want to use the new ciphers (which offer stronger security) for the webservices communication, you need to recreate this file and update it manually after upgrade for any customizations done before upgrade.
To use the latest ciphers, perform the following steps:
- Back up the existing bladelogic.keystore file, located in the <installDirectory>/NSH/br/deployments directory.
- Recreate the bladelogic.keystore file using the blmkcert utility, located in the <installDirectory>/NSH/bin/blmkcert directory. For more information, see To generate the keystore using blmkcert.
- Import your other certificates (for example, certificates for integrations with TSAC, TSO, etc.) from the backed up file into the bladelogic.keystore file.
- .Copy the bladelogic.keystore file in the <installDirectory>/NSH/br/deployments directory on all the Application Servers in a Multiple Application Server (MAS) environment.
- For Windows patching, you may still be using the PD5.cab, or HF7b.cab ( PD5.xml, or HF7b.xml) configuration files for Windows patching. However, TrueSight Server Automation 8.9.03 and later versions do not support the PD5, or HF7b configuration files, and you must use the WindowsPatchData.zip file instead. The Windows catalog update job fails if you use the .cab or .xml configuration files. To update the configuration files used for Windows patching see, Global configuration parameters.
- On SuSE 11, the Application Server does not start automatically at the end of the upgrade. You must start the Application Server manually at the end of the upgrade using the following command:
/etc/init.d/blappserv start. - To fully support TLS version 1.2 as the default communication protocol used by the RSCD Agent in TrueSight Server Automation 8.9.01 or later, ensure that also the Network Shell component is upgraded to version 8.9.01 or later on any computer that hosts the TrueSight Server Automation Console. The Network Shell is normally upgraded together with the TrueSight Server Automation Console.
- Starting from version 21.3, TrueSight Server Automation no longer supports 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 store the path to the 64-bit DLLs. For instructions, see Implementing-PKI-authentication.
- If TrueSight Server Automation is integrated with TrueSight Orchestration, enable the HTTPS support for TrueSight Orchestration on TrueSight Server Automation again.