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 Network Device

This topic provides information on mapping for network devices. The CIs created are described in this topic.

Load balancers are mapped as Network Devices. The mapping is described in CDM-Mapping-for-Load-Balancer-nodes.

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.
  • A number of attributes are not present in CMDB 7.5, as noted below.


Click here for reference information on impact and the data models.

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

Data 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_ComputerSystem

The root Network Device node is mapped to a root BMC_ComputerSystem CI with the following attributes:

Attribute

Details

Name

Network Device name attribute. The configured name of the network device

ShortDescription

Network Device name

Description

Network Device name

CapabilityList

List of device capabilities

EndOfExtendedSupport

Source node end of Extended Support date.

EndOfLife

Source node end of Life date.

EndOfSecuritySupport

Source node end of Security Support date.

EndOfSupport

Source node end of Support date.

firmware_version

Network Device firmware version

HostName

Network Device name

isVirtual

Network Device virtual

LastScanDate

Network Device last_update_success — the date and time the device was last scanned

ManufacturerName

Network Device vendor

Model

Network Device model

PrimaryCapability

Switch, Router, or other network device enumeration value

SerialNumber

Network Device serial

PartitionID

NetworkDevice partition_id

SystemOID

Network Device sysobjectid

Category

"Network"

Type

"Switch" or "Router"

Item

"Data Switch" or "Access Router"

The BMC_UPS class exists as a hosted system component, though given the nature of UPS devices and their usual standalone nature, BMC_ComputerSystem is a more appropriate mapping. Particularly as they are IP connected and the BMC_ComputerSystem class provides additional flexibility that the BMC_UPS class does not. 

Relationships

Relationships are created to represent the connection between edge switches and hosts. Switch-to-switch connections are not mapped.

Relationship

Name

Source

Destination

BMC_Dependency
NETWORKLINK

BMC_ComputerSystem (network device)

BMC_ComputerSystem (host)

Impacted

Relationships are created to represent the connection between SAN switch Network Devices and hosts, and SAN switch Network Devices and Storage Systems.

Relationship

Name

Source

Destination

BMC_Dependency
NETWORKLINK

BMC_ComputerSystem (network device)

BMC_ComputerSystem (host)

BMC_Dependency
NETWORKLINK

BMC_ComputerSystem (network device)

BMC_ComputerSystem (Storage System)

Relationships are created from Stack Member Network Devices to Stack Network Device (stack linkage) and from Stack Network Devices to Stack Member Network Devices.

Relationship

Name

Source

Destination

BMC_Dependency
DEVICEINSTACK

BMC_ComputerSystem (stack member)

BMC_ComputerSystem (stack network device)

Impacted

Relationships are created from the Stack Network Device NetworkInterface link to Stack Member Network Device.

Relationship

Name

Source

Destination

BMC_Dependency
STACKMEMBERINTERFACE

BMC_ComputerSystem (network device)

BMC_NetworkPort

Relationships are created to represent NetworkDevice management of other devices.

Relationship

Name

Source

Destination

BMC_Dependency
DEVICEMANAGER

BMC_ComputerSystem (network device)

BMC_ComputerSystem (device)

Impacted

BMC_Dependency
DEVICEMANAGER

BMC_ComputerSystem (network device)

BMC_ComputerSystem (Host  Container)

Impacted

Relationships are created to represent NetworkDevice detail host linkage.

Relationship

Name

Source

Destination

BMC_Dependency
NETWORKLINK

BMC_ComputerSystem (network device)

BMC_ComputerSystem (host)Impacted

BMC_Dependency
NETWORKLINK

BMC_ComputerSystem (SNMP managed device)

BMC_ComputerSystem (host)Impacted

BMC_Dependency
NETWORKLINK

BMC_Printer (printer)

BMC_Printer (printer)Impacted

BMC_Dependency
NETWORKLINK

BMC_ComputerSystem (Storage System)

BMC_ComputerSystem (host)Impacted

In some Cisco ACI configurations, ports on one ACI leaf switch can be connected to the management port on another ACI leaf switch for management tasks. In this case, we do not create the dependency relationship between the ACI leaf switches.

BMC_ComputerSystem (Host Container)

HostContainer nodes directly connected to the root Network Device in the BMC Helix Discovery model are mapped to BMC_ComputerSystem CIs representing the partitioned container.

Attribute

Details

Name

Host Container name

ShortDescription

Host Container name

Description

Host Container name

CapabilityList

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

EndOfExtendedSupport

Source node end of Extended Support date.

EndOfLife

Source node end of Life date.

EndOfSecuritySupport

Source node end of Security Support date.

EndOfSupport

Source node end of Support date.

LastScanDate

Host last_update_success

ManufacturerName

Host Container vendor

Model

Host Container model

OtherCapabilityDescription

Host Container type

PrimaryCapability

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

SerialNumber

Host Container serial

Category

"Hardware"

Type

"Hardware"

Item

HadwareContainer type

TokenId

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

See TokenId rules.

Host containment relationships

Relationship

Name

Source

Destination

BMC_Component
SYSTEMPARTITION

BMC_ComputerSystem (container)

BMC_ComputerSystem (contained)

BMC_HardwareSystemComponent

Any ManagementController for a HostContainer containing the root Network Device in the BMC Helix Discovery model is mapped to BMC_HardwareSystemComponent.

Note

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

BMC_HardwareSystemComponent

Attribute

Details

Name

Management controller name.

NameFormat

"HostName"

ShortDescription

Management controller name.

Description

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

EndOfExtendedSupport

Source node end of Extended Support date.

EndOfLife

Source node end of Life date.

EndOfSecuritySupport

Source node end of Security Support date.

EndOfSupport

Source node end of Support date.

ManufacturerName

Management controller vendor name.

VersionNumber

Management controller version number.

Model

Management controller model.

PowerManagementSupported

Yes (0) or null if not known.

Company

Host Company.

Category

"Hardware"

Type

"Hardware"

Item

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

Hardware system component relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
SYSTEMHARDWARE
BMC_ComputerSystem

Corresponds to a Host or a HostContainer, depending on whether
the ManagementController controls a chassis, or a host directly.

BMC_HardwareSystemComponent

BMC_OperatingSystem

The root Network Device node is also mapped to a BMC_OperatingSystem CI:

Attribute

Details

Name

"os_vendor os_type os_version" orNetwork Device name : computersystem name if the target is Remedyforce.

ShortDescription
"os_type os_version"
Description

"os_vendor os_type os_version"

BuildNumber

Network Device os_build

EndOfExtendedSupport

Source node end of Extended Support date.

EndOfLife

Source node end of Life date.

EndOfSecuritySupport

Source node end of Security Support date.

EndOfSupport

Source node end of Support date.

ManufacturerName

Network Device os_vendor

MarketVersion

Network Device os_version

Model

Network Device os_type

OSType

Linux or Other.

VersionNumber

Network Device os_version

Category

"Software"

Type

"Operating System Software"

Item

"Network Operating System"

BMC_OperatingSystem relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
SYSTEMOS
BMC_ComputerSystem
BMC_OperatingSystem

BMC_NetworkPort, BMC_LANEndpoint and BMC_IPEndpoint

Each Network Interface node connected to the root Network Device in the BMC Helix Discovery model is mapped to a BMC_NetworkPort, and its MAC address is mapped to a BMC_LANEndpoint.

Where BMC Helix Discovery connects a Network Device to a Host, a BMC_Dependency relationship is created between the two BMC_ComputerSystem CIs representing the host and the network device.

BMC_NetworkPort

Attribute

Details

Name

NetworkInterface interface_name or NetworkInterface {{code language="none"}}
interface_name : computersystem name
{{/code}} 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 speed

Category

"Hardware"

Type

"Card"

Item

"Network interface card"

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

Attribute

Details

Name

FibreChannelHBA description and FibreChannelPort wwpn 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 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

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

Name

NetworkInterface mac_addr or NetworkInterface mac_addr{{code language="none"}}
 : interface_name : computersystem name
{{/code}} 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)

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

Each IP Address node related to the root Network Device node is mapped to a BMC_IPEndpoint CI:

Attribute

Details

Name

IP Address ip_addr or IP Address ip_addr : computersystem name if the target is Remedyforce.

NameFormat

"IP"

ShortDescription

IP Address ip_addr

Description

IP Address name

Address

IP Address ip_addr

AddressType

IPv4 (1) or IPv6 (2)

DNSHostName

IP Address fqdns (first item in list)

ProtocolType

IPv4 (2) or IPv6 (3)

SubnetMask

IP Address netmask

ManagementAddress

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

Category

"Network"

Type

"Address"

Item

"IP Address"

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 is mapped to BMC_IPConnectivitySubnet:

Attribute

Details

Name

Subnet ip_address_range

ShortDescription

Subnet ip_address_range

Description

Subnet ip_address_range

AddressType

IPv4 (1) or IPv6 (2)

PrefixLength

IP Address prefix_length

SubnetMask

IP Address netmask

SubnetNumber

Subnet ip_address_range

Category

"Network"

Type

"Subnet"

Item

"TCP/IP"

Subnet relationships

Relationship

Name

Source

Destination

BMC_InIPSubnet
INIPSUBNET
BMC_IPConnectivitySubnet
BMC_IPEndpoint

BMC_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_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
BMC_DataBase
BMC_Cluster

(Impacted)

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_DataBase
BMC_Cluster

Relationship

Name

Source

Destination (Dependant)

BMC_Dependency
APPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_DataBase
BMC_Cluster

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
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 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*