Just to add on to Kathleen's comment above, we also recommend incorporating a 2nd switch into the topology to avoid having a single point of failure.  This portion of the doc that Kathleen linked to shows what this topology would look like: https://documentation.meraki.com/MX/Deployment_Guides/MX_Warm_Spare_-_High_Availability_Pair#Recommended_Topologies   Thanks Ian ... View more

Hi @dandlfa,   Unfortunately, Android Go doesn't support Android Enterprise, meaning that devices running Android Go cannot be enrolled into Meraki Systems Manager.   A full list of supported operating systems can be found at this link: https://documentation.meraki.com/SM/Other_Topics/Supported_Operating_Systems_with_Meraki_SM   Let me know if you have any other questions! ... View more

Hi Zack,   Thanks for your question.  There's no functionality in place to reboot the integrated cellular interface on the MX without power cycling the device.   It'd be helpful to know why you and your colleagues are needing to reboot the cellular interface in the first place, as it shouldn't be coming offline while the MX is powered on.  Have you and your team identified the root cause behind the loss of service?  Any additional information would be great.   Thanks Ian ... View more

Hi Naomi, Good question! Yes, you can still use NAT mode even if an overlapping subnet exists on the network. Client traffic is translated to use the IP address of the access point when accessing internet resources. Therefore, it won't cause any addressing conflicts with your existing 10.0.0.0/8 network. To answer your 2nd question, there is no way to edit which subnet is used for NAT mode. This is a fixed setting. To learn more about NAT mode, you can check out this article from our documentation: https://documentation.meraki.com/MR/Client_Addressing_and_Bridging/NAT_Mode_with_Meraki_DHCP ... View more