Onboard Meraki MX to Security Cloud Control

MX devices can be managed by both Security Cloud Control and the Meraki dashboard. Security Cloud Control deploys configuration changes to the Meraki dashboard, which in turn deploys the configuration securely to the device.

Before you begin

  • Review Connect Security Cloud Control to your Managed Devices

  • Review How Does Security Cloud Control Communicate With Meraki

  • You must first register the Meraki MX in the Meraki dashboard. Without having access to the Meraki dashboard, your organization will not be recognized by the Meraki cloud and you will not be able to generate an API token to onboard your device.

  • Security Cloud Control silently converts invalid CIDR prefix notation IP addresses and IP address ranges to valid form by zeroing all bits associated with the host.

  • Onboarding Meraki MX devices or templates no longer requires a connection through a Secure Device Connector (SDC). If you have some Meraki MX devices that have already been onboarded and connect to Security Cloud Control using an SDC, that connection will continue to work unless you remove and re-onboard the device or update its connection credentials.

  • MX devices do not have to be connected to the Meraki Cloud in order to be managed by Security Cloud Control. If a MX device has never connected to the cloud, the device connectivity is listed as unreachable. This is normal, and does not affect your ability to manage or deploy policies to this device.

Procedure

 Command or ActionPurpose

Step 1

When you onboard a Meraki MX device, you must generate a Meraki API key. The key authenticates the dashboard and allows you to securely onboard a device. See Generate and retrieve a Meraki API key.

Step 2

Onboard a Meraki Device to Security Cloud Control using the API key.