Walkthrough: Upgrading to version 8.9 for Linux

If you are running BMC Server Automation version 8.6 or later, and are running a 64-bit Linux platform, you can use the unified product installer to upgrade to version 8.9.

The topic includes the following sections:

The video at right provides helpful tips on how to upgrade your BladeLogic Application Server running on Linux.

Note

If you need to upgrade from BMC Server Automation version 8.5.x or earlier, you must first upgrade to one of the following:

  • BMC Server Automation version 8.7 (as discussed in the Upgrading section of the BMC Server Automation 8.7 online documentation)
  • BMC Server Automation version 8.6 (as discussed in the Upgrading section of the BMC Server Automation 8.6 online documentation)

Review the supported upgrade paths information, available in the Before you begin section below.


  https://youtu.be/6oce5bNZHZY

Before you begin

Note

As of BMC Server Automation 8.6, the upgrade process has changed and there are two available methods to perform the upgrade:

  • Unified Product Installer: This option handles all parts of the upgrade from a single user interface and upgrades all parts of the BMC Server Automation Infrastructure
  • Configurator Method: This option handles the database migration and moving the blasadmin configurations into the database (for 8.5 or below upgrades). You then run the individual component installers after the Configurator utility.
  •   Click here to review the supported upgrade paths.


    BMC Server Automation supports direct upgrade from versions 8.3.xx and 8.5.xx. 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.

    The following figures illustrate the supported upgrade paths to BMC Server Automation 8.6.x.

     

    You cannot upgrade from version 8.6.00 to 8.6.00 Patch 1.

    In the above diagrams, abbreviations are defined as follows:

    • BSA stands for BMC Server Automation
    • SP stands for Service Pack
    • P stands for Patch

  • Review the requirements and tasks to complete prior to upgrade in 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 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.

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

  • Note the following limitations when using the unified product installer for product upgrade.
    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 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 the TFTP server in your environment. If you manually enabled the BMC Server Automation Console Upgrade Service, the console is also automatically upgraded; otherwise, you must manually upgrade it. The checklist below walks you through the process of upgrading Windows and Linux environments using the unified product installer.

Tip

Prior to upgrading your production environment, it is best practice to test the upgrade in a duplicated environment.

Step 1: Prepare the environment for upgrade

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.
    • 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 – /opt/bmc/bladelogic/NSH
      • PXE Server – /opt/bmc/bladelogic/NSH
        If you are upgrading the PXE server, follow the upgrade instructions for 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. 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. Make sure all the 32-bit and 64-bit required packages are installed, especially compat-libtermcap.
  8. Make sure you have 4 GB on disk with temp space and 4 GB on disk with installation directory.

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

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

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

Step 2: Download the files

Download and extract the installation files to a temporary location.

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

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

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

  1. Make sure that the RSCD Agent, Application Server, and PXE Server are running. 
  2. Navigate to the temporary directory that contains the installation files. On a Linux machine, you must assign an executable permission to the installer file (setup.bin) by entering the following command:
    chmod +x -R <temporary directory>
  3. Run the installation program (setup.bin for Linux)
  4. Select the language in which you want to run the installer and click OK

    Note: If problems arise during the upgrade, the on-screen error messages contain instructions and guidance to help you troubleshoot the problems, and further information is available in the log files. For a list of log files written during the upgrade process, see the Troubleshooting section.
  5. Read through the basic information about the unified product installer and the types of nodes that are installed in the environment.
  6. Click Next.
  7. Read the two pages of the End User License Agreement (EULA) and select I agree to the terms of the license agreement.
  8. Click Next.
  9. Enter your Authentication profile credentials to proceed with the upgrade procedure. The profile that you specify must be associated with the same Application Server where you are performing the upgrade. Note that only secure remote password (SRP), LDAP, or Domain Authentication type profiles can be used with the unified product installer. 
  10. Click Next.
  11. Review the BMC Server Automation infrastructure discovered in your environment.
  12. Review the different types of servers that are present in the BMC Server Automation environment, their count, and their status. If the unified product installer was successful in connecting with all servers, you can proceed with the upgrade. 
  13. If the PXE Server is on a host than the target server, select Remote Site to copy the PXE installers to the installer dump drive. However, in this scenario, the PXE Server is not on a remote site, so the check box is unselected by default. The installer copies the installer to the current host. Depending on your environment, you might experience some time delays.
  14. If the PXE Server is on a different subnet than the target server, select Different Subnet. In this scenario, the unified product installer does not automatically copy the installation files to the remote machine. For Linux, you must manually copy the PXE installer to the remote machine (for example, to the /tmp directory).
  15. Click Next.
  16. Preview the upgrade.
  17. Select the I acknowledge that the installer will bring down the BladeLogic Server Automation (BSA) environment for upgrade check box.
  18. Click Install.
  19. When the upgrade is finished, review the summary and the upgrade log, and then click Done
     

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

You cannot use a version of the BSA Console that is incompatible with the connecting Application Server, as shown in the following screenshot.

BMC strongly recommends in production environments that you do not install the console on the same system as the Application Server. Therefore, uninstall the existing version of the BSA Console before you upgrade the Application Server and the other components unless you absolutely need to create a ready-to-use test environment. For more information, see Upgrading the BMC Server Automation Console.

Before you begin

To uninstall BMC Server Automation components on Linux

  1. Log on as root.
  2. Navigate to the directory in which BMC Server Automation components are installed. By default, this directory is /opt/bmc/bladelogic or /opt/bmc/bladelogic/appserver.
  3. Navigate to the UninstallBMCClientInstaller subdirectory.
  4. Invoke the installation script by entering the following command:
    ./uninstall.bin
    An X Window opens. The installation program displays a series of messages.
  5. Select the language in which you want to run the installer and click OK
     
  6. When the Welcome window opens, click Next.

    A window displays the components that you can uninstall.
  7. Select the components, and then click Next.

    A window displays the components to be uninstalled.
  8. Click Uninstall.

    A window displays the successful completion of uninstallation.
  9. (optional) To view the uninstallation log, click View Log.
     
  10. Click Done.
    Uninstallation is complete.

    Note

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

Step 5: Install the new console on a separate system

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

Note

BMC recommends that you do not install or upgrade the console on the same system as the Application Server. Copy the console installation files located on the Application Server (for example, ../BBSA88-LIN64/Disk1/files/installers/rcp) to a separate system and install the console there.

Before you begin

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

To install the console on a separate system

Note

This example uses BMC Server Automation version 8.8; however, the process is applicable to versions 8.6 and later.

  1. Navigate to the directory containing installation files and run the installation script for the BMC Server Automation Console. (Script names follow the convention: BBSACONSOLE<version>-<platformbit>, for example, BBSACONSOLE88-LIN64.bin) You must execute the installation from a root shell. Do not execute the installation script from a non-root account.
  2. The BMC BladeLogic Server Automation Suite Installation window opens.
  3. Select a language, and then click OK.
    A series of messages indicate progress. This process might take several minutes. Then the Welcome window opens.
  4. Click Next.
    The Review License Agreement page opens.
  5. To accept the license agreement, select I agree to the terms of the license agreement, and then click Next.
    The User Inputs window opens.
  6. (optional) Remove the check marks from any components that you do not want to install, and then click Next.
    A series of messages indicate progress.
  7. (optional) Select Check to install the default .nsh resource files into /etc/skel.
  8. Click Next.
    The Installing window previews the features to be installed.
  9. To install, click Install. To change your selections, click Previous.
    A series of messages indicate progress. This process might take several minutes. Then the Installation Summary window opens, indicating successful installation.
  10. (optional) Click View Log.
  11. Click Done.
    The window closes. Installation is complete.
  12. Start the RSCD Agent and then start the console (for example, /opt/bmc/BladeLogic/8.0/CM/rcp/launcher). To configure the console so that it connects to the default Application Server, click Options.

  13. Click the Authentication Profiles tab and click Add. BSA clients use authentication profiles to facilitate single sign-on feature. You must create an Authentication profile before you start using the Console. For more information about why we use Authentication Profiles, see System capabilities related to security.

  14. Enter the following information.

    1. Assign a name to the authentication profile. For example, you could assign a name such as QATeam, DevTeam, or defaultProfile.
    2. Enter the name or IP address (IPv4 or IPv6) of the default Application Server to which the client should connect.
    3. Enter an Authentication Port number to which the client should connect. The same port is used for all BMC Server Automation authentication mechanisms. The default Port is 9840. For more information about Console ports, see BMC Server Automation ports.
    4. Select any one authentication mechanism for the authentication profile:

      • Secure Remote Password.
      • AD/Kerberos Single Sign-on.
      • Domain Authentication.
      • LDAP.
      • RSA SecurID Authentication.
      • Public Key Infrastructure Authentication.
      In this walkthrough we will use the Secure Remote Password mechanism. For information about implementing the other authentication mechanisms, see Implementing authentication
    5. Click OK.
  15. Click Connect to log on the Application Server using the BLAdmin user that is created while installing the default Application Server node.

  16. If you see a security alert that the certificate is not initially trusted, optionally, you can view the certificate. Or you can simply click Yes to proceed. 

  17. The quick start page is the first page that is displayed once you log on the the BSA Console. It introduces you to the main use cases of BMC Server Automation and allows you to execute them from a centralized UI immediately after installing the BSA set up. For information about using the quick start page, see Quick start page. For general information about the UI of the BSA Console, see Navigating the interface.

Step 6: Manually upgrade additional components

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

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

Related topic:

Upgrading the RSCD agent on Linux and UNIX

Step 7: Perform additional post-upgrade tasks

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

Run the Update Model Objects Job.

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

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

Compliance Content add-ons

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

Related topic: Installing and configuring Compliance Content add-ons

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