If you have saved L2TP/IPSec settings on your device, you can continue to use them after upgrading to Android 12. However, you won't be able to add new L2TP/IPSec settings. To connect to a VPN on Android 12 or higher, you can install a third-party VPN client, such as AnyConnect (or Cisco Secure Client). This can be downloaded from the Play Store. You then can setup the AnyConnect page on your Meraki device and use the given URL to connect the Android device to the network over a VPN. Meraki Support can also help walk you through this if you run into any issues, and they can also check for any limitations your configuration may have.

Hi @richjordan9375, I would recommend checking out the Port Mapping (documentation.meraki.com/MX/Other_Topics/MX_Cold_Swap_Replacing_an_Existing_MX_with_a_Different_MX#Port_Mapping_for_different_MX_models) for different MX models for the most detailed explanation. What is currently configured as the first LAN port on your MX84 (Port 3) will be retained as the first LAN port on your MX85 (Port 5), and the same with all remaining ports from there. One good way to test this beforehand is to simply clone your MX84 network and temporarily assign your MX85 to the new network. You should observe the same LAN port configurations as are in place for your MX84, just starting with Port 5 instead of Port 3.

Thank you so much @setoseng! That means so much to all of us, and we will pass along that great compliment to Colin. We are so lucky to have him!

You can certainly configure a site to site VPN tunnel between Meraki and non Meraki peers, however you would need to configure this connection manually rather than utilizing the Meraki AutoVPN feature. Here’s the documentation for this scenario: documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings#Non-Meraki_VPN_Peers It’s also possible to use Meraki MX/Z devices as a VPN concentrator behind a non Meraki firewall to gain the ability to use the AutoVPN feature.

Thank you! @@RhinoNetworks

Meraki HA (or hot spare configurations) is only available when using the same MX models at each location. Example: You can set up two MX105's in HA / hot spare, but you cannot set up an MX67 & MX105 in this way. Cloning the network is a great option for minimizing downtime, but there will be a few extra steps required if you have a combined network (MX, MS, MR etc.) and will need to split, then recombine the networks afterwards.

Thanks for the information, yes hot swap wont work as i am replacing MX81 with MX85. @@RhinoNetworks

Thanks, Bruce! Your assumption is correct! That’s one of the beauties of Meraki: your configurations are made, applied, and stored in the cloud. Whether changing an MX with the same model, or upgrading to a more powerful firewall, your experience will be the same! Make sure you check the SD-WAN & Traffic Shaping page as it will typically retain the bandwidth capabilities of the previous MX model after upgrading. Let us know if you have any other questions and good luck with the upcoming deployment!

Hi @pging8328! This is the full video for this particular tutorial. Is there something you would like us to touch up on in a new video?

@@RhinoNetworks I was expecting that you would go into more detail on how the actual site to site connection would be made? Lotta opportunity to explain, and demonstrate your knowledge!?

@@pging8328 That is absolutely something we can expand upon in an upcoming video. Thank you for the suggestion!

Thank you so much for catching that error! We would love to send you a swag pack for having such an observant eye. Please send your mailing address to [email protected]. Thank you again!

Good morning, @bryanmiller4453. We hate to hear that you didn’t find this short tutorial beneficial. What content would you like to see covered in future videos? We create videos for all levels of understanding, attempting to help everyone, no matter where they are on their IT journey.

@@RhinoNetworks I appreciate the inquiry. And while I do agree with you 100% that all IT professionals are at varying degrees of knowledge and experience, I feel that it is safe to assume that if an IT professional is knowledgeable enough to be logged in as an admin on a Meraki device then they also can find their way around the menus easily enough to already understand everything covered in this video. What could have been covered in this video based solely on the title is not just where to go to create a group policy but why you would want to create a group policy, how to use it in your configuration, what are the benefits to using Group Policies, what does it replace in the configuration, what is the order of operations when it comes to Group Policies versus configuring your rules manually etc. My point here is that most people who already got past the how do I connect and log into my MX probably already figured out where the sections are within the menu system just by exploring and clicking on all of the menu items. This video is very similar to the type of help you get from poor support documentation that just says "To create a Group Policy, go to the Group Policy and click on the plus sign and create a Group Policy." I just felt this video could have been so much more. You have a great presentation style and the production itself was quality. But it lacked real content to be helpful to most IT professionals. And I say this as someone who has interviewed, hired, and managed IT professionals for more than 10 years. Just some thoughts. Thanks for listening.

Hi Stefan - thank you for the recommendation! We will certainly consider that for future content. In the meantime, you can reference Meraki's instructions for group policy scheduling located here: documentation.meraki.com/General_Administration/Cross-Platform_Content/Creating_and_Applying_Group_Policies#Scheduling_Examples You can also schedule availability for an entire SSID if using Meraki MR access points - documentation.meraki.com/MR/Other_Topics/SSID_Availability

Your active directory configurations will be carried over automatically but remember to check your Meraki AutoVPN configurations if applicable. Generally speaking this process takes 5-20 minutes in our experience, as the MX will automatically update to the firmware version of your network along with downloading the configurations.

Hi ƦάĸēšЊ, That is not a license related error. This error would be more indicitivate of a firewall rule or ISP issue. You may want to review your firewall rules on the source and destination networks as a starting point. If still unable to resolve, Meraki support should be able to assist with further troubleshooting (Navigate to Help > Get Help from within your dashboard).

Make sure you are not in the same Meraki Network when you try to vpn, you will need to be in a Hotspot or another Wireless Network :) Let me know if works?

Hi Philip, this is specifically referring to re-enabling AutoVPN. If using Non-Meraki VPN Peers, this is an organization level setting and is not impacted by this process. Depending on how you are utilizing configuration templates, AutoVPN may or may not need to be re-enabled, but you should double check this to be safe after upgrading your MX on dashboard.

Hi Weelzup, that is correct, non Meraki VPN Peer configurations are not impacted by replacing your Meraki MX using this method.

Hi Gustavo, This video shows how to enable Meraki's AutoVPN feature for connecting Meraki MX/Z appliances with other Meraki MX/Z appliances. You may want be able to connect your Linux device using Meraki Client VPN or Site-to-site non Meraki VPN peer process. documentation.meraki.com/MX/Client_VPN/Client_VPN_OS_Configuration#Linux

Hey Kevin, thank you for the kind words! As for your question, the DDNS hostname is tied to the network and is not impacted by changing the MX associated to the network.

@@RhinoNetworks Thank you so much for the quick reply. This is most helpful. Have a great New Year!

We're glad you found this video helpful! Check out our other videos for more product info, configuration guides, and Rhino adventures! Also feel free to reach out to us directly if you have needs that aren't covered in KZbin (yet) - [email protected].

Nomnohiritow.

You can export up to 12 hours in a single export. Additional information regarding video export and sharing options can be found on Meraki's documentation here: documentation.meraki.com/MV/Processing_Video/Sharing_Video

Hey Dhanibel, Here is a helpful Meraki troubleshooting guide that may be able to point you in the right direction: documentation.meraki.com/MX/Client_VPN/Guided_Client_VPN_Troubleshooting If you are still unable to connect after taking a look at this, you should contact Meraki Support here: meraki.cisco.com/support/

Hey Andres! Please check out the documentation from the link below. If that doesn't solve your issue, contact Meraki Support and they should be able to point you in the right direction. documentation.meraki.com/MX/Client_VPN/Troubleshooting_Client_VPN

The credentials are used when first connecting to the VPN, as shown at 7:40 (although different credentials were used than the example user we created at 5:05).