New in version 8.3 SP2

This section describes new features for BMC Atrium Discovery version 8.3 SP2, released on 27 February 2012.

If you are new to BMC Atrium Discovery, BMC Software recommends that you refer to Getting started as an introduction to using the product.

BMC Atrium Discovery version 8.3 SP2 patch 2

The version of BMC Atrium Discovery currently available on the BMC EPD site is version 8.3 SP2 patch 2. This replaces the original version 8.3 SP2 to correct an issue with PDF generation. You should ensure that the user interface refers to the version number as 8.3.2.2.

New in BMC Atrium Discovery 8.3 SP2

  • Network device discovery redesign: Network discovery has been redesigned in order to make it much faster and use fewer resources.
    • Network topology discovery has been removed in this version. It was replaced in BMC Atrium Discovery version 8.3 with Edge Connectivity discovery.
    • The SNMP Device page has been modified to display the SNMP queries used for each call to each device, rather than the current dump of all of the OIDs.
    • The list of SNMP devices per manufacturer now has a Notes field which shows additional notes on devices if they are required.
  • Scheduled DDD removal blackout windows: In BMC Atrium Discovery systems where discovery (or consolidation) is in progress for most of the available time, contention between the removal (aging out) of DDD nodes (in this case DA nodes and their children) and the creation of new nodes, may affect the performance of in-progress discovery runs. To avoid this performance impact you can schedule DDD removal blackout windows during which no DDD removal is undertaken. This is only likely to be needed at the Consolidated Enterprise scale, or possibly in the very largest scanning appliances.
  • DDD removal statistics: A new DDD removal statistics page has been added to the appliance performance pages which shows the total number of DAs in the datastore and those eligible for removal. The DDD removal statistics page can be used to track the removal of DDD if you have scheduled DDD removal blackout windows, and to help decide whether you actually need to schedule DDD removal blackout windows.
  • Changes to datastore cache: Changes have been made to the datastore cache which should improve performance in some situations:
    • Default datastore cache size: The default datastore cache size has been changed to be equal to half of the RAM in the appliance. This value is shown in the drop-down list of cache sizes on the Model Maintenance page. On upgrade to this release, the new default is used if the existing cache size is set to the previous default of 1GB.
    • Datastore cache performance: A new Datastore cache performance page has been added to the appliance performance pages which shows information on the performance of the datastore cache.
  • Datastore page size: For new installations of 8.3 SP2, the page size used in the datastore for some operations has been changed.
  • Lightweight vSphere API: VMware ESX and ESXi hosts are now discovered using a new lightweight API. The lightweight API provides improved performance and uses less memory than the one used in BMC Atrium Discovery 8.3.
  • Mainframe discovery methods optimized: The getDatabase and getMQDetail methods have been split into separate calls to reduce the likelihood of timeouts when large quantities of database and MQ (Message Queue) data are being discovered.
  • Query builder enhancements: The query builder has been improved and made more efficient and robust.
    • When removing a column, it is now immediately removed from the column list. Previously it was displayed in strikethrough text.
    • The Apply button has been renamed Refresh results.
  • Windows Proxy Manager: The Windows Proxy Manager is a new management UI that has been added to the Windows Proxy, permitting users to run multiple proxies on one Windows server with different accounts. This is useful for the rare case where a customer needs to use multiple credential on the same (or trusted) Windows domain to do discovery. If you have multiple credentials from different domains unrelated by trust relationships, you will still require multiple Windows servers - one per domain.
  • Show matching credentials: Where many credentials are configured, finding those that match a given IP address is now made simpler using Show matching credentials in the Hosts and other credentials pages.
  • Prevent cross site framing: The user interface is now prevented from being "framed" into another user interface to defend against possible "clickjacking" attacks. You can re-enable framing (and accept the resulting security risks) in the Security policies page.
  • Other security improvements have been made.
  • Support for Microsoft Internet Explorer version 6 is deprecated.
Was this page helpful? Yes No Submitting... Thank you

Comments