Default language.

Important This documentation space contains information about the SaaS version of BMC Helix Discovery. If you are using the on-premises version of BMC Helix Discovery, see BMC Helix Discovery 25.2 (On-Premises).

CDM Mapping for Load Balancer nodes

LoadBalancerInstance is mapped to details on the base NetworkDevice BMC_ComputerSystem. Network devices with the Load Balancer primary capability are mapped as follows:

  • Category: "Hardware",
  • Type: "Hardware",
  • Item: "Load balancer"

The mappings for the remaining load balancer components are described in this topic.

Load balancer nodes

  • LoadBalancerService nodes are mapped to BMC_LogicalSystemComponent CIs.
  • LoadBalancerPool nodes are mapped to BMC_ResourcePool CIs.

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_LogicalSystemComponent

LoadBalancerService nodes are mapped to BMC_LogicalSystemComponent CIs.

Attribute

Details

TokenId

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

See TokenId rules.

Name

Load Balancer Service name or
Load Balancer Service name : computersystem name if the target is Remedyforce.

ShortDescription

Load Balancer Service Name

Description

Load Balancer Service Name

isCloud

Yes if the load balancer is known to be cloud hosted; null if not

CloudID

Load Balancer Service unique cloud identifier (cloud_id).

Model

Load Balancer Service Type

Company

Load Balancer Service Company

Category

"Network"

Type

"Service"

Item

"Load balancer service"

BMC_LogicalSystemComponent relationships

Relationship

Name

Source

Destination

BMC_Dependency
LOADBALANCERSERVICE
BMC_ComputerSystem
BMC_LogicalSystemComponent

Impacted

BMC_ResourcePool

LoadBalancerPool nodes are mapped to BMC_ResourcePool CIs.

Attribute

Details

TokenId

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

See TokenId rules.

Name

Load Balancer Pool name or
Load Balancer Pool name : computersystem name if the target is Remedyforce.

ShortDescription

Load Balancer Pool Name

Description

Load Balancer Pool Name

ResourceType

Other (0)

OtherResourceType

"Load Balancer Pool"

Company

Load Balancer Pool Company

Category

"Network"

Type

"Service"

Item

"Load balancer pool"

BMC_ResourcePool Relationships

Relationship

Name

Source

Destination

BMC_Component
HOSTEDRESOURCEPOOL

BMC_ComputerSystem (Host)

BMC_ResourcePool
BMC_Component
HOSTEDRESOURCEPOOL
BMC_SoftwareServer
BMC_ResourcePool
BMC_Dependency
LOADBALANCERSERVICEPOOL
BMC_ResourcePool
BMC_LogicalSystemComponent

Impacted

BMC_Cluster

Load Balancer Group nodes are mapped as BMC_Cluster CIs. Software load balancers are not mapped.

Attribute

Details

TokenId

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

See TokenId rules.

Name

Load Balancer Group name

Description

Load Balancer Group name

ShortDescription

Load Balancer Group name

Model

Load Balancer Group type

Company

computersystem.Company

Category

"Hardware"

Type

"Hardware"

Item

"Load balancer cluster"

BMC_Cluster relationships

Relationship

Name

Source

Destination

BMC_Component
CLUSTEREDSYSTEM
BMC_Cluster

Impacted

BMC_ComputerSystem 
(Network Device)

BMC_ResourcePool linking

BMC_ResourcePool CIs are linked to BMC_ApplicationService, BMC_SoftwareServer, BMC_ApplicationSystem, BMC_ComputerSystem or BMC_VirtualSystemEnabler CIs.

BMC_ApplicationService

BMC_ApplicationService CIs (mapped from Software Components) are linked to BMC_ResourcePool (mapped from Load Balancer Pool nodes).

Relationship

Name

Source

Destination

BMC_Dependency
LOADBALANCERMEMBER
BMC_ApplicationService
BMC_ResourcePool

Impacted

BMC_SoftwareServer and BMC_ApplicationSystem

BMC_SoftwareServer CIs (mapped from First-order Software Instances) are linked to BMC_ResourcePool (mapped from Load Balancer Pool nodes).

BMC_ApplicationSystem CIs (mapped from Second-order Software Instances) are linked to BMC_ResourcePool (mapped from Load Balancer Pool nodes).

Relationship

Name

Source

Destination

BMC_Dependency
LOADBALANCERMEMBER
BMC_SoftwareServer
BMC_ResourcePool

Impacted

BMC_Dependency
LOADBALANCERMEMBER
BMC_ApplicationSystem
BMC_ResourcePool

Impacted

BMC_LogicalSystemComponent

BMC_LogicalSystemComponent CIs (mapped from LoadBalancerServices) are linked to BMC_ResourcePool (mapped from Load Balancer Pool nodes). 

Relationship

Name

Source

Destination

BMC_Dependency
LOADBALANCERMEMBER
BMC_LogicalSystemComponent
BMC_ResourcePool

Impacted

BMC_ComputerSystem

BMC_ComputerSystem CIs (mapped from Hosts) are linked to BMC_ResourcePool (mapped from Load Balancer Pool nodes) only if there is no software link.

Relationship

Name

Source

Destination

BMC_Dependency
LOADBALANCERMEMBER
BMC_ComputerSystem
BMC_ResourcePool

Impacted

BMC_VirtualSystemEnabler

BMC_VirtualSystemEnabler CIs (mapped from VMs) are linked to BMC_ResourcePool (mapped from Load Balancer Pool nodes) only if there is no software or Host link.

Relationship

Name

Source

Destination

BMC_Dependency
LOADBALANCERMEMBER
BMC_VirtualSystemEnabler
BMC_ResourcePool

Impacted

TokenId rules

TokenId is an attribute that, in some circumstances, aids the reconciliation of CIs populated by multiple data sources. BMC Helix 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*