In short
Meraki setup means designing the network, creating a dashboard organisation and networks, claiming the order's devices and licences, building settings (VLANs, SSIDs, firewall rules, switch ports, templates), scheduling firmware, then staging, installing and cutting over. Devices download their configuration from the Meraki cloud when they first come online, so most of the work happens in the dashboard.
Want help with Meraki setup and deployment?
We can plan it with you or do it for you. Tell us where you are up to.
What a Meraki deployment involves
Cisco Meraki devices are managed from the Meraki dashboard, a web console hosted by Cisco. When a Meraki access point, switch or security appliance is plugged in and can reach the internet, it checks in to the cloud and downloads the configuration you have prepared for it. That is why Meraki is often described as zero-touch: the person on site plugs it in; the configuration comes from the dashboard.
That convenience moves the work rather than removing it. A Meraki setup that runs well for years usually has:
- a clear organisation and network structure in the dashboard
- an addressing and VLAN plan that suits every site, not just the first
- SSIDs, firewall rules and switch port profiles designed around how people work
- licences claimed into the right model (subscription or co-term) with known expiry or renewal dates
- admin accounts, roles and alerts set up before go-live, not after the first incident
- documentation a new engineer can follow
The steps below cover a typical deployment of access points, switches and an MX security and SD-WAN appliance. Smaller jobs skip some steps; larger ones repeat them per site.
Meraki setup step by step
- Gather requirements. Users and devices per area, applications, internet circuits, existing equipment, security and compliance needs, and any sites, home workers or cellular backup to include.
- Survey the building for Wi-Fi. Coverage and capacity depend on walls, ceilings and how many devices connect at once. A wireless site survey turns floor plans into access point positions before anything is ordered.
- Design the network. VLANs and IP addressing, SSIDs and authentication, firewall and traffic-shaping rules, switch port roles and power over Ethernet budgets, VPN topology between sites and uplink failover.
- Choose hardware and licensing. Pick product families (MR or Cisco Wireless Wi-Fi 7 access points, MS switches or cloud-managed Catalyst switches, MX appliances) and a licensing model: subscription or co-term.
- Create the organisation and networks. One organisation per company is usual, with a network per site. Decide now whether sites will share a configuration template.
- Claim the order. Devices are claimed into the organisation's inventory individually by their Cloud ID (the Meraki serial number) or in bulk with the order claim key, then added to networks. The Meraki mobile app can scan and claim devices on site. Licences are claimed in the same place.
- Build the configuration. Addressing, VLANs, DHCP, SSIDs, group policies, firewall rules, switch port profiles, Auto VPN and alerts, either per network or in a template.
- Set firmware. Pick the Recommended Release for each product, set maintenance windows and schedule upgrades from the dashboard's firmware upgrades tool.
- Stage and test. Power devices up on a bench or in the comms room, confirm they check in, take the right firmware and pass traffic as designed.
- Install and cut over. Mount and patch devices, move users and services over in a planned order, and keep a way back to the old network until the new one is proven.
- Validate. Check Wi-Fi coverage and roaming in the real building, test failover, confirm guest isolation and security rules.
- Document and hand over. Record the design, addressing, admin accounts, licence dates and any exceptions, and agree who looks after changes from here.
Our own projects follow this path, with the order and depth agreed for each job. We confirm timescales at quote, because they depend on lead times, access to the building and how much of the old network has to keep running during the change.
Organisation and network structure
The dashboard has a simple hierarchy, and getting it right early makes everything after it easier.
| Dashboard level | What it is | Setup advice |
|---|---|---|
| Organisation | The top level: inventory, licensing, administrators and every network belong to it | Usually one per company. Licensing models cannot be mixed within one organisation |
| Network | A site or logical group of devices; access points, switches and an MX can share one combined network | One network per site keeps monitoring, alerts and firmware scheduling clear |
| Configuration template | A base configuration that many networks are bound to, so one change reaches every bound site | Ideal for many similar sites such as branches or stores. Some settings cannot be changed locally on a bound network |
| Network tags | Labels on networks | Use them to give admins access to a group of networks, such as one region |
| Device tags and names | Labels and names on individual devices | Agree a naming convention before claiming, for example site, floor and role |
For organisations with many sites, read our guide to multi-site networks, which covers templates, Auto VPN and central visibility in more depth.
Not sure which level applies to you? Ask us
Tell us about your organisation and we will point you to the right level.
Notes by device type
Meraki switch setup
Plan port roles before the switches arrive: access ports for desks, ports for access points, voice and cameras, trunk uplinks and any ports that need power over Ethernet. Port profiles and switch templates let you apply the same settings to many ports or many switches of the same model. If the switches will stack, cable the stack and add it in the dashboard as one stack; our Meraki MS page covers physical and virtual stacking.
Meraki MX setup
The MX is usually the site's gateway and firewall, so its WAN settings come first. Check what each internet circuit needs (DHCP or static addressing), then plan uplink preferences, VLANs, firewall rules and Auto VPN. If an MX needs a static IP address before it can reach the cloud, it can be set on the device's local status page. Two MX appliances can run as a warm spare high-availability pair. Security features depend on the licence edition: see Enterprise vs Advanced Security.
Access point setup
Access points take their SSIDs, authentication and radio settings from the network or template. Decide which SSIDs are bridged onto your VLANs and which use NAT mode, set the band and channel strategy, and add a floor plan so access points appear in the right place on the map. Guest and staff design is covered on our cloud managed Wi-Fi page.
Upstream firewalls
Meraki devices need outbound access to the Meraki cloud. The exact destinations and ports for your organisation are listed in the dashboard under Help > Firewall info. Check them against any firewall or web filter between your devices and the internet before installation day.
Meraki best practices we build in
| Area | Practice | Why it matters |
|---|---|---|
| Management | A dedicated management VLAN for switches and access points, with addressing planned per site | Keeps device management apart from user traffic and makes troubleshooting predictable |
| Naming | One naming convention for networks, devices, SSIDs and VLANs | Searching, alerts and reports make sense to everyone |
| Admin access | At least two organisation administrators with full rights, everyone else on the least access they need, permissions by network tag where it helps | Meraki recommends at least two full organisation admins; fewer full admins means fewer accounts to protect |
| Sign-in security | Two-factor authentication on every admin account, or SAML single sign-on through your identity provider | The dashboard controls every device, so admin accounts are high-value targets. See Meraki dashboard login |
| Alerts | Email or webhook alerts for devices going offline, uplink failover and configuration changes | Problems are noticed by the people responsible for them |
| Firmware | Recommended Release by default, maintenance windows outside working hours, beta only to test a specific fix | Upgrades happen when they cause least disruption, and a recently upgraded network can be rolled back |
| Templates | Use templates for genuinely similar sites; keep one-off sites as standalone networks | Templates save time at scale, but some settings cannot be changed locally on a bound network |
| Licensing | Record the licensing model and expiry or renewal dates, and who is responsible for them | Unlicensed devices stop working after any grace period. See Meraki licence expiry |
Prefer a hand with this?
We can help you plan it and set it up, alongside your own team.
Moving from an existing network
Most Meraki projects replace something: an older controller-based Wi-Fi system, unmanaged switches, a firewall from another vendor or a small-business product such as Meraki Go. Things that need care during the change:
- Addressing. Keep the existing IP ranges, or re-address and update every server, printer and static device that depends on them.
- Firewall rules and VPNs. Rules built up over years on the old firewall need reviewing, not copying line for line. Partners' site-to-site VPNs need new settings agreed with them.
- Wi-Fi names and passwords. Keeping existing SSIDs avoids reconfiguring every device; changing them is a chance to move to WPA3 or certificate-based access.
- Voice and cameras. Phones and cameras need the right VLANs and power budgets on the new switches.
- Timing. Cut over when the business can live with a short interruption, with a plan to roll back.
Moving from Meraki Go is a special case covered in Meraki Go alternative, and the wider choice between cloud and on-premise management is on cloud vs on-premise networking.
How Forever Systems helps with Meraki setup
Forever Systems is a Cisco Partner. We can design the network, survey the building, supply the hardware and licences, build the dashboard configuration, stage and install the equipment and plan the cutover. If you already own Meraki equipment, we can review an existing setup against the practices above and help tidy it up.
Ask us for a quote: contact us with your sites, rough device numbers and what you are replacing.
Working with us on Cisco Meraki
Forever Systems helps organisations plan, buy and run cloud-managed networks built on Cisco Meraki wireless, switching, security and SD-WAN.
- Plan the network: we look at your sites, users and existing kit, and can arrange a wireless site survey before anything is ordered
- Choose the right products: access points, switches, security appliances, cellular gateways, sensors and cameras sized to what each site needs, rather than a one-size bundle
- Licensing made clear: we explain co-termination, per-device and subscription licensing, check renewal dates and quote the licences you need
- Deployment help: we can set up the Meraki dashboard, organisations, networks, templates and policies, and help move you from older or on-premise kit
- Ongoing help: changes, licence renewals and reviews as your sites grow, with the scope agreed at quote
Ask us for a quote and we will confirm what is included for your organisation.
Frequently asked questions
How do I set up a Meraki network?
Create an organisation and networks in the Meraki dashboard, claim your devices and licences into the organisation's inventory, add the devices to networks, build the configuration (VLANs, SSIDs, firewall rules, switch ports), schedule firmware, then connect the devices to the internet so they download their settings. Design and a wireless survey come first for anything beyond a very small site.
How do I add a device to the Meraki dashboard?
Claim it into your organisation's inventory using its Cloud ID (the Meraki serial number on the device), or claim everything on an order at once with the order claim key, then add it to a network. The Meraki mobile app can also scan and claim devices. Catalyst devices are claimed with their Cloud ID, not the Cisco serial number.
Do Meraki devices need internet access to be set up?
Yes. Meraki devices download their configuration from the Meraki cloud, so they need an internet path the first time they come online. If a device needs a static IP address to get online, it can be set on the device's local status page. User traffic does not pass through the cloud.
What firewall rules does Meraki need?
Meraki devices need outbound access to the Meraki cloud. The destinations and ports for your organisation are listed in the dashboard under Help > Firewall info. Check them against any upstream firewall or web filter before installation.
Should I use Meraki configuration templates?
Use them when you have several sites that genuinely share one design, such as branches or stores: one change then reaches every bound network. Keep unusual sites as standalone networks, because some settings cannot be changed locally on a network bound to a template.
How long does a Meraki deployment take?
It depends on the number of sites, hardware lead times, building access and how the changeover has to be phased. We agree a plan and timescale with you at quote rather than giving a standard figure.
Still have a question about Meraki setup and deployment?
Ask us and a member of our team will reply by email.