Host nodes in the Discovery model are mapped to the Common Data Model as shown in this automatically-generated diagram:
The CIs created are described below.
 | CMDB version differences
The default mapping works with CMDB versions 7.5, 7.6 and 7.6.03 and later. The data model in each is slightly different.
- BMC_Impact relationships are not created with CMDB 7.6.03 and later, since the CMDB automatically maintains them itself.
- With the "CMDB 7.6.03 and later with impact relationships" data model, BMC_Impact relationships are created with Name ImpactOnly rather than IMPACT.
- A number of attributes are not present in CMDB 7.5, as noted below.
|
 | Differences from BMC Atrium Discovery 8.1
Except where noted below, the model populated by BMC Atrium Discovery version 8.2 is the same as that populated by version 8.1. |
BMC_ComputerSystem
The root Host node is mapped to a root BMC_ComputerSystem CI with the following attributes:
| Attribute |
Details |
| Name |
The fully qualified name of the host if available, otherwise the unqualified name; if no names are available, the IP address |
| NameFormat |
"DNS", "HostName" or "IP" |
| ShortDescription |
Host name attribute |
| Description |
The host name and the fully qualified domain name separated by a colon |
| CapabilityList |
A single value corresponding to Server, Desktop, or Laptop |
| Domain |
Host dns_domain – the DNS domain of the host |
| HostName |
Host hostname – the hostname reported by the host |
| isVirtual |
Yes if the host is known to be virtual (or partitioned hardware); not set if not |
| LastScanDate |
Host last_update_success – the date and time the host was last scanned |
| ManufacturerName |
Host vendor – the manufacturer of the host |
| Model |
Host model |
| PrimaryCapability |
Server, Desktop or Laptop |
| SerialNumber |
Host serial |
| SystemType |
Enumeration value corresponding to the system type |
| TokenId |
See TokenId rules below |
| TotalPhysicalMemory |
Host ram – total Host ram |
| VirtualSystemType |
Enumeration value corresponding to the type of virtual machine |
| Workgroup |
Host workgroup – the Windows workgroup |
| Category |
"Hardware" |
| Type |
"Processing Unit" |
| Item |
"Server", "Desktop" or "Laptop" |
TokenId rules
TokenId is an attribute that in some circumstances aids reconciliation of CIs populated by multiple data sources. Discovery sets TokenId for BMC_ComputerSystem. It does not set it for any other class.
For most hosts, TokenId is of the form hostname:DNS domain name.
For some virtual hosts, TokenId contains a UUID:
- For VMware, TokenId is of the form "VI-UUID:ABCD-EF-GH-IJ-KLMNOP". Where each letter represents a hexadecimal digit.
- For Hyper-V, TokenId is of the form "HYPERV-ID:ABCD-EF-GH-IJ-KLMNOP". With Hyper-V, the UUID is only available on the physical machine, so TokenId is only set for virtual machines that have been successfully linked to their hosting physical machines.
- For Xen, TokenId is of the form "XEN-ID:ABCD-EF-GH-IJ-KLMNOP".
BMC_OperatingSystem
The root Host is also mapped to a single BMC_OperatingSystem CI, with the following attributes:
| Attribute |
Details |
| Name |
Host os_type |
| NameFormat |
"OSName" |
| ShortDescription |
"OS type version version on hostname" |
| Description |
Host os |
| ManufacturerName |
Host os_vendor |
| MarketVersion |
Host os_version
This attribute is available only in versions 8.2.02 and later. |
| Model |
Host os_type |
| OSType |
Enumeration value for OS type |
| OSProductSuite |
Enumeration value for OS product suite |
| ServicePack |
Host service_pack |
| VersionNumber |
Host os_version |
| Category |
"Software" |
| Type |
"Operating System Software" |
| Item |
"Standard OS" |
Operating system relationships
| Relationship |
Name |
Source |
Destination |
| BMC_HostedSystemComponents |
SYSTEMOS |
BMC_ComputerSystem |
BMC_OperatingSystem |
| BMC_Impact |
IMPACT |
BMC_OperatingSystem |
BMC_ComputerSystem |
BMC_Processor
The root Host is mapped to a number of BMC_Processor CIs.
- For physical machines, the number of CIs corresponds to the number of physical CPU packages present in the machine.
- For virtual machines, the number of CIs corresponds to the number of logical CPUs the operating system is scheduling across.
In some circumstances, it is not possible to discover the number of physical CPU packages in a physical machine. In such cases, no BMC_Processor CIs are created for the machine.
| Attribute |
Details |
| Name |
"CPUindex" (e.g. "CPU0", "CPU1", etc.) |
| NameFormat |
"ProcessorName" |
| ShortDescription |
Host processor_type |
| Description |
Description of the processor and its index |
| isVirtual |
Yes if the Host is virtual; not set if physical. (Not present in CMDB 7.5.) |
| MaxClockSpeed |
Host processor_speed |
| Model |
Host processor_type |
| NumberOfCores |
Host cores_per_processor (only set for physical machines) |
| NumberOfLogicalProcessors |
Host num_logical_processors / num_processors (only set for physical machines) |
| OtherProcessorFamilyDescription |
Host processor_type (only set if ProcessorFamily is "Other") |
| ProcessorArchitecture |
Enumeration representing the architecture |
| ProcessorFamily |
Enumeration representing the processor family |
| ProcessorStatus |
1 – CPU enabled |
| ProcessorType |
2 – Central processor |
| UpgradeMethod |
1 – Unknown |
| Category |
"Hardware" |
| Type |
"Component" |
| Item |
"CPU" |
| Difference from BMC Atrium Discovery 8.1
BMC Discovery version 8.1 always created one single BMC_Processor CI, regardless of the circumstances. |
Processor relationships
| Relationship |
Name |
Source |
Destination |
| BMC_HostedSystemComponents |
SYSTEMHARDWARE |
BMC_ComputerSystem |
BMC_Processor |
BMC_IPEndpoint and BMC_LANEndpoint
Each NetworkInterface node connected to the root Host in the Discovery model is mapped to a pair of endpoint CIs in the CDM, one BMC_IPEndpoint and one BMC_LANEndpoint.
Where Discovery has been able to connect a NetworkInterface to a NetworkDevice (via associated port nodes), a BMC_Dependency relationship is created between the two BMC_ComputerSystem CIs representing the host and the network device.
BMC_IPEndpoint
| Attribute |
Details |
| Name |
NetworkInterface ip_addr |
| NameFormat |
"IP" |
| ShortDescription |
NetworkInterface ip_addr |
| Description |
"IP address on hostname" |
| Address |
NetworkInterface ip_addr |
| AddressType |
"IPv4" |
| DNSHostName |
NetworkInterface fqdns (first item in list) |
| ProtocolType |
2 – Enumeration value meaning IPv4 |
| SubnetMask |
NetworkInterface netmask |
| ManagementAddress |
True if the IP address was used to scan the host; false if not. (Not in CMDB 7.5.) |
| Category |
"Miscellaneous" |
| Type |
"Address" |
| Item |
"IP Address" |
BMC_LANEndpoint
MAC addresses in the Discovery data model are stored in the conventional form with colons separating each pair of hexadecimal digits; in the CDM, MAC addresses are stored as just the hexadecimal digits, with no separating colons.
| Attribute |
Details |
| Name |
MAC address |
| NameFormat |
"MAC" |
| ShortDescription |
MAC address |
| Description |
"MAC address on hostname" |
| Address |
NetworkInterface ip_addr |
| MACAddress |
MAC address |
| ProtocolType |
"Ethernet" |
| Category |
"Miscellaneous" |
| Type |
"Address" |
| Item |
"MAC Address" |
Endpoint relationships
| Relationship |
Name |
Source |
Destination |
| BMC_HostedAccessPoint |
HOSTEDACCESSPOINT |
BMC_ComputerSystem |
BMC_IPEndpoint |
| BMC_HostedAccessPoint |
HOSTEDACCESSPOINT |
BMC_ComputerSystem |
BMC_LANEndpoint |
| BMC_Dependency |
BINDSTO |
BMC_LANEndpoint |
BMC_IPEndpoint |
| BMC_Dependency |
NETWORKLINK |
BMC_ComputerSystem (network device) |
BMC_ComputerSystem (host) |
| BMC_Impact |
IMPACT |
BMC_ComputerSystem (network device) |
BMC_ComputerSystem (host) |
BMC_IPConnectivitySubnet
Discovery Subnet is mapped to BMC_IPConnectivitySubnet:
| Attribute |
Details |
| Name |
Subnet ip_address_range |
| ShortDescription |
Subnet ip_address_range |
| Description |
Subnet ip_address_range |
Subnet relationships
| Relationship |
Name |
Source |
Destination |
| BMC_InIPSubnet |
INIPSUBNET |
BMC_IPConnectivitySubnet |
BMC_IPEndpoint |
BMC_Cluster
Host Cluster nodes are mapped to BMC_Cluster:
| Attribute |
Details |
| Name |
Cluster name |
| NameFormat |
"ClusterName" |
| Description |
Cluster name |
| ShortDescription |
Cluster name |
Cluster relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Component |
CLUSTEREDSYSTEM |
BMC_Cluster |
BMC_ComputerSystem |
| BMC_Impact |
IMPACT |
BMC_Cluster |
BMC_ComputerSystem |
BMC_VirtualSystemEnabler and virtualization
When a physical machine hosts one or more virtual machines, the Discovery model represents it as a number of SoftwareInstance nodes related to the physical Host, one SoftwareInstance per virtual host. In the CDM, the BMC_ComputerSystem corresponding to the physical machine has a BMC_HostedSystemComponents relationship to a single BMC_VirtualSystemEnabler CI. (Strictly speaking, it is one per technology, so a physical machine running more than one virtualization technology could have more than one BMC_VirtualSystemEnabler CI.)
| Attribute |
Details |
| Name |
BMC_ComputerSystem Name |
| NameFormat |
BMC_ComputerSystem NameFormat |
| ShortDescription |
"VM type on hostname" |
| Description |
"VM type on hostname" |
| BuildNumber |
SoftwareInstance build |
| EnablerType |
Enumeration representing the type of virtualization technology |
| ManufacturerName |
Publisher from the Pattern maintaining the SoftwareInstance |
| Model |
SoftwareInstance type |
| PatchNumber |
SoftwareInstance patch |
| ServicePack |
SoftwareInstance service_pack |
| VersionNumber |
SoftwareInstance version |
| Category |
"Software" |
| Type |
"Operating System Software" |
| Item |
"Virtualization OS" |
Virtualization relationships
| Relationship |
Name |
Source |
Destination |
BMC_Hosted
SystemComponents
Name split to improve presentation. |
HOSTEDSYSTEMCOMPONENTS |
BMC_ComputerSystem (physical) |
BMC_VirtualSystemEnabler |
| BMC_Dependency |
VIRTUALSYSTEMOS |
BMC_VirtualSystemEnabler |
BMC_ComputerSystem (virtual) |
| BMC_Dependency |
HOSTEDVIRTUALSYSTEM |
BMC_ComputerSystem (physical) |
BMC_ComputerSystem (virtual) |
| BMC_Impact |
IMPACT |
BMC_ComputerSystem (physical) |
BMC_VirtualSystemEnabler |
| BMC_Impact |
IMPACT |
BMC_VirtualSystemEnabler |
BMC_ComputerSystem (virtual) |
| BMC_Impact |
IMPACT |
BMC_ComputerSystem (physical) |
BMC_ComputerSystem (virtual) |
BMC_SoftwareServer
Each SoftwareInstance in the Discovery model is mapped to a corresponding BMC_SoftwareServer CI.
| Attribute |
Details |
| Name |
"hostname:type:name" |
| NameFormat |
"HostName:Model:Name" |
| ShortDescription |
SoftwareInstance name |
| Description |
SoftwareInstance name |
| BuildNumber |
SoftwareInstance build |
| ManufacturerName |
Publisher specified in the maintaining Pattern |
| MarketVersion |
SoftwareInstance product_version
This attribute is available only in versions 8.2.02 and later. |
| Model |
SoftwareInstance type |
| OtherSoftwareServerType |
SoftwareInstance type |
| PatchNumber |
SoftwareInstance patch |
| ServicePack |
SoftwareInstance service_pack |
| SoftwareServerType |
Enumeration representing the type of SoftwareServer. Often 0 meaning "Other". |
| VersionNumber |
SoftwareInstance version |
| Category |
"Software" |
| Type |
"Application" |
| Item |
Product category from the maintaining Pattern |
Note that SoftwareInstance nodes are also mapped (in an indirect manner) to BMC_Product.
| Item values
The Item attribute is populated from the Pattern that is maintaining the SoftwareInstance. To obtain a list of all the possible Item values, perform the following query in the Discovery Generic Query page:
search Pattern show categories processwith countUnique(0)
|
| Differences from BMC Atrium Discovery 8.1
BMC Atrium Discovery version 8.2 maps all SoftwareInstance nodes to BMC_SoftwareServer. Vesion 8.1 mapped those SoftwareInstances containing other SoftwareInstances to BMC_ApplicationInfrastructure.
Version 8.1 always hard-coded Item to "BMC Discovered"; 8.2 populates it with a more specific value. |
Software Server relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Dependency |
APPLICATIONSYSTEMCOMPUTER |
BMC_ComputerSystem |
BMC_SoftwareServer |
| BMC_Component |
APPLICATIONSYSTEMHIERARCHY |
BMC_SoftwareServer (containing) |
BMC_SoftwareServer (contained) |
| BMC_Dependency |
APPLICATIONSYSTEMDEPENDENCY |
BMC_SoftwareServer (depended upon) |
BMC_SoftwareServer (dependant) |
| BMC_Impact |
IMPACT |
BMC_ComputerSystem |
BMC_SoftwareServer |
| BMC_Impact |
IMPACT |
BMC_SoftwareServer (contained) |
BMC_SoftwareServer (containing) |
As shown in the table, BMC_SoftwareServer CIs can be related to each other with a BMC_Dependency relationship. This is mapped from both Dependency and Communication relationships between the SoftwareInstance nodes in the Discovery model.
BMC_SoftwareServer CIs also have relationships to BMC_Product, shown in the table below.
BMC_Product
BMC_Product represents the installed aspects of a product. BMC Atrium Discovery uses SoftwareInstance nodes and associated metadata to provide an accurate picture of the installed products, regardless of how the products are installed. The mapping groups the SoftwareInstance nodes according to the product information on the maintaining patterns, and maintains one BMC_Product CI for each unique product on the Host. SoftwareInstance nodes with different types can belong to a single product. So, for example, a server running four Oracle database instances and one Oracle TNS Listener would have five SoftwareInstance nodes; those five SoftwareInstances would map to a single "Oracle Database" BMC_Product CI.
| Attribute |
Details |
| Name |
"product name:product version" |
| NameFormat |
"ProductName:Version" |
| ShortDescription |
"product name product version" |
| Description |
"product name product version on hostname" |
| BuildNumber |
SoftwareInstance build |
| ManufacturerName |
Publisher from Pattern |
| MarketVersion |
SoftwareInstance product_version
This attribute is available only in versions 8.2.02 and later. |
| Model |
Product name from Pattern |
| PatchNumber |
SoftwareInstance patch |
| ServicePack |
SoftwareInstance service_pack |
| VersionNumber |
SoftwareInstance product_version |
| Category |
"Software" |
| Type |
"Application" |
| Item |
Product category from the maintaining Pattern |
| Item values
The Item attribute is populated from the Pattern that is maintaining the SoftwareInstance. To obtain a list of all the possible Item values, perform the following query in the Discovery Generic Query page:
search Pattern show categories processwith countUnique(0)
|
| Difference from BMC Atrium Discovery 8.1
BMC Atrium Discovery version 8.1 always hard-coded Item to "BMC Discovered"; 8.2 populates it with a more specific value. |
Product relationships
| Relationship |
Name |
Source |
Destination |
BMC_Hosted
SystemComponents
Name split to improve presentation. |
INSTALLEDSOFTWARE |
BMC_ComputerSystem |
BMC_Product |
| BMC_Dependency |
APPLICATIONSYSTEMPRODUCT |
BMC_Product |
BMC_SoftwareServer |
BMC_ApplicationService
SoftwareComponent is mapped to BMC_ApplicationService.
| Name |
SoftwareComponent name |
| ShortDescription |
SoftwareComponent name |
| Description |
SoftwareComponent name |
| Model |
SoftwareComponent type |
| VersionNumber |
SoftwareComponent version |
| ApplicationServiceType |
Enumeration value representing the service type |
Application service relationships
| Relationship |
Name |
Source |
Destination |
BMC_Application
SystemServices
Name split to improve presentation. |
APPLICATIONSYSTEMSERVICES |
BMC_SoftwareServer |
BMC_ApplicationService |
BMC_Application
BusinessApplicationInstance is mapped to BMC_Application. Contained SoftwareInstance and BusinessApplicationInstance nodes are mapped to corresponding BMC_Component relationships.
| Name |
BusinessApplicationInstance name |
| ShortDescription |
BusinessApplicationInstance name |
| Description |
BusinessApplicationInstance name |
| MarketVersion |
BusinessApplicationInstance product_version
This attribute is available only in versions 8.2.02 and later. |
| Model |
BusinessApplicationInstance type
This attribute is available only in versions 8.2.02 and later. |
| VersionNumber |
BusinessApplicationInstance version
This attribute is available only in versions 8.2.02 and later. |
| Category |
"Software" |
| Type |
"Application" |
| Item |
"Application Platform" |
Application relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Dependency |
APPLICATIONSYSTEMCOMPUTER |
BMC_ComputerSystem |
BMC_Application |
| BMC_Component |
APPLICATIONSYSTEMHIERARCHY |
BMC_Application |
BMC_SoftwareServer |
| BMC_Component |
APPLICATIONSYSTEMHIERARCHY |
BMC_Application (containing) |
BMC_Application (contained) |
| BMC_Impact |
IMPACT |
BMC_ComputerSystem |
BMC_Application |
| BMC_Impact |
IMPACT |
BMC_SoftwareServer |
BMC_Application |
| BMC_Impact |
IMPACT |
BMC_Application (contained) |
BMC_Application (containing) |
Classes no longer populated
| Differences from BMC Atrium Discovery 8.1
In addition to the changes outlined above, the following classes were populated in 8.1, but are not populated in 8.2:
- BMC_VirtualSystemSettingData: BMC Atrium Discovery does not currently discover any attributes of this class that are not already stored on the BMC_ComputerSystem CI.
- BMC_DataBase: Version 8.1 incorrectly created one BMC_DataBase for each database SoftwareInstance. If it is to be populated at all, it should be populated with one CI per logical database. Version 8.2 chooses not to map databases in this way.
- BMC_ConnectivitySegment: Version 8.1 incorrectly mapped IP subnet information to BMC_ConnectivitySegment as well as to BMC_IPConnectivitySubnet. It is intended for layer-2 network information, rather than IP (layer-3) information. Version 8.2 chooses not to populate such layer-2 information.
|
Tideway Blog
2 Comments
comments.show.hideSep 20, 2010
Petrus Johansson
Comment to my previous post:
If anyone is interested I have a Product Catalogue Alias Mapping spreadsheet (ready to be loaded to Remedy with DataLoad tool) with mapping data between BMC ADDM Pattern Categorizations to BMC Best Practice Categorization: (Available in the BMC Atrium CMDB 7.5.00 Data Modeling Guide @ https://docs.google.com/viewer?url=http://documents.bmc.com/supportu/documents/77/40/97740/97740.pdf
Mar 02, 2011
Rocco Padula
I would appreictae looking at that spreadsheet if you can post it again. the link provided does not seem to be working. thank you.