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 Storage


This topic provides information about mapping for storage. 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_ComputerSystem

The StorageSystem node is mapped to BMC_ComputerSystem CIs.

BMC_ComputerSystem

Attribute

Details

Name

StorageSystem name

ShortDescription

StorageSystem name

Description

StorageSystem name

CapabilityList

List of capabilities

ManufacturerName

StorageSystem vendor

Model

StorageSystem type:StorageSystem model

isVirtual

True if the Storage System is virtual; not set if physical.

PrimaryCapability

Storage

SerialNumber

StorageSystem serial number

Category

The CDM category, for example, "Hardware".

Type

The CDM type, for example, "Disk device".

Item

The CDM item, for example, "Disk array".

BMC_ComputerSystem relationships

Populate the Company attribute for BMC_ComputerSystem CIs mapped from StorageSystem nodes.

Creates links to manager CI and sets LastScanDate and SystemOID where available.

Note

Do not create an extension syncmapping that extends this one. If you need to access nodes accessed in the traversals here, traverse again. This priority syncmapping must complete before any other CIs are created.


  • First-order Software Instances are mapped to BMC_SoftwareServer CIs.
  • Second-order Software Instances are mapped to BMC_ApplicationSystem CIs.

Relationship

Name

Source

Destination

BMC_Dependency
SYSTEMMANAGER
BMC_SoftwareServer
BMC_ComputerSystem
BMC_Dependency
SYSTEMMANAGER
BMC_ApplicationSystem
BMC_ComputerSystem
BMC_Dependency
SYSTEMMANAGER
BMC_SoftwareServer
BMC_ComputerSystem
BMC_Dependency
SYSTEMMANAGER
BMC_ApplicationSystem
BMC_ComputerSystem
BMC_Dependency
STORAGEUSE

BMC_ComputerSystem
Storage System

BMC_ComputerSystem
Consuming Host
Impacted

BMC_Dependency
STORAGEUSE

BMC_ComputerSystemBackend Storage System

BMC_ComputerSystemconsuming NAS host

BMC_Dependency
BACKENDSTORAGEUSE

BMC_ComputerSystem
Backend Storage System

BMC_ComputerSystem
Consuming Host
Impacted

BMC_DependencyIntroduced in January 2021 TKU.

NETWORKLINK

BMC_ComputerSystem
Network Device (SAN Switch)

BMC_ComputerSystem
Storage System
Impacted

BMC_OperatingSystem

StorageSystem OS is mapped to BMC_OperatingSystem.

Attribute

Details

key

StorageSystem key,

Name

"%device.os_vendor% %device.os_type% %device.os_version%" or
StorageSystem name : hostname if the target is Remedyforce.

ShortDescription

"%device.os_type% %device.os_version%"

Description

"%device.os_vendor% %device.os_type% %device.os_version%" or
StorageSystem name : hostname if the target is Remedyforce.

ManufacturerName

StorageSystem os_vendor

MarketVersion

StorageSystem os_version

Model

StorageSystem os_type

OSType

0 (Other)

VersionNumber

StorageSystem os_version

Company

StorageSystem Company

Category

"Software"

Type

"Operating System Software"

Item

"Storage Operating System"

BMC_OperatingSystem relationships

Relationship

Name

Source

Destination

BMC_Component
SYSTEMOS

BMC_ComputerSystem 
(Storage System)

BMC_OperatingSystem

BMC_ResourcePool

The StoragePool node is mapped to the BMC_ResourcePool CI.

BMC_ResourcePool

Attribute

Details

TokenId

TokenId is of the form "ADDM:StoragePool key".

See TokenId rules.

Name

StoragePool name or
StoragePool name : computer system name if the target is Remedyforce.

ShortDescription

StoragePool ID

Description

StoragePool name

AllocationUnits

"byte"

Capacity

StoragePool capacity

CurrentlyConsumedResource

StoragePool consumed capacity

Primordial

If the pool type is primordial, "Primordial"

ResourceType

32=Storage Volume

Company

StorageSystem Company

Category

"Hardware"

Type

"Storage"

Item

"Storage pool"

BMC_ResourcePool relationships

Relationship

Name

Source

Destination

BMC_Component
HOSTEDRESOURCEPOOL

BMC_ComputerSystem 
(Storage System)

BMC_ResourcePool
BMC_Dependency
VIRTUALSYSTEMOS
BMC_ResourcePool

BMC_ComputerSystem 
(Storage System)

BMC_HardwarePackage

The StorageProcessor node is mapped to the BMC_HardwarePackage CI. Serial number attribute is added for StorageProcessor.

BMC_HardwarePackage

Attribute

Details

TokenId

TokenId is of the form "ADDM:StorageProcessor.key".

See TokenId rules.

Name

StorageProcessor description or
StorageProcessor name : computersystem name if the target is Remedyforce.

ShortDescription

StorageProcessor identifier.

Description

StorageProcessor description.

ManufacturerName

StorageProcessor vendor.

Model

StorageProcessor model name.

Company

StorageProcessor company.

Serial

StorageProcessor serial number.

Category

"Hardware"

Type

"Storage"

Item

"Storage processor"

BMC_HardwarePackage relationships

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
SYSTEMHARDWARE

BMC_ComputerSystem
(Storage System)

BMC_HardwarePackage

BMC_HardwareSystemComponent

StorageSystem linking to contained HardwareContainers.

BMC_HardwareSystemComponent

Attribute

Details

key

hardware_container.key

TokenId

TokenId is of the form "ADDM:HardwareContainer.key".

See TokenId rules.

Name

Hardware Container Name

ShortDescription

Hardware Container Name

Description

Hardware Container Name

ManufacturerName

Hardware Container Vendor

Model

Hardware Container Model

SerialNumber

Hardware Container Serial

Company

Company

Category

"Hardware"

Type

"Hardware"

Item

Hardware Container Serial type

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
SYSTEMHARDWARE

BMC_ComputerSystem (Storage System)

BMC_HardwareSystemComponent

BMC_NetworkPort, BMC_IPEndpoint and BMC_LANEndpoint

Each Network Interface node connected to the root StorageSystem in the BMC 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.

The IP addresses of a StorageSystemGroup are mapped to BMC_IPEndpoint CIs.

BMC_NetworkPort

Attribute

Details

Name

Interface name of the Network Interface

ShortDescription

Interface name of the Network Interface

Description

Full name of the Network Interface

AutoSense

Negotiation setting, 0=Yes, 1=No.

FullDuplex

Full duplex, 0=Yes, 1=No.

LinkTechnology

2. (Ethernet)

ManufacturerName

The Network Interface manufacturer

PermanentAddress

MAC address.

PortType

2. (Ethernet)

Speed

The interface speed in bps

Company

Network Interface Company

Category

"Hardware"

Type

"Card"

Item

"Network interface card"


The front-end FibreChannelPort is mapped to BMC_NetworkPort.

Note

Note that Fibre Channel is the correct spelling for the technology. Do not "correct" the Item to Fiber Channel.


Attribute

Details

TokenId

TokenId is of the form "World Wide Name:World Wide Port Number".

See TokenId rules.

Name

Fibre Channel Port name or
Fibre Channel Port name : storage processor name if the target is Remedyforce.

ShortDescription

Fibre Channel Port name

Description

Fibre Channel Port name : WWPN

LinkTechnology

4. (Fibre Channel)

ManufacturerName

Storage processor vendor

Model

Storage processor model

PermanentAddress

Fibre Channel Port WWPN

PortType

6. (Fibre Channel)

Company

Host Company

Category

"Hardware"

Type

"Card"

Item

"Fibre Channel HBA card"

BMC_NetworkPort relationship

Relationship

Name

Source

Destination

BMC_HostedSystemComponents
SYSTEMHARDWARE

BMC_ComputerSystem 
(Storage System)

BMC_NetworkPort
BMC_Component
SUBHWCOMPONENT

BMC_HardwarePackage
(Storage Processor)

BMC_NetworkPort

BMC_LANEndpoint

Attribute

Details

Name

MAC Address

NameFormat

"MAC"

ShortDescription

MAC Address (with colons)

Description

"MAC address on hostname"

Address

MAC address (no separating colons)

MACAddress

MAC address (no separating colons)

ProtocolType

14. (Ethernet)

Company

Network Interface Company

Category

"Network"

Type

"Address"

Item

"MAC Address"

BMC_LANEndpoint relationships

Relationship

Name

Source

Destination

BMC_HostedAccessPoint
HOSTEDACCESSPOINT

BMC_ComputerSystem 
(Storage System)

BMC_LANEndpoint
BMC_Dependency
ENDPOINTPORT
BMC_NetworkPort
BMC_LANEndpoint

BMC_IPEndpoint

Attribute

Details

Name

IP address ip_addr

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

IPv6 prefix length in bits

SubnetMask

IPv4 subnet mask

Company

Network Interface Company

Category

"Network"

Type

"Address"

Item

"IP Address"

BMC_IPEndpoint relationships

Relationship

Name

Source

Destination

BMC_HostedAccessPoint
HOSTEDACCESSPOINT

BMC_ComputerSystem 
(Storage System)

BMC_IPEndpoint
BMC_HostedAccessPoint
HOSTEDACCESSPOINT

BMC_ComputerSystem 
(Storage System Group)

BMC_IPEndpoint
BMC_Dependency
ENDPOINTPORT
BMC_NetworkPort
BMC_IPEndpoint
BMC_Dependency
BINDSTO
BMC_LANEndpoint
BMC_IPEndpoint

BMC_IPConnectivitySubnet

The Subnet node is mapped to BMC_IPConnectivitySubnet.

Attribute

Details

Name

Subnet ip_address_range

ShortDescription

Subnet ip_address_range

Description

Subnet ip_address_range

SubnetNumber

Subnet ip_address_range

AddressType

IPv4 (1) or IPv6 (2)

PrefixLength

IPv6 prefix length in bits

SubnetMask

IPv4 subnet mask

Company

Cluster Company

Category

"Network"

Type

"Subnet"

Item

"TCP/IP"

BMC_IPConnectivitySubnet relationships

Relationship

Name

Source

Destination

BMC_InIPSubnet
INIPSUBNET
BMC_IPConnectivitySubnet
BMC_IPEndpoint

BMC_Cluster

The StorageSystemGroup node is mapped to the BMC_Cluster CI.

Attribute

Details

TokenId

TokenId is of the form "ADDM:StorageSystemGroup key".

See TokenId rules.

Name

StorageSystemGroup name.

ShortDescription

StorageSystemGroup name.

Description

StorageSystemGroup name.

ManufacturerName

StorageSystem vendor.

Model

StorageSystemGroup type.

SerialNumber

StorageSystemGroup serial.

Company

StorageSystemGroup Company.

Category

"Hardware"

Type

"Storage"

Item

"Storage cluster"

Where clustered, the StorageSystem node is also mapped to the BMC_Cluster CI.

Attribute

Details

TokenId

TokenId is of the form "ADDM:Device key".

See TokenId rules.

Name

StorageSystem name.

ShortDescription

StorageSystem name.

Description

StorageSystem name.

ManufacturerName

StorageSystem vendor.

Model

StorageSystem type.

Company

StorageSystem Company.

Category

"Hardware"

Type

"Storage"

Item

"Storage cluster"

BMC_Cluster relationships

Relationship

Name

Source

Destination

BMC_Component
CLUSTEREDSYSTEM
BMC_Cluster

Impacted

BMC_ComputerSystem

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*