Upgrading the operating system

The upgrade is a compressed shell script that contains all of the required packages and binaries.

The preferred method of upgrading the operating system, in standalone or clustered systems, is to use the upgrade UI.

You can also upgrade the operating system using the command line utility, tw_run_upgrade. The tw_run_upgrade utility recommended only if there is an upgrade issue and you are required to resolve it by using the options provided by the utility. If you do choose to run the command line utility, only the local machine is updated (not the cluster) and it is not rebooted automatically. 

Before you upgrade

Changes to OS Configuration Files

If you have made changes to operating system configuration files on the appliance, these changes may be overwritten by the upgrade process. After the upgrade has completed, you must check any configuration files you have previously modified and reapply the changes as required.

Retaining the set timezone

When you run the upgrade, the timezone you have specified will be overwritten and returned to Europe/London unless you have updated the variable ZONE in /etc/sysconfig/clock (CentOS 6 and Red Hat Enterprise Linux (RHEL) 6) or the value set using timedatectl (CentOS 7 and RHEL 7). See Localizing the appliance for information on how to do this.

Obtaining the OS upgrade

Operating system and architecture

The script is operating system and architecture specific. Download the one appropriate to your architecture, and its associated checksum from the BMC Electronic Product Distribution (EPD) site. The compressed script name is of the following form:

  • ADDM_OS_Upgrade_CentOS_64_V.yy.mm.dd_nnnnnn_ga.sh.gz (CentOS 6 and 7)
  • ADDM_OS_Upgrade_64_V.yy.mm.dd_nnnnnn_ga.sh.gz (RHEL 6)
  • ADDM_OS_Upgrade_RHEL_64_7.yy.mm.dd_nnnnnn_ga.sh.gz (RHEL 7)


  • V is the RHEL/CentOS version
  • yy.mm.dd is the date of the last package update from Red Hat or CentOS, as appropriate to the OS type or version
  • nnnnnn is the build number

Location of the OS upgrade files on EPD

The latest OS upgrade files are available for download from the BMC EPD site. Log on to the EPD site with your Support Contract ID and password. From the Licensed Products tab, perform the steps corresponding to your product:

  1. Navigate to BMC Discovery.
  2. Select the Products tab
  3. The directory contains the latest OS upgrade files and associated checksums. The following available OS upgrades support the corresponding versions of BMC Discovery:
    • OS upgrade on CentOS 7, 64 bit: Supports BMC Discovery new installations of version 11.3.
    • OS upgrade on RHEL 7, 64 bit: Supports BMC Discovery new installations of version 11.3 patch 6 and later on RHEL 7. (Support for BMC Discovery running on RHEL 7 was introduced with BMC Discovery 11.3 patch 6.)
    • OS upgrade on CentOS 6, 64 bit: Supports BMC Discovery new installations of version 11.2 or later and upgrades thereof.
    • OS upgrade on RHEL 6, 64 bit: Supports BMC Discovery new installations of version 9.0 or later and upgrades thereof.

No upgrade path from BMC Discovery 11.3 on CentOS 7 to RHEL 7

You cannot upgrade a BMC Discovery 11.3 appliance running on CentOS 7 to an 11.3 appliance running on RHEL 7; rather, you must perform a new installation and then migrate your data. See Upgrading in the BMC Discovery 11.3 documentation for more information on upgrade/migration paths

Baseline changes

The baseline tool tracks changes to the system configuration from a known baseline. After an upgrade, the operating system configuration will have changed significantly. You should view the baseline page after an operating system upgrade and examine the changes made to the system. Then you can rebaseline the appliance so that the tool can check for changes from the configuration henceforth.

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