CDM Mapping for Printer

This topic provides information about mapping for printer nodes. 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_Printer

The root Printer node is mapped to a root BMC_Printer CI with the following attributes:

Attribute	Details
Name	Printer name
ShortDescription	Printer name
Description	Printer name
CapabilityList	Print
EndOfExtendedSupport	End of Extended Support date.
EndOfLife	End of Life date.
EndOfSecuritySupport	End of Security Support date.
EndOfSupport	End of Support date.
firmware_version	Printer firmware version
HostName	Printer sysname
LastScanDate	Printer last_update_success — the date and time the device was last scanned
ManufacturerName	Printer vendor
Model	Printer model
PrimaryCapability	Print (11)
PrinterType	Network Printer (3)
SerialNumber	Printer serial
SystemOID	Printer sysobjectid
Category	"Hardware"
Type	"Peripheral"
Item	"Printer"

BMC_NetworkPort, BMC_LANEndpoint and BMC_IPEndpoint

Each Network Interface node connected to the root Printer node 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 has been able to connect a Printer node to a Network Device node, a BMC_Dependency relationship is created between the two BMC_ComputerSystem CIs representing the printer and the network device.

BMC_NetworkPort

Attribute	Details
Name	NetworkInterface interface_name
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	HostCompany
Category	"Hardware"
Type	"Card"
Item	"Network interface 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
Name	NetworkInterface mac_addr
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

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 Printer node is mapped to a BMC_IPEndpoint CI:

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