Technology Knowledge Update 2016-Jul-1


BMC Discovery Technology Knowledge Update 2016-Jul-1 is a deliverable for BMC Atrium Discovery 10.0, 10.110.2 and BMC Discovery 11.0 series.

Info

From version 11.0, BMC Atrium Discovery and Dependency Mapping has been renamed BMC Discovery. Also, If you are running BMC Discovery version 11.0 you must upgrade to 11.0.0.1 (patch 1) to use TKU April 2016 and subsequent releases.

Note

The Extended Data Pack TKU July 2016 release comes with a new feature! BMC Discovery now automatically links to National Vulnerability Database. This is available only for users who have a license for the Extended Data Pack. Please see here the details of the new feature.

Command/File Matrix

The Command/File Matrix file has been enhanced and is now being shipped in the modern Microsoft Excel format of .xlsx rather than the older .xls.

Note

Please be aware that Configuration Block for Oracle RDBMS pattern was updated. "List of custom locations to Oracle Installer location file" part was added.

Release Compatibility

TKU 2016-Jul-1 is released in the following streams:

  • Release compatible with BMC Atrium Discovery 10.x series
  • Release compatible with BMC Discovery 11.x series

Download

Customers can access this TKU release from the BMC Electronic Product Distribution Website. If you are a customer or partner and do not already have a login please contact your BMC account manager.

Check out this demo if you are unsure how to download from BMC EPD site.

Contents

The release comprises components packaged as such entities:

  • BMC Atrium Discovery Extended Data Pack, which is a separately licensable product.
    • Hardware Reference Data - Patterns and data import CSV file that populate BMC Discovery with power and heat consumption figures for various hosts.
    • National Vulnerability Database – A pattern that populates BMC Discovery with information about the CPE ID of each product, full details here
    • Product Lifecycle - Patterns that populate BMC  Discovery with information about End-of-Life, End-of-Support, and End-of-Extended-Support for versions of certain host Operating Systems as well as versions of certain software products
  • BMC Discovery for Storage, which is a separately licensable product.
    • Storage Systems: Patterns that model many Storage Systems. See the full list of currently supported storage devices here. Visit the Storage System Release Notes page to get details about what's new. 
    • Improvements on existing Storage patterns. See what we have fixed or improved in existing patterns in the Storage Systems Release Notes page.

Installation and Upgrade

  • Atrium Discovery 10.0 series - Installation and upgrade instructions are provided here
  • Atrium Discovery 10.1 series - Installation and upgrade instructions are provided here
  • Atrium Discovery 10.2 series - Installation and upgrade instructions are provided here
  • BMC Discovery 11.0 series - Installation and upgrade instructions are provided here

A matrix covering ALL commands executed and ALL files retrieved by the patterns is available to our customers from the BMC Electronic Product Distribution Website. The filename is TKU_Command_File_Matrix-2016-07-1.xlsx

New Pattern Modules

Products

Vendor

Product

Category

Platforms

Instances

Versioning

Product Page

BMC

BMC Remedy Encryption Security

Process Automation Middleware

Windows, Unix

Y

Y

BMC

BMC TrueSight Middleware Administrator

Process Automation Middleware

Windows, Unix

Y

Y

Docker

Docker Swarm

Virtual Machine Software

Unix

Y

N

 

Enhanced Pattern Modules for Cluster Awareness in BMC Discovery 11.x series

BMC Discovery 11.0.x  introduces a new extended cluster discovery.

Cluster Modeling approaches and Key changes:

  1. Clustering Platform  that generate a Cluster Node. In most cases the Key doesn’t change.
  2. Clustered Software.  In previous releases, the SIs were modeled running on Host nodes.  Now, if they are running on a cluster, they are modeled running on the Cluster node .That means that instances of these products that run on clusters have changed Keys. Instances that do not run on clusters do not have changed Keys.
  3. Software Performing Clustering - products that implement their own Clustering Scheme without using a Clustering Platform. In general, the SoftwareCluster is given the same Key that was previously given to the SoftwareInstance.

 More about new clustering technologies and clustering models you may find here.

 

Task No

Product Page

Enhancement

Clustering Model

Key Change

DRDC1-6371

New pattern for Docker module which supports the new Cluster data model

Software Performing Clustering

N

DRUD1-18009

SoftwareInstance nodes representing the virtual machines in a cluster will no longer be linked to the Cluster node, and will only now be linked to the host they are running on.

Clustering Platform

N

DRDC1-6445

Removed cluster identifier from the name in SystemMirror Cluster node 

Clustering Platform

N

Enhanced Pattern Modules

RFEs

RFE ref.

Product Page

Enhancement

SI Key Change

Esc091146

Pattern enhancement implemented

N

DRDC1-6360

Added BMC TrueSight Operations Manager latest version support (10.5)

N

DRDC1-6411

Fixed the issue when pattern does not find cluster name + model details as software components 

N

Esc091009

Fixed TKU Data Quality issue

N

DRDC1-6435

Removed -s option for olsnodes command for specific versions

N

DRDC1-6296

SI type updated

N

DRDC1-6412

SI type updated

N

DRDC1-6303

Fixed the issue with discovering virtual machines

N

DRDC1-6290

Fixed opatch issue

N

DRDC1-5673

Added a new version support

N

Esc090695

Fixed Weblogic discovery issue

N

DRDC1-6405

Fixed Instance Splunk Forwarder SI creation issue

N

DRDC1-6448

Fixed the issue with oracle DBs detection

N

DRDC1-6447

Updated vm_hostname assignment

N

DRDC1-6285

MongoDB pattern update

N

DRDC1-6488

Trigger updates implemented

N

DRDC1-6492,

DRDC1-6493

Versioning methods updated

N

DRDC1-6486

Package name update

N

DRDC1-6441

Minor pattern enhancement

N

 

Defects Resolved

The following defects have been fixed in this BMC Discovery Technology Knowledge Update.

Defect No

Details

Product Page

DRDC1-6487

Problem:  Syntax error in OralceRDBMS.tplpre 
Solution: Code fix.

DRDC1-6438

Problem: Pattern issues
Solution: Code fix.

DRDC1-6044

Problem: vCenter Cluster Nodes disappear after scan of vCenter because queries fail  
Solution: Code fix.

DRDC1-6339,

DRDC1-6358 

Problem: Some LDOMs missing information and some LDOM guest domains are not linked to host containers  
Solution: Code fix.

DRDC1-6502

Problem: Oracle WebLogic Application Server pattern path versioning does not correctly handle modern versions  
Solution: Code fix.

Esc 088627

Problem: Citrix Xen UUID are not reliable to use them for linking of VMs. Same Situations when Citrix Xen Server has no UUID at all  
Solution: Code fix.

DRDC1-5969

Problem: Relationship between software components and JDBC rerources is missing   
Solution: Code fix.

DRDC1-6128

Problem: CandidateSoftwareInstance shouldn't be created for interactive SQL clients    
Solution: Code fix.

DRDC1-6444

Problem: VMware vCenter pattern does not handle situation where discovery.vSphereGetLicenses fails    
Solution: Code fix.

DRDC1-6456

Problem : Host_Processor ADDM 11.0+ sync mapping always has no manufacturer for new processor details
Solution
: Code Fix

Command/File Matrix

The Command/File Matrix lists every command executed or file read by a TKU pattern. The workbook contains one worksheet named 'Sheet1' (This will change in TKU August 2016).

This worksheet has the following columns:

Column

Command or FilePath Related

Description

Product

Both

The name of the product as mentioned in the tkn_name metadata within the pattern module

Pattern

Both

The name of the pattern or function (if called from a define block)

Command

Command

The command being executed

Reason

Command

The reason for needing to execute the command

Platform

Command

The platform (Windows, UNIX, Linux, Solaris, AIX, HP-UX, UNIX/Windows) on which the command will be executed

Privileges

Command

A note of whether Discovery requires elevated privileges in order to execute the command

When

Command

A note of the circumstances under which the command will be executed

FilePath

FilePath

The path and leafname of the file being read (or accessed)

Reason

FilePath

The reason for needing to read the file

Platform

FilePath

The platform (Windows, UNIX, Linux, Solaris, AIX, HP-UX, UNIX/Windows) on which the file will be read

Privileges

FilePath

A note of whether Discovery requires elevated privileges in order to read the file

When

FilePath

A note of the circumstances under which the file will be read

TKU Last Updated

Both

The TKU release (e.g. TKU_2016_07_01) in which the pattern or function were last updated

TKU When Command/FilePath Last Changed

Both

The TKU release (e.g. TKU_2016_07_01) in which the command to be executed or file to be read were added or last updated

The format outlined above is considered a legacy format and will be changed for TKU August 2016.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*