Rule 3 - Mapping of Meraki 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 Meraki 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
Meraki
Organisations	cmdb_ci_sdwan_controller
Network	cmdb_ci_ni_site
Switches	cmdb_ci_ip_switch
Appliances	cmdb_ci_sdwan_edge
Cameras	cmdb_ci_ip_camera
Cellular Gateways	cmdb_ci_modem_network
Secure Connects	cmdb_ci_modem_network
Sensors	cmdb_ci_ot_industrial_sensor
Wireless Access Points	cmdb_ci_wap_network
Wireless Controllers	cmdb_ci_network_controller

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

Secondary/Child Records	Default Target Class
Ports (for Switches)	cmdb_switch_port
Ports (for Networks)	cmdb_ci_sdwan_port
VLANs (for Networks)	cmdb_ci_network_topology
Tags	cmdb_key_value

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

The target CI Class can be amended per Cisco Meraki Asset Type.
The target Related List/Child Record table can be amended per Cisco Meraki 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