Upgrading from BMC Atrium Discovery version 10

In BMC Atrium Discovery 10.0 and later, 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.0
  • 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.

    Note

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

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:
    ADDM_Upgrade_Vn_nnnnnn_ga.tgz
    Where Vn is the BMC Atrium Discovery version number to which you are upgrading to and nnnnnn is the build number.  
  • For OS upgrades:
    ADDM_OS_Upgrade_64_6.yy.mm.dd_nnnnnn_ga.sh.gz
    Where yy.mm.dd is the date of the last package update from Red Hat and nnnnnn is the build number.

Warnings

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.

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

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.

 Model changes - RAM and Physical RAM

In BMC Atrium Discovery version 10, the model changed to detail Physical RAM and Logical RAM on a host. As part of the upgrade from versions of BMC Atrium Discovery prior to version 10, the old RAM attribute of an existing host is set to zero and it, and the Logical RAM attribute will be repopulated when the host is next scanned.

 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 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. An option is provided (--redo) to re-run an upgrade as if no previous upgrades to this version have previously run.

 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 me
    1. (Applicable only in a cluster) All the members of the cluster are functioning.
    2. Discovery is stopped.
    3. The credential vault is open.
    4. No discovery run or consolidation in progress.
    5. 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/upgradedirectory. 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:
    When the upgrade completes, the system reboots
    This screen displays the progress of the cluster upgrade from the UI.






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.
Was this page helpful? Yes No Submitting... Thank you

Comments