VWAN Migration

Question

My client is about doing a POC for VWAN before migration current VNET hub to VWAN. We would like a better explanation and guide.

1. BGP/IPSEC setup between Virtual Wan and on-premises and setting up BGP neighbor.
2. Create second link to on-premises, second vent peering, second link to partners, my question is how to keep second link inactive on Azure before migration (using BGP AS-Path, or weight of static route like in traditional routing)

Answer 1

@Love Arinze

1.BGP/IPSEC setup between Virtual Wan and on-premises and setting up BGP neighbor.

1.BGP/IPSEC setup between Virtual Wan and on-premises and setting up BGP neighbor.

• This is same as setting up a VPN Gateway
• Refer : Create a site-to-site connection using Azure Virtual WAN
• "VPN Site" is the equivalent of having an "LNG" with traditional VPN Gateway
• You just have to specify the BGP Peer IP and ASN number while creating the VPN Site
  • 
• Download the configuration file for this VPN Site from the Portal.
  • Use 'Instance0 BgpPeeringAddresses' for gatewayconfiguration from the configuration file.
    • For Active-active connections (from OnPrem end), use Instance1.
• This should create the connection

---

2.Create second link to on-premises, second vent peering, second link to partners, my question is how to keep second link inactive on Azure before migration (using BGP AS-Path, or weight of static route like in traditional routing

• Here, I am not sure what the requirement is
• Second link to on-premises
  • Both VPN Gateway and ExpressRoute come with Active-active connections so we always have a backup path
  • Second vent peering
  • This is not possible. A Vnet can be only peered to one Hub
  • Second link to partners
  • Please elaborate on your requiremen

---

3.If the above is with respect to during/before migration of traditional Hub Spoke architecture

Create second link to on-premises

You don't need it

The HubVnet will be either peered to the VHub or be deleted.

Second vent peering

You will be removing the VNetPeerings and creating a new one to the VHub

A Vnet can have only one remote gateway (so, you can't have both)

Second link to partners

Second link to partners

Please elaborate on what partners are we talking about.

---

You will be required to have a maintenance window.

• The second link you are talking about is in fact your old connection, and I don't think of a scenario where both of them (vWAN) can be active and working
• Let's say you migrate a Peered VNet
  • This will either succeed and now you will have connectivity via vWAN
  • or This will fail and you will still continue to have connectivity via existing VPN
• Same goes for HubVnet
  • You will either peer this to vWAN (or delete it - this should not cause any concerns)
  • If this succeeds, you will have connectivity via vWAN
  • If this fails, existing VPN connection will still be there
• So there is no requirement of having two working connections at the same time
• And even if we did, I don't think so this will work as a Vnet can have only one remote gateway as stated already.

---

Kindly let us know if this helps or you need further assistance on this issue.

Kindly let us know if this helps or you need further assistance on this issue.

Thanks,

Kapil

Please Accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer.