A detailed walkthrough and collection of best practices for setting up as a Meraki Managed Service Provider
- Getting Started
- Introduction to Meraki Dashboard
- Determining Organizational Structure
- Creating a Meraki Dashboard Account
- Activating the MSP Portal
- Configuring Organization Administrators
- Creating a New Customer Organization
- Configuring Single Sign On (SSO)
- Branding and Customization
- Ordering & Title Guidelines
- Infrastructure Financing Options
Using the MSP Portal
A description of next-generation services that are readily available with the Meraki platform
Meraki offers a zero-touch deployment model, allowing partners to offer rapid deployment through automated hardware provisioning. There are several Dashboard features, in particular, that are designed for highly scaled deployments which are typically standardized across all sites.
Network Configuration Cloning
At time of network creation, administrators are given the option to Clone from existing network. This powerful feature allows for cloning of all network settings from an existing network to the new network being created. To use this capability, choose the option Clone from existing network when prompted:
Configuration Sync (MR/MX Only)
Sometimes it is convenient or necessary to copy configurations from one network to another. If an Organization has multiple networks, it is possible to copy an existing MX or MR network configuration to another network. For MXs in particular, the traffic shaping and content/security filtering settings can be copied.
Configuration templates allows many Cisco Meraki devices to be deployed following a single base configuration. This not only makes it easier and quicker to roll-out new sites/users, but also to maintain consistency across each site’s configuration. This feature is most valuable in cases where a large number of sites exist that share a common network design — such as a retail deployment with many stores, or a large number of home users with Z1s connecting to a corporate network over VPN.
Sites as part of a template can have exceptions to the base configuration, and devices that need to be treated differently, can still be bound to a template. It is, however, important to note that not all settings can be changed on a site bound to a template. See Meraki Documentation for more information:
Meraki offers the Meraki Dashboard API – a modern, RESTful API using HTTPS for transport and JSON for object serialization. To learn more please see our API documentation.
Leave a Reply
You must be logged in to post a comment.