I want to use Azure VMware Solution, what should I know about networking?

What else do I need to know when using Azure VMware Solution (AVS)?

Networking Edition

I have been working with many customers over the last little while that are looking at Azure VMware Solution (AVS).

Often the idea and use case for the customer is correct. There are a few great reasons to use AVS. If you fit within the use cases, you are in for a real treat.

Deciding whether or not you are a fit is part of the equation, there is more to this scenario. Let’s dive in a bit more.

1. You are using the Azure platform but on dedicated hardware.
2. You will probably want to extend the connection from AVS to your existing data centre. This will introduce Global Reach if connecting back to on-premises with an ExpressRoute.
3. You will most likely use HCX as part of your migration.

So what does all of the above mean?

Networking can start to get a little interesting as there would now be many routing paths over a combination of Layer 2 and Layer 3 connections.

1. Asymmetric routing can become a real issue.
2. “Accidental” latency can be very easily introduced.
3. Traffic flow may not flow as expected.
4. A PoC (proof of concept) is very important with this technology.
5. Migration planning with network segments in mind is key.
6. Migration should be as “short-term” as possible, the longer the migration takes, the more networking challenges and complexities will arise.

Guidance for networking can be found here