Configuring after upgrade

The post-upgrade activities that you might consider are the same as post-installation activities. If you have already performed these configuration steps, they are retained on upgrade and do not need to be repeated.

After you upgrade to 20.08 (12.1), the UI displays a set of tasks that you must complete. The following sections list all the possible tasks. These tasks can vary in your case, depending on the version and configuration of your system before upgrading.

Related topics

Preparing for upgrade

Performing optional configuration

Transitioning to scopes/overlapping IP addresses

The BMC Discovery 20.08 release introduces scopes, a means of distinguishing overlapping IP addresses. On upgrade to BMC Discovery 20.08, all existing discovered devices are considered to be in the default scope. When you scan an endpoint, all scanned devices appear in the scan's scope and will be distinct from devices scanned in any other scope.

However, if an endpoint has already been discovered, and is then scanned using a non-default scope, this creates a duplicate inferred device. To avoid this, upgraded appliances use scope transition mode, where discovered endpoints that do not exist in the scan's scope are matched against existing endpoints in the default scope. If the endpoint is the same, it is updated, including the addition of the scope.

All AWS EC2 hosts have a scope whether discovered by using AWS Systems Manager or ssh, and scope transition mode will update existing EC2 the updated host scripts with the scope.

When you upgrade to BMC Discovery 20.08, and choose to use scope, you should leave the appliance in transition mode until you have scanned the endpoints covered by the BMC Discovery Outposts or appliances where scope has been configured.

If you do not have overlapping IP addresses and do not scan EC2 hosts, you do not need to consider scopes.

Mapping files for synchronization to ServiceNow CMDB

The mapping files for synchronization to ServiceNow CMDB released with the previous version of BMC Discovery no longer work with the updated sync for ServiceNow CMDB. New mapping files are available from EPD. However, to ensure correct operation, you must use the following procedure:

Delete the sync for ServiceNow mappings
Upload the new sync for ServiceNow mappings
Restart the cmdb_sync_transformer service. As the tideway user, enter:
```
tw_service_control --restart cmdb_sync_transformer
```

To remove legacy network devices imported from CiscoWorks

CiscoWorks import was deprecated in BMC Discovery 11.0 and removed in version 20.02 (12.0). If you have any legacy imported CiscoWorks network devices, you should remove them. You can find the legacy imported CiscoWorks network devices using the following generic search query:

SEARCH NetworkDevice WHERE type = "Imported Switch"

The resulting list page shows the network devices and you can remove them using the UI controls. Select All, and then Actions > Destroy..

To ensure that Integration Points are converted to Data Sources

Data sources are a flexible and intuitive way to add static sources of information to your discovered information. Data sources replace the 'Integration Points' used in previous releases. The upgrade from BMC Discovery 11.3 to 20.08 converts any existing Integration Points to database data sources. The name of converted Integration Points is ip_name.connection_name, where ip_name is the name of the Integration Point, and connection_name is the name of the connection used for the Integration Point. You should ensure that your converted Integration Points are available on the Data Sources page.

Integration Point patterns using definition blocks continue to work.

Consolidation continues to work correctly to BMC Discovery 20.08 consolidating appliances, whether or not the scanning appliance is upgraded. See Consolidation for more details on BMC Discovery versions and consolidation.

To re-authenticate the AIM provider with the CyberArk vault

If you upgrade from BMC Discovery 11.x and you have configured a CyberArk integration, you must re-authenticate the AIM provider with the CyberArk vault. For information on re-authenticating the AIM provider, see Integrating with CyberArk Enterprise Password Vault.

To activate the new TKU with the latest patterns

The upgrade installs a new TKU package but does not activate it. You must activate the new TKU before performing discovery. If you do not activate the new TKU, the pre-upgrade patterns remain active.

For additional information, see Knowledge management and latest TKU activation Open link .

From BMC Discovery 20.02 (12.0) and onwards, TKU devices and product content are no longer the same for all versions. When updating TKUs in future, insure that you download and install the correct version.

To reapply customizations to the new Discovery scripts

Where this topic refers to default scripts, it refers to the discovery scripts that were shipped with the release. For example, in a version 11.3 appliance, the default scripts are those that shipped with 11.3. If you upgrade the appliance to version 20.02 (12.0), the default scripts are those that shipped with version 20.02 (12.0).

When you upgrade from one BMC Discovery version to a later version, the discovery scripts may change to implement the new capabilities of the release or to fix defects in the scripts. The new scripts replace the default scripts from the previous release. However, if you have customized any discovery scripts, those are not replaced. Platforms with modified scripts are shown on the Discovery Platforms page with a change bar. When you click through to the platform page you can see the individual scripts that have been modified. Where a script has been modified you are provided with the following additional controls:

Show Differences – shows side by side versions of the current file and the modified file with highlighted changes. Use this view to identify your modifications, and the changes made during the upgrade, and decide how to move your changes to the new default script.
Reset To Default – replaces the modified file with the new default script.

Important

If you customize the default scripts they are not upgraded automatically when you upgrade BMC Discovery. You must ensure that you update the scripts manually, incorporating your changes. Alternatively, you can use the new version's defaults, by using Reset To Default.

To reconfigure the changed 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.