Rule 3 - Mapping of Lansweeper Cloud Asset Types to CMDB CI Classes

Rule Synopsis

These are the rule/s that determine the target CMDB CI Tables/Classes used by CI Sync for each Lansweeper Asset Type.

The target CI Table/CI Class is used by CI Sync for two purposes:

  1. To search for an existing CIs during a CI Update Operation.

  2. To write new CIs during a CI Insert Operation.

Rule Details and Default

The default table mappings for Primary/Parent Resource Types are shown below.

Primary/Parent Resource Types

Default Target Class/Classes

Computer Systems

Apple Mac

Default Target: cmdb_ci_computer

Linux Server

Default Target: cmdb_ci_linux_server

Cross-Class Search: cmdb_ci_unix_server, cmdb_ci_server, cmdb_ci_computer

Unix Server

Default Target: cmdb_ci_unix_server

Cross-Class Search: cmdb_ci_linux_server, cmdb_ci_server, cmdb_ci_computer

Windows PCs

Default Target: cmdb_ci_computer

Cross-Class Search: cmdb_ci_win_server

Windows Servers

Default Target: cmdb_ci_win_server

Cross-Class Search: cmdb_ci_server, cmdb_ci_computer

Chrome Books#2


Windows Cluster#2


Virtualization#2

Hyper-V Server


VMWare vCentre


ESX Server


Data Base Systems

Windows Server SQL Server Instance

Default Target: cmdb_ci_db_mssql_instance

Windows PC SQL Server Instance

Default Target: cmdb_ci_db_mssql_instance

Mobility#2

Android


iPhone


iPads


Other Mobile


Tablet


Network Equipment

Firewalls

Default Target: cmdb_ci_ip_firewall

Cross-Class Search: cmdb_ci_ip_netgear

Load Balancer

Default Target: cmdb_ci_lb_network

Routers

Default Target: cmdb_ci_ip_router

Cross-Class Search: cmdb_ci_ip_switch, cmdb_ci_ip_netgear

Switches

Default Target: cmdb_ci_ip_switch

Cross-Class Search: cmdb_ci_ip_router, cmdb_ci_ip_netgear

Wireless Access Points

Default Target: cmdb_ci_wap_network

Wireless Controller

Default Target: cmdb_ci_network_controller

Fiber Switch#2


Storage

Network Attached Storage (NAS)

Default Target: cmdb_ci_storage_server

Storage Area Network (SAN)

Default Target: cmdb_ci_san

Operational Technology (OT)

OT PLC

Default Target: cmdb_ci_ot_plc

OT Field Device

Default Target: cmdb_ci_ot_field_device

OT Human Machine Interface

Default Target: cmdb_ci_ot_hmi

OT Industrial Drive

Default Target: cmdb_ci_ot_industrial_drive

OT Industrial Sensor

Default Target: cmdb_ci_ot_industrial_sensor

OT Module

Default Target: cmdb_ci_ot_control_module

OT OPC Server

Default Target: cmdb_ci_ot_opc_server

Other

Network Printers

Default Target: cmdb_ci_printer

Cross-Class Search: cmdb_ci_mfp_printer, cmdb_ci_personal_printer

Remote Access Controllers

Default Target: cmdb_ci_outofband_device

Scanners

Default Target: cmdb_ci_scanner

Uninterruptible Power Supply (UPS)

Default Target: cmdb_ci_ups

VOIP Gateway

Default Target: cmdb_ci_voice_gateway

VOIP Phone

Default Target: cmdb_ci_ip_phone

KVM Switches

Default Target: cmdb_ci_keyboard_video_mouse_switch

Displays (as Assets)#1, #2


IP Camera#2


Certificates

Certificates

Default Target: u_cmdb_ci_certificate

Footnote #1

The way CI Sync handles Displays as either a peripheral of a main/parent asset, or as an asset in their own right depends on the connection setting described on this page: https://syncfish.atlassian.net/wiki/x/CADoeeUE

Footnote #2

CI Sync mappings for these record sets are being progressively added by Syncfish (so may not yet be available). Please contact Syncfish for information about the current status of these record sets.

Footnote #3

These record sets are available via the Lansweeper On-Prem connector, but not currently available via the Lansweeper Cloud API.

The default table mappings for Secondary/Child Records are shown below.

Secondary/Child Records

Default Target Class

Displays (as Peripherals)#1, #2

cmdb_ci_display_hardware

Software Installs (for multiple record types)

cmdb_software_instance

Memory Modules (for multiple record types)

cmdb_ci_memory_module

Network Adapters (for multiple record types)

cmdb_ci_network_adapter

Disk (for multiple record types)

cmdb_ci_disk

File System (for multiple record types)

cmdb_ci_file_system

IP Address (for multiple record types)

cmdb_ci_ip_address

Windows Patches (for Windows devices)

cmdb_ci_patches

Registry Entries (for Windows devices)

cmdb_ci_config_file_tracked

Mapped Network Drives (for Windows devices)

cmdb_ci_file_system

Windows Services (for Windows devices)#2

cmdb_ci_win_service

Windows Licence Keys#3

alm_entitlement_asset

Windows Cluster Nodes (for Windows Servers)#2

cmdb_ci_win_cluster_node

Hyper-V Instances#2

cmdb_ci_hyper_v_instance

Hyper-V Networks#2

cmdb_ci_hyper_v_network

VMWare Datacentre#2

cmdb_ci_vcenter_datacenter

VMWare ESX Server Cluster (for vCentres)#2

cmdb_ci_vcenter_cluster

vCentre Datastore#2

cmdb_ci_vcenter_datastore

vCentre Network#2

cmdb_ci_vcenter_network

VMWare Virtual Machine Instance#2

cmdb_ci_vmware_instance

User Database (for SQL Server Instances)

cmdb_ci_db_mssql_database

System Database (for SQL Server Instances)

cmdb_ci_db_mssql_database

Ethernet Ports (for Firewalls, Routers, Switches, WLCs)

cmdb_switch_port

Ethernet Ports (for Fiber Switches)#2

cmdb_switch_port

Fiber Channel Ports (for Fiber Switches)#2

cmdb_ci_fc_port

Footnote #1

The way CI Sync handles Displays as either a peripheral of a main/parent asset, or as an asset in their own right depends on the connection setting described on this page: https://syncfish.atlassian.net/wiki/x/CADoeeUE

Footnote #2

CI Sync mappings for these record sets are being progressively added by Syncfish (so may not yet be available). Please contact Syncfish for information about the current status of these record sets.

Footnote #3

These record sets are available via the Lansweeper On-Prem connector, but not currently available via the Lansweeper Cloud API.

Override Options

Context

Customers may consider changing these mappings to target different CMDB CI Tables/Classes shown above.  This can often be required when existing CIs are already present in the CMDB (in Classes different to those shown below) and CI Sync is expected to correlate to the existing CIs.

Options

  1. The target CI Class can be amended per Lansweeper Asset Type.

  2. The target Related List/Child Record table can be amended per Lansweeper Asset Type.

Overriding via Connection Settings

Not Available - Requires a Custom Data Sync Rule (and therefore a Syncfish Support Plan to modify the default behaviour)

Additional Information

N/A

N/A