- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Meraki Devices needed for communication with MG Gateway
What Meraki devices are needed on the remote site for the MG Gateway from the other site to communicate with it? Does the remote site need to have an MG Gateway as well?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can run a full stack behind the MG, or you can run the MG as an independent 5G gateway - up to you based on the architecture of your site. Keep in mind bandwidth varies by carrier, by region, by time of day even.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As per @javalins, there's no dependency in either direction; another vendor's firewall or switches could be provided with cellular Internet connectivity using an MG. And/or an MX could use another vendor's cell gateway to provide its Internet uplink. The advantage of pairing MG and MX (and indeed other Meraki devices like switches, APs, sensors or cameras) is the simplicity of having them all working together, managed and monitored all together in one deployment via a simple cloud-hosted GUI; https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Combined_Dashboar...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you have a Cisco account, this link is a free training course that provides an overview of the MG and how to use it.
https://learning.meraki.net/#/online-courses/6e38fe24-83bd-44c7-8829-8e7aac265175
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Just one other thought, reading this again.
MG is not involved in setting up secure tunnels between locations - if that's what you need. That would be an MX (or a vMX) to do that. For best functionality you'd have an MX (or a vMX) at the other end too, but it could in principle be IPSec device; either another vendor's device, a compliant cloud service (SSE / SASE) or an MX / vMX that resides in a different Dashboard Organization.
