Skip to Content

_prepForUpgrade

Build information for 24.4

Release

Build number

EPD version number

Release date

Version 24.4

24.4.00.??

24.4

December 6, 2024

Build information for 24.2

Release

Build number

EPD version number

Release date

Version 24.2

24.2.00.22

24.2

May 24, 2024

Build information for 23.4

Release

Build number

EPD version number

Release date

Version 23.4

23.4.00.13

23.4

Oct 31, 2023

Build information for 23.2

Release

Build number

EPD version number

Release date

Version 23.2

23.2.00.25

23.2

May 5, 2023

Build information for 23.1

Release

Build number

EPD version number

Release date

Version 23.1

23.1.00.10

23.1

January 30, 2023

Build information for 22.2

Release

Build number

EPD version number

Release date

Version 22.2

22.2.00.26

22.2

June 23, 2022

Build information for 21.3

Release

Build number

EPD version number

Release date

Version 21.3

21.3.00.38

21.3

October 21, 2021

Build information for 21.02

Release

Build number

EPD version number

Release date

Patch 1 for Version 21.02

21.02.01.211

21.02.01

May 27, 2021

Version 21.02

21.02.00.162

21.02

Mar 12, 2021


Build information for 20.02


Release

Build number

EPD version number

Release date

Patch 1 for version 20.02

20.02.01.106

20.02.01

September 15, 2020

Version 20.02

20.02.00.31

20.02

February 21, 2020

Build information for 8.9

The following table lists information for the most recent TrueSight Server Automation version 8.9 builds.


Release

Build number

EPD version number

Release date

Patch 3 for Service Pack 4 for version 8.9

8.9.04.xxx

8.9.04.003

November, 2019

Patch 2 for Service Pack 4 for version 8.9

8.9.04.253

8.9.04.002

September 18, 2019

Patch 1 for Service Pack 4 for version 8.9

8.9.04.227

8.9.04.001

June 21, 2019

Service Pack 4 for version 8.9

8.9.04.200

8.9.04

January 28, 2019

Patch 1 for version 8.9 Service Pack 3

8.9.03.647

8.9.03.001

October 5, 2018

Service Pack 3 for version 8.9

8.9.03.162

8.9.03

June 11, 2018

If your TrueSight Server Automation environment includes TrueSight Smart Reporting for Server Automation, upgrade TrueSight Smart Reporting for Server Automation before upgrading TrueSight Server Automation. For more information, see the online technical documentation for TrueSight Smart Reporting for Server Automation.

Supported upgrade paths

The following diagram shows the supported upgrade paths for TrueSight Server Automation 24.4:

image-2024-6-26_20-29-58.png

The following diagram shows the supported upgrade paths for TrueSight Server Automation 24.2:

image-2023-11-2_13-42-41.png

The following diagram shows the supported upgrade paths for TrueSight Server Automation 23.4:

TSSA_234_UpgradePaths.png

The following diagram shows the supported upgrade paths for TrueSight Server Automation 23.2:

image-2023-4-20_17-38-30.png

The following diagram shows the supported upgrade paths for TrueSight Server Automation 23.1:

TSSA_231_UpgradePAths.png

The following diagram shows the supported upgrade paths for TrueSight Server Automation 22.2:

tssa_222_upgrade_paths.png


The following diagram shows the supported upgrade paths for TrueSight Server Automation 21.3:

tssa_213_upgrade_paths.png


The following diagram shows the supported upgrade paths for TrueSight Server Automation 21.02:

UpgardePaths200203.png


The following diagram shows the supported upgrade paths for TrueSight Server Automation 20.02.01:

tssa_upgrade_path_200201.png


The following diagram shows the supported upgrade paths for TrueSight Server Automation 20.02.01:

tssa_upgrade_path_200201.png


The following diagram shows the supported upgrade paths for TrueSight Server Automation 20.02:

tssa_upgrade_path_2002.png


Upgrade methods

TrueSight Server Automation provides a centralized upgrade UI for upgrading all TrueSight Server Automation components.

BMC recommends using the centralized UI in the unified product installer, but also provides the individual component installers for operating systems that are not supported by the unified product installer. For a centralized upgrade of multiple product components, you can also choose to run the unified product installer in unattended (silent) mode.

UPI upgrade prerequisites for Windows

Note the following information prior to preparing the environment for upgrade:

Category

Requirement

Product integrations

If your TrueSight Server Automation environment includes TrueSight Smart Reporting for Server Automation, upgrade TrueSight Smart Reporting for Server Automation before upgrading TrueSight Server Automation. For more information, see the TrueSight Smart Reporting for Server Automation online technical documentation.

Base requirements

Review the following key requirements.

Click here to review.
  • During an upgrade, the unified product installer automatically installs an RSCD Agent on every Application Server machine that does not already have an agent installed. If you are not interested in having PsExec installed in your environment or if you are not interested in providing details of the required credentials, you can install an RSCD Agent manually on each of the detected machines.
  • If you have external PXE servers in your environment, copy the appserver installation script (for example, ..\installers/appserver_64\BSA<version>-WIN64.sh) to the C:\Windows path on Windows PXE Servers to use the Remote Site default option in Unified product installer before you start the upgrade.

  • Ensure that Microsoft Visual C++ 2015 Redistributable Update 3 is installed on the server. For more information, see Installing an RSCD agent (Windows).
    Note:

    As a prerequisite to install Microsoft Visual C++ 2015 Redistributable Update 3 on Windows 2012 R2, you must have the following patches installed on your server:

    • KB2919442 (Required for 2919355)
    • KB2919355. This patch requires several other patches: clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018. This are all available on the download page for KB2919355.
    For more information about the prerequisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.

  • NSH must be present on each Application Server machine (that is NSH proxy server, Configuration server, Job server, or PXE server).
  • Unified installer should be run only from a node set up as a Configuration server (for more about this type of Application Server setup, see Application Server types).
  • During the upgrade, the installer checks the existing version of Perl. If the host computer on which you are installing the Network Shell has:
    • 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 installation copies files that allow you to install the Perl module after you have installed the supported version of Perl
  • On 64-bit Windows systems, confirm that the %WINDIR%\SysWOW64 directory contains a copy of the chcp.com file. The installer uses this file to set the code page of standard output (stdout). You can obtain the file from a 32-bit version of Windows.

Supported platforms

The unified installer supports Windows 64-bit and Linux 64-bit operating systems. For a complete list of platforms supported by the unified installer, see Supported-platforms.

PXE servers

To improve performance during the upgrade, create a new folder on your remote PXE server (by default, %SystemDrive%/BSAInstallerDumpDir, for example, C:/BSAInstallerDumpDir) and then manually copy the PXE installer binary (..\installers\pxe_64\PXE<version>-WIN32) into the %SystemDrive%/BSAInstallerDumpDir folder prior to upgrading. 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.


Install mode

If you are using Microsoft Windows 2003 or 2008, you must upgrade in Install mode instead of Execute mode, see Using-Install-mode-instead-of-Execute-mode.

Configuration objects

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent.

The product installation is automatically upgraded to the appropriate version when you upgrade the agent. However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. Configure this job to target servers to which custom configuration objects need to be distributed. For a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom-configuration-objects.

To upgrade custom configuration objects

Click here to see the steps for upgrading custom configuration objects.
  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.

To upgrade virtualization configuration objects

Click here to see the steps for upgrading virtualization configuration objects.

The Upgrade Model Object Job is not supported for upgrading virtualization configuration objects.

To upgrade configuration objects that you distributed in prior versions, complete the following steps:

  1. Import the new version of the virtualization configuration object (for example, the VMware vCenter configuration object).
  2. Restart the RSCD agent on which the configuration object is distributed. This step is a prerequisite for successful upgrade of the configuration object on the target server.
  3. Run the Distribute Configuration Objects Job to distribute the configuration objects to the target agent (see Distributing-configuration-objects).
  4. To identify the configuration objects that failed, run the Upgrade Model Objects Job on all jobs, templates, and BLPackages that reference the configuration object.
  5. After the Upgrade Model Objects Job completes, open the objects for which the job failed.
  6. Remove the parts that are marked as failed and add new ones from the upgraded configuration object.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent.  The  installation are automatically upgraded to the appropriate version when you upgrade the agent. (See Custom-configuration-objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. The job should target servers to which custom configuration objects should be distributed.

Potential issues

Click here to review a list of potential issues you can encounter during an upgrade.
  • Upgrade to version 8.6 or later does not grant the DBMS_LOCK privilege to user - Before you start upgrading from a previous version to TrueSight Server Automation 8.6, ensure that the TrueSight Server Automation user is granted the DBMS_LOCK privilege. This privilege is required for carrying out a handshake between TrueSight Server Automation database and the TrueSight Smart Reporting for Server Automation ETL during database clean up. You can use the SYS user to grant the DBMS_LOCK privilege by entering the following command: GRANT EXECUTE on DBMS_LOCK TO <User>
  • Upgrade to version 8.6 or later disables PropertySync - As of TrueSight Server Automation version 8.5, the PropertySync feature has been deprecated. During migration of the database, PropertySync is disabled and the migration results table displays the migration warning: PropertySync has been changed from true to false. Contact BMC Support for further assistance.
  • Upgrade to version 8.5 or later deprecates the Provision provisionDevice BLCLI command. Earlier releases supported the Provision:provisionDevice command. This command has been deprecated. BMC recommends that you use the ProvisionJob:createProvisionJob command instead.
  • Upgrade to version 8.6 or later causes Citrix XenServer Provision Jobs to fail - After an upgrade from TrueSight Server Automation version 8.3 or earlier to TrueSight Server Automation version 8.5 or later, existing Citrix XenServer Provision Jobs fail (QM001706976). Failed jobs display the error message: com.bladelogic.om.infra.mfw .util.BlException: Proxy cannot be null, Error: Proxy cannot be null. To work around the issue, open the Provision Job in the content editor. On the Server Settings panel, browse the Server Properties option to select or create a valid agentless managed object (AMO).
  • Audit performed with snapshots captured using earlier versions of the RSCD agent can fail - When capturing data from target servers, version 8.6.00 of TrueSight Server Automation skips IPv6 addresses and masks. After an upgrade to version 8.6.00 or later from version 8.3 or earlier, an audit performed with snapshots captured using older versions of an RSCD agent can fail if the targets had IPv6 enabled.
  • In a multiple application server (MAS) environment, if the RSCD Agent is not present on the secondary node and the primary node is using PsExec version 2.43, upgrade to version 21.3 or later on the secondary node fails. To fix the issue, perform one of the following tasks:
    • Install RSCD Agent on the secondary node and start the upgrade process again on the secondary node.
    • Use PsExec version 2.2 instead of version 2.43 on the primary node, and start the upgrade process again on the secondary node.

Certificate issue

If your id.pem certificate was created with a key size of 1024 bits (or less), you will need to regenerate it with a higher key size (2048 or higher). This is due to a change in the FIPS requirement for minimum key length (now 2048 bits).


UPI upgrade pre-reqs for Linux

Note the following information prior to preparing the environment for upgrade:

Category

Requirement

Product integrations

If your TrueSight Server Automation environment includes TrueSight Smart Reporting for Server Automation, upgrade TrueSight Smart Reporting for Server Automation before upgrading TrueSight Server Automation. For more information, see the TrueSight Smart Reporting for Server Automation online technical documentation.


Base requirements

Review the following key requirements.

Click here to review.
  • During an upgrade, the unified product installer automatically installs an RSCD Agent on every Application Server machine that does not already have an agent installed. If you are not interested in providing details of the required credentials, you can install an RSCD Agent manually on each of the detected machines.
  • If you have external PXE servers in your environment, copy the appserver installation script (for example, ../installers/appserver_64/BSA<version>-LIN64.sh) to the /tmp path on Linux PXE Servers to use the Remote Site default option in unified product installer before you start the upgrade.
  • NSH must be present on each Application Server machine (that is NSH proxy server, Configuration server, Job server, or PXE server).
  • Run the Unified installer only from an Application Server system that is set up as a Configuration server (for more about this type of Application Server setup, see Application Server types).
  • Run the installer from a computer where a Windows X server is installed.
  • If the host computer on which you are installing the Network Shell has:
    • 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 installation copies files that allow you to install the Perl module after you have installed the supported version of Perl
  • Ensure that the Bash shell is the default shell on all machines where TrueSight Server Automation is being upgraded.

  • Ensure that the bladmin user belongs to the bladmin primary group before upgrading the Application Server. To check if the primary group is bladmin, run the following command:
    id bladminSample output:
    uid=54322(bladmin) gid=54331(bladmin) groups=54331(bladmin)
    (the ids may vary on your system)

    If that is not the primary group id, then modify the user account. Use the following sample code:
    Usermod -g bladmin bladmin


Supported platforms

The unified installer supports Windows 64-bit and Linux 64-bit operating systems. For a complete list of platforms supported by the unified installer, see Supported-platforms.

PXE server upgrades

To improve performance for the upgrade of remote PXE servers, manually copy 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.

Windows X server requirement

You must run the installer from a computer where a Windows X server is installed. Follow these steps before you install the product from a computer with X server software:

  1. Start the X server software.
  2. Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.
  3. Connect to the remote system where you want to install the product and start a terminal session on that system, for example, an X terminal (xterm).

Configuration objects

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent.

The product installation is automatically upgraded to the appropriate version when you upgrade the agent. However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. Configure this job to target servers to which custom configuration objects need to be distributed. For a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom-configuration-objects.

To upgrade custom configuration objects

Click here to see the steps for upgrading custom configuration objects.
  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.

To upgrade virtualization configuration objects

Click here to see the steps for upgrading virtualization configuration objects.

The Upgrade Model Object Job is not supported for upgrading virtualization configuration objects.

To upgrade configuration objects that you distributed in prior versions, complete the following steps:

  1. Import the new version of the virtualization configuration object (for example, the VMware vCenter configuration object).
  2. Restart the RSCD agent on which the configuration object is distributed. This step is a prerequisite for successful upgrade of the configuration object on the target server.
  3. Run the Distribute Configuration Objects Job to distribute the configuration objects to the target agent (see Distributing-configuration-objects).
  4. To identify the configuration objects that failed, run the Upgrade Model Objects Job on all jobs, templates, and BLPackages that reference the configuration object.
  5. After the Upgrade Model Objects Job completes, open the objects for which the job failed.
  6. Remove the parts that are marked as failed and add new ones from the upgraded configuration object.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent.  The  installation are automatically upgraded to the appropriate version when you upgrade the agent. (See Custom-configuration-objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. The job should target servers to which custom configuration objects should be distributed.

Potential issues

Click here to review a list of potential issues you can encounter during an upgrade.
  • Upgrade to version 8.6 or later does not grant the DBMS_LOCK privilege to user - Before you start upgrading from a previous version to TrueSight Server Automation 8.6, ensure that the TrueSight Server Automation user is granted the DBMS_LOCK privilege. This privilege is required for carrying out a handshake between TrueSight Server Automation database and the TrueSight Smart Reporting for Server Automation ETL during database clean up. You can use the SYS user to grant the DBMS_LOCK privilege by entering the following command: GRANT EXECUTE on DBMS_LOCK TO <User>
  • Upgrade to version 8.6 or later disables PropertySync - As of TrueSight Server Automation version 8.5, the PropertySync feature has been deprecated. During migration of the database, PropertySync is disabled and the migration results table displays the migration warning: PropertySync has been changed from true to false. Contact BMC Support for further assistance.
  • Upgrade to version 8.5 or later deprecates the Provision provisionDevice BLCLI command. Earlier releases supported the Provision:provisionDevice command. This command has been deprecated. BMC recommends that you use the ProvisionJob:createProvisionJob command instead.
  • Upgrade to version 8.6 or later causes Citrix XenServer Provision Jobs to fail - After an upgrade from TrueSight Server Automation version 8.3 or earlier to TrueSight Server Automation version 8.5 or later, existing Citrix XenServer Provision Jobs fail (QM001706976). Failed jobs display the error message: com.bladelogic.om.infra.mfw .util.BlException: Proxy cannot be null, Error: Proxy cannot be null. To work around the issue, open the Provision Job in the content editor. On the Server Settings panel, browse the Server Properties option to select or create a valid agentless managed object (AMO).
  • Audit performed with snapshots captured using earlier versions of the RSCD agent can fail - When capturing data from target servers, version 8.6.00 of TrueSight Server Automation skips IPv6 addresses and masks. After an upgrade to version 8.6.00 or later from version 8.3 or earlier, an audit performed with snapshots captured using older versions of an RSCD agent can fail if the targets had IPv6 enabled.
  • In a multiple application server (MAS) environment, if the RSCD Agent is not present on the secondary node and the primary node is using PsExec version 2.43, upgrade to version 21.3 or later on the secondary node fails. To fix the issue, perform one of the following tasks:
    • Install RSCD Agent on the secondary node and start the upgrade process again on the secondary node.
    • Use PsExec version 2.2 instead of version 2.43 on the primary node, and start the upgrade process again on the secondary node.

Certificate issue

If your id.pem certificate was created with a key size of 1024 bits (or less), you will need to regenerate it with a higher key size (2048 or higher). This is due to a change in the FIPS requirement for minimum key length (now 2048 bits).


Security requirements for Linux

The unified product installer must be run by a super user, that is, root or a root-equivalent user. This enables the installer to install components on remote Application Servers using existing RSCD Agents and SSH.

If you have a high security level enabled in your TrueSight Server Automation installation, the unified installer cannot upgrade the product through the RSCD Agent on the remote host computers. Before upgrading, you must temporarily adjust the security level on the machines where you want to upgrade the Application Servers. At the beginning of the upgrade process, the unified installer checks the security setup and, if problems are detected, issues an error message. This message helps you decide on the actions that you must take to adjust the security settings. After the upgrade, remember to re-adjust your security settings, based on your unique needs and the IT security policies at your organization.

Before initiating the upgrade, the installer discovers the existing Application Servers and checks whether an RSCD Agent is installed on each Application Server. For Application Servers that do not have an RSCD Agent installed, the installer prompts you for the credentials of the relevant host computers and installs a fully authorized RSCD Agent on each server. Note that if you suspend or abort the upgrade, you will need to manually uninstall the RSCD Agent on each of the servers. After the upgrade, remember to re-adjust your security settings, based on your unique needs and the IT security policies at your organization.

In addition, ensure that the following security requirements are met before initiating the upgrade:

  • Ensure that you have authentication profiles of any of the following types set up at your TrueSight Server Automation installation: Secure Remote Password (SRP) or LDAP. 

    Upgrade to TrueSight Server Automation version 8.9.03 or later is not supported through Active Directory Kerberos, PKI, or RSA SecureID authentication profiles.

  • You must disable the use of client-side certificates that secure access between Application Servers and agents or repeaters before you upgrade using the unified product installer. For more information, see TLS-with-client-side-certs-Discontinuing-use-of-client-side-certificates.
  • Ensure that your firewall allows communication on all ports used by various components of TrueSight Server Automation. For more information on ports, see TrueSight-Server-Automation-ports.
  • Ensure that the port number that is used by the SSH service running on all hosts is 22, which is the default port number for SSH.


Security requirements for Windows

The unified product installer must be run by a super user, that is, a local Administrator or Administrator-equivalent local user. This enables the installer to install components on remote Application Servers using existing RSCD Agents and PsExec.

In a domain environment, this can be a domain user who is part of the local Administrators group. In such a case, ensure that you prepare the same local Administrator user on any remote Application Server that does not have an RSCD Agent installed.

If you have a high security level enabled in your TrueSight Server Automation installation, the unified installer cannot upgrade the product through the RSCD Agent on the remote host computers. Before upgrading, you must temporarily adjust the security level on the machines where you want to upgrade the Application Servers. At the beginning of the upgrade process, the unified installer checks the security setup and, if problems are detected, issues an error message. This message helps you decide on the actions that you must take to adjust the security settings. After the upgrade, remember to re-adjust your security settings, based on your unique needs and the IT security policies at your organization.

Before initiating the upgrade, the installer discovers the existing Application Servers and checks whether an RSCD Agent is installed on each Application Server. For Application Servers that do not have an RSCD Agent installed, the installer prompts you for the credentials of the relevant host computers and installs a fully authorized RSCD Agent on each server. Note that if you suspend or abort the upgrade, you will need to manually uninstall the RSCD Agent on each of the servers. After the upgrade, remember to re-adjust your security settings, based on your unique needs and the IT security policies at your organization.

In addition, ensure that the following security requirements are met before initiating the upgrade:

  • Ensure that you have authentication profiles of any of the following types set up at your TrueSight Server Automation installation: Secure Remote Password (SRP), LDAP, or Microsoft Windows Domain Authentication. 

    Upgrade to TrueSight Server Automation version 8.9.03 or later is not supported through Active Directory Kerberos, PKI, or RSA SecureID authentication profiles.

  • You must disable the use of client-side certificates that secure access between Application Servers and agents or repeaters before you upgrade using the unified product installer. For more information, see TLS-with-client-side-certs-Discontinuing-use-of-client-side-certificates.
  • Ensure that your firewall allows communication on all ports used by various components of TrueSight Server Automation. For more information on ports, see TrueSight-Server-Automation-ports.
  • Ensure that the port number that is used by the SSH service running on all hosts is 22, which is the default port number for SSH.

Limitations when using the unified product installer

Category

Description of support or limitation

Multiple Application Server (MAS) environments

The unified product installer only supports upgrade of an homogeneous MAS environment, that is, either all Application Servers run on Linux 64-bit operating systems or all run on Windows 64-bit operating systems.

"Mixed" Application Server/database environments

The unified product installer supports upgrade of "mixed" Application Server/database environments (for example, Linux Application Server + Microsoft SQL Server database). The UPI does not require the database or the file server operating system to match the operating system of the Application Servers.

PXE servers

For PXE servers to be upgraded by the unified product installer, they must be:

  • Up and running.
  • Running the same OS as the Application Server.

If your environment includes hybrid PXE servers (that is, PXE servers not running Windows or Linux), you must perform a workaround for the upgrade

Click here to see the workaround.
  1.  Stop the hybrid PXE server / TFTP server.
  2. Run the unified product installer. The installer ignores the PXE server, as it is in a stopped state. The installer upgrades the rest of the infrastructure, with the exception of the hybrid PXE server.
  3. Once the unified product installer has completed the upgrade, run the configurator utility on that PXE server. See Migrating-the-database-and-persisting-configuration-data-to-the-database.
  4. Upgrade the PXE server according to the instructions in Upgrading-the-Provisioning-System.
  5. Copy the global.property file from the Application Server to the /br/deployments/ directory on the PXe server.
  6. Restart the PXE server.

Upgrade scenarios

The unified product installer does not support the following upgrade scenarios:

  • 32-bit Windows or 32-bit Linux machines
  • Solaris SPARC machines
  • Upgrading the TrueSight Server Automation Console (RCP client). Uninstall the older version of the console and install the new version on a different host.
  • Application Servers installed with the -local flag, that is installed in a self-contained directory structure.

  

Preparing the database

During an upgrade process, core data is migrated to the upgraded TrueSight Server Automation database. To ensure that this migration completes successfully, you must prepare your database before performing the upgrade. To prepare your database, review the following list of prerequisite tasks and perform the tasks that are relevant for your environment.

Task

Description

Back up the TrueSight Server Automation database.

You must back up before beginning the data upgrade process.

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.

Remove unnecessary deployments

The migration process uses the database system ID information in the _template deployment to identify the database to migrate. In addition,
the configurations from each existing deployment are processed, so each deployment present in the Deployments directory should have the correct configuration.

Certain deployments are transitory and can be removed before an upgrade as they are not needed for normal operation.

  • _install, _postmig, and _util can be removed from the deployments directory if present, and provided that an installation,

    postmigration process, or blcontent process is not being run.

  • (optional) _launcher is for the Application Server Launcher. 

    This does not include database configuration information. 

    Both _spawner and _pxe include database configuration information. 

    The _template deployment is used to create new deployments, including those used during migration.

    However, you can delete them for stale deployments (user created deployments that are not in use anymore).

Ensure that the database configuration information on the deployments of the Application Server is up-to-date

Before upgrading the Application Server, ensure that the database configuration information on the deployments of the Application Server is up-to-date.

You can use the blasadmin utility to check the database related and file server related information for each of the deployments (except _launcher).

You can use the following blasadmin commands. If either of these commands returns an error, you can use the blasadmin utility to
correct the configuration information and proceed with the upgrade.

  • blasadmin -s <deloyment name> show database all (for the _pxe deployment use blasadmin -s _pxe show pxe all)
  • blasadmin -s <deployment name> show file all

If these commands return an error, use the blasadmin utility to correct the configuration so that those commands do not return an error.

Ensure that the blgroup table does not contain duplicate entries

Before you start the upgrade, connect to the database and run the following query:

select name, parent_group_id, group_type_id, count(*)
from blgroup
group by name, parent_group_id, group_type_id
having count(*)>1;

If the above query returns any rows, contact BMC Support for further actions.

(Oracle only) Ensure that the sufficient free space, which is required for migration to 21.3 or later versions, is available on the tablespaces

Before you start the upgrade, connect to the database and run the following query:

select table_size_mbs, table_space_free_space_mbs
from(select sum(bytes)/1024/1024 table_size_mbs
from user_segments us
where segment_name in(select ut.table_name
from user_tables ut
where ut.table_name in (select column_value
from table(LANG_UTIL.STR_TO_ARRAY('JOB_RUN_EVENT,COMPLIANCE_RULE_RESULT'))))
) tab_size,
(select sum(dfs.bytes)/1024/1024 table_space_free_space_mbs
from dba_free_space dfs
where dfs.tablespace_name = (select tablespace_name from user_segments where segment_name = 'JOB_RUN_EVENT')
group by dfs.tablespace_name
) free_space;

If the value returned by the table_space_free_space_mbs column is lesser than the value returned by the table_size_mbs column, increase the tablespace size.

(Oracle only) Grant privileges explicitly to the user account

For an Oracle database, you must grant certain privileges explicitly to the user account (typically BLADELOGIC) that will be used during the upgrade.

Some of the privileges can be revoked after database migration is performed during the upgrade. For the complete list, see List-of-required-database-permissions.

(SQL only) Configure the database to use the simple recovery mode

For information about configuring the simple recovery mode, see the appropriate Microsoft documentation.

(SQL only) Shrink the transaction log file.

For more information, see the appropriate Microsoft documentation.

To prepare the environment for upgrade (Windows)

UPI prep for Windows

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 your connection to Microsoft SQL database is not encrypted. TrueSight Server Automation does not support using an encrypted Microsoft SQL database connection at the time of upgrade. However, after the product is upgraded successfully, TrueSight Server Automation can use an encrypted connection to communicate with the Microsoft SQL database. For steps on enabling and disabling an encrypted connection to your SQL database server, see Encrypting-your-database-connection.
  3. Verify that the following components are up and running for the upgrade to be successful:
    • All Application Servers
    • PXE Server
    • RSCD agents on Application Servers, PXE servers, and file servers. 

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

    • Application Server: C:\Program Files\BMC Software\BladeLogic\NSH

    • PXE Server: C:\Program Files\BMC Software\BladeLogic\PXE

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

    Error
    Important

    Ensure that all files and folders in the installation directory and its sub-directories do not have the read-only attribute enabled. The upgrade might fail, if the read-only attribute is enabled on any file.

    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 %WINDIR%\rsc\HOME file.

  5. 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.
  6. Ensure that there is an RSCD agent installed on each Application Server to avoid potential errors in the upgrade process.
  7. Ensure that there is an RSCD agent and NSH are installed on the PXE server.
  8. Back up the existing certificate.pem, RSCD log files and respective signature files. 
  1. Make sure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.

  2. 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 -appserver_protocol clear -T encryption_only -e tls

    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 -T encryption_only -e tls

  3. To preserve the Live Reporting dashboard environment, back up the cacerts file (for example,C:\Program Files\BMC Software\BladeLogic\appserver\NSH\jre\lib\security\cacerts for Windows) 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.

  4. Ensure that Microsoft Visual C++ 2015 Redistributable Update 3 is installed on the server. For more information, see Installing an RSCD agent (Windows).

    Warning

    Note

    As a prerequisite to install Microsoft Visual C++ 2015 Redistributable Update 3 on Windows 2012 R2, you must have the following patches installed on your server:

    • KB2919442 (Required for 2919355)
    • KB2919355. This patch requires several other patches: clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018. This are all available on the download page for KB2919355.
    For more information about the prerequisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.

  5. If you have already enabled file server access restrictions when configuring the file server agent ACLs, then perform the following steps:
    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=Administrator
    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.

Component prep for Windows

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 your connection to Microsoft SQL database is not encrypted. TrueSight Server Automation does not support using an encrypted Microsoft SQL database connection at the time of upgrade. However, after the product is upgraded successfully, TrueSight Server Automation can use an encrypted connection to communicate with the Microsoft SQL database.
  3. Shut down the TrueSight Server Automation environment:
    1. Stop the Application Server. 
    2. Stop the PXE server. See Starting-and-stopping-a-PXE-server.

  4. Back up the installation directories for all Application Servers and PXE servers. 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 %WINDIR%\rsc\HOME file.

    The default installation locations are:

    • Application Server: C:\Program Files\BMC Software\BladeLogic\NSH

    • PXE Server: C:\Program Files\BMC Software\BladeLogic\PXE

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

    Error
    Important

    Ensure that all files and folders in the installation directory and its sub-directories do not have the read-only attribute enabled. The upgrade might fail, if the read-only attribute is enabled on any file.

     

  5. Ensure that there is an RSCD agent installed on each Application Server to avoid potential errors in the upgrade process.
  6. Ensure that there is an RSCD agent and NSH are installed on the PXE server.
  7. If you are upgrading an RSCD agent in a domain controller environment, perform the following tasks:
    1. Change the BladeLogicRSCDDC password as per your company's password policies by using the chapw command. For instructions on changing the password, Changing-the-BladeLogicRSCDDC-account-password-on-domain-controllers.
    2. Ensure that Administrators do not have the Delete permission on the HKEY_LOCAL_MACHINE\SAM\SAM node in the Windows Registry. By default, Administrators have the Read Control and Write DAC registry access permissions.
      image2022-11-25_19-15-17.png
  1. Make sure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.
  2. 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:

  3. 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

  • To preserve the Live Reporting dashboard environment, back up the cacerts file (for example, C:\Program Files\BMC Software\BladeLogic\appserver\NSH\jre\lib\security\cacerts for Windows) 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.
  • Ensure that Microsoft Visual C++ 2015 Redistributable Update 3 is installed on the server. For more information, see Installing an RSCD agent (Windows).
Warning

Note

As a prerequisite to install Microsoft Visual C++ 2015 Redistributable Update 3 on Windows 2012 R2, you must have the following patches installed on your server:

  • KB2919442 (Required for 2919355)
  • KB2919355. This patch requires several other patches: clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018. This are all available on the download page for KB2919355.
For more information about the prerequisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.

To prepare the environment for upgrade (Linux)

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. 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.

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. Shut down the TrueSight Server Automation environment:
    1. Stop the Application Server.
    2. Stop the PXE server. See Starting-and-stopping-a-PXE-server.

  3. Back up the installation directories for all Application Servers and PXE servers. 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).

    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.

  4. 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.
  5. Ensure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.

  6. 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

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.

Component upgrade pre-reqs for Windows

 

Category

Requirement

Product integrations

If your TrueSight Server Automation environment includes TrueSight Smart Reporting for Server Automation, upgrade TrueSight Smart Reporting for Server Automation before upgrading TrueSight Server Automation. For more information, see the TrueSight Smart Reporting for Server Automation online technical documentation.

Supported platforms

For a complete list of platforms supported by the individual component installers, see Supported-platforms.

Install mode

If you are using Microsoft Windows 2003 or 2008, you must upgrade in Install mode instead of Execute mode, see Using-Install-mode-instead-of-Execute-mode.

Configuration objects

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent.

The product installation is automatically upgraded to the appropriate version when you upgrade the agent. However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. Configure this job to target servers to which custom configuration objects need to be distributed. For a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom-configuration-objects.

To upgrade custom configuration objects

Click here to see the steps for upgrading custom configuration objects.
  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.

To upgrade virtualization configuration objects

Click here to see the steps for upgrading virtualization configuration objects.

The Upgrade Model Object Job is not supported for upgrading virtualization configuration objects.

To upgrade configuration objects that you distributed in prior versions, complete the following steps:

  1. Import the new version of the virtualization configuration object (for example, the VMware vCenter configuration object).
  2. Restart the RSCD agent on which the configuration object is distributed. This step is a prerequisite for successful upgrade of the configuration object on the target server.
  3. Run the Distribute Configuration Objects Job to distribute the configuration objects to the target agent (see Distributing-configuration-objects).
  4. To identify the configuration objects that failed, run the Upgrade Model Objects Job on all jobs, templates, and BLPackages that reference the configuration object.
  5. After the Upgrade Model Objects Job completes, open the objects for which the job failed.
  6. Remove the parts that are marked as failed and add new ones from the upgraded configuration object.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent.  The  installation are automatically upgraded to the appropriate version when you upgrade the agent. (See Custom-configuration-objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. The job should target servers to which custom configuration objects should be distributed.

Potential issues

Click here to review a list of potential issues you can encounter during an upgrade.
  • Upgrade to version 8.6 or later does not grant the DBMS_LOCK privilege to user - Before you start upgrading from a previous version to TrueSight Server Automation 8.6, ensure that the TrueSight Server Automation user is granted the DBMS_LOCK privilege. This privilege is required for carrying out a handshake between TrueSight Server Automation database and the TrueSight Smart Reporting for Server Automation ETL during database clean up. You can use the SYS user to grant the DBMS_LOCK privilege by entering the following command: GRANT EXECUTE on DBMS_LOCK TO <User>
  • Upgrade to version 8.6 or later disables PropertySync - As of TrueSight Server Automation version 8.5, the PropertySync feature has been deprecated. During migration of the database, PropertySync is disabled and the migration results table displays the migration warning: PropertySync has been changed from true to false. Contact BMC Support for further assistance.
  • Upgrade to version 8.5 or later deprecates the Provision provisionDevice BLCLI command. Earlier releases supported the Provision:provisionDevice command. This command has been deprecated. BMC recommends that you use the ProvisionJob:createProvisionJob command instead.
  • Upgrade to version 8.6 or later causes Citrix XenServer Provision Jobs to fail - After an upgrade from TrueSight Server Automation version 8.3 or earlier to TrueSight Server Automation version 8.5 or later, existing Citrix XenServer Provision Jobs fail (QM001706976). Failed jobs display the error message: com.bladelogic.om.infra.mfw .util.BlException: Proxy cannot be null, Error: Proxy cannot be null. To work around the issue, open the Provision Job in the content editor. On the Server Settings panel, browse the Server Properties option to select or create a valid agentless managed object (AMO).
  • Audit performed with snapshots captured using earlier versions of the RSCD agent can fail - When capturing data from target servers, version 8.6.00 of TrueSight Server Automation skips IPv6 addresses and masks. After an upgrade to version 8.6.00 or later from version 8.3 or earlier, an audit performed with snapshots captured using older versions of an RSCD agent can fail if the targets had IPv6 enabled.
  • In a multiple application server (MAS) environment, if the RSCD Agent is not present on the secondary node and the primary node is using PsExec version 2.43, upgrade to version 21.3 or later on the secondary node fails. To fix the issue, perform one of the following tasks:
    • Install RSCD Agent on the secondary node and start the upgrade process again on the secondary node.
    • Use PsExec version 2.2 instead of version 2.43 on the primary node, and start the upgrade process again on the secondary node.

Certificate issue

If your id.pem certificate was created with a key size of 1024 bits (or less), you will need to regenerate it with a higher key size (2048 or higher). This is due to a change in the FIPS requirement for minimum key length (now 2048 bits).

Component upgrade pre-reqs for Linux

Category

Requirement

Product integrations

If your TrueSight Server Automation environment includes TrueSight Smart Reporting for Server Automation, upgrade TrueSight Smart Reporting for Server Automation before upgrading TrueSight Server Automation. For more information, see the TrueSight Smart Reporting for Server Automation online technical documentation.

Supported platforms

For a complete list of platforms supported by the component installers, see Supported-platforms.

X server requirement

You must run the installer from a computer where an X server is installed. Follow these steps before you install the product from a computer with the X server software:

  1. Start the X server software.
  2. Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.
  3. Connect to the remote system where you want to install the product and start a terminal session on that system, for example, an X terminal (xterm).

Configuration objects

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent.

The product installation is automatically upgraded to the appropriate version when you upgrade the agent. However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. Configure this job to target servers to which custom configuration objects need to be distributed. For a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom-configuration-objects.

To upgrade custom configuration objects

Click here to see the steps for upgrading custom configuration objects.
  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.

To upgrade virtualization configuration objects

Click here to see the steps for upgrading virtualization configuration objects.

The Upgrade Model Object Job is not supported for upgrading virtualization configuration objects.

To upgrade configuration objects that you distributed in prior versions, complete the following steps:

  1. Import the new version of the virtualization configuration object (for example, the VMware vCenter configuration object).
  2. Restart the RSCD agent on which the configuration object is distributed. This step is a prerequisite for successful upgrade of the configuration object on the target server.
  3. Run the Distribute Configuration Objects Job to distribute the configuration objects to the target agent (see Distributing-configuration-objects).
  4. To identify the configuration objects that failed, run the Upgrade Model Objects Job on all jobs, templates, and BLPackages that reference the configuration object.
  5. After the Upgrade Model Objects Job completes, open the objects for which the job failed.
  6. Remove the parts that are marked as failed and add new ones from the upgraded configuration object.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent.  The  installation are automatically upgraded to the appropriate version when you upgrade the agent. (See Custom-configuration-objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. The job should target servers to which custom configuration objects should be distributed.

Potential issues

Click here to review a list of potential issues you can encounter during an upgrade.
  • Upgrade to version 8.6 or later does not grant the DBMS_LOCK privilege to user - Before you start upgrading from a previous version to TrueSight Server Automation 8.6, ensure that the TrueSight Server Automation user is granted the DBMS_LOCK privilege. This privilege is required for carrying out a handshake between TrueSight Server Automation database and the TrueSight Smart Reporting for Server Automation ETL during database clean up. You can use the SYS user to grant the DBMS_LOCK privilege by entering the following command: GRANT EXECUTE on DBMS_LOCK TO <User>
  • Upgrade to version 8.6 or later disables PropertySync - As of TrueSight Server Automation version 8.5, the PropertySync feature has been deprecated. During migration of the database, PropertySync is disabled and the migration results table displays the migration warning: PropertySync has been changed from true to false. Contact BMC Support for further assistance.
  • Upgrade to version 8.5 or later deprecates the Provision provisionDevice BLCLI command. Earlier releases supported the Provision:provisionDevice command. This command has been deprecated. BMC recommends that you use the ProvisionJob:createProvisionJob command instead.
  • Upgrade to version 8.6 or later causes Citrix XenServer Provision Jobs to fail - After an upgrade from TrueSight Server Automation version 8.3 or earlier to TrueSight Server Automation version 8.5 or later, existing Citrix XenServer Provision Jobs fail (QM001706976). Failed jobs display the error message: com.bladelogic.om.infra.mfw .util.BlException: Proxy cannot be null, Error: Proxy cannot be null. To work around the issue, open the Provision Job in the content editor. On the Server Settings panel, browse the Server Properties option to select or create a valid agentless managed object (AMO).
  • Audit performed with snapshots captured using earlier versions of the RSCD agent can fail - When capturing data from target servers, version 8.6.00 of TrueSight Server Automation skips IPv6 addresses and masks. After an upgrade to version 8.6.00 or later from version 8.3 or earlier, an audit performed with snapshots captured using older versions of an RSCD agent can fail if the targets had IPv6 enabled.
  • In a multiple application server (MAS) environment, if the RSCD Agent is not present on the secondary node and the primary node is using PsExec version 2.43, upgrade to version 21.3 or later on the secondary node fails. To fix the issue, perform one of the following tasks:
    • Install RSCD Agent on the secondary node and start the upgrade process again on the secondary node.
    • Use PsExec version 2.2 instead of version 2.43 on the primary node, and start the upgrade process again on the secondary node.

Certificate issue

If your id.pem certificate was created with a key size of 1024 bits (or less), you will need to regenerate it with a higher key size (2048 or higher). This is due to a change in the FIPS requirement for minimum key length (now 2048 bits).

Ensure that your connection to Microsoft SQL database is not encrypted. TrueSight Server Automation does not support using an encrypted Microsoft SQL database connection at the time of installation. However, after the product is installed successfully, TrueSight Server Automation can be configured to use an encrypted connection to communicate with the Microsoft SQL database.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

TrueSight Server Automation 24.4