Upgrading to version 8.6 SP1 for Microsoft Windows and Linux

If you are running BMC Server Automation 8.3.x or later, and are running 64-bit Linux and Windows platforms, you can use the unified product installer to upgrade to version 8.6 SP1.

For Solaris platforms, use the manual upgrade process described in Upgrading to version 8.6 SP1 for Solaris.

 

Note

If you need to upgrade from a BMC Server Automation version earlier than 8.3, you must first upgrade to the latest 8.5 service pack, as discussed in the Upgrading section of the BMC Server Automation 8.5 online documentation. Afterwards, you can upgrade from version 8.5.xx to 8.6.x.

Before you begin

Review the requirements and tasks to complete prior to upgrade in Preparing for a Windows upgrade using the unified product installer or Preparing for a Linux or UNIX upgrade using the unified product installer.

 Click here to review the key requirements for running the unified product installer on Windows.

  • 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 PXE servers on your setup, you must copy the PXE installers to <windows-drive>\Windows (typically C:\Windows) on Windows PXE server before starting Unified product installer.
  • 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:
    • 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.

 Click here to review the key requirements for running the unified product installer on Linux.

  • 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 PXE servers on your setup, you must copy the PXE installers to /tmp path on Linux PXE Servers before starting unified product installer.


  • 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:
    • 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 BMC Server Automation is being upgrade.

Note the limitations when using the unified product installer for product upgrade below.

Note

As of BMC Server Automation 8.6 SP1, the task of running SQL Update scripts, which was necessary in the past for any upgrade to a BMC 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.

Note

If you are upgrading from BMC Server Automation 8.6 SP1 to BMC Server Automation 8.6 SP2 (8.6.01.106) and you have RSA authentication configured in your environment, the deployment fails to migrate to the latest version and the upgrade is not even attempted. As a workaround, disable RSA authentication before you start the upgrade. When you finish upgrading, then re-enable RSA authentication. For more information, see Implementing RSA SecurID authentication.

Limitations when using the unified product installer for upgrade

CategoryDescription of support or limitation
Multiple Application Server (MAS) environmentsThe 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 environmentsThe 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 BMC 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.

  

Upgrading using the unified product installer

Note

If you are not an experienced user, see the related topics listed in the table to review the required planning information for upgrading the product.

The unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server and TFTP server, and console in your environment, with certain exceptions. The checklist below walks you through the process of upgrading Windows and Linux environments using the unified product installer.

StepDescription
Prepare the BMC Server Automation environment.
  1. Ensure that the following components must be up and running for the upgrade to be successful:
    • All Application Servers
    • PXE Server (if your environment includes a PXE server that is not on Windows or Linux, see Workaround for hybrid PXE server environments).
    • RSCD agents on Application Servers, PXE servers, and file servers.
    • (Linux only) RSCD agents installed with the –local option on Application Servers, PXE servers, and file servers.   
  2. Back up the database.
  3. Back up the installation directories for all Application Servers and PXE servers.

    The default installation locations are:

      • Application Server
        • (Windows) C:\Program Files\BMC Software\BladeLogic\NSH
        • (UNIX) /opt/bmc/bladelogic/NSH
      • PXE Server
        • ((Windows) C:\Program Files\BMC Software\BladeLogic\PXE
        • (UNIX) /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. Back up the BMC 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. Similarly, if an RSCD agent and NSH are not already installed on the PXE server, install them now.
  6. (Linux only)  You must install the product from a computer where 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

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

Preparing for a Windows upgrade using the unified product installer

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

Download the files.Download and extract the installation package to a temporary location
  1. Download the BBSA86-SP1.zip file (which contains the unified product installation program files) to the host computer of the Application Server that was set up as a configuration server.
  2. Extract the RSCDAgent.zip file from the package and copy the rscd folder to one of the following locations before running the unified product installer (The unified product installer uses the RSCD installers while installing or upgrading BMC Server Automation in your environment):
     
    • (Windows<temporary location>/files/installer/ 

    • (Linux): <temporary location>/Disk1/files/installers/

Run the unified product installer on the Application Server.

The unified product installer automatically upgrades the database, file server, Application Server, agents, PXE server and TFTP server, and console in your environment, with certain exceptions (see . 

 To run the unified product installer the Application Server

  1. Navigate to the temporary directory that contains the installation files. If you are on a Linux machine you must assign an executable permission to the installer file (setup.bin) by entering the following command: chmod +x -R <temporary directory>
  2. Run the installation program (setup.exe for Windows or setup.bin for Linux)
    Note: For Windows 2008, right-click the installer file and select Run as administrator.
  3. Follow the instructions in the installation wizard and click Next. Enter your Authentication profile credentials to proceed with the upgrade procedure. Note that only secure remote password (SRP), LDAP, or Domain Authentication type profiles can be used with the unified product installer.
  4. The unified product installer program displays the different types of servers that are present in the BMC Server Automation environment and their count. Click Install to proceed with the upgrade of all BMC Server Automation components that are present in your environment.
    Note: If problems arise during the upgrade, the on-screen error messages contain instructions and guidance to help you troubleshoot the problems, and further information is available in the log files. For a list of log files written during the upgrade process, see the Troubleshooting section.

Related topic: Upgrading on Windows using the unified product installer

Upgrade the console.

To upgrade the console

After completing the upgrade using the unified product installer, you can attend to the upgrade of the console, according to the following scenarios:

  • If you had enabled the BMC Server Automation Console Upgrade Service check box while installing the previous 8.3.x or 8.5.x installation, the console will automatically be upgraded by the system (see BMC Server Automation Console Automatic Upgrade: Windows only).
  • If you had not enabled the BMC Server Automation Console Upgrade Service check box or if you are having the installation on a Linux platform, you need to manually upgrade the Console by running its individual component installer, see Upgrading the BMC Server Automation Console.

Related topic: Upgrading the BMC Server Automation Console 

Upgrade components that were not upgraded

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

  • NSH clients on non-Application Server host computers - Use the instructions in  Upgrading the Network Shell on Linux and UNIX and Upgrading the Network Shell on Windows 
  • 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 Windows or Upgrading a PXE server on Linux or UNIX.
  • Upgrade any agents that you may have that fall into the following categories. You can perform this step anytime after the upgrade.
    • Agents not on target (managed) servers
    • Agents on a file server installed on a separate host, if that file server host runs Linux and the Application Server runs Windows
    • Agent on an online or offline patch repository
    • Agent on a basic/standard repeater
    • Agent on a VMware vCenter server

Related topics:

Upgrading the RSCD agent on Linux and UNIX

Upgrading RSCD agents on Windows

Run the Update Model Objects Job.

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

  1. Run an Update Server Properties Job on the agents you have upgraded. For more information, see Creating Update Server Properties Jobs.
  2. If you are not upgrading all of your agents at this time, make copies of all component templates, BLPackages, Snapshot Jobs, and Audit Jobs that reference custom configuration objects that have dependencies on agents running earlier versions. You must maintain a version match between component templates, BLPackages, Snapshot Jobs, and Audit Jobs and custom configuration objects and agents. The objects that you copy in this step are the objects that you can use to maintain the version match.
  3. If you upgrade to the latest version of BMC Server Automation and you are using BMC 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 BMC Server Automation.

  4. To ensure that all configuration-object-based assets within existing content are upgraded, run an Upgrade Model Objects Job that targets any component templates, BLPackages, Snapshot Jobs, or Audit jobs that you want to upgrade. For more information about the Upgrade Model Objects Job, see Creating or modifying Upgrade Model Objects Jobs.
    Note: Do not run the Upgrade Model Objects Job against the copies of objects that you created in step 3.
    If you open an existing component template, BLPackage, Snapshot Job, or Audit Job that references a custom configuration object and a later version of that custom configuration object exists, the system displays a message saying it will automatically upgrade the referenced custom configuration object. To maintain a version match with an earlier agent, close the component template, BLPackage, Snapshot Job, or Audit Job without saving.

  5. After executing the Upgrade Model Objects Job, display the results of the job run to see which assets were successfully upgraded and which were not. If you find that certain assets were not automatically upgraded, you must upgrade them manually. Perform the following steps:

    1. Open the object (template, package, or job).
    2. Manually remove the asset of the earlier version and add the asset of the latest version.
    3. Save the object.

Related topics:

Upgrading custom configuration objects

Creating or modifying Upgrade Model Objects Jobs

Upgrade Compliance Content.

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

Related topic: Installing and configuring Compliance Content add-ons

Workaround for hybrid PXE server environments

If your environment includes a PXE server that is not on Windows or Linux, complete the following steps:

  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 from the Application Server to PXE server in /br/deployments/.
  6. Restart the PXE server.
Was this page helpful? Yes No Submitting... Thank you

Comments