This section describes the new features and enhancements that are available in BMC Discovery version 11.1. You can upgrade to BMC Discovery version 11.1 from versions 10.1, 10.2, and 11.0. The upgrade procedure is described in upgrading BMC Discovery.
If you are new to BMC Discovery, BMC recommends that you refer to Getting started as an introduction to using the product.
The following topics are covered in this section:
BMC Discovery version 11.1 patch 3
BMC Discovery version 11.1 patch 3 resolves some important defects. As a result of those enhancements, an appliance running 11.1 patch 3 cannot join a cluster running 11.1 patch 2 or earlier.
In normal circumstances, all cluster members have the same version. You can upgrade a cluster running any version from 10.1 onwards to 11.1 patch 3.
There is one obscure circumstance in which you may require a new appliance running 11.1 patch 2. If you have a fault tolerant cluster running 11.1 patch 2 (or an earlier patch) and a member has failed, then your cluster is in a degraded state. In that state, you must replace the failed member before you can upgrade the cluster. You cannot replace the failed member with a new appliance running 11.1 patch 3, so you must use an appliance running 11.1 patch 2. Once the cluster has recovered from the failure, it is possible to upgrade the whole cluster to 11.1 patch 3 as usual.
If you are in this situation, and you do not have an image of 11.1 patch 2 with which to replace the failed cluster member, please contact Customer Support. They will provide a suitable download.
What's new in BMC Discovery version 11.1?
This section describes the new features and enhancements that have been introduced in BMC Discovery version 11.1.
Start anywhere application modeling
Start anywhere application modeling has been substantially improved since its initial release in BMC Discovery 11.0. The following new features and tools are provided:
- A new software visualization view. The following software views are available:
- Visualize - Software - Connected–focuses on software and communication between items of software and shows some details of the hosts and load balancers involved.
- Visualize - Software–focuses on software and communication between items of software running on a host.
- A new intelligent focus. The system determines the most appropriate view and automatically shows your visualization in that view.
- You can now create exclusion rules in the UI for the following:
- Specific kinds of Software Instances, Software Components, Software Clusters and Database Details using a Never show node kind tool.
- All relationships from specific node kinds
- Relationships from specific node kinds to specific destination node kinds
- A “Show more nodes” tool enables you to show nodes that are not currently shown because of rules you have defined or boundaries set by the tool.
You can undo the creation of exclusion rules in a new Removal Rules tab on the Removed Nodes list. If you have removed multiple nodes the Removed Nodes list now groups them by removal time or node kind making it easier to find the node or nodes you want to restore. You can also restore groups of nodes, grouped by time of removal or kind.
You can now define rules to prevent the creation of specific types of candidate SIs. Creating such a rule also deletes all instances of that candidate SI throughout the datastore and may affect other existing models.
The first release of the BMC Discovery REST API is available. In BMC Discovery 11.1, the REST API version is 1.0.
You can now automate many common management tasks via the REST API. Some of the tasks you can accomplish using the REST API are:
- Initiate a scan
- Retrieve data
- POST an event to the event source
- Upload new TKUs
- Manage credentials.
You can browse the API endpoints using the integrated Swagger UI.
Event driven model updates
User defined event sources
You can now define generic event sources which are collectors for defined events. Once the event source is configured, you can use the REST API to POST an event to the event source. When an event is received, you can use them to trigger patterns to perform tasks.
VMware event collection
VMware event collection uses a built in event source to automatically poll discovered vCenter servers for events. When events, such as those representing the moving or renaming of a VM are received, they trigger TKU patterns to perform scans on the affected machines and automatically update the BMC Discovery model. You can enable VMware event collection in Event Sources.
Integration with BMC Remedy Single Sign-On
BMC Discovery can now integrate with Remedy Single Sign-On (Remedy SSO) for user authentication.
You can upload a CA bundle to verify the identity of the Remedy SSO server, and you can also pin a certificate downloaded from the Remedy SSO server. BMC recommend that you use a pinned certificate and use a trusted CA bundle to identify the Remedy SSO server during the pinning operation.
The minimum supported version of Remedy SSO is 9.1.01.
If you use BMC Discovery 11.1 / 11.1 patch 1 / 11.1 patch 2, BMC Discovery integration with Remedy Single Sign-On does not support Remedy Single Sign-On 9.1.02. Upgrade BMC Discovery to 11.1 patch 3 where the integration problem has been fixed.
If you are using Remedy Single Sign-On 9.1.01 with BMC Discovery 11.1 / 11.1 patch 1 / 11.1 patch 2, you should not upgrade to Remedy Single Sign-On 9.1.02 until you upgrade BMC Discovery to 11.1 patch 3 where the integration problem has been fixed.
Integration with CyberArk Enterprise Password Vault
The integration with CyberArk Enterprise Password Vault (CyberArk Vault) enables you to store some, or all of your credentials for scanning discovery targets credentials in the CyberArk Vault. In this way, you can use the CyberArk Vault to maintain the password policies used by your organization. The integration requires the CyberArk Application Identity Manager version 9.6, though the version of the CyberArk Vault can be earlier.
CMDB synchronization performance improvements
The performance of CMDB synchronization has been greatly improved. It can now exploit multiple processors more effectively by running several concurrent workers in parallel. Use the Concurrent Workers parameter to tune your CMDB Sync to maximize throughput and reduce synchronization times.
CMDB resynchronization improvements
If a CMDB resynchronization is interrupted for any reason, you can now resume processing where it left off. Resynchronization also benefits from the concurrent workers performance improvements described above.
You can now choose one of the following resynchronization types:
- One step resync–If you are confident about your resynchronization you can now select a single step process which will complete without further intervention.
- Incremental resync–Instead of waiting for a complete resynchronization commit, you get back to normal synchronization activity immediately, by performing resynchronization incrementally in the background.
Performance graphs are now cluster aware so that you can view either performance graphs for a standalone appliance, a single member of a cluster, or a consolidated view of the cluster.
vCenter support and modeling
vCenter 6 is now supported, and vCenter appliances are now modeled as Host nodes.
Consolidation is now cluster aware
Scanning appliances can now connect to any member of the consolidating cluster. See Consolidation for more information.
Hidden attributes in the Query Builder
In the Query Builder you can now display attributes starting with a single underscore, for example,
_all_cores_per_processor, by clicking Show All. However, Show All does not show attributes starting with a double underscore, such as
__all_ip_addrs. Attributes starting with a double underscore can be accessed by entering them in the text search box.
There are now additional user types for accessing the REST API and Event Sources. When adding a new user, templates are provided for the types of user you can create:
• User to create a standard UI login user account.
• API Access Only to create a user account only to be used for access to an API.
• Event Source to create a user account only to be used as an event source.
The following changes were made:
Additional permissions required on XML and CSV APIs
or updating group permissions to include the api/access permission
revious releases, reasoning reported that it was ready to start before the discovery service had stopped completely. This may lead to a slight increase in time before the START ALL SCANS button is displayed.