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:
-
To search for an existing CIs during a CI Update Operation.
-
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 |
|
Chrome Books#2 |
Default Target: cmdb_ci_comm Cross Class Search: cmdb_ci_handheld_computing |
|
Linux Server |
Default Target: cmdb_ci_linux_server |
|
Unix Server |
Default Target: cmdb_ci_unix_server |
|
Windows Servers |
Default Target: cmdb_ci_win_server |
|
Windows Cluster |
Default Target: cmdb_ci_win_cluster |
|
Windows PCs |
Default Target: cmdb_ci_computer |
|
Virtualization |
|
|
Hyper-V Server |
Default Target: cmdb_ci_hyper_v_server |
|
VMWare vCentre |
Default Target: cmdb_ci_vcenter |
|
ESX Server |
Default Target: cmdb_ci_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 |
Default Target: cmdb_ci_comm Cross Class Search: cmdb_ci_handheld_computing |
|
iPhone |
Default Target: cmdb_ci_comm Cross Class Search: cmdb_ci_handheld_computing |
|
iPads |
Default Target: cmdb_ci_comm Cross Class Search: cmdb_ci_handheld_computing |
|
Other Mobile |
Default Target: cmdb_ci_comm Cross Class Search: cmdb_ci_handheld_computing |
|
Tablet |
Default Target: cmdb_ci_comm Cross Class Search: cmdb_ci_handheld_computing |
|
Network Equipment |
|
|
Firewalls |
Default Target: cmdb_ci_ip_firewall |
|
Routers |
Default Target: cmdb_ci_ip_router |
|
Switches |
Default Target: cmdb_ci_ip_switch |
|
Load Balancer |
Default Target: cmdb_ci_lb_network |
|
VOIP Gateway |
Default Target: cmdb_ci_voice_gateway |
|
Wireless Access Points |
Default Target: cmdb_ci_wap_network |
|
Wireless Controller |
Default Target: cmdb_ci_network_controller |
|
Other |
|
|
Fiber Switch |
Default Target: cmdb_ci_storage_switch |
|
Displays (as Asset)#1 |
Default Target: cmdb_ci_display_hardware |
|
IP Phone |
Default Target: cmdb_ci_ip_phone |
|
KVM Switches |
Default Target: cmdb_ci_keyboard_video_mouse_switch |
|
Printers |
Default Target: cmdb_ci_printer |
|
Remote Access Controllers |
Default Target: cmdb_ci_outofband_device |
|
Network Attached Storage (NAS) |
Default Target: cmdb_ci_storage_server |
|
Scanners |
Default Target: cmdb_ci_scanner |
|
Storage Area Network (SAN) |
Default Target: cmdb_ci_san |
|
Uninterruptible Power Supply (UPS) |
Default Target: cmdb_ci_ups |
|
IP Camera |
Default Target: cmdb_ci_ip_camera |
|
Operational Technology (OT) |
|
|
PLC |
Default Target: cmdb_ci_ot_plc |
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
See Override Options below for option to override the defaults for Mobile Device asset types.
The default table mappings for Secondary/Child Records are shown below.
|
Secondary/Child Records |
Default Target Class |
|---|---|
|
Displays (as Peripherals)#1 |
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_storage_device |
|
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) |
cmdb_ci_win_service |
|
Windows Licence Keys |
alm_entitlement_asset |
|
Windows Cluster Nodes (for Windows Servers) |
cmdb_ci_win_cluster_node |
|
Hyper-V Instances |
cmdb_ci_hyper_v_instance |
|
Hyper-V Networks |
cmdb_ci_hyper_v_network |
|
VMWare Datacentre |
cmdb_ci_vcenter_datacenter |
|
VMWare ESX Server Cluster (for vCentres) |
cmdb_ci_vcenter_cluster |
|
vCentre Datastore |
cmdb_ci_vcenter_datastore |
|
vCentre Network |
cmdb_ci_vcenter_network |
|
VMWare Virtual Machine Instance |
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, Fiber Switches, WLCs) |
cmdb_switch_port |
|
Fiber Channel Ports (for Fiber Switches) |
cmdb_ci_fc_port |
Override Options
Context
Customers may want to change the default behaviour as follows:
-
For mobile asset types (Chromebook, Android, iPhone, iPad, Other Mobile and Tablet), customers may want to change the mappings of to target cmdb_ci_handheld_computing instead of cmdb_ci_comm.
-
For all other asset types, customers may want to change the mappings to target different CMDB CI Tables/Classes then those shown in the table 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
-
For mobile asset types (Chromebook, Android, iPhone, iPad, Other Mobile and Tablet), customers can use a CI Sync connection setting to change the target tables between cmdb_ci_comm and cmdb_ci_handheld_computing.
-
For all other asset types, customers must request Syncfish to change the target tables.
Overriding via Connection Settings
For mobile asset types, customers can perform the mobile asset target table override using a “Connection Setting” via the CI Sync User Interface (i.e. customers can perform the overrides themselves). Additional information for this is available via the following documentation:
-
For a general overview of CI Sync Connection Settings please read Understanding the use of CI Sync Connection Settings.
-
For the specific CI Sync Connection Setting/s related to the rule described on this page please read Target Mobile Table Class for Lansweeper On-Prem.
For documentation on all CI Sync Connection Settings please visit the page tree Connection Setting Guides.
Additional Information
N/A
Related Rules
N/A