×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the product is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

BMC Discovery 11.3 ... Integrating CMDB synchronization Default CDM Mapping

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

CMDB version differences

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.

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

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

HostName

Network Device name

isVirtualNetwork 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

PartitionIDNetworkDevice 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 Members Network Devices to Stack Network Device (stack linkage).

Relationship

Name

Source

Destination

BMC_Dependency

DEVICEINSTACK

BMC_ComputerSystem (stack member)

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

Dependency relationships are created from managing Network Devices to the managed device.

Relationship

Name

Source

Destination

BMC_Dependency

DEVICEMANAGER

BMC_ComputerSystem (network device)

BMC_ComputerSystem (managed device)

Impacted

BMC_ComputerSystem (Host Container)

HostContainer nodes directly connected to the root Network Device in the 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)

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

Attribute that aids reconciliation of CIs populated by multiple data sources.
TokenId is of the form "ADDM:hashedkey", where hashedkey is a hash of HostContainer key

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 Discovery model is mapped to BMC_HardwareSystemComponent.

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.

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" or
Network Device name : computersystem name if the target is Remedyforce.

ShortDescription

"os_type os_version"

Description

"os_vendor os_type os_version"

ManufacturerName

Network Device os_vendor

MarketVersion

Network Device os_version

Model

Network Device os_type

OSType

Other (0)

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 Discovery model is mapped to a BMC_NetworkPort, and its MAC address is mapped to a BMC_LANEndpoint.

Where Discovery has been able to connect 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 interface_name : computersystem name 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

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:

AttributeDetails
Name

FibreChannelHBA description and FibreChannelPort wwpn or 
FibreChannelHBA description or 
FibreChannelHBA description and hostname if the target is Remedyforce.

ShortDescriptionFibreChannelPort wwpn
DescriptionFibreChannelHBA description and FibreChannelPort wwpn or just FibreChannelPort wwpn
LinkTechnologyFibre Channel (4)
ManufacturerNameFibreChannelHBA vendor
ModelFibreChannelHBA model
PermanentAddressFibreChannelPort wwpn
PortTypeFibre Channel (6)
SerialNumberFibreChannelHBA serial
CompanyHostCompany
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 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 : computersystem name 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_DependencyBINDSTOBMC_LANEndpoint

BMC_IPEndpoint

BMC_IPConnectivitySubnet

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_DependencyAPPLICATIONSYSTEMDEPENDENCY

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_DependencyAPPLICATIONSYSTEMDEPENDENCY

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_DataBase
BMC_Cluster

BMC_SoftwareServer
BMC_ApplicationSystem
BMC_ApplicationService
BMC_DataBase
BMC_Cluster

(Impacted)

  

Was this page helpful? Yes No Submitting... Thank you
Last modified by Duncan Tweed on Jan 12, 2021

Comments

Log in or register to comment.

CDM Mapping for MFPart
CDM Mapping for Load Balancer nodes
© Copyright 2004 - 2022 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2023 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.