CDM Mapping for multiple device types
Contained Management Controllers for a HardwareContainer ComputerSystem are mapped to BMC_HardwareSystemComponent CIs when the Management Controller does not have a shared attribute, which is true in the majority of cases. Conversely, they are mapped to BMC_ComputerSystem CIs when the Management Controller does have the shared attribute. For the details of BMC_ComputerSystem mapping, see CDM-Mapping-for-Host.
BMC_ComputerSystem (HardwareContainer)
HardwareContainer and child HardwareContainer nodes are mapped to BMC_ComputerSystem CIs.
Attribute | Details |
---|---|
key | Hardware container key |
TokenId | "ADDM:%hashed_key%" See TokenId rules. |
Name | Hardware container name |
ShortDescription | Hardware container name |
Description | Hardware container name |
CapabilityList | capability_list |
EndOfExtendedSupport | End of Extended Support date. |
EndOfLife | End of Life date. |
EndOfSecuritySupport | End of Security Support date. |
EndOfSupport | End of Support date. |
LastScanDate | host.last_update_success |
ManufacturerName | Hardware container vendor |
Model | Hardware container model |
OtherCapabilityDescription | Hardware container type |
PrimaryCapability | primary_capability |
SerialNumber | Hardware container serial |
ComponentAliases | Hardware container cdm_component_aliases |
Company | Hardware container Company |
Category | "Hardware" |
Type | "Hardware" |
Item | Hardware container type |
Containment relationships between nodes are mapped to a component relationship between CIs.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Component | HARDWARECONTAINMENT | BMC_ComputerSystem (Hardware container) | BMC_ComputerSystem (Host) |
BMC_Component | SYSTEMHARDWARE | BMC_ComputerSystem (Hardware container) | BMC_HardwareSystemComponent |
BMC_Component | HARDWAREUSE | BMC_HardwareSystemComponent (Hardware container) | BMC_ComputerSystem (Host) |
The child HardwareContainer nodes are also mapped to BMC_ComputerSystem CIs.
Attribute | Details |
---|---|
key | Hardware container key |
TokenId | "ADDM:%hashed_key%" See TokenId rules. |
Name | Hardware container (child) name |
ShortDescription | Hardware container (child) name |
Description | Hardware container (child) name |
ManufacturerName | Hardware container (child) vendor |
Model | Hardware container (child) model |
Company | Hardware container (child) Company |
Category | "Hardware" |
Type | "Hardware" |
Item | Hardware container (child) type |
Containment relationships between nodes are mapped to a component relationship between CIs.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Component | HARDWARECONTAINMENT | BMC_ComputerSystem (Hardware container) | BMC_ComputerSystem (Host) |
BMC_Component | HARDWARECONTAINMENT | BMC_ComputerSystem (Hardware container) | BMC_ComputerSystem (NetworkDevice) |
BMC_Component | HARDWARECONTAINMENT | BMC_ComputerSystem (Hardware container) | BMC_ComputerSystem (SNMPManagedDevice) |
BMC_Component | HARDWARECONTAINMENT | BMC_ComputerSystem (Hardware container) | BMC_ComputerSystem (StorageSystem) |
BMC_HardwareSystemComponent
Contained ManagementController for a HardwareContainer ComputerSystem mapped to BMC_HardwareSystemComponent.
Note that there is no way to map the ManagementControllers IP information to the CDM.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_HardwareSystemComponent | SYSTEMHARDWARE | BMC_ComputerSystem (Hardware container) | BMC_HardwareSystemComponent |
BMC_ComputerSystem
Contained ManagementController with the shared attribute for a HardwareContainer ComputerSystem mapped to BMC_ComputerSystem.
Note (only for ManagementControllers that have the shared attribute) that there is no way to map the ManagementControllers IP information to the CDM.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_ComputerSystem | SYSTEMHARDWARE | BMC_ComputerSystem (ManagementController) | BMC_ComputerSystem(Hardware container) |
BMC_NetworkPort, BMC_IPEndpoint and BMC_LANEndpoint
For Network Device, SNMP Managed Device, Printer, StorageProcessor, and Storage System node, each connected Network Interface node in the BMC Helix 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 Helix 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 |
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 | DeviceCompany |
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 |
Name | FibreChannelHBA description and FibreChannelPort wwpn and hostname or |
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
As StorageProcessor is mapped as BMC_HardwarePackage, it cannot use the BMC_HostedSystemComponents relationship, instead it uses the BMC_Component relationship.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_HostedSystemComponents | SYSTEMHARDWARE | BMC_ComputerSystem(Network Device, SNMP Managed Device, Printer, or Storage System) | BMC_NetworkPort |
BMC_Component | SYSTEMHARDWARE | BMC_HardwarePackage(Storage Processor) | BMC_NetworkPort |
BMC_LANEndpoint
MAC addresses in the BMC Helix 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 |
Name | NetworkInterface mac_addr : or |
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
As StorageProcessor is mapped as BMC_HardwarePackage, it cannot use the BMC_HostedAccessPoint relationship, instead it uses the BMC_Dependency relationship.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_HostedAccessPoint | HOSTEDACCESSPOINT | BMC_ComputerSystem (Network Device, SNMP Managed Device, Printer, or Storage System) | BMC_LANEndpoint |
BMC_Dependency | HOSTEDACCESSPOINT | BMC_ComputerSystem (Storage Processor) | BMC_LANEndpoint |
BMC_Dependency | ENDPOINTPORT | BMC_NetworkPort | BMC_LANEndpoint |
BMC_IPEndpoint
Attribute | Details |
---|---|
Key | "%host.key%/IP/%ip_addr%" or |
Name | NetworkInterface IP address or |
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 Helix Discovery Subnet nodes are mapped to BMC_IPConnectivitySubnet:
Attribute | Details |
---|---|
Name | Subnet ip_address_range or |
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_BusinessService (Business Service), BMC_BusinessService (Technical Service), and BMC_Application
Business Services and Technical Services are mapped to BMC_BusinessService CIs. Business Application Instances are mapped to BMC_Application CIs.
Nodes contained in Model Definitions that are in the review-suggested state are skipped.
BMC_BusinessService (Business Service) and BMC_BusinessService (Technical Service)
Attribute | Details |
---|---|
key | Business service key |
Name | Business service name |
ShortDescription | Business service name |
Description | Business service name |
MarketVersion | Business service product_version |
Model | Business service type |
ServiceType | Service type |
VersionNumber | Business service version |
ComponentAliases | Business service cdm_component_aliases |
Company | Business service company. |
Category | "Miscellaneous" |
Type | "Service" |
Item | Business service category, Technical service (20), or Business service (10) |
BMC_Application
Attribute | Details |
---|---|
key | Business application key |
Name | Business application name |
ShortDescription | Business application name |
Description | Business application name |
MarketVersion | Business application product_version |
Model | Business application type |
VersionNumber | Business application version |
ComponentAliases | Business application cdm_component_aliases |
Company | Business application company |
Category | "Software" |
Type | "Application" |
Item | Business application category or "Application Platform" |
Relationships for BMC_BusinessService (Business Service), BMC_BusinessService (Technical Service), and BMC_Application
The following relationships represent an 'upward' dependency between services and applications, leading to the 'top' service.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMDEPENDENCY | BMC_BusinessService (BusinessService) | BMC_BusinessService (BusinessService) |
BMC_Component | APPLICATIONSYSTEMHIERARCHY | BMC_BusinessService (BusinessService) | BMC_Application (Dependant) |
The following relationships represent a 'downward' dependency between services and applications, starting from a service that is at the 'top' of the impact tree.
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | APPLICATIONSYSTEMDEPENDENCY | BMC_BusinessService (BusinessService) | BMC_BusinessService (BusinessService) |
BMC_Component | APPLICATIONSYSTEMHIERARCHY | BMC_Application (Depended) | BMC_BusinessService (BusinessService) |
BMC_LogicalSystemComponent
NetworkService nodes are mapped to BMC_LogicalSystemComponent CIs.
Attribute | Details |
---|---|
key | Network service key |
TokenId | ADDM:%key% See TokenId rules. |
Name | Name. Of the form:
|
ShortDescription | Network service short_name or network_service.name |
Description | Network service name |
isCloud | Network service cloud |
Model | Network service type |
ManufacturerName | Network service publisher. If there is no network service publisher then the name is taken from the pattern, otherwise it is taken from the defaults. |
CloudId | Network service cloud_id |
Company | Container service company |
Category | "Network" |
Type | "Service" |
Item | "Network service" |
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_Dependency | NETWORKSERVICE | BMC_LogicalSystemComponent (Cloud Service) | BMC_LogicalSystemComponent (Network Service) |
BMC_Tags
Where node kinds have one or more key-value tags, the mapping creates the following related BMC_Tag CIs.
- BMC_ComputerSystem
- BMC_Cluster
- BMC_VirtualSystemEnabler
- BMC_AdminDomain (AdminCollection)
- BMC_AdminDomain (Namespace)
- BMC_AdminDomain (Cloud Management Group)
- BMC_AdminDomain (Nested Cloud Management Group)
- BMC_AdminDomain (Owned Cloud Management Group)
- BMC_ConcreteCollection (Deployment)
- BMC_SoftwareServer
- BMC_ApplicationSystem
- BMC_Cluster
- BMC_Cluster (Software)
- BMC_DataBase
- BMC_DataBase (Cloud)
- BMC_LogicalSystemComponent
- BMC_Cluster (Cloud)
Attribute | Details |
---|---|
key | "%node.key%/%tag_name%" |
Name | "%tag_name% : %ci.Name%" |
ShortDescription | tag_name |
Description | tag_name : CI description |
TagName | tag_name |
TagValue | tag_value |
Company | Company |
Category | "Miscellaneous" |
Type | "Metadata" |
Item | "Tag" |
Relationship | Name | Source | Destination |
---|---|---|---|
BMC_RelatedTo | ITEMWITHTAG | BMC_ComputerSystem | BMC_Tag |
Custom tag synchronization
Synchronizing large volumes of data might lead to performance issues. To prevent load on the system, consider customizing the sync process. You can configure tags belonging to a certain category by modifying or disabling any of the following pattern modules:
- CMDB.Cloud_Tags
- CMDB.Kubernetes_Tags
- CMDB.Tags
Module | CIs |
---|---|
CMDB.Cloud_Tags |
|
CMDB.Kubernetes_Tags |
|
CMDB.Tags |
|
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:
or
or
For databases, TokenId is a database host found as a result of all possible combinations of where the database might be running:
and
For the Fibre Channel Node, TokenId is of the form:
For physical hosts, TokenId is of the form:
If the domain name is unavailable, then
For virtual hosts that are running in the cloud, TokenId contains instance_id.
- For Alibaba, TokenId is of the form:
- For Azure, TokenId is of the form:
- For AWS, TokenId is of the form:
- For GCP, TokenId is of the form:
- For IBM, TokenId is of the form:
- For OCI, TokenId is of the form:
For virtual hosts that are running in the hypervisor, TokenId contains UUID.
- For AHV, TokenId is of the form:
- 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:
- For KVM (including RedHat Enterprise Virtualization), TokenId is of the form:
- For VMware, TokenId is of the form where each letter represents a hexadecimal digit:
- For Xen (including Oracle VM), TokenId is of the form:
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% |