Upgrading BMC Atrium Discovery

You can upgrade to BMC Atrium Discovery 10.2 or later from BMC Atrium Discovery version 10.1 and later. 

 Upgrading from an earlier version?

If you are using an earlier version of BMC Atrium Discovery, see the appropriate upgrade documentation to upgrade to a version from which this upgrade is supported.

You can perform the following upgrade operations on a cluster or a standalone machine from the appliance's UI:

  • Upgrade BMC Atrium Discovery to a Patch, Service Pack or a version later than 10.2
  • Upgrade the Operating System

To run an upgrade, you must be a user with admin security privileges such as the system user.

The preferred way to upgrade is through the UI. You can also use the tw_run_upgrade command line utility, though this is intended for use if there is an upgrade issue which cannot be resolved from the UI.

To prepare for the upgrade

  1. Download the compressed upgrade archive from the BMC Electronic Product Distribution (EPD) site. See upgrade archive naming conventions
  2. Upload the upgrade archive to the /usr/tideway/var/upgrade directory on any machine in the cluster or on the standalone machine. This can also be done through the upgrade UI if you are using a browser that supports HTML5 sufficiently.


    To upload the upgrade archive using the UI, you must have sufficient space in /tmp, approximately 1.6GB.

Upgrade archive naming conventions

To help you locate the necessary file, the upgrade archives for BMC Atrium Discovery use the following file naming conventions. Product upgrades from BMC Atrium Discovery version 10 and later use a .tgz file extension. Previous versions used a .sh.gz extension and required manual verification using checksums. The compressed OS upgrade archive retains the .sh.gz file extension.

  • For product upgrades later than 10.0:
    Where Vn is the BMC Atrium Discovery version number to which you are upgrading to and nnnnnn is the build number.  
  • For OS upgrades:
    Where yy.mm.dd is the date of the last package update from Red Hat and nnnnnn is the build number.


Changes to OS Configuration Files

If you have made changes to OS configuration files on the appliance, these changes might 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.

Database upgrade

This upgrade performs an upgrade of the BMC Atrium Discovery database. It is highly recommended that you do not skip running a backup. Where a backup is created, it can only be restored to an appliance running the pre-upgrade version.

This upgrade includes significant changes to CMDB synchronization. In particular the filtering is changed. Many existing filters will not be compatible with the new filtering and will need to be recreated in the CMDB Sync filter tab after upgrade and before CMDB synchronization can be used.

For more information see, CMDB synchronization filters.

Upgrade considerations

Click the following items to show additional information or explanation.

 For users with consolidating appliances

When a system uses consolidation, the suggested approach in this upgrade is:

  1. Stop discovery on scanning appliances.
  2. Ensure that all consolidation operations are complete.
  3. Stop discovery on consolidating appliances.
  4. Upgrade consolidating appliances.
  5. Restart discovery on the consolidating appliances.
  6. Upgrade scanning appliances as required.
  7. Restart discovery on the scanning appliances.

Version 9.x scanning appliances can consolidate to version 10.x consolidating appliances, but version 10.x scanners cannot consolidate to earlier consolidating appliances. Once you have upgraded your consolidating appliances, you can then upgrade scanning appliances as required. You should definitely plan to upgrade them all eventually, it is not a permanent solution to leave some scanners at version 9.

 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. See Localizing the appliance for information on how to do this.

 For users of CMDB Sync
  • The synchronization mechanism has changed in 10.2, to reduce the amount of querying performed on the CMDB. As a result it will be necessary to resynchronize a connection that existed prior to the upgrade. See Resyncing a CMDB Connection for more information.
  • Where an upgrade makes changes to syncmapping files (see Default CDM Mapping and Syncmapping block), the initial CMDB syncs after upgrade might result in longer reconciliation times. Examples of such changes are key changes or attribute changes on a CMDB CI.
 Miscellaneous upgrade items

The following items are also affected by the upgrade:

  • SQL and JDBC credentials — where SQL and JDBC credentials are in use, their existing properties files continue to be used and updated properties files are installed but not used. Where such credentials are unused, the old properties files are replaced with the latest.
 Re-running an upgrade

You can re-run the upgrade to BMC Atrium Discovery 10.2 if it is terminated or fails. Destructive actions are recorded and are skipped on subsequent upgrade runs. Consequently when an upgrade is re-run, it is usually significantly quicker. You are unlikely to need to run the upgrade more than once, as it would only be required if an upgrade fails. See also the tw_run_upgrade command to re-run an upgrade.

 Temporary files directory (default: /usr/tideway/tmp) must be readable by tideway user

The location used by the upgrade for temporary files must be readable by the tideway user. The default location (which will be created if it does not exist) is /usr/tideway/tmp, and can be changed using the command line option --tmpdir.

To run the upgrade

  1. The upgrade places temporary files in /usr/tideway/tmp. If this directory already exists, make sure it is readable and writeable by the tideway user.
  2. From the Appliance section of the Administration page, click Upgrade.
    The following dialog opens:
    This screen shows the Upgrade page.

  3. Ensure that there are no warnings in the Pre-Upgrade Check section. All pre-upgrade checks pass when the following required conditions for the upgrade are met:
    • (Applicable only in a cluster) All the members of the cluster are functioning.
    • Discovery is stopped.
    • The credential vault is open.
    • No discovery run or consolidation in progress.
    • No synchronization with BMC Atrium CMDB in progress.
  4. Create a backup of the appliance or cluster before running the upgrade.
  5. Copy the upgrade archive to the /usr/tideway/var/upgrade directory. This can be done through the upgrade UI if you are using a browser that supports HTML5 sufficiently.
    1. If the upgrade file is missing and your browser supports HTML5, you see an Upload button. Click this and choose the upgrade archive from your file system. Click upload to upload the archive. A progress bar shows the progress of the upload.
    2. If the upgrade file is missing and your browser does not support HTML5, the following message is displayed: "No upgrade archive found. Please upload an ADDM upgrade archive to :/usr/tideway/var/upgrade ". Once you have uploaded an archive, click Check for upgrade archive.
      This screen shows Upgrade page where an archive has been uploaded.

  6. At this stage you can choose the Advanced mode upgrade, to do this, continue this procedure from Advanced mode upgrade.
  7. To perform the "no questions" upgrade click Apply Upgrade.
    If you are using a cluster, the archive is distributed to other members of the cluster. The upgrade runs and when it completes, the system reboots.

Advanced mode upgrade

In the final step of the previous procedure, you click Apply Upgrade to start a "no questions" upgrade. To perform an upgrade in which you control when the files are distributed and when the actual upgrade starts, select the Advanced Mode checkbox.

  1. Click Prepare Upgrade.
    The upgrade files in the compressed upgrade archive are extracted and the UI displays the status in the progress bar and notifies you on completion.
  2. (Only if you are upgrading a cluster) Click Distribute Upgrade.
    When the distribution starts, you can monitor the progress of the distribution for all the cluster members. Once the distribution is completed, you see a screen similar to this:
    This screen shows the upgrade procedure where the upgrade file has been distributed but has not yet run.

  3. Click Run Upgrade.
    A window shows the progress of the upgrade and details of the upgrade:
    This screen displays the progress of the cluster upgrade from the UI.

    When the upgrade completes, the system reboots.

Post upgrade messages

When the system reboots after an upgrade, some upgrade actions are carried out in the background. Some of these actions may require your intervention and those are listed as Post Upgrade Messages and can be viewed and dismissed by clicking the User Notification Messages icon in the dynamic toolbox. These messages are available only to users with admin security privileges and contain the following information:

  • The components which have raised the messages.
  • The corresponding severity level of each message.
    • Error — a high priority issue requiring immediate attention.
    • Warning — a medium priority issue which will require attention soon.
    • Information — a low priority issue of which you should be aware.
  • A link to the UI page from where the issue can be resolved may also be displayed.

Example post upgrade messages

Depending on the configuration of the pre-upgrade system, some of the following steps may be displayed:

CMDB synchronization filters 

In version 10.2 the CMDB synchronization mechanism has been changed and most filters created using previous versions will no longer work. The filters may be in one of the following states:

For further information, see Recreating legacy filters.

Review patterns flagged by the upgrade

The upgrade flags any pattern modules that refer to the old data model and therefore need changes to continue to work correctly. Flagged TKU patterns are addressed by activating the new TKU. However, flagged custom patterns require manual review to decide what changes are required.

The Knowledge management page lists pattern modules flagged by the upgrade. If no modules are listed then no action is required. Any listed modules show the errors and/or warnings generated by the upgrade when patterns were compiled. Depending on the severity of the compile messages, pattern modules can be left enabled or disabled. However, all messages should be reviewed to avoid future issues with your patterns. Pattern modules and packages should be updated in the usual way for your environment; either by editing via the user interface or by uploading a new version.

Any pattern packages that you do not wish to update immediately can be deactivated and will no longer be listed. Alternatively, any pattern packages that are no longer required can be deleted.

Activate new TKU

The upgrade installs a new TKU package (TKU-2015-04-2-ADDM-10.2+) but does not activate it. The new TKU must be activated before performing discovery. Information on activating and deactivating TPL packages is available here.

Export mapping sets

The upgrade checks whether there is a newer version of each of the installed mapping sets. If a mapping set has changed since the last version, either by the user modifying it or BMC releasing a newer version, then a warning is displayed to the user. The original mapping is renamed by the upgrade to append ".old" to the mapping set descriptor (the file ending with ".properties") and "_old" to the directory containing the mapping files. You can either:

  • Ignore the warning if the export framework is not being used.
  • Compare the old mapping set to the new one and keep the new one (i.e. do nothing).
  • Compare the old mapping set to the new one and decide to keep the old one, in which case the user needs to manually delete the newer mapping descriptor and directory and rename the old ones (removing the .old and _old postfixes).
  • Compare the old mapping set to the new one and merge the changes. If the changes to the mapping set have been performed by BMC Software then these changes will be listed in the release notes and the user can apply these changes manually to their own copy of the mapping set.

Check Windows proxy compatibility 

BMC Atrium Discovery 8.3 Windows Proxies

The default keys and certificates used in very old versions of BMC Atrium Discovery expire in 2015. The transition to newer default keys started with version 9.0, meaning that, as long as the version 10.2 appliance is configured to use the legacy keys, an appliance can use a version 9.0 proxy, but it cannot use a version 8.3.x proxy that uses the default keys.

To use a version 8.3.x proxy, by far the best approach is to upgrade the proxy to version 10.2. If that is not possible, suitable CA certificates must be installed on the proxy.

To make 8.x proxies operate with a 10.2 appliance

To make 8.x proxies operate with a 10.2 appliance you must copy the new certificate authority file to the main proxy folder and each of the runtime folders. To do this:

  1. Ensure that the appliance is using the legacy key and certificate.
  2. Concatenate the two files containing the public keys, /usr/tideway/etc/ca/appliance_ca.pem (new public key) and /usr/tideway/etc/ca/appliance_ca_1.pem (old public key), using the following command:
    cat /usr/tideway/etc/ca/appliance_ca.pem /usr/tideway/etc/ca/appliance_ca_1.pem > /usr/tideway/etc/ca/appliance_ca.pem
  3. Copy /usr/tideway/etc/ca/appliance_ca.pem from the appliance to the 8.x proxy folders. Put a separate copy in the main proxy folder and each of the runtime folders. For example:
    • C:\Program Files (x86)\BMC Software\ADDM Proxy\etc
    • C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name1>\etc
    • C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name2>\etc
  4. Restart all of the proxies.
  5. Move the appliance_ca.pem file out of the /usr/tideway/etc/ca/ directory, for example to the /tmp directory.
To make proxies upgraded from 8.x to 9.x operate with a 10.2 appliance

Proxies that have been upgraded from 8.x to 9.x also require a manual upgrade of their default certificates in order to operate with a 10.2 appliance. To do this:

  1. Copy C:\Program Files (x86)\BMC Software\ADDM Proxy\etc\ca_01.pem into each of the proxy runtime folders. For example:
    • C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name1>\etc
    • C:\Program Files (x86)\BMC Software\ADDM Proxy\runtime\<proxy name2>\etc
  2. Restart all of the proxies.

Proxies deployed from a 9.x proxy manager, whether upgraded or newly installed, work without any manual configuration.

Check the Windows proxy compatibility matrix to determine whether you need to upgrade Windows proxies.

Baseline changes

The baseline tool tracks changes to the system configuration from a known baseline. After an upgrade, the appliance configuration will have changed significantly. You should view the baseline page after an appliance upgrade and examine the changes made to the system. When you understand the changes that have been made, you can rebaseline the appliance so that the tool can check for changes from the configuration after upgrading to the newer version of BMC Atrium Discovery.

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


  1. Cesar Flores

    Download the compress file from Mozilla Firefox or command line, IExplorer rename the files and put .tar extension and that cause that the upgrade via UI don't work even if you rename the file.

    Jan 26, 2016 03:56
    1. Mark Wilkinson

      Should the browser alter the file extension, changing it back to .tgz will definitely work.

      Note that in modern Windows file extensions are hidden by default, so that when trying to rename a file from .tar to .tgz it is possible to inadvertently rename the file .tgz.tar, which will not work. Chrome has also been seen to alter the file name.

      Jan 27, 2016 01:55