Transitioning from vMX100 to vMX: A Smooth and Successful Upgrade

Share Post :

At Exine LLC, we’re dedicated to helping our clients keep their network infrastructure up-to-date and reliable. Recently, we transitioned a client from the vMX100 to the new vMX M, providing a significant boost in performance, flexibility, and support for expanded regions. This upgrade was a proactive step, especially as the vMX100 approaches its end-of-life date. Here’s an overview of the transition process and what it means for those still using the vMX100.

What Happens with the Existing vMX100?

For those currently relying on the vMX100, it’s important to understand the product’s lifecycle and plan for an upgrade. Cisco Meraki announced the end-of-sale for the vMX100 on September 29, 2020, with the last orders expected by December 22, 2020, depending on stock availability. Support for the vMX100 will officially end on December 22, 2027. Here’s a quick summary:

  • End-of-Sale Announcement Date: September 29, 2020
  • End-of-Sale Date: December 22, 2020
  • End-of-Support Date: December 22, 2027

Refer to the official vMX100 End-of-Life (EoS) notice for more details. While the vMX100 remains functional and supported until 2027, upgrading to a newer model, such as the vMX M, ensures access to enhanced features and support.

Key Questions About the vMX100 and vMX M Transition

Can I Upgrade the vMX100 to MX 15.X Firmware? Will I Have Access to C5 and Additional Regional Support?

Yes, the vMX100 can be upgraded to the latest MX 15 firmware, but it cannot be migrated to a C5 instance type or access the new regions supported by C5. To leverage the benefits of C5 instance types and additional regional support, you’ll need to delete the vMX100 and redeploy it as a new instance.

What Is the Difference Between vMX100 and vMX M?

The main difference between vMX100 and vMX M lies in the support for AWS C5 and the additional regional support it offers. The vMX100 and vMX M are equivalent when deployed in Azure, but in AWS, vMX M provides expanded capabilities.

The Transition Process from vMX100 to vMX M

Our transition process for upgrading from vMX100 to vMX M involved several carefully executed steps to ensure minimal disruption:

  1. Removing the Existing vMX100 – We started by deleting the vMX100 instance from the platform where it was hosted. Then, we navigated to Security & SD-WAN > Monitor > Appliance Status and clicked Remove appliance from network under the config status to remove the vMX100 from the network.
  2. Updating Licenses – Next, we added the necessary vMX M license to the client’s Meraki organization, ensuring a smooth setup of the new appliance.
  3. Adding the vMX M Appliance – We used the Add vMX-M button on the appliance status page to deploy the new vMX M appliance. This step automatically applied all necessary settings for the upgrade.
  4. Re-enabling Site-to-Site VPN – During the swap, the site-to-site VPN was temporarily disabled. Once the vMX M was active, we re-enabled the VPN to re-establish all necessary connections with hubs and spokes.
  5. Firmware and Testing – We set the network to the desired firmware version to ensure compatibility. We then tested the configuration, verifying that routing and VPN connections were functioning as expected.

How to Upgrade from vMX100 to vMX-S/M/L

If you’re considering an upgrade, here’s a simplified guide to transitioning from vMX100 to the vMX-S/M/L series:

  1. Delete the vMX100 instance from the hosting platform.
  2. Go to Security & SD-WAN > Monitor > Appliance Status.
  3. Click on Remove appliance from network to remove the vMX100 from the dashboard.
  4. Add the required vMX-S/M/L license to your Meraki organization.
  5. Use the Add vMX-S/M/L button to create the new appliance.
  6. Re-enable site-to-site VPN if it was previously enabled, as it is temporarily disabled during the swap.
  7. Set the network to the supported firmware version and redeploy on AWS, Azure, GCP, Alicloud, or NFVIS.

How to Upgrade from vMX-S to vMX-M/L

If you’re already on vMX-S and want to upgrade to vMX-M or L, here’s a quick overview:

  1. Delete the vMX-S instance from its hosting platform.
  2. Navigate to Security & SD-WAN > Monitor > Appliance Status.
  3. Click Remove appliance from network to disconnect the vMX-S.
  4. Add the necessary vMX-M/L license to your Meraki organization.
  5. Use the Add vMX-M/L button to add the new appliance to your network.
  6. Re-enable site-to-site VPN if needed, as it will be temporarily disabled.
  7. Set the network to the correct firmware version and redeploy on the desired platform.

Smooth Transition and Successful Outcome

Our transition to vMX M went smoothly. After the upgrade, the routing and site-to-site VPN connections came up seamlessly without any interruptions to the client’s operations. The improved performance and expanded regional support have provided noticeable benefits for their network.

Final Thoughts

With the end-of-support date for the vMX100 set for December 2027, upgrading to a newer model like the vMX M is a forward-thinking step that ensures continued support and access to the latest network features. At Exine LLC, we specialize in making transitions like these smooth and hassle-free. Contact us today to explore how we can support your network upgrade and keep your infrastructure running at its best!e LLC, we are committed to making upgrades like these as smooth as possible. If you’re interested in enhancing your network infrastructure, don’t hesitate to reach out to us for assistance.

Maybe You Like

How Network PenTesting Protects Your Digital Infrastructure

Smooth Migration to Windows 11 with Exine

Ransomware Trends: Key Strategies for Data Protection

Protect Your Digital Footprint With Cyber Hygiene

Receive the latest news

Looking for reliable IT solutions?

Sign up now and get 15% off your first service! Stay updated on the latest IT trends, services, and exclusive offers.