New in this version

This section describes the new features and enhancements that have been introduced in BMC Atrium Discovery version 10.0. If you are new to BMC Atrium Discovery, BMC recommends that you refer to Getting started as an introduction to using the product.

Before you begin

Before you upgrade to the latest vesion of 10.x, make sure you note the following details:

  • If you are on any of the previous versions of BMC Atrium Discovery 10.0.x, you can upgrade to 10.0 Patch 2 or higher from the appliance’s UI. The upgrade procedure is described in Upgrading from BMC Atrium Discovery version 10.
  • If you are upgrading from 9.0.x on RHEL 6 to 10.0 Patch 2 or higher, the upgrade procedure is similar to Upgrading to version 10.0.

No architecture changes required

No architecture changes required

When upgrading from 9.x to 10.0 there is no need to change your deployment architecture. Rather, BMC strongly recommend that you upgrade using your existing architecture and test version 10.0 in a known configuration. If testing reveals that you require the performance improvements offered by a cluster, you can then add hardware and replace one or more version 10 machines with a cluster.

 

Major enhancements and changes have been introduced in the following areas:

Big Discovery

Discover and get usable results from even the largest Data Centers in the shortest time possible.

  • Distributed system — BMC Atrium Discovery can now operate as a distributed system aiming to achieve near linear scalability. Multiple BMC Atrium Discovery machines operate in a cluster which is controlled by a single coordinator. Additional machines can be added to the cluster at any time. When you do so, the system spreads the existing data out amongst all the machines evenly, in order to maximize performance and utilization of each machine in the cluster. This can take a while to happen, but the system is fully usable while it happens: you can do discovery and browse the data. After initial configuration, features now work whether you are logged into the coordinator or not. For example, if you upload a TKU from any machine it is automatically shared with all other machines. Also, if you change an option on a machine, it changes everywhere.
  • Cluster Management — The Cluster Management page enables you to control the operation of your cluster. For example, you can:
  • Fault toleranceFault tolerance is designed to prevent data loss in the event of hardware failure. It works by storing data on multiple machines so that the loss of a single machine cannot lose the only copy of some data.

Managing your cluster has been made as simple as possible. Use any machine in the cluster to manage all others: update TKUs, add credentials and scans, and even upgrade the product itself from a single place.

All existing features have been updated to operate in the clustered environment. The behavior of the following features has changed, or additional consideration is required to use them:

  • Disk configuration in a cluster — The disk configuration utility enables you to move BMC Atrium Discovery data onto new disks and create swap space on new disks on all of the machines in a cluster. When making changes to disks and swap space on a cluster member, all members of the cluster need to be shut down. To minimize cluster downtime, changes are queued and then applied in parallel.
  • Free disk space — The free disk space available on each cluster member is monitored and displayed in the Cluster Management page.
  • Back up and restore in a clusterAppliance backup has been extended to back up the entire cluster. If you choose to backup to local filesystem (the On Member option), each cluster member is backed up onto its local filesystem. Where you backup a cluster to a remote destination, the appliance backup feature creates a single backup in which each machine's backup is contained in a subdirectory.
  • ConsolidationConsolidation now works with clusters. A typical setup is for scanning appliances to consolidate to a cluster. In this case, all scanners must set the coordinator of the cluster as the consolidation target.
  • Back up and restore in a cluster — The appliance backups created can now be smaller, at the expense of slower restore. You can restore a backup to any cluster with the same number of machines as the cluster from which it came.
  • Centralized collection of data for support cases — Gathering data for support cases from an entire cluster can be undertaken from any machine in the cluster.
  • HTTPS supported in a clusterHTTPS access to the appliance has now been extended to clusters.
  • CMDB synchronizationCMDB synchronization is configured from any machine in the cluster, however, synchronization always occurs between the coordinator and BMC Atrium CMDB.

Fixing a broken cluster — The tw_cluster_control utility enables you to revert a cluster member to a standalone machine.

Knowledge management

  • In this release, pattern and knowledge management have been improved and a new Knowledge Management page has been added, replacing the previous Pattern management and Knowledge management pages accessed through the Administration tab.
  • The data model has changed enabling an improvement in the way that patterns are activated. On large systems in particular, TKUs take less time to install. The new data model shares pattern module nodes between knowledge upload nodes rather than duplicating them as in previous releases. Additionally, the components that made up a TKU release are now combined into a single package.
  • These features have made it possible to provide automatic cleanup capability to the installed patterns.
  • On the Knowledge Management page pattern modules are now organized by product categories providing a more logical way to find individual modules. For example, Structured Data Management Software > Relational Database Management Systems > Oracle RDBMS.
  • Disabling and deactivating patterns and packages has been simplified.

Redesigned UI

  • Redesigned UI — The BMC Atrium Discovery UI has been refreshed to look more up to date and to fit in with other BMC products.

Security

The following security enhancements have been added in this release.

  • Single sign-on — BMC Atrium Discovery can now integrate with BMC Atrium SSO. This is the preferred method of implementing single sign-on.
  • HTTP Header web authentication — A new web authentication mechanism is provided using information included in an HTTP header. This enables you to integrate with third party single sign-on applications.

Compliance support

The following enhancements have been added in this release to help support standards compliance.

  • DISA Secure Technical Implementation Guidelines (STIG) compliance — BMC Atrium Discovery version 10.0 can be configured to be STIG compliant by running a script.
  • VMware Ready — BMC Atrium Discovery and Dependency Mapping is certified VMware Ready.

Management enhancements

The following management enhancements have been added in this release.

  • Enable and disable scheduled discovery runs — You can now enable or disable individual or all scheduled discovery runs.
  • Preserve root node identity after tw_model_init — You can now preserve the identity of your data between tw_model_init use, preventing duplicates in the CMDB. We also changed and renamed the utility to tw_model_wipe.
  • tw_top — Provides a filter on the open source top utility which enables you to view just BMC Atrium Discovery processes.
  • LDAP user lookup — From the Group Mapping page you can now look up an LDAP user to determine which groups that they are in.
  • Query Builder — The Query Builder has been improved internally. The only difference visible in the UI is in the raw query view, where the query itself is simpler, more efficient, and easier to understand.
  • UI based upgrade — You can upgrade a BMC Atrium Discovery version 10 machine from a single UI page. You can even upgrade all the machines in a cluster from the UI of any member. The same page enables you to apply OS upgrades, again, to a standalone machine or all machines in a cluster.
  • NTP configuration UI — A new UI has been provided enabling you to perform time synchronization.
  • CMDB Sync performance — CMDB sync is now faster in many cases.
  • Discovery performance and interactivity — Discovery configuration now provides an option to trade discovery performance with interactivity.

Browsing node information

The following security enhancements have been added in this release.

  • Related nodes — A new related nodes drop-down enables you to navigate around the model by traversing from a node to any other related node. The drop down displays the relationship type and the target node, and where different relationships exist to the same node kind, the label is shown to differentiate between them, for example IPv4 and IPv6 addresses. Click the required item to navigate to its page, or to a list page where there are multiple items linked by the same relationship.
  • Search by node kind — When using quick search you can now limit the results to a particular node kind. For example, to search for hosts containing the word Atrium, limit the search to host nodes by entering host: Atrium. To limit the search to software instances containing the word Atrium, enter si: Atrium.

Node deletion

The following enhancement has been added in this release.

  • Inferred nodes deletion — Now you can remove inferred nodes in the same way as any discovered node.

Miscellaneous enhancements

  • SNMP binary data — TPL can now retrieve binary data via SNMP enabling you to query for items such as IP and MAC addresses.
  • Pill UI — The pill UI is used for entering IP addresses. It has been made simpler to use and a filter provided to show invalid IP addresses.
  • Windows proxies — Windows proxies are now supported on Windows 2012 and Windows 2012 R2.
Was this page helpful? Yes No Submitting... Thank you

Comments