Upgrading to version 8.6 SP1 for Solaris

This topic highlights the process for upgrading Solaris environments to version 8.6 SP1 from version 8.6 or earlier. The topic includes the following sections:

Before you begin

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

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 configurator utility, which was introduced in version 8.6.

To manually upgrade Solaris platforms

StepDescription
Shut down the BMC Server Automation environment

Stop any running Application Servers

The stop operation ends running jobs and stops the Application Server, providing a controlled shutdown. You can select options for managing the running jobs. You cannot use the stop operation on an Application Server to which a BMC Server Automation Console is connected.

  1. In the BMC Server Automation Console, from the Configuration menu, select Infrastructure Management.
  2. Expand the Application Servers node.
  3. Right-click the Application Server and select Stop.
  4. In the Stop Application Server dialog box, select the method for managing any running jobs:
    • Stop immediately without waiting for running jobs to finish.
    • Stop when all running jobs finish.
    • Stop when all running jobs finish or after specified number of minutes, whichever comes first.
  5. Click OK.

Repeat steps 3-5 for each Application Server that shows up under Infrastructure Management and can run jobs (type JOB or ALL). This could be many Application Servers spread over multiple hosts.

Allow a window of time (an hour or so, if possible) to ensure that any running jobs have stopped, and then stop the Application Server service, on each Application Server host.

  • Type the command:/etc/init.d/blappserv stop

To stop the process spawner on the Application Server

  • Enter the following command: 
    /etc/init.d/blprocserv stop

Repeat this step for each Application server in your environment.

To stop the PXE server

Type the command:/etc/init.d/blpxe stop

Related topic: Starting and stopping a PXE server

Back up the environment prior to upgrade.

Before you upgrade, you must back up the environment.

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

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 to the host computer of the Application Server.
  2. Extract the contents of the file to a temporary location:<temporary location>/Disk1/files
Copy the configuration data on the database.

The configurator utility performs a database migration and then persists configuration data into the database. You must run the configurator on all Application Servers and PXE servers in your BMC Server Automation environment before you upgrade the servers using the individual component installers.  

  1. Before running the configurator utility through the unified product installer wizard, stop any application server, spawner, or PXE server that is running on this machine. However, ensure that the RSCD agent service is still running on this machine.
  2. Ensure that NSH is installed on all the PXE servers on which you intend to run the configurator utility.   
  3. Navigate to the <temporary location> directory containing installation files and run the installation file using the the following command.
    ./setup.bin –J STATELESS_ONLY=true
    Note: BMC recommends that you execute the installation as a root user. Do not execute the installation file from a non-root account.
  4. Follow the instructions in the installation wizard to persist the configuration data to the database. 

Related topic: Migrating the database and persisting configuration data to the database

Run the Application Server upgrade program.

To upgrade the Application Server

  1. Log on as root.
  2. Stop the Application Server.
  3. Navigate to the temporary directory that contains Application Server installer files. 
  4. Run the installer file using the ./<BL_Installer_file.sh> command.
  5. Enter y to continue with the upgrade.
  6. Enter the number corresponding to the language that you want to use.
  7. Enter y to continue with the upgrade.
  8. Enter y to agree to the license agreement.
    A list displays the BMC Server Automation components to be upgraded and prompts you to continue.
  9. Enter y on the confirmation panel.
    A series of messages is displayed, and then the upgrade script is complete.

Note: If the console is installed on the Application Server (which is not recommended by BMC), go to step 10 and run the console upgrade program before moving to step 4.

Related topic: Upgrading product components on Linux and UNIX

Execute the postmigration file

After migration is complete, you need to update BLPackages that refer to old Group Policy Object (GPO) assets, such as certain compliance content templates and policy files by running the postmigration file.

Note: You need to perform this step on one Application Server only.

To execute the postmigration file

    MultiExcerpt named 'postmigrationTask' was not found
The page: Performing post-migration updates was found, but the multiexcerpt named 'postmigrationTask' was not found. Please check/update the page name used in the 'multiexcerpt-include macro.

Related topic: Performing post-migration updates

Upgrade any agents installed with the -local option

If an agent was installed with the -local option, you must use the -local option to upgrade that agent. However, you must set several environment variables before starting the upgrade process.

  1. Before invoking the installer for the upgrade process, set several environment variables using the following commands.

    INSTALL_DIR="<installDir>"
    NSHDIR=${INSTALL_DIR}/NSH
    LD_LIBRARY_PATH=${LD_LIBRARY_PATH:=}
    ${LD_LIBRARY_PATH:+:}${NSHDIR}/lib
    export INSTALL_DIR NSHDIR LD_LIBRARY_PATH
  2. Invoke the installer using a command such as the following:
    sh BBSA-LIN64.sh -local

Related topic: Upgrading components using the local option on UNIX or Linux

Upgrade the RSCD agent on the File Server.

If the File Server is on the same server as the Application Server, then you can skip this step, as the agent would have been upgraded in step 4.

To run the RSCD agent upgrade program on the File Server

  1. Log on as root.
  2. Navigate to the directory that contains upgrade files and run the installation program for the RSCD agent. (Script names follow the convention: RSCD<version>-<platform>.)

    Note: If you are upgrading a server with components installed other than the RSCD agent, you must use an installation script that includes those other components. For example, if you are upgrading the RSCD agent on a server where Network Shell is also installed, the installation package you are using must include Network Shell.

  3. Enter y to continue with the upgrade.
  4. Enter the number corresponding to the language that you want to use.
  5. Enter y on the welcome panel to continue.
  6. Enter y to agree to the liecense agreement.
  7. Enter y to continue with the upgrade.
  8. Press Enter to install accept the default RSCD log directory or enter another directory path.
  9. Press Enter to install accept the default directory for temp files or enter another directory.
    Several messages are displayed, and the upgrade is complete.

Related topic: Upgrading the RSCD agent on Linux and UNIX

Start the Application Server.

To start the Application Server

From the directory where BMC Server Automation is installed, enter the following:
/etc/init.d/blappserv start

To start the spawner service

Enter the following command: 
/etc/init.d/blprocserv start

Related topic: Starting and stopping BMC Server Automation components 

If you are using PXE-based provisioning, upgrade the PXE server.

To upgrade the PXE Server

Note: If PXE is installed on the Application Server, the Application Server installer will upgrade it automatically.

If the PXE server is installed as part of the Application Server installation, an upgrade of the Application Server also upgrades the PXE server.

 Click here for more information.

  1.  Log on as root.
  2. Record the following settings for the PXE server:
    • Database connectivity information
      The PXE server uses the same database as the Application Server. One way to obtain this information is to start the Application Server Administration Console (also known as the blasadmin utility) and enter the following command:
      show database all
    • Host name and IP address of the PXE server
    • DHCP server location (local or remote)
    • TFTP root directory
      You do not have to record the name and location of the data store.
    • If you are using the Multi-Database mode, make a note of the additional database configuration parameters found in the <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml file.
  3. Make a backup copy of configuration files.
    If you are using the pxe.conf configuration override file, make a copy of the <install directory>/NSH/br/pxe.conf file.
  4. Navigate to the directory that contains upgrade files and run the upgrade script for BMC Server Automation. (Script names follow the convention: BBSA<version>-<platform>.)
    The following message is displayed:
    A previous installation already exists.
    Do you wish to continue (y/n) ?
  5. Enter y.
    A message prompts you to choose a language for the installation program.
  6. Enter the number corresponding to the language that you want to use.
    The following message is displayed:
    Welcome to the BMC BladeLogic Server Automation Release <versionNumber> installation script ...
    A previous installation has been detected. This installation will be upgraded to BMC BladeLogic BMC BladeLogic Server Automation <versionNumber>.
    Do you wish to continue (y/n) ?
  7. Enter y.
    Licensing text is displayed and concludes with the following message:
    Do you agree to the terms of the license agreement (y for Yes) ?
  8. Enter y.
    A list displays the BMC Server Automation components to be upgraded and prompts you to continue.
  9. Enter y.
    A series of messages is displayed, and then the upgrade script is complete.
  10. Copy the backup of the pxe-data-sources.xml file into <install directory>/NSH/br/deployments/_pxe/pxe-data-sources.xml.
  11. Merge the configurations of the <install directory>/NSH/br/pxe.conf and the backed up copy.
  12. During the upgrade process, the PXE server global.properties file is overwritten. Copy the global.properties file on the Application Server to the br/deployments directory on the PXE machine.
  13. Restart the PXE server. See Starting and stopping a PXE server.

Related topic: Upgrading a PXE server on Linux or UNIX

Upgrade the console.

To upgrade the console

Note: If the console is installed on the Application Server (which is not recommended by BMC), stop the agent and the Application Server and run the console upgrade program.

    MultiExcerpt named 'upgrade_console' was not found
The page: Upgrading the BMC Server Automation Console was found, but the multiexcerpt named 'upgrade_console' was not found. Please check/update the page name used in the 'multiexcerpt-include macro.

Once you have upgraded the console, test the upgrade by logging on to the console and verifying that you can connect to the upgraded Application Server.

Related topic: Upgrading the BMC Server Automation Console 

(MAS environments only) Upgrade additional Application Servers

If this is a multiple application server environment (MAS), upgrade your other Application Servers now.

For each additional Application Server. repeat steps 3, 6, and 8.

Upgrade the RSCD agents on target servers

At this point, upgrade the agents on the target servers (enrolled servers) in your environment, as needed. You can perform this step anytime after the upgrade.

To upgrade agents

  1. Log on as root.
  2. Navigate to the directory that contains upgrade files and run the installation program for the RSCD agent. (Script names follow the convention: RSCD<version>-<platform>.)

    Note: If you are upgrading a server with components installed other than the RSCD agent, you must use an installation script that includes those other components. For example, if you are upgrading the RSCD agent on a server where Network Shell is also installed, the installation package you are using must include Network Shell.

  3. Enter y to continue with the upgrade.
  4. Enter the number corresponding to the language that you want to use.
  5. Enter y on the welcome panel to continue.
  6. Enter y to agree to the liecense agreement.
  7. Enter y to continue with the upgrade.
  8. Press Enter to install accept the default RSCD log directory or enter another directory path.
  9. Press Enter to install accept the default directory for temp files or enter another directory.
    Several messages are displayed, and the upgrade is complete.

Related topic: Upgrading the RSCD agent on Linux and UNIX

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.

Related topic: Installing and configuring Compliance Content add-ons

Was this page helpful? Yes No Submitting... Thank you

Comments