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

CDM Mapping for Cloud

This topic provides information about mapping for cloud nodes. The CIs created are described in this topic. 

Data models

Note

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.


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 model

CMDB versions

Effect

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

BMC_CloudInstance (Provider)

The CloudProvider node is mapped to a BMC_CloudInstance CI with the following attributes:

Attribute

Details

Name

Cloud provider name

ShortDescription

Cloud provider short_name, or name

Description

Cloud provider name

ManufacturerName

Cloud region vendor

Model

Cloud provider code

TokenId

Cloud provider key

See TokenId rules.

Company

Cloud provider company.

Category

"Cloud"

Type

"Cloud Provider"

Item

"Cloud Provider"

BMC_CloudInstance relationships

Relationship

Name

Source

Destination

BMC_Component
CLOUDREGIONFORPROVIDER

BMC_CloudInstance(Provider)

Impacted

BMC_CloudInstance(Region)


BMC_CloudInstance (Region)

The CloudRegion node is also mapped to a BMC_CloudInstance CI. It has the following attributes:

Attribute

Details

Name

Cloud region name

ShortDescription

Cloud region short_name, or name

Description

Cloud region name

ManufacturerName

Cloud region vendor

Model

Cloud region code

TokenId

Cloud region key

See TokenId rules.

Company

Cloud region company.

Category

"Cloud"

Type

"Cloud Provider"

Item

"Cloud Region"

BMC_CloudInstance relationships

Relationship

Name

Source

Destination

BMC_Component
CLOUDSERVICEINREGION

BMC_CloudInstance
(Region)

BMC_CloudInstance(Service)

Impacted

BMC_CloudInstance (Service)

The CloudService node is also mapped to a BMC_CloudInstance CI. It has the following attributes:

Attribute

Details

Name

Cloud service name

ShortDescription

Cloud service short_name, or name

Description

Cloud service name

ConsumedService

Cloud service type

LastScanDate

Cloud service last_update_success

Model

Cloud service code

TokenId

Cloud service key

See TokenId rules.

Category

"Cloud"

Type

"Cloud Provider"

Item

Cloud service type

BMC_Cluster

A cluster dependent on CloudService mapped to a BMC_Cluster CI. It has the following attributes:

Attribute

Details

TokenId

TokenId is of the form "ADDM:%lb_service.key%".

See TokenId rules.

Name

Cluster name.

NameFormat

"ClusterName"

ManufacturerName

Publisher comes from Cluster itself.

Model

Cluster type.

Description

Cluster name.

ShortDescription

Cluster name.

isCloud

Yes if the service exists directly within a cloud; null if not.

ComponentAliases

Cluster aliases.

Company

Cloud service Company.

Category

"Unknown".

Type

"Unknown".

Item

"BMC Discovered".

Relationship

Name

Source

Destination

BMC_Dependency
CLOUDSERVICECLUSTER

BMC_CloudInstance
(Service)

BMC_Cluster
Impacted


BMC_LogicalSystemComponent

The cloud LoadBalancerService is mapped to BMC_LogicalSystemComponent. It has the following attributes:

Attribute

Details

TokenId

TokenId is of the form "ADDM:%lb_service.key%".

See TokenId rules.

Name

Load balancer service name or
Load balancer service name : cloud service name if the target is Remedyforce.

ShortDescription

Load balancer service short_name, or name

Description

Load balancer service name

isCloud

Yes if  the service exists directly within a cloud; null if not

Model

Load balancer service model

Company

Cloud service Company

Category

"Network"

Type

"Service"

Item

"Load Balancer service"

BMC_LogicalSystemComponent relationships

Relationship

Name

Source

Destination

BMC_Dependency
LOADBALANCERSERVICE

BMC_CloudInstance(Service)

BMC_LogicalSystemComponentImpacted

BMC_ResourcePool

The cloud LoadBalancerPool is mapped to BMC_ResourcePool. It has the following attributes:

Attribute

Details

TokenId

TokenId is of the form "ADDM:%lb_pool.key%".

See TokenId rules.

Name

Load balancer pool name or
Load balancer pool name : cloud service name if the target is Remedyforce.

ShortDescription

Load balancer pool short.name

Description

Load balancer pool name

ResourceType

Other (0)

Company

Cloud service Company

Category

"Network"

Type

"Service"

Item

"Load Balancer pool"

BMC_ResourcePool relationships

Relationship

Name

Source

Destination

BMC_Component
HOSTEDRESOURCEPOOL

BMC_CloudInstance(Service)

BMC_ResourcePool
BMC_Dependency
LOADBALANCERSERVICE

BMC_ResourcePool
(Service)

BMC_LogicalSystemComponentImpacted

BMC_AdminDomain (AdminCollection)

The cloud AdminCollection node is mapped to BMC_AdminDomain. It has the following attributes:

Attribute

Details

Name

Administrative collection name orAdministrative collection name : cloud service name if the target is Remedyforce.

ShortDescription

Administrative collection short_name, or name

Description

Administrative collection name

Model

Administrative collection type

TokenId

Administrative collection {{code language="none"}}
key
{{/code}}

See TokenId rules.

Company

Cloud service Company

Category

"Cloud"

Type

"Administrative Collection"

Item

Administrative collection name

BMC_AdminDomain (AdminCollection) relationships

Relationship

Name

Source

Destination

BMC_Dependency
CLOUDADMINCOLLECTION

BMC_CloudInstance(Service)

BMC_AdminDomain
BMC_Dependency
ADMINCOLLECTIONMEMBER
BMC_AdminDomain
BMC_BaseElement

BMC_AdminDomain (CloudManagementGroup, NestedCloudManagementGroup, OwnedManagementGroup)

The cloud CloudManagementGroup,  NestedCloudManagementGroup, and OwnedManagementGroup nodes are each mapped to BMC_AdminDomain. This mapping was updated in the November 2020 TKU. It has the following attributes:

Attribute

Details

Name

Management Group name

ShortDescription

Management Group short_name or name

Description

Management Group name

ConsumedService

Management Group type

isCloud

Yes if the service exists directly within a cloud; null if not.

LastScanDate

Cloud service last_update_success

Model

Management Group type

SerialNumber

Management Group id

TokenId

Management Group cloud_id

See TokenId rules.

Company

Cloud service Company

Category 

"Cloud"

Type

"Cloud Management Group"

Item

Management Group type

BMC_AdminDomain (CloudManagementGroup) relationships

Relationship

Name

Source

Destination

BMC_MemberOfCollection
CLOUDMANAGEMENTGROUPPROVIDER
BMC_CloudRegion

BMC_AdminDomain
(CloudManagementGroup)
impacted

BMC_Component
CLOUDMANAGEMENTGROUPHIERARCHY

BMC_AdminDomain
(parent CloudManagementGroup)

BMC_CloudManagementGroup (child CloudManagementGroup)

BMC_MemberOfCollection
CLOUDMANAGEMENTGROUPOWNEDACCOUNT

BMC_AdminDomain(owning CloudManagementGroup)

BMC_AdminDomain
(owned CloudManagementGroup)

BMC_ConcreteCollection

The cloud Deployment node is mapped to BMC_ConcreteCollection. It has the following attributes:

Attribute

Details

Name

Deployment name or
Deployment name : cloud service name if the target is Remedyforce.

ShortDescription

Deployment short_name, or name

Description

Deployment name

Model

Deployment type

TokenId

Deployment {{code language="none"}}
key
{{/code}}

See TokenId rules.

Company

Cloud service Company

Category

"Cloud"

Type

"Deployment"

Item

Deployment name

BMC_ConcreteCollection relationships

Relationship

Name

Source

Destination

BMC_Dependency
CLOUDDEPLOYMENT

BMC_CloudInstance(Service)

BMC_ConcreteCollection
BMC_Dependency
CLOUDDEPLOYMENT

BMC_Cluster(Service)

BMC_ConcreteCollection
BMC_Dependency
MEMBERINDEPLOYMENT
BMC_ConcreteCollection
BMC_BaseElement

Mapping of VirtualMachine nodes, SoftwareInstance nodes, and contained Database nodes

Where VirtualMachine nodes, SoftwareInstance nodes, and contained Database nodes that are cloud hosted are populated, it is done so using the same rules as for those on a Host node. The mapping rules are shown below:

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

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 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 [[confluencePage:page:Configipedia.TLS Certificates Discovery]].

\\

(% 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.DISCO121._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
)))

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*