This documentation supports the 20.02 (12.0) version of BMC Discovery.To view an earlier version of the product, select the version from the Product version menu.

CDM Mapping for Host

This topic provides information for CDM mapping for Host nodes. The CIs created are described in this topic.

BMC_ComputerSystem

A 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 hostname as reported by the OS; if no names are available, then 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, or if the fully qualified domain name is not available, then just the host name.

CapabilityList

A single value corresponding to Server, Desktop, Laptop, or Other

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

isCloud

Yes if the host is known to be cloud hosted; 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, Mainframe, or Laptop

SerialNumber

Host serial

PartitionId

Host partition_id – the identifier of a partition host

TokenId

TotalPhysicalMemory

Host ram — total Host ram

VirtualSystemType

Enumeration value corresponding to the type of virtual machine

Workgroup

Host workgroup — the Windows workgroup

ComponentAliases

 BMC_ComputerSystem:hostname

Category

"Hardware"

Type

"Processing unit"

Item

"Server", "Desktop" or "Laptop"

Relationship

Name

Source

Destination

BMC_Dependency
STORAGEUSE

BMC_ComputerSystem (Storage system)

BMC_ComputerSystem (Host)
impacted

BMC_Dependency
BACKENDSTORAGEUSE

BMC_ComputerSystem (Backend Storage system)

BMC_ComputerSystem (Host)
impacted

BMC_HostedSystemComponents
SYSTEMHARDWARE
BMC_ComputerSystem (Host)
BMC_HardwareSystemComponent

BMC_DependencyIntroduced in January 2021 TKU.

NETWORKLINK

BMC_ComputerSystem (Network Device (SAN Switch))
impacted

BMC_ComputerSystem (Host)

BMC_OperatingSystem

The root Host is also mapped to a single BMC_OperatingSystem CI, with the following attributes:

Attribute

Details

Name

Host os_name or
Host os_name : hostname if the target is Remedyforce.

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

Company

Host Company

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, though they can be different in cases that a physical machine has more than one type of CPU.

If BMC Discovery ProcessorInfo nodes are not present, the system reverts to the previous (before version 11.0 mapping) using Host node attributes.

Note

This mapping is unusual, in that it creates a number of BMC_Processor CIs corresponding to the number of processors in a Host, stored as numeric attributes. As a result, you cannot modify the created CIs with an extension mapping in the usual way with "mapping from", because there is no suitable traversal loop to extend. Instead, if you wish to make modifications, you should copy this mapping to a new file with a new name, then declare that it "overrides" this one in its overview block.


Attribute

Details

Name

Host CPUindex or
Host CPUindex : hostname if the target is Remedyforce.
CPUindex is, for example, "CPU0", "CPU1", and so on.)

NameFormat

"ProcessorName"

ShortDescription

Host processor_type or "Unknown CPU"

Description

Description of the processor, its index, and host

isVirtual

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

ManufacturerName

Manufacturer of the processor.

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

Company

Host Company

Category

"Hardware"

Type

"Component"

Item

"CPU"

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 BMC 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 BMC 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

Key

NetworkInterface key.

Name

NetworkInterface interface_name or
NetworkInterface "interface_name : hostname" if the target is Remedyforce.

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

Company

HostCompany

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:

Attribute

Details

Key

"%hba_node.key%/%fcp_node.wwpn%" or
Fibre Channel Port node key if the target is Remedyforce.

Name

FibreChannelHBA description and FibreChannelPort wwpn and hostname or
FibreChannelHBA description or
FibreChannelHBA description and hostname if the target is Remedyforce.

ShortDescription

FibreChannelPort wwpn

Description

FibreChannelHBA description and FibreChannelPort wwpn or just FibreChannelPort wwpn

LinkTechnology

Fibre Channel (4)

ManufacturerName

FibreChannelHBA vendor

Model

FibreChannelHBA model

PermanentAddress

FibreChannelPort wwpn

PortType

Fibre Channel (6)

SerialNumber

FibreChannelHBA serial

Company

HostCompany

Category

“Hardware”

Type

“Card”

Item

“Fibre Channel HBA card” 

BMC_NetworkPort relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
SYSTEMHARDWARE
BMC_ComputerSystem
BMC_NetworkPort

BMC_LANEndpoint

MAC addresses in the BMC 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

Key

"%host.key%/MAC/%mac_addr%" or
NertworkInterface key if the target is Remedyforce.

Name

NetworkInterface mac_addr : or
NetworkInterface "mac_addr : interface_name: hostname" if the target is Remedyforce.

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)

Company

HostCompany

Category

"Network"

Type

"Address"

Item

"MAC Address"

BMC_LANEndpoint relationships

Relationship

Name

Source

Destination

BMC_HostedAccessPoint
HOSTEDACCESSPOINT
BMC_ComputerSystem
BMC_LANEndpoint
BMC_Dependency
ENDPOINTPORT
BMC_NetworkPort
BMC_LANEndpoint

BMC_IPEndpoint

Attribute

Details

Key

"%host.key%/IP/%ip_addr%" or
IPAddress key if the target is Remedyforce.

Name

NetworkInterface IP address or
NetworkInterface IP address : hostname if the target is Remedyforce.

NameFormat

"IP"

ShortDescription

IP Address ip_addr

Description

IP Address name

AddressType

IPv4 (1) or IPv6 (2)

Address

IP Address ip_addr

DNSHostName

IP Address fqdns (first item in list)

ManagementAddress

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

ProtocolType

IPv4 (2) or IPv6 (3)

PrefixLength

IP Address prefix_length

SubnetMask

IP Address netmask

Company

HostCompany

Category

"Network"

Type

"Address"

Item

"IP Address"

BMC_IPEndpoint relationships

Relationship

Name

Source

Destination

BMC_HostedAccessPoint
HOSTEDACCESSPOINT
BMC_ComputerSystem
BMC_IPEndpoint
BMC_Dependency
ENDPOINTPORT
BMC_NetworkPort
BMC_IPEndpoint
BMC_Dependency
BINDSTO
BMC_LANEndpoint
BMC_IPEndpoint

BMC_IPConnectivitySubnet

BMC Discovery Subnet nodes are mapped to BMC_IPConnectivitySubnet:

Attribute

Details

Name

Subnet ip_address_range

ShortDescription

Subnet ip_address_range

Description

Subnet ip_address_range

SubnetNumber

Subnet ip_address_range

AddressType

IPv4 (1) or IPv6 (2)

PrefixLength

IP Address prefix_length

SubnetMask

IP Address netmask

Company

HostCompany

Category

"Network"

Type

"Subnet"

Item

"TCP/IP"

Subnet relationships

Relationship

Name

Source

Destination

BMC_InIPSubnet
INIPSUBNET
BMC_IPConnectivitySubnet
BMC_IPEndpoint

BMC_Cluster

Host cluster

Host Cluster nodes are mapped to BMC_Cluster:

Attribute

Details

TokenId

Name

Cluster name

NameFormat

"ClusterName"

InstanceName

  • Microsoft Cluster:<cluster name>
  • vCenter Cluster:<hostname of vCenter server>:<DNS domain>

ManufacturerName

The manufacturer name.

Model

The cluster type

Description

Cluster name

ShortDescription

Cluster name

ComponentAliases

Cluster cdm_component_aliases

Company

HostCompany

Category

"Unknown"

Type

"Unknown"

Item

"BMC Discovered"

Host Cluster relationships

Relationship

Name

Source

Destination

BMC_Component
CLUSTEREDSYSTEM

BMC_Cluster 
Impacted

BMC_ComputerSystem
BMC_Component
CLUSTEREDSYSTEM

BMC_Cluster 
Impacted

BMC_ComputerSystem(NetworkDevice)

BMC_Dependency
CLUSTERMANAGER

BMC_Cluster

BMC_Cluster 
Managed cluster
Impacted

BMC_Dependency
CLUSTERMANAGER
BMC_Cluster

BMC_Cluster 
Managed cluster
Impacted

Software cluster

Software Cluster nodes are mapped to BMC_Cluster:

Attribute

Details

TokenId

Name

Software Cluster name

ShortDescription

Cluster name

Description

Cluster name

InstanceName

  • Microsoft Cluster:<cluster name>
  • vCenter Cluster:<hostname of vCenter server>:<DNS domain>


ManufacturerName

Publisher from the Pattern maintaining the Software Cluster

MarketVersion

Software Cluster product_version

Model

Software Cluster type

PatchNumber

Software Cluster patch

VersionNumber

Software Cluster {{code language="none"}}
version
{{/code}}

ComponentAliases

Software Cluster cdm_component_aliases

Company

HostCompany

Category

"Software"

Type

"Cluster"

Item

Category specified in the maintaining Pattern or "BMC Discovered"

Software Cluster relationships

Relationship

Name

Source

Destination

BMC_Component
SOFTWARECLUSTER

BMC_Cluster 
Impacted

BMC_SoftwareServer First-order SI.

BMC_Component
SOFTWARECLUSTER

BMC_Cluster 
Impacted

BMC_ApplicationSystem Second-order SI.

BMC_IPEndpoint (Cluster)

ClusterService node IP addresses are mapped to BMC_IPEndpoint CIs.

Attribute

Details

Name

IP Address or
IP address : Cluster name if the target is Remedyforce.

NameFormat

"IP"

ShortDescription

Cluster service name name

Description

"ClusterService name:IP address"

AddressType

IPv4 (1) or IPv6 (2)

Address

IP Address ip_addr

ProtocolType

IPv4 (2) or IPv6 (3)

Company

HostCompany

Category

"Network"

Type

"Address"

Item

"IP Address"

IP address relationships

Relationship

Name

Source

Destination

BMC_HostedAccessPoint

HOSTEDACCESSPOINT
BMC_Cluster
{{code language="none"}}
BMC_IPEndpoint
{{/code}}

BMC_Dependency

ADDRESSOFSYSTEMRESOURCE
BMC_SystemResource
BMC_IPEndpoint

BMC_SystemResource (Cluster)

ClusterService node IP addresses are also mapped to BMC_SystemResource CIs.

Attribute

Details

key

cluster_service.key

Name

ClusterService name: DNS name or
ClusterService name or
ClusterService name: Cluster name if the target is Remedyforce.

ShortDescription

ClusterService name

Description

ClusterService name: DNS name" or
"ClusterService name"

ResourceType

Cluster Resource Group (2)

Company

HostCompany

Category

"Unknown"

Type

"Unknown"

Item

"BMC Discovered"

Relationship

Name

Source

Destination

BMC_HostedSystemComponents

SYSTEMRESOURCES
BMC_Cluster

BMC_SystemResource
(Impacted)

BMC_Dependency

USERESOURCE
BMC_SystemResource

BMC_SoftwareServer
(Impacted)

BMC_LogicalSystemComponent (Cluster)

LoadBalancerService nodes are mapped to BMC_LogicalSystemComponent CIs. 

Attribute

Details

key

Load balancer service key

TokenId

"ADDM:%lb_service.key%"
See TokenId rules.

Name

Load balancer service name

ShortDescription

Load balancer service name

Description

Load balancer service name

isCloud

Load balancer service cloud

Company

Cluster Company

Category

"Network"

Type

"Service"

Item

"Load balancer service"

Relationship

Name

Source

Destination

BMC_Dependency

LOADBALANCERSERVICE
BMC_Cluster

BMC_LogicalSystemComponent 
(Impacted)

BMC_ResourcePool (Cluster)

LoadBalancerPool nodes are mapped to BMC_ResourcePool CIs. 

Attribute

Details

key

Load balancer pool key

TokenId

"ADDM:%lb_pool.key%"
See TokenId rules.

Name

Load balancer pool name

ShortDescription

Load balancer pool name

Description

Load balancer pool name

ResourceType

0 (Other)

OtherResourceType

"Load Balancer Pool"

Company

Cluster Company

Category

"Network"

Type

"Service"

Item

"Load balancer pool"

Relationship

Name

Source

Destination

BMC_Dependency

LOADBALANCERSERVICEPOOL
BMC_Cluster
BMC_LogicalSystemComponent

BMC_HardwareSystemComponent

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

Note

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

BMC_HardwareSystemComponent

Attribute

Details

Name

Management controller name or
Management controller name:hostname if the target is Remedyforce.

ShortDescription

Management controller name.

Description

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

LastScanDate

Management controller last_update_success

ManufacturerName

Management controller vendor name.

Model

Management controller model.

PowerManagementSupported

Yes (0) or null if not known.

SerialNumber

Management controller serial number.

Company

Host Company.

VersionNumber

Management controller version number.

ComponentAliases

Management controller cdm_component_aliases

Category

"Hardware"

Type

"Hardware"

Item

"Management controller"

Hardware system component relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
SYSTEMHARDWARE

BMC_ComputerSystem (HostContainer)
BMC_ComputerSystem (HardwareContainer)
BMC_ComputerSystem (Host)
BMC_ComputerSystem (SNMPManagedDevice)

BMC_HardwareSystemComponent

BMC_ComputerSystem (Host Container)

HostContainer nodes are mapped to BMC_ComputerSystem representing the partitioned container.

Attribute

Details

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.

See TokenId rules.

Name

Host Container name

ShortDescription

Host Container name

Description

Host Container name

CapabilityList

"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

TotalPhysicalMemory

Host Container ram

ComponentAliases

VM cdm_component_aliases

Company

Host Container Company.

Category

"Hardware"

Type

"Hardware"

Item

Host Container type

Host containment relationships

Relationship

Name

Source

Destination

BMC_Component
SYSTEMPARTITION

BMC_ComputerSystem (container)

BMC_ComputerSystem (contained)
Impacted

BMC_HostedSystemComponents
SYSTEMHARDWARE
BMC_ComputerSystem
BMC_HardwareSystemComponent

BMC_VirtualSystemEnabler and virtualization

When a physical machine hosts one or more virtual machines, the BMC Discovery model represents it as a number of Virtual Machine nodes related to the physical Host, one Virtual Machine node per virtual host. A BMC_VirtualSystemEnabler CI is created for each VirtualMachine node.

Note

Previous releases of BMC Discovery, before version 11.2 created a single BMC_VirtualSystemEnabler CI to represent all virtual machines hosted by a physical machine. Upon first synchronization after upgrade from versions before 11.2, these singleton CIs will be marked as deleted, and new separate CIs will be created corresponding to the separate virtual machines.


Attribute

Details

Name

VirtualMachine name

ShortDescription

VirtualMachine short_name or name

Description

VirtualMachine name

BuildNumber

VirtualMachine build

EnablerType

Enumeration representing the type of virtualization technology

InstanceName

<type>:<hostname>:<DNS domain>:<instance name>

where <type>  is the value of the BMC Discovery type attribute from the corresponding SoftwareInstance or Database node, for example, “Microsoft SQL Server” or “Oracle Database”


isCloud

Yes if the virtual machine is known to be cloud hosted; null if not

ManufacturerName

Publisher.

MarketVersion

VirtualMachine product_version

Model

VirtualMachine type

PatchNumber

VirtualMachine patch

ServicePack

VirtualMachine service_pack

VersionNumber

VirtualMachine version

ComponentAliases

VirtualMachine cdm_component_aliases

Company

Host Company

Category

"Software"

Type

"Operating System Software"

Item

"Virtualization OS"

Virtualization relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
HOSTEDSYSTEMCOMPONENTS

BMC_ComputerSystem (physical)

BMC_VirtualSystemEnablerImpacted

BMC_HostedSystemComponents
HOSTEDSYSTEMCOMPONENTS
BMC_CloudInstance

BMC_VirtualSystemEnablerImpacted

BMC_Dependency
VIRTUALSYSTEMOS
BMC_VirtualSystemEnabler

BMC_ComputerSystem (virtual host)
BMC_ComputerSystem (virtual network device)
BMC_ComputerSystem (virtual SNMP managed device)
BMC_ComputerSystem (virtual storage system)

Impacted

BMC_VirtualSystemEnabler
VIRTUALSYSTEMOS
BMC_VirtualSystemEnabler

BMC_ComputerSystem (virtual)

BMC_SoftwareServer and BMC_ApplicationSystem

Each SoftwareInstance in the BMC 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

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 Software Instance key.

See TokenId rules.

Name

Software Instance name

ShortDescription

Software Instance short_name or Software Instance name

Description

Software Instance name

BuildNumber

Software Instance build

InstanceName

<type>:<hostname>:<DNS domain>:<instance name>

where <type>  is the value of the BMC Discovery type attribute from the corresponding SoftwareInstance or Database node, for example, “Microsoft SQL Server” or “Oracle Database”


isCloud

Yes if the software instance is known to be cloud hosted; null if not

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

ComponentAliases

Software Instance cdm_component_aliases

Company

Software Instance Company.

Category

"Software"

Type

"Application"

Item

Product category from the maintaining Pattern

Note

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)

BMC_SoftwareServer and BMC_ApplicationSystem relationships

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 BMC Discovery model.

BMC_SoftwareServer and BMC_ApplicationSystem CIs also have relationships to

BMC_Product
, shown in the Product relationships table.

Relationship

Name

Source

Destination

BMC_Dependency
APPLICATIONSYSTEMCOMPUTER

BMC_ComputerSystem
{{code language="none"}}
BMC_Cluster
BMC_CloudInstance
{{/code}}

BMC_SoftwareServerImpacted

BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationSystem (containing)
Impacted

BMC_SoftwareServer (contained)

BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_SoftwareServer (containing)

BMC_SoftwareServer (contained)

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer or BMC_ApplicationSystem (depended upon)
Impacted

BMC_SoftwareServer or BMC_ApplicationSystem (dependant)

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer (facet)

BMC_SoftwareServer (main facet)
Impacted

Communication relationships between nodes are mapped to a dependency between CIs.

Relationship

Name

Source

Destination

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

Server (depended upon)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster
BMC_VirtualSystemEnabler
BMC DataBase
BMC DataBase (Cloud)

(dependant)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster
BMC_VirtualSystemEnabler
BMC DataBase
BMC DataBase (Cloud)

Impacted

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

Client (dependant)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster
BMC_VirtualSystemEnabler
BMC DataBase
BMC DataBase (Cloud)

Impacted

Server (depended upon)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_Cluster
BMC_VirtualSystemEnabler
BMC DataBase
BMC DataBase (Cloud)

Observed Communication relationship between nodes mapped to Dependency between CIs. Due to the very high volume of Observed Communication relationships, only those that are part of application models are synchronized.

Relationship

Name

Source

Destination

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

Listening

BMC_SoftwareServer
BMC_SoftwareServer

Impacted

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY
BMC_SoftwareServer

Connecting

BMC_SoftwareServer

Impacted

Management relationships

Relationship

Name

Source

Destination

BMC_Dependency
SYSTEMMANAGER

BMC_Cluster
BMC_SoftwareServer First-order SI.{{code language="none" source="string:
{{code language=~"none~"~}~}BMC_ApplicationSystem{{/code~}~}"/}}{{/code}} Second-order SI{{code language="none" source="string:{{code language=~"none~"~}~}
.
{{/code~}~}"/}}
)))|(((
{{code language="none" source="string:{{code language=~"none~"~}~}
BMC_Cluster
{{/code~}~}"/}}
)))
|(((
{{code language="none"}}
BMC_Dependency
{{/code}}
)))|(((
{{code language="none"}}
SOFTWAREMANAGER
{{/code}}
)))|(((
####BMC_Cluster
{{code language="none"}}BMC_SoftwareServer{{/code}}#### First-order SI.{{code language="none"}}{{code language="none" source="string:
{{code language=~"none~"~}~}BMC_ApplicationSystem{{/code~}~}"/}}{{/code}} Second-order SI.
)))|(((
{{code language="none"}}BMC_SoftwareServer{{/code}} First-order SI.
{{code language="none"}}BMC_ApplicationSystem{{/code}} Second-order SI.
)))

Although the manager impacts the CI it is managing, we do not mark the relationship as impactful, to avoid impact cycles.

== {{id name="CDMMappingforHost-BMC_Document"/}}BMC_Document ==

(% style="color: rgb(33,33,33);" %)The new synchronization mapping attribute DocumentType "TLS Certificate" has been added to the BMC_Document CIs. (% style="color: rgb(33, 33, 33); color: rgb(51, 51, 51)" %)When SoftwareInstance or (%%)LoadBalancerService (% style="color: rgb(51,51,51);" %)nodes represent (%%)[[web servers>>confluencePage:page:Configipedia.Supported TLS Certificates||style="letter-spacing: 0.0px;" shape="rect"]](% style="color: rgb(51,51,51);" %) for which TLS/SSL certificates have been discovered, they have related Detail nodes with the type "TLS Certificate". The BMC_Document mapping was introduced in [[Technology Knowledge Update TKU 2020-Sep-1>>confluencePage:page:Configipedia.Technology Knowledge Update TKU 2020-Sep-1||shape="rect"]]. For more information, see [[TLS Certificates Discovery>>confluencePage:page:Configipedia.TLS Certificates Discovery||shape="rect"]].

\\

(% style="color: rgb(51,51,51);" %)These Detail nodes are mapped to BMC_Document CIs with the following attributes:

(% style="margin-left: 2.0px;" %)
|=(((
Attribute
)))|=(((
Details
)))
|(((
Name
)))|(((
Detail name
)))
|(((
ShortDescription
)))|(((
Detail short_name
)))
|(((
Description
)))|(((
Detail common_name
)))
|(((
Author
)))|(((
Detail issuer. The certificate issuer.
)))
|(((
DocumentType
)))|(((
"TLS Certificate"
)))
|(((
EndDate
)))|(((
Detail expiry_date. The certificate end (valid to) date.
)))
|(((
SerialNumber
)))|(((
Detail serial. The certificate serial number.
)))
|(((
StartDate
)))|(((
Detail start_date. The certificate start (valid from) date.
)))
|(((
Company
)))|(((
Host Company.
)))
|(((
Category
)))|(((
"Software"
)))
|(((
Type
)))|(((
"TLS Certificate"
)))
|(((
Item
)))|(((
"BMC Discovered"
)))

(% style="font-size: 16.0px;font-weight: bold;letter-spacing: -0.006em;" %)BMC_Document relationships

|=(((
Relationship
)))|=(((
Name
)))|=(((
Source
)))|=(((
Destination
)))
|(((
{{code language="none"}}
BMC_Dependency
{{/code}}
)))|(((
{{code language="none"}}
CERTIFICATE
{{/code}}
)))|(((
{{code language="none"}}
BMC_Document
{{/code}}
)))|(((
{{code language="none"}}
BMC_SoftwareServer
{{/code}}
)))

== {{id name="CDMMappingforHost-BMC_DataBase"/}}BMC_DataBase ==

{{code language="none"}}Database{{/code}} nodes (logical databases) are mapped to {{code language="none"}}BMC_DataBase{{/code}}:

|=(((
Attribute
)))|=(((
Details
)))
|(((
TokenId
)))|(((
{{code language="none"}}TokenId{{/code}} is of the form {{code language="none"}}"%hosting_ci.TokenId%:%database_node.type%:%si_instance%:%database_node.instance%" {{/code}}or{{code language="none"}} "%hosting_ci.Name%:%database_node.type%:%si_instance%:%database_node.instance%"{{/code}}

See [[TokenId rules>>doc:||anchor="CDMMappingforHost-TokenIdrules"]].
)))
|(((
Name
)))|(((
Database{{code language="none"}} name{{/code}} or
Database ##{{code language="none"}}name{{/code}} : software cluster name" ##if the target is Remedyforce.
)))
|(((
ShortDescription
)))|(((
Database {{code language="none"}}instance{{/code}}
)))
|(((
Description
)))|(((
Description is of the form {{code language="none"}}"%database_node.name% in %si_instance% on %hosting_ci.Name%"{{/code}} or

{{code language="none"}}
"%database_node.name% on %cloud_svc_ci.Name%"
{{/code}}
)))
|(((
InstanceName
)))|(((
(% class="content-wrapper" %)
(((
##<//type//>:<//hostname//>:<//DNS domain//>:<//instance name//>##

where //{{code language="none"}}<type>{{/code}}//  is the value of the {{excerpt-include 0="IT-Operations-Management.Discovery.BMC-Discovery.DISCO120._Includes._productNameLibrary.WebHome" name="DiscoName" nopanel="true"/}} type attribute from the corresponding SoftwareInstance or Database node, for example, “Microsoft SQL Server” or “Oracle Database”

\\
)))
)))
|(((
IsCloud
)))|(((
{{code language="none"}}Yes{{/code}} if the database is known to be cloud hosted; null if not.
)))
|(((
Model
)))|(((
DatabaseDetail {{code language="none"}}type{{/code}}
)))
|(((
ComponentAliases
)))|(((
Database component aliases
)))
|(((
Company
)))|(((
Host Company.
)))
|(((
Category
)))|(((
"{{code language="none"}}Miscellaneous{{/code}}"
)))
|(((
Type
)))|(((
"{{code language="none"}}Instance{{/code}}"
)))
|(((
Item
)))|(((
"{{code language="none"}}Database{{/code}}"
)))
|(((
ManufacturerName
)))|(((
Software Instance {{code language="none"}}vendor{{/code}}
)))
|(((
MarketVersion
)))|(((
Software Instance {{code language="none"}}product_version{{/code}}
)))
|(((
PatchNumber
)))|(((
Software Instance {{code language="none"}}patch{{/code}}
)))
|(((
ServicePack
)))|(((
Software Instance {{code language="none"}}service_pack{{/code}}
)))
|(((
VersionNumber
)))|(((
Software Instance {{code language="none"}}version{{/code}}
)))

=== {{id name="CDMMappingforHost-BMC_DataBaserelationships"/}}BMC_DataBase relationships ===

|=(((
Relationship
)))|=(((
Name
)))|=(((
Source
)))|=(((
Destination
)))
|(((
{{code language="none"}}
BMC_Dependency
{{/code}}
)))|(((
{{code language="none"}}
MANAGEDDATABASE
{{/code}}
)))|(((
{{code language="none"}}
BMC_SoftwareServer
{{/code}}
)))|(((
{{code language="none"}}BMC_DataBase
{{/code}}Impacted
)))
|(((
{{code language="none"}}
BMC_Dependency
{{/code}}
)))|(((
{{code language="none"}}
MANAGEDDATABASE
{{/code}}
)))|(((
{{code language="none"}}
BMC_ApplicationSystem
{{/code}}
)))|(((
{{code language="none"}}BMC_DataBase
{{/code}}Impacted
)))
|(((
{{code language="none"}}
BMC_Dependency
{{/code}}
)))|(((
{{code language="none"}}
MANAGEDDATABASE
{{/code}}
)))|(((
{{code language="none"}}
BMC_Cluster
{{/code}}
)))|(((
{{code language="none"}}BMC_DataBase
{{/code}}Impacted
)))
|(((
{{code language="none"}}
BMC_Dependency
{{/code}}
)))|(((
{{code language="none"}}
MANAGEDDATABASE
{{/code}}
)))|(((
{{code language="none"}}
BMC_CloudInstance
{{/code}}
)))|(((
{{code language="none"}}BMC_DataBase
{{/code}}Impacted
)))

BMC_Product

BMC_Product represents the installed aspects of a product. BMC 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

Publisher product name:product version or
name:hostname if the target is Remedyforce.

NameFormat

"ManufacturerName: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

Company

Host Company.

Category

"Software Application/System"

Type

"Application"

Item

Product category from the maintaining Pattern

Note

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)

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

TokenId

TokenId is of the form "ADDM:hashedkey", where hashedkey is a hash of Software Component key.

See TokenId rules.

Name

Software Component name or
Software Component name : hostname if the target is Remedyforce.

ShortDescription

Software Component name

Description

Software Component name

Model

Software Component type

VersionNumber

Software Component version

ApplicationServiceType

Enumeration value representing the service type. Either comes from the component or defaults to unknown.

Company

Host Company.

Category

"Software"

Type

"Application Service"

Item

"BMC Discovered"

Application service relationships

Relationship

Name

Source

Destination

BMC_ApplicationSystemServices

APPLICATIONSYSTEMSERVICES(for non-clustered components)

BMC_SoftwareServer

BMC_ApplicationServiceImpacted

BMC_ApplicationSystemServices

CLUSTERSERVICES(for clustered components)

BMC_SoftwareServer

BMC_ApplicationServiceImpacted


BMC_Application

BusinessApplicationInstance is mapped to BMC_Application. Contained SoftwareInstance and BusinessApplicationInstance nodes are mapped to corresponding BMC_Component relationships. Only Hosts directly contained within the application are synced. A Host that is included in a ModelDefinition, but is not at the "top" of the application model, will be implicitly included in the CMDB through software CIs.

Attribute

Details

Name

Business Application Instance name

ShortDescription

Business Application Instance name

Description

Business Application Instance name

MarketVersion

Business Application Instance product_version

VersionNumber

Business Application Instance version

Model

Business Application Instance type

ComponentAliases

Business Application Instance cdm_component_aliases

Company

Host Company.

Category

"Software"

Type

"Application"

Item

"Application Platform"

Application relationships

Relationship

Name

Source

Destination

BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_ComputerSystem
(Host)

BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_SoftwareServer
BMC_Component
APPLICATIONSYSTEMHIERARCHY

{{code language="none"}}
BMC_Application

{{/code}}Impacted

BMC_ApplicationSystem
BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_ApplicationService
BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_Cluster
BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_VirtualSystemEnabler
BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_DataBase(Cloud Database)

BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_ConcreteCollection
BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_DataBase
BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_ComputerSystem
(Load Balancer)

BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_ApplicationImpacted

BMC_Printer
BMC_Component
APPLICATIONSYSTEMHIERARCHY

BMC_Application (containing)Impacted

BMC_Application (contained)

BMC_Component

APPLICATIONSYSTEMCOMPONENT

BMC_ApplicationImpacted

BMC_ComputerSystem
(Host)

BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application
BMC_SoftwareServer
BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application
BMC_ApplicationSystem
BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application
BMC_ApplicationService
BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application
BMC_VirtualSystemEnabler
BMC_Component

APPLICATIONSYSTEMCOMPONENT

BMC_ApplicationImpacted

BMC_DataBase(Cloud Database)

BMC_Component

APPLICATIONSYSTEMCOMPONENT

BMC_ApplicationImpacted

BMC_ConcreteCollection
BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application
BMC_Cluster
BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application
BMC_DataBase
BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application

BMC_ComputerSystem
(Load Balancer)

BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application
BMC_Printer
BMC_Component
APPLICATIONSYSTEMCOMPONENT
BMC_Application

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_ApplicationService
BMC_Component
ITEMINFUNCTIONALCOMPONENT
BMC_ConcreteCollection
BMC_Cluster
BMC_Component
ITEMINFUNCTIONALCOMPONENT
BMC_ConcreteCollection
BMC_DataBase
BMC_Component
ITEMINFUNCTIONALCOMPONENT
BMC_ConcreteCollection

BMC_DataBase Cloud

BMC_Component
ITEMINFUNCTIONALCOMPONENT
BMC_ConcreteCollection
BMC_Application
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 (first or second order)
  • SoftwareComponent
  • SoftwareCluster
  • DatabaseDetail
  • BAI

Dependency relationships

Relationship

Name

Source (Depended)

Destination

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
{{code language="none" source="string:{{code language=~"none~"~}~}
BMC_VirtualSystemEnabler
{{/code~}~}"/}}{{/code}}
BMC_DataBase
BMC_Cluster

(Impacted)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
{{code language="none" source="string:{{code language=~"none~"~}~}
BMC_VirtualSystemEnabler
{{/code~}~}"/}}{{/code}}
BMC_DataBase
BMC_Cluster

Relationship

Name

Source

Destination (Dependant)

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
{{code language="none" source="string:{{code language=~"none~"~}~}
BMC_VirtualSystemEnabler
{{/code~}~}"/}}{{/code}}
BMC_DataBase
BMC_Cluster

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
{{code language="none" source="string:{{code language=~"none~"~}~}
BMC_VirtualSystemEnabler
{{/code~}~}"/}}{{/code}}
BMC_DataBase
BMC_Cluster

(Impacted)

TokenId rules

TokenId is an attribute that, in some circumstances, aids the reconciliation of CIs populated by multiple data sources. BMC Discovery sets TokenId depending on the Node kind.

For most Nodes, TokenId is one of the forms:

key

or

ADDM:%key%

or

ADDM:%hashed_key%

For databases, TokenId is a database host found as a result of all possible combinations of where the database might be running:

%hosting_ci.TokenId%:%database_node.type%:%si_instance%:%database_node.instance%

and

%hosting_ci.Name%:%database_node.type%:%si_instance%:%database_node.instance%

For the Fibre Channel Node, TokenId is of the form:

WWN:%wwpn% 

For physical hosts, TokenId is of the form:

%host.hostname%:%host.dns_domain%

If the domain name is unavailable, then

%host.hostname%

For virtual hosts that are running in the cloud, TokenId contains instance_id.

  • For Alibaba, TokenId is of the form:
%alibaba_instance_id%
  • For Azure, TokenId is of the form:
%azure_vm_id%
  • For AWS, TokenId is of the form:
%aws_instance_id%
  • For GCP, TokenId is of the form:
%gce_instance_id%
  • For IBM, TokenId is of the form:
%instance_id%
  • For OCI, TokenId is of the form:
%ocid%

For virtual hosts that are running in the hypervisor, TokenId contains UUID.

  • For AHV, TokenId is of the form:
AHV-UUID:%uuid%
  • For 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:
HYPERV-ID:%vm_uuid%
  • For KVM (including RedHat Enterprise Virtualization), TokenId is of the form:
KVM-ID:%uuid%
  • For VMware, TokenId is of the form where each letter represents a hexadecimal digit:
VI-UUID:%uuid%
  • For Xen (including Oracle VM), TokenId is of the form: 
XEN-ID:%uuid%

The following table shows how TokenId looks like for different Node Kinds:

Node Kind

CI

TokenId

AdminCollection

BMC_AdminDomain

key

Cluster (cloud)

BMC_Cluster

key

LoadBalancerService

BMC_LogicalSystemComponent

ADDM:%key%

LoadBalancerPool

BMC_ResourcePool

ADDM:%key%

CloudManagementGroup

BMC_AdminDomain

cloud_id

CloudProvider

BMC_CloudInstance

key

CloudRegion

BMC_CloudInstance

key

CloudService

BMC_CloudInstance

key

Cluster

BMC_Cluster

ADDM:%hashed_key%

Database (cloud)

BMC_DataBase

ADDM:%key%

Database


BMC_DataBase


%hosting_ci.TokenId%:%database_node.type%:%si_instance%:%database_node.instance%
%hosting_ci.Name%:%database_node.type%:%si_instance%:%database_node.instance%

HardwareComponent

BMC_HardwareSystemComponent

ADDM:%hashed_key%

HardwareContainer

BMC_ComputerSystem

ADDM:%hashed_key%

HostContainer

BMC_ComputerSystem

ADDM:%hashed_key%

Host








BMC_ComputerSystem








%host.hostname%:%host.dns_domain%
%host.hostname%
ALIBABA-ID:%alibaba_instance_id%
AWS-ID:%aws_instance_id%
GCP-ID:%gce_instance_id%
IBM-ID:%instance_id%
OCI-ID:%ocid%
AZURE-ID:%azure_vm_id%
HYPERV-ID:%vm_uuid%
XEN-ID:%uuid%
KVM-UUID:%uuid%
AHV-UUID:%uuid%
VI-UUID:%uuid%

LoadBalancerGroup

BMC_Cluster

ADDM:%key%

MFPart

BMC_ComputerSystem

key

Namespace

BMC_AdminDomain

key

Deployment

BMC_ConcreteCollection

key

NetworkService

BMC_LogicalSystemComponent

ADDM:%key%

FibreChannelPort

BMC_NetworkPort

WWN:%wwpn%

SoftwareCluster

BMC_Cluster

ADDM:%hashed_key%

SoftwareComponent

BMC_ApplicationService

ADDM:%hashed_key%

SoftwareInstance

BMC_ApplicationSystem

ADDM:%hashed_key%

SoftwareInstance

BMC_SoftwareServer

ADDM:%hashed_key%

VirtualMachine

BMC_VirtualSystemEnabler

ADDM:%hashed_key%

StorageDevice

BMC_Cluster

ADDM:%key%

StoragePool

BMC_ResourcePool

ADDM:%key%

StorageSystemGroup

BMC_Cluster

ADDM:%key%

StorageProcessor

BMC_HardwarePackage

ADDM:%key%

HardwareContainer

BMC_HardwareSystemComponent

ADDM:%hashed_key%

 

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