CDM Mapping for Host

This topic provides information for CDM mapping for Host nodes.

Host nodes in the Discovery model are mapped to the Common Data Model (CDM) as shown in this automatically-generated diagram:

This diagram illustrates how the Host nodes in the Discovery model are mapped to the Common Data Model.

The CIs created are described in this topic.

Data models

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 normally created with CMDB 7.6.03 and later, since the CMDB automatically maintains them itself. See the information about impact relationships for more details.
  • A number of attributes are not present in CMDB 7.5, as noted below.
 Click here for reference information on impact and the data models.

Different versions of the CMDB have subtly different data models. Syncmappings can support multiple data models with datamodel declarations. CMDB data models are assigned simple integer values:

Data modelCMDB versionsEffect

6

7.6.03 and later

HasImpact and ImpactDirection attributes are set as appropriate.

5

7.6.03 and later

Only to be used with legacy SIM version 7.4. BMC_Impact relationships with Name “ImpactOnly” are created.

4

7.6.03 and later

No impact details are set by BMC Atrium Discovery. They may be set by Impact Normalization in the CMDB.

3

7.6 before 7.6.03

BMC_Impact relationships with name “IMPACT” are created.

2

7.5

BMC_Impact relationships with name “IMPACT” are created.

Differences from previous versions of BMC Atrium Discovery

  • Except where noted below, the model populated by BMC Atrium Discovery version 9.0 is the same as that populated by earlier versions.
  • Starting from version 10.0, in the model populated by BMC Atrium Discovery, the ram attribute is now used for storing the physical memory volume and the new logical_ram attribute is added for the reported logical memory volume.

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); null 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

PartitionId

Host partition_id – the identifier of a partition host (new in CMDB 8.1) - from TKU 2014-Mar-1 onwards

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. The following describes how discovery sets TokenId for BMC_ComputerSystem.

For most hosts, TokenId is of the form hostname:DNS domain name.

For some virtual hosts, TokenId contains a UUID:

  1. For VMware, TokenId is of the form "VI-UUID:ABCD-EF-GH-IJ-KLMNOP". Where each letter represents a hexadecimal digit.
  2. 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.
  3. For Xen (including Oracle VM), TokenId is of the form "XEN-ID:ABCD-EF-GH-IJ-KLMNOP".
  4. For KVM (including RedHat Enterprise Virtualization), TokenId is of the form "KVM-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 on hostname"

Description

Host os

ManufacturerName

Host os_vendor

MarketVersion

Host os_version

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

"Operating System"

Operating system relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents

SYSTEMOS

BMC_ComputerSystem

BMC_OperatingSystem

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 OS 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.

All the BMC_Processor CIs for a host are normally identical to each other. New in BMC Atrium Discovery 8.3, they can be different in cases that a physical machine has more than one type of CPU.

Attribute

Details

Name

"CPUindex" (for example, "CPU0", "CPU1", and so on.)

NameFormat

"ProcessorName"

ShortDescription

Host processor_type

Description

Description of the processor and its index

isVirtual

True if the Host is virtual; not set if physical. (Not present in CMDB 7.5.)

ManufacturerName

Manufacturer of the processor. (New in ADDM 8.3.)

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_NetworkPort, BMC_IPEndpoint and BMC_LANEndpoint

Each Network Interface node connected to the root Host in the Discovery model is mapped to a BMC_NetworkPort CI, and its MAC address is mapped to a BMC_LANEndpoint CI. Each of its associated IP addresses are mapped to BMC_IPEndpoint CIs.

Where Discovery has been able to connect a Network Interface node to a Network Device node (via associated port nodes), a BMC_Dependency relationship is created between the two BMC_ComputerSystem CIs representing the host and the network device.

BMC_NetworkPort

Attribute

Details

Name

NetworkInterface interface_name

ShortDescription

NetworkInterface interface_name

Description

NetworkInterface name"

AutoSense

Yes (0) or No (1) or null if not known

FullDuplex

Yes (0) or No (1) or null if not known

LinkTechnology

Ethernet (2)

ManufacturerName

NetworkInterface manufacturer

PermanentAddress

NetworkInterface mac_addr

PortType

Ethernet (2)

Speed

NetworkInterface raw_speed

Category

"Hardware"

Type

"Card"

Item

"Network interface card"

Each Fibre Channel HBA card node is mapped to the BMC_NetworkPort CI with the following attributes:

AttributeDetails
NameFibreChannelHBA description and FibreChannelPort wwpn or just FibreChannelPort wwpn
ShortDescriptionFibreChannelPort wwpn
DescriptionFibreChannelHBA description and FibreChannelPort wwpn or just FibreChannelPort wwpn
LinkTechnologyFibre Channel (4)
ManufacturerNameFibreChannelHBA vendor
ModelFibreChannelHBA model
PermanentAddressFibreChannelPort wwpn
PortTypeFibre Channel (6)
SerialNumberFibreChannelHBA serial
Category“Hardware”
Type“Card”
Item“Fibre Channel HBA card” 

Differences from earlier BMC Atrium Discovery versions

BMC_NetworkPort was not created in versions prior to 8.3.

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

NetworkInterface mac_addr

NameFormat

"MAC"

ShortDescription

NetworkInterface mac_addr

Description

"MAC address on hostname"

Address

MAC address (no separating colons)

MACAddress

MAC address (no separating colons)

ProtocolType

Ethernet (14)

Category

"Network"

Type

"Address"

Item

"MAC Address"

Differences from earlier BMC Atrium Discovery versions

Prior to version 8.3, Category was set to "Miscellaneous" instead of "Network," and Address was set to the "IP address", not the MAC address.

BMC_IPEndpoint

Attribute

Details

Name

IP Address ip_addr

NameFormat

"IP"

ShortDescription

IP Address ip_addr

Description

IP Address name

Address

IP Address ip_addr

AddressType

IPv4 (1) or IPv6 (2)

DNSHostName

IP Address fqdns (first item in list)

ProtocolType

IPv4 (2) or IPv6 (3)

SubnetMask

IP Address netmask

ManagementAddress

Yes (1) if the IP address was used to scan the host; No (0) if not. (Not in CMDB 7.5.)

Category

"Network"

Type

"Address"

Item

"IP Address"

Differences from earlier BMC Atrium Discovery versions

Prior to version 8.3, Category was set to "Miscellaneous" instead of "Network".

NetworkPort and Endpoint relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents

SYSTEMHARDWARE

BMC_ComputerSystem

BMC_NetworkPort

BMC_HostedAccessPoint

HOSTEDACCESSPOINT

BMC_ComputerSystem

BMC_IPEndpoint

BMC_HostedAccessPoint

HOSTEDACCESSPOINT

BMC_ComputerSystem

BMC_LANEndpoint

BMC_Dependency

ENDPOINTPORT

BMC_NetworkPort

BMC_IPEndpoint

BMC_Dependency

ENDPOINTPORT

BMC_NetworkPort

BMC_LANEndpoint

BMC_Dependency

BINDSTO

BMC_LANEndpoint

BMC_IPEndpoint

BMC_Dependency

NETWORKLINK

BMC_ComputerSystem (network device)

BMC_ComputerSystem (host)

Impacted

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

AddressType

IPv4 (1) or IPv6 (2)

PrefixLength

IP Address prefix_length

SubnetMask

IP Address netmask

SubnetNumber

Subnet ip_address_range

Category

"Network"

Type

"Subnet"

Item

"TCP/IP"

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

Category

"Unknown"

Type

"Unknown"

Item

"BMC Discovered"

Cluster relationships

Relationship

Name

Source

Destination

BMC_Component

CLUSTEREDSYSTEM

BMC_Cluster

Impacted

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 Software Instance nodes related to the physical Host, one Software Instance 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

Software Instance name

ShortDescription

"VM type on hostname"

Description

"VM type on hostname"

BuildNumber

Software Instance build

EnablerType

Enumeration representing the type of virtualization technology

ManufacturerName

Publisher from the Pattern maintaining the Software Instance

MarketVersion

Software Instance product_version

Model

Software Instance type

PatchNumber

Software Instance patch

ServicePack

Software Instance service_pack

VersionNumber

Software Instance version

Category

"Software"

Type

"Operating System Software"

Item

"Virtualization OS"

Differences from earlier BMC Atrium Discovery versions

Prior to version 8.3, Name was set to the BMC_ComputerSystem Name.

Virtualization relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents

HOSTEDSYSTEMCOMPONENTS

BMC_ComputerSystem (physical)

BMC_VirtualSystemEnabler

Impacted

BMC_Dependency

VIRTUALSYSTEMOS

BMC_VirtualSystemEnabler

BMC_ComputerSystem (virtual)

Impacted

BMC_Dependency

HOSTEDVIRTUALSYSTEM

BMC_ComputerSystem (physical)

BMC_ComputerSystem (virtual)

Impacted

BMC_HardwareSystemComponent.

Any Management Controller node with a direct Management relationship to the root Host in the Discovery model is mapped to a BMC_HardwareSystemComponent CI.

Any ManagementController for a HostContainer containing the root Host in the Discovery model is mapped to BMC_HardwareSystemComponent.

There is no way to map the ManagementController's IP information to the CDM.

BMC_HardwareSystemComponent

Attribute

Details

Name

Management controller name.

NameFormat

"HostName"

ShortDescription

Management controller name.

Description

Vendor name, controller model and type. With serial if known.

ManufacturerName

Management controller vendor name.

VersionNumber

Management controller version number.

Model

Management controller model.

PowerManagementSupported

Yes (0) or null if not known.

Company

Host Company.

Category

"Hardware"

Type

"Hardware"

Item

"Management controller" where managed element is a directly connected host.
"Chassis manager" where the managed element is a chassis.

Hardware system component relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents

SYSTEMHARDWARE

BMC_ComputerSystem

BMC_HardwareSystemComponent

BMC_ComputerSystem (Host Container)

HostContainer nodes are mapped to BMC_ComputerSystem representing the partitioned container.

Attribute

Details

Name

Host Container name

ShortDescription

Host Container name

Description

Host Container name

CapabilityList

"Blade System" (48) or "Other" (2)

LastScanDate

Host last_update_success

ManufacturerName

Host Container vendor

Model

Host Container model

OtherCapabilityDescription

Host Container type

PrimaryCapability

"Blade System" (48) or "Other" (2)

SerialNumber

Host Container serial

Category

"Hardware"

Type

"Hardware"

Item

HadwareContainer type

TokenId

Attribute that aids reconciliation of CIs populated by multiple data sources.
TokenId is of the form "ADDM:hashedkey", where hashedkey is a hash of HostContainer key

Host containment relationships

Relationship

Name

Source

Destination

BMC_Component

SYSTEMPARTITION

BMC_ComputerSystem (container)

BMC_ComputerSystem (contained)

Impacted

BMC_SoftwareServer and BMC_ApplicationSystem

Each SoftwareInstance in the Discovery model is mapped to either a BMC_SoftwareServer CI or a BMC_ApplicationSystem CI:

  • SoftwareInstance nodes with DDD triggers are directly running on a single host, and are mapped to BMC_SoftwareServer
  • SoftwareInstance nodes composed of other SoftwareInstance nodes are mapped to BMC_ApplicationSystem.

SoftwareInstance nodes are also mapped (in an indirect manner) to BMC_Product.

Except as noted, the attributes set are the same in BMC_SoftwareServer and BMC_ApplicationSystem.

Attribute

Details

Name

Software Instance name

ShortDescription

Software Instance name

Description

Software Instance name

BuildNumber

Software Instance build

ManufacturerName

Publisher specified in the maintaining Pattern or on the Software Instance

MarketVersion

Software Instance product_version

Model

Software Instance type

OtherSoftwareServerType

Software Instance type (Only in BMC_SoftwareServer)

PatchNumber

Software Instance patch

ServicePack

Software Instance service_pack

SoftwareServerType

Enumeration representing the type of SoftwareServer. Often 0 meaning "Other". (Only in BMC_SoftwareServer)

VersionNumber

Software Instance 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 Software Instance. 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 earlier BMC Atrium Discovery versions

Prior to version 8.3, Name was set to "hostname:type:name".

Version 8.2 mapped all SoftwareInstance nodes to BMC_SoftwareServer. Version 8.1 mapped those SoftwareInstances containing other SoftwareInstances to BMC_ApplicationInfrastructure.

Version 8.1 always hard-coded Item to "BMC Discovered".

BMC_SoftwareServer and BMC_ApplicationSystem relationships

Relationship

Name

Source

Destination

BMC_Dependency

APPLICATIONSYSTEMCOMPUTER

BMC_ComputerSystem

BMC_SoftwareServer

Impacted

BMC_Dependency

APPLICATIONSYSTEMCOMPUTER

BMC_ComputerSystem

BMC_ApplicationSystem

BMC_Component

APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationSystem (containing)

Impacted

BMC_SoftwareServer (contained)

BMC_Dependency

APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer or BMC_ApplicationSystem (depended upon)

BMC_SoftwareServer or BMC_ApplicationSystem (dependant)

Impacted

As shown in the table, BMC_SoftwareServer and BMC_ApplicationSystem 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 and BMC_ApplicationSystem 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 version 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

Software Instance build

ManufacturerName

Publisher from Pattern or SoftwareInstance

MarketVersion

Software Instance product_version

Model

Product name from Pattern or SoftwareInstance

PatchNumber

Software Instance patch

ServicePack

Software Instance service_pack

VersionNumber

Software Instance version (in CMDB 7.6.03 and later) or product_version

Category

"Software"

Type

"Software Application/System"

Item

Product category from the maintaining Pattern

Item values

The Item attribute is populated from the Pattern that is maintaining the Software Instance. 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".

Product relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents

INSTALLEDSOFTWARE

BMC_ComputerSystem

BMC_Product

BMC_Dependency

APPLICATIONSYSTEMPRODUCT

BMC_Product

BMC_SoftwareServer

BMC_Dependency

APPLICATIONSYSTEMPRODUCT

BMC_Product

BMC_ApplicationSystem

BMC_ApplicationService

SoftwareComponent is mapped to BMC_ApplicationService.

Attribute

Details

Name

Software Component name

ShortDescription

Software Component name

Description

Software Component name

Model

Software Component type

VersionNumber

Software Component version

ApplicationServiceType

Enumeration value representing the service type

Category

"Software"

Type

"Application Service"

Item

"BMC Discovered"

Application service relationships

Relationship

Name

Source

Destination

BMC_ApplicationSystemServices

APPLICATIONSYSTEMSERVICES

BMC_SoftwareServer

BMC_ApplicationService

BMC_DataBase

DatabaseDetail nodes representing logical databases are mapped to BMC_DataBase:

Attribute

Details

Name

DatabaseDetail name

ShortDescription

DatabaseDetail instance

Description

DatabaseDetail name

ManufacturerName

Software Instance vendor

MarketVersion

Software Instance product_version

Model

DatabaseDetail type

PatchNumber

Software Instance patch

ServicePack

Software Instance service_pack

VersionNumber

Software Instance version

Category

"Miscellaneous"

Type

"Instance"

Item

"Database"

BMC_DataBase relationships

Relationship

Name

Source

Destination

BMC_Dependency

MANAGEDDATABASE

BMC_SoftwareServer

BMC_DataBase

Impacted

Differences from earlier BMC Atrium Discovery versions

BMC_DataBase was not created in version 8.2.

BMC_Application

BusinessApplicationInstance is mapped to BMC_Application. Contained SoftwareInstance and BusinessApplicationInstance nodes are mapped to corresponding BMC_Component relationships.

Attribute

Details

Name

Business Application Instance name

ShortDescription

Business Application Instance name

Description

Business Application Instance name

MarketVersion

Business Application Instance product_version

Model

Business Application Instance type

VersionNumber

Business Application Instance version

Category

"Software"

Type

"Application"

Item

"Application Platform"

Application relationships

Relationship

Name

Source

Destination

BMC_Dependency

APPLICATIONSYSTEMCOMPUTER

BMC_ComputerSystem

BMC_Application

Impacted

BMC_Component

APPLICATIONSYSTEMHIERARCHY

BMC_Application

Impacted

BMC_SoftwareServer

BMC_Component

APPLICATIONSYSTEMHIERARCHY

BMC_Application

Impacted

BMC_ApplicationSystem

BMC_Component

APPLICATIONSYSTEMHIERARCHY

BMC_Application (containing)

Impacted

BMC_Application (contained)

BMC_ConcreteCollection

FunctionalComponent nodes representing CAM Functional Components are mapped to BMC_ConcreteCollection.

Attribute

Details

Name

Functional Component name

ShortDescription

Functional Component name

Description

Functional Component name

Model

Functional Component type

Company

Host Company

Category

"Software"

Type

"Application"

Item

"Functional Component"

Functional Component relationships

Relationship

Name

Source

Destination

BMC_Component

ITEMINFUNCTIONALCOMPONENT

BMC_ConcreteCollection

BMC_SoftwareServer First-order SI.

BMC_Component

ITEMINFUNCTIONALCOMPONENT

BMC_ConcreteCollection

BMC_ApplicationSystem Second-order SI.

BMC_Component

ITEMINFUNCTIONALCOMPONENT

BMC_ConcreteCollection

BMC_DataBase

BMC_Component

ITEMINFUNCTIONALCOMPONENT

BMC_ConcreteCollection

BMC_Application

BMC_Component

ITEMINFUNCTIONALCOMPONENT

BMC_ConcreteCollection

BMC_ApplicationService

BMC_Component

FUNCTIONALCOMPONENTINAPPLICATION

BMC_Application

BMC_ConcreteCollection

The relationship between BMC_Application and BMC_ConcreteCollection is used for Functional Components reached from any of the following node kinds:

  • SoftwareInstance
  • DatabaseDetail
  • BAI
  • SoftwareComponent
Was this page helpful? Yes No Submitting... Thank you

Comments