This documentation refers to a previously released version of BMC Discovery.
See the information on this topic for the latest version (11.2) or see the documentation on 11.1.

You can upgrade to the latest version of BMC Discovery by using the UI or the tw_run_upgrade command line utility. The UI-based upgrade, which enables you to upgrade standalone machines and clusters from a single, is the recommended approach. However, if an upgrade issue occurs that cannot be resolved by using the UI, you use the command line utility.

In the upgrade to BMC Discovery version 11.0.00, a defect exists which prevents the services restarting. It occurs if the F5 load balancer pattern configuration has been modified from the default setting to include zone details where IPv4z or IPv6z are being used. Before upgrading, perform the following search (Search Options > Generic Search Query):
SEARCH LoadBalancerService WHERE ip_addr HAS SUBSTRING "%"

If the search returns no results, you can proceed with the upgrade.

If the search returns results, you must:

  1. Edit the F5_BIG_IP_LoadBalancer pattern configuration and set the exclude_zones pattern variable to TRUE.
  2. Discover the F5 load balancers.
  3. Re-run the search (SEARCH LoadBalancerService WHERE ip_addr HAS SUBSTRING "%").
  4. If the search returns no results, you can proceed with the upgrade.

If you cannot restart the services after an upgrade, contact Customer Support to obtain a utility to make the changes required to enable you to do so.

The upgrade to BMC Discovery version 11 includes a substantial UI and icon redesign. Occasionally, when logging in to the upgraded system, the UI may display with a combination of old icons and and new UI. This is caused by the browser cache settings and can be avoided by clearing your browser cache.

You can upgrade to a Patch, Service Pack, and perform OS upgrades by using the appliance's UI. To run an upgrade, you must be a user with admin security privileges such as the system user.

Upgrading from an earlier version?

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

To download the upgrade files

  1. Download the compressed upgrade archive from the BMC Electronic Product Distribution (EPD) site.
    For more information, 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.
    You can also do this 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.6GB.

To perform the upgrade

Use the following steps to perform an upgrade where the installer controls when the files are distributed and when the actual upgrade starts.

  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 main menu, click the Administration icon.
    The Administration page is displayed.
  3. From Appliance section click Upgrade.
    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:
    • For clustered deployments, 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.
  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.

    To complete the upgrade, and start using BMC Discovery version 11, you must open the credentials vault using the existing passphrase. The credentials cannot be upgraded until the vault has been opened. Once this is done the upgrade is complete and you can then change the passphrase.

To perform the upgrade in advanced mode

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.

    To complete the upgrade, and start using BMC Discovery version 11, you must open the credentials vault using the existing passphrase. The credentials cannot be upgraded until the vault has been opened. Once this is done the upgrade is complete and you can then change the passphrase.

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.

BMC Discovery 11 new clustering model

BMC Discovery 11.0 changes how clusters are modeled. In previous versions, the software running on clusters was modeled as SIs running on each host in the cluster. In version 11, the software running on a cluster is modeled as a single SI running on the cluster itself. At the time of release not all TKU patterns have been updated to build this new model. As updated patterns are activated and used to discover existing clusters they will automatically change the inferred model. When you scan a host which is a member of a cluster that has software recognized by one of these updated patterns, the system:

  • creates a new SI linked to the cluster (rather than the host),
  • remembers the value of the type attribute of the created SI,
  • searches all hosts in the cluster for SIs that have the same type attribute value and deletes them.

Example post upgrade messages

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

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.

CMDB sync mappings

The structure of the CMDB sync mappings has changed in BMC Discovery version 11 so you must consider any extensions to existing mappings. The mapping position they extend from may have changed. The syncmapping versions have been incremented and the knowledge management system will require that you review modules flagged by the upgrade before you can activate patterns.

Before you can activate patterns you must edit the syncmapping extensions. In most cases, you only need to update the version number of an import, but more complex extensions may require more rework because the underlying mappings are quite different.

Activate new TKU

The upgrade installs a new TKU package but does not activate it. You must activate the new TKU before performing discovery. Information on activating and deactivating TPL packages is available here.

CMDB sync filters 

The CMDB synchronization mechanism was changed in version 10.2 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.

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 (that is, 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 Discovery 8.3 Windows Proxies

The default keys and certificates used in very old versions of BMC Discovery expired in 2015. The transition to newer default keys started with version 9.0, meaning that, as long as the version 11.0 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.

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

To make 8.x proxies operate with a 11.0 appliance

To make 8.x proxies operate with a 11.0 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 11.0 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 11.0 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 Discovery.

Upgrading from BMC versions 11.0 or 11.0.00.1 to 11.0.00.2 and later introduces a fix to the preferred ssh authentication order. Although the actual credentials are not changed, baseline reports that all ssh credentials have changed.

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

3 Comments

  1. how to Uploading and activates TKU in 11.0?? I am not able to find it

    1. Hi Bupesh,

      That was renamed a few releases ago when we improved the pattern/knowledge management. Try this link: Uploading knowledge.

      Hope that helps, Duncan.

  2. it has very limited steps. Post update how to verify


© Copyright 2017 BMC Software, Inc. © Copyright 2017 BladeLogic, Inc.

Legal notices

© Copyright 2017 BMC Software, Inc.
Legal notices