Skip to content

Meraki Launchpad Labs logo

Meraki MX SD-WAN with Secure Access


Learning Objectives

In this lab, you will be learning and practicing how to:

  • Deploy and configure Meraki MX security appliances across branch and data center environments, including implementing security policies and advanced security features.

  • Build and optimize an Auto-VPN SD-WAN fabric, using intuitive dashboard workflows and practicing performance-based routing for resilient connectivity.

  • Integrate branch networks with the Cisco Secure Access SSE platform for Secure Internet Access (SIA) use cases, establishing IPsec connectivity and enabling cloud-delivered security services.

This lab is expected to take approximately 1 -- 1.5 hours to complete.

Note

If you're viewing this lab manual but don't currently have access to a lab environment, please contact your Cisco technical sales representative—they can help you reserve a lab pod.


How to Read the Lab Manual

Throughout all the lab manuals you will see various notations that serve to call out different types of information. These are classified into the following categories:

Important

These are high priority, critical bits of instructions that you must read carefully and pay close attention to performing correctly or they could have an adverse effect on your lab.

Note

These are typically warnings that usually serve as reminders as they are sometimes easily overlooked or missed.

Hint

These are useful pieces of advice that could help point you in the right direction or help draw your attention to hard-to-find or confusing configurations.

Information

These serve as additional footnotes and reference materials sourced from the official Meraki documentation portal (located at: https://documentation.meraki.com) for various topics or technologies.


Getting Started

Welcome and Lab Access

For now, if the provided email during the lab deployment is associated with an existing Dashboard account, you should have received a message from Meraki Dashboard, notifying you that the new Cisco Meraki administrator privileges have been granted to your account. Please follow the instructions to verify your email and accept the new privileges.

Example email for existing dashboard account

If this is your first time accessing the Meraki Dashboard with this email, the message you receive will be slightly different and will guide you to create a password (see example below).

Example email for new dashboard account

Important

If your Meraki dashboard account is also associated with other organizations—especially production environments. DO NOT perform any of the steps in this guide on your own organization. You should only work within the provided lab organization, which follows the naming pattern "Org-[org_id]". If you're still unsure, navigate to Organization > Administrators in the Dashboard. If you see an admin named ENLS with the email launchpad-labs-ops@cisco.com, that's the lab organization you should be working in.

Lab Pod Inventory and Topology

Your lab station contains the following equipment as depicted in the following topology diagram:

Topology illustration Topology illustration

Topology Illustration

In this lab environment, there are three networks: a full stack of Meraki Branch network and two Datacenter networks with a security appliance in each. You will have full permissions to all these networks and read-only to the organization.

Each lab organization will be assigned both primary and secondary Secure Access Tunnel Groups, to which you will build VPN tunnels to enable the Secure Internet Access (SIA) for the branch network during the lab.

Note

This lab focuses on Secure Internet Access and does not include SSE use cases such as BGP over IPsec tunnels or Remote Access.

Important

To complete the lab, you will need full organization permissions to the lab environment. If you don't have it yet, please check with your Cisco proctor who reserved the lab for you.

Important

Since you are a full-permission administrator for the lab organization, please strictly follow the lab guide. Unless specifically advised, do not make any changes at the organization level, such as administrators, inventory, or licenses.