Guide Overview

This guide is designed to give Incident IQ administrators an overview of the following Cisco Meraki integration app related topics:

  • Managing settings that control asset creation and deletion, as well as when and what information is updated during syncs
  • Setting up location and model mappings
  • Enable remote device actions
  • Sync and asset history lookup tools
  • Frequently asked integration questions

 

Guide Index

You can use the following links below to quickly navigate to a specific section in this document. To quickly return to this index simply use the "Return to Index" link located at the end of any section.

  1. Introduction
  2. Installing Cisco Meraki 
  3. Integration Overview
    1. Overview Tab
    2. General Settings Tab
    3. Location Mappings Tab
    4. Model Mappings Tab
    5. Sync History Tab
    6. Asset History Tab
  4. Remote Device Actions

Introduction

The Cisco Meraki integration app is designed to give school districts the ability to create, manage, and automatically assign assets to students in Incident IQ by utilizing Cisco Meraki asset data. In addition, this integration with Incident IQ also allows agents and admins the ability to view an asset's metadata in one convenient location. This includes basic device information, OS and firmware versions, as well as other data agents may find useful during the course of working a ticket.

When installed, you can access the Cisco Meraki Integration app by selecting Incident IQ Apps > Apps Management. This will take you to your Installed Apps page where you can select the Manage button to access the Cisco Meraki Integration management page.

mceclip5.png

[Return to Index]

 

Installing Cisco Meraki

To install the Cisco Meraki integration, begin by clicking on Incident IQ Apps > Browse on the left side bar. Next, under the Asset Management section, click on the Cisco Meraki.

mceclip0.png

From here, simply select Install and follow the steps to complete the installation.

mceclip1.png

Once installed in Incident IQ you will need to click on Manage App Settings.

mceclip2.png

Next, under the General Setting tab, you will need to allow access to your Cisco Meraki asset data by entering the following Cisco Meraki information:

  • Network ID 
  • API Key 

mceclip3.png

Next, you will need to run a sync. Navigate to the Overview Tab and click Start Full Sync. This will accomplish the following:

  • Establish a connection Incident IQ and Cisco Meraki asset information. 
  • Allows Incident IQ to see what models are available in your Cisco Meraki. This is necessary to set up automatic asset creation.

mceclip1.png

[Return to Index]

 

Integration Overview

The following sections is designed to give you a detailed overview of each tab of the integration and the tabs intended purpose. After installing Cisco Meraki and running your first sync. Your next steps are to:

  1. Enable how your assets are create and updated within iiQ under the General Settings Tab. 
  2. Map the location of assets under the Location Mapping Tab.
  3. Map the model for your assets under the Model Mapping Tab.
  4. Run a full sync under the Overview Tab.

mceclip0.png

[Return to Index]

 

 Overview Tab

The Overview Tab provides gives you the ability to quickly review the status of the most recent sync between Incident IQ and Cisco Meraki. While syncs will automatically run overnight, you have additional options: 

  • Start Full Sync - manually start a new sync.
  • Re-Run Last Sync - run the very last sync again. 

mceclip1.png

Additionally, you can use the View Details button to take you directly to the Sync History tab where you can review the count of assets updated, added, or skipped over during the most recent sync.

mceclip2.png

[Return to Index]

 

 General Settings Tab

The General Settings tab has the settings that control when information is brought in or updated automatically, as well as field mappings between the Cisco Meraki and Incident IQ. As such, you can find the following settings here:

  • Authentication fields to enter the Cisco Meraki Network ID and API Key.
  • Options that control if assets are automatically created, updated, and deleted during system syncs.
  • The ability to turn on automatic room assignment for assets if you are storing this data in Cisco Meraki.
  • Custom field asset mapping options to pull in additional data for use in asset filters and custom view columns
  • An option to enable the use of remote asset features available in Cisco Meraki directly on an asset detail's page by administrators and agents with the correct permissions

The Authentication section is where you enter in the following fields for Cisco Meraki School authentication information: 

  • Network ID
  • API Key

mceclip3.png

The Mapping section manages what data is created and updated in Incident IQ based on data coming from Cisco Meraki. This includes:

  • Create Asset: Selecting this will automatically create assets in IIQ to match any new device discovered in Cisco Meraki during a sync.
  • Update Asset: Selecting this will automatically update assets in IIQ to match any updates to a device's data discovered in Cisco Meraki during a sync.
  • Update Custom Fields: Selecting this option will only allow new information being pulled into custom fields to update during a sync.
  • Delete Asset: Selecting this will automatically delete assets in IIQ to match any assets deletions that have occurred in Cisco Meraki during a sync.

mceclip6.png

Next, under the Import Options section you can enable the Create Rooms option. This will automatically create rooms associated with assets in Cisco Meraki if these rooms do not already exist in Incident IQ. 

mceclip4.png

The Map custom values section allows you to select additional values you want imported and map them to default or custom fields in iiQ. This gives you the ability to pull in custom data fields and custom view column options. Click on the Add button. 

mceclip3.png

Next, fill out the following field mapping options:
Please note, there may be pre-configured mapping and they can not be changed.

  1. Select the custom value  
  2. Select the iiQ field the custom value should map too. You can map to default field or map to a custom field.
    • If you map to a Custom Field, you will need to set a field name, select a field type (text, number, or date), and set whether the field information needs to be searchable through filters.

mceclip4.png

You can control whether or not the Cisco Meraki integration will update the owner field in Incident IQ using the following options in the Meraki MDM options section:

  • Automatically update asset owner in iiQ: This option will automatically update the device ownership of assets in Incident IQ based on the owner in Meraki.
  • Remove existing owner in iiQ for assets that have an empty owner field in Meraki MDM.
  • Remove existing owner in iiQ for assets where the owner field in Meraki MDM can't be matched to a valid user.

mceclip5.png

The last section is the Remote Device Actions. You can enable remote device actions that administrators and agents with the correct permissions can access directly on an asset's details page in Incident IQ. These options include:

    • Meraki MDM: Remote Lock Device: Allow a user to remotely lock an Meraki managed device.
    • Meraki MDM: Wipe Device: Allow a user to remotely wipe a Meraki managed device.

Please see the section below for more details on enable device actions based on users roles. 

mceclip6.png

[Return to Index]

 

 Location Mappings Tab

This tab allows you to select or modify your current location mappings between IIQ and Cisco Meraki. You can choose to automatically assign a device to a default location in Incident IQ if it does not match any location mappings set. This is especially important if you are using the Cisco Meraki integration to automatically create assets because assets must have a location set to be created.

Location is required for an asset to be created in iiQ. The way this works during a sync is as follows:

  • If an asset matches the location mapping, then the asset will get created and assigned to the corresponding location the mapping is set to.
  • If an asset does not match a location mapping, or no location mappings are present, and a default location is selected, then the asset will get created and assigned to the default location.
  • If an asset does not match a custom mapping, or no custom mappings are present, and there is no default location set, then the asset will not be created during a sync.

mceclip9.png

The Custom Mapping Options allows you to choose how you would like devices to map in IIQ. When Location Name is selected, you will be presented with a list of locations currently in the system. 

mceclip10.png

[Return to Index]

 

 Model Mappings Tab

This tab allows you to select or modify your current model mappings between IIQ and the Cisco Meraki. You can use the Auto-Map Models button to automatically attempt to match models in your list of devices with models that already exist in IIQ.

mceclip12.png

Alternatively, you can also manually select what model your device should map to using the drop-down menus to the right of each listed device.

mceclip16.png

If your device will not auto-map and is not available from the drop-down options, then it most likely does not currently exist in IIQ. In this case, simply select the Create New Model button on the right of the device mapping in question to automatically create and activate this model during your data sync.

mceclip17.png

[Return to Index]

 

 Sync History Tab

This tab allows you to view your sync history between IIQ and the Cisco Meraki. Every sync, whether it completed successfully or not, is logged for reference purposes and available for review in the View details of a sync list.

mceclip12.png

Clicking on any sync, in particular, will open that sync's details. From here, you can review the full list of what devices were updated, created, deleted, or skipped during the sync. Additionally, you can narrow down your view by using the filter options at the top of the list.

mceclip13.png

[Return to Index]

 

 Asset History Tab

The Asset History tab allows you to search for basic information on any device currently located in your Cisco Meraki. Simply enter in a valid serial number in the Search for asset field to begin your search.

mceclip24.png

Once you've selected a device, you'll be able to see the following Cisco Meraki information:

  • External ID
  • Model
  • Owner Email
  • Organizational Unit
  • Serial Number
  • Location Name

Additionally, you'll also see a list of actions applied to this device during recent system syncs.

mceclip14.png

[Return to Index]

 

Remote Device Actions

Under the General Settings tab at the bottom of the page, you can enable remote device actions that administrators and agents with the correct permissions can access directly on an asset's details page in Incident IQ. These options include:

  • Meraki MDM: Remote Lock Device: Allow a user to remotely lock an Meraki managed device.
  • Meraki MDM: Wipe Device: Allow a user to remotely wipe a Meraki managed device.

mceclip9.png

Please note, administrators are given full access to all remote features permissions by default. However, each of the remote features listed above are controlled by an individual permission. This makes it possible to customize which permissions an agent has access to, without needing to give them full access to all of the remote features. These permissions can be found underneath the App Specific section on policies and individual user permissions pages.

mceclip8.png

On the asset details page you will have access to preform these actions. 

mceclip11.png

[Return to Index]

Was this article helpful?
0 out of 0 found this helpful