You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-wan/virtual-wan-faq.md
+19-1Lines changed: 19 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,7 @@ An Azure Virtual WAN connection is composed of 2 tunnels. A Virtual WAN VPN gate
161
161
162
162
### What happens during a Gateway Reset in a Virtual WAN VPN Gateway?
163
163
164
-
The Gateway Reset button should be used if your on-premises devices are all working as expected but Site to Site VPN connections in Azure are in a Disconnected state. Virtual WAN VPN Gateways are always deployed in an Active-Active state for high availability. This means there is always more than one instance deployed in a VPN Gateway at any point of time. When the Gateway Reset button is used, it reboots the instances in the VPN Gateway in a sequential manner, so your connections are not disrupted. There will be a brief gap as connections move from one instance to the other, but this gap should be less than a minute. Additionally, please note that resetting the gateways will not change your Public IPs.
164
+
The Gateway Reset button should be used if your on-premises devices are all working as expected but Site to Site VPN connections in Azure are in a Disconnected state. Virtual WAN VPN Gateways are always deployed in an Active-Active state for high availability. This means there is always more than one instance deployed in a VPN Gateway at any point of time. When the Gateway Reset button is used, it reboots the instances in the VPN Gateway in a sequential manner, so your connections are not disrupted. There will be a brief gap as connections move from one instance to the other, but this gap should be less than a minute. Additionally, please note that resetting the gateways will not change your Public IPs.
165
165
166
166
### Can the on-premises VPN device connect to multiple hubs?
167
167
@@ -337,6 +337,24 @@ When you choose to deploy a security partner provider to protect Internet access
337
337
338
338
For more information regarding the available options third-party security providers and how to set this up, see [Deploy a security partner provider](../firewall-manager/deploy-trusted-security-partner.md).
339
339
340
+
### Will BGP communities generated by on-premises be preserved in Virtual WAN?
341
+
342
+
Yes, BGP communities generated by on-premises will be preserved in Virtual WAN. You can use your own public ASNs or private ASNs for your on-premises networks. You can't use the ranges reserved by Azure or IANA:
343
+
* ASNs reserved by Azure:
344
+
* Public ASNs: 8074, 8075, 12076
345
+
* Private ASNs: 65515, 65517, 65518, 65519, 65520
346
+
* ASNs reserved by IANA: 23456, 64496-64511, 65535-65551
347
+
348
+
### In Virtual WAN, what are the estimated performances by ExpressRoute gateway SKU?
### Why am I seeing a message and button called "Update router to latest software version" in portal?
353
+
354
+
The Virtual WAN team has been working on upgrading virtual routers from their current Cloud Services infrastructure to Virtual Machine Scale Sets (VMSS) based deployments. This will enable the virtual hub router to now be availability zone aware and have enhanced scaling out capabilities during high CPU usage. If you navigate to your Virtual WAN hub resource and see this message and button, then you can upgrade your router to the lastest version by clicking on the button. The Cloud Services infrastructure will be deprecated soon, so **please migrate by May 31, 2022.**
355
+
356
+
Note that you’ll only be able to update your virtual hub router if all the resources (gateways/route tables/VNET connections) in your hub are in a succeeded state. Additionally, as this operation requires deployment of new VMSS based virtual hub routers, you’ll face an expected downtime of 30 minutes per hub. Within a single Virtual WAN resource, hubs should be updated one at a time instead of updating multiple at the same time. When the Router Version says “Latest”, then the hub is done updating.
357
+
340
358
## Next steps
341
359
342
360
* For more information about Virtual WAN, see [About Virtual WAN](virtual-wan-about.md).
>*Scale units 2-10, during maintenance operations, maintain aggregate throughput. However, scale unit 1, during a maintenance operation, may see a slight variation in throughput numbers.
0 commit comments