CDM Mapping for multiple device types

Contained ManagementControllers for a HardwareContainer ComputerSystem are mapped to BMC_HardwareSystemComponent. HardwareContainer nodes are mapped to BMC_ComputerSystem.

BMC_ComputerSystem (HardwareContainer)

HardwareContainer and child HardwareContainer nodes are mapped to BMC_ComputerSystem CIs.

Attribute	Details
`key`	Hardware container `key`
`TokenId`	"ADDM:%hashed_key%"
`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_ComputerSystem` (NetworkDevice) `BMC_ComputerSystem` (SNMPManagedDevice) `BMC_ComputerSystem` (StorageSystem) Impacted
`BMC_Component`	`SYSTEMHARDWARE`	`BMC_ComputerSystem` (Hardware container)	`BMC_HardwareSystemComponent`
`BMC_Component`	`HARDWAREUSE`	`BMC_HardwareSystemComponent` (Hardware container)	`BMC_ComputerSystem` (Host) `BMC_ComputerSystem` (NetworkDevice) `BMC_ComputerSystem` (SNMPManagedDevice) `BMC_ComputerSystem` (StorageSystem)

The child HardwareContainer nodes are also mapped to BMC_ComputerSystem CIs.

Attribute	Details
`key`	Hardware container `key`
`TokenId`	"ADDM:%hashed_key%"
`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) Impacted
`BMC_Component`	`HARDWARECONTAINMENT`	`BMC_ComputerSystem` (Hardware container)	`BMC_ComputerSystem` (NetworkDevice) Impacted
`BMC_Component`	`HARDWARECONTAINMENT`	`BMC_ComputerSystem` (Hardware container)	`BMC_ComputerSystem` (SNMPManagedDevice) Impacted
`BMC_Component`	`HARDWARECONTAINMENT`	`BMC_ComputerSystem` (Hardware container)	`BMC_ComputerSystem` (StorageSystem) Impacted

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` (Key is key of controller)

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

As StorageProcessor is mapped as BMC_HardwarePackage, it cannot use the BMC_HostedSystemComponents relationship, instead it uses the BMC_Component relationship.

If the "Exclude Orphaned Weak CIs" option is enabled, after reconciliation, BMC_NetworkPort CIs will be missing.

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

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 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 Helix Discovery Subnet nodes are mapped to BMC_IPConnectivitySubnet:

Attribute	Details
`Name`	Subnet `ip_address_range` or Subnet `ip_address_range :` Subnet `scope`
`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) and BMC_BusinessService (Technical Service)

Dependant Business Services and Technical Services are mapped to BMC_BusinessService CIs. Business Services and Technical Services that are depended upon are mapped to BMC_BusinessService CIs in the same way.

Nodes contained in Model Definitions that are in the review-suggested state are skipped.

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)

Relationship	Name	Source	Destination
`BMC_Dependency`	`APPLICATIONSYSTEMDEPENDENCY`	`BMC_BusinessService` (BusinessService) `BMC_BusinessService` (TechnicalService) `BAI_Application`	`BMC_BusinessService` (Dependant) Impacted
`BMC_Dependency`	`APPLICATIONSYSTEMDEPENDENCY`	`BMC_BusinessService` (Depended)	`BMC_BusinessService` (BusinessService) `BMC_BusinessService` (TechnicalService) `BAI_Application`Impacted

BMC_Application

Dependant BusinessApplicationInstances are mapped to BMC_Application CIs. BusinessApplicationInstances that are depended upon are mapped to BMC_Application CIs in the same way.