Aviatrix Answers

This article was written prior to the availability of the AWS Transit Gateway; it assumes use of Aviatrix Gateways in each Spoke VPC. Looking for AWS Transit Gateway? See Transit Gateway Overview or AWS Transit Gateway Quick Reference Guide or Transit Gateway Orchestration Answers.

How do I migrate from a vRouter based transit hub to a software-defined AWS Transit Hub?

How-to Guide
2 minute read

As cloud teams move more and more applications and workloads to the public cloud, the challenges with networking become more evident. The problem is that while public cloud vendors such as AWS have done a great job of making compute and storage cloudlike—meaning dynamic, scalable, and elastic—networking in the cloud remains complex, linear and slow. One of the questions we are often asked when customers are considering migrating away from vRouters is “What is the difference between a software defined approach like Aviatrix and a vRouter approach like the Cisco CSR?” So, let’s start there.

A vRouter – in most cases – was built for the on-premise data center. In a very real sense, they represent an older generation of networking technology. vRouters require the skills of highly certified specialists comfortable with CLIs via ssh, BGPs, route summarizations, and other old-school networking functionality and troubleshooting paradigms. Read our CTO’s blog here for more.

In contrast, today’s cloud teams consist of professionals who think in terms of applications and services optimization, not routing tables. They’re much more likely to speak about VPCs, REST APIs, Chef, Puppet, and Terraform—in other words, the language of the cloud, of automated software environments, and of the future direction their company is going.

If you already have a deployed Cisco CSR transit hub solution that uses AWS VGWs in Spoke VPCs, we’ve created step by step instructions for you to migrate to an Aviatrix deployment. If you want to check out the Aviatrix product first – which we always recommend – you can try it on AWS for free here.

If you’re ready to migrate, you can use the how-to instructions below to complete the migration successfully. We’ve documented these steps as best practices from working with other companies on the same migration. The objective with this migration process is:

  1. Not require any changes to the on-premises network,
  2. Not require changes to Direct Connect,
  3. Not require changes to existing VPC infrastructure and
  4. to minimize downtime.

Visit our how-to documentation to learn the entire Cisco CSR transit hub migration process.

Get started.

Seven Criteria for Building an AWS Global Transit Network

AWS Bootcamp (40 minutes)

Global Transit Network design is critical to the success of your AWS deployment. This bootcamp covers seven criteria all good designs have in common.

See a Demo

Personalized Walkthrough

Want to see a live demonstration of our cloud-native networking and get answers to your questions about Aviatrix and Global Transit Networks?

Comparing Aviatrix Partner Solution for Global Transit to AWS Solution with CSR

Related Reading

What should you know about your choices for AWS Global Transit Network architecture? This chart provides a point-by-point comparison of features.