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/route-server/troubleshoot-route-server.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,6 +86,10 @@ In this example, 10.0.1.1 is the default gateway IP in the subnet where your NVA
86
86
87
87
When you deploy a Route Server to a virtual network, we need to update the control plane between the gateways and the virtual network. During this update, there's a period of time when the VMs in the virtual network lose connectivity to the on-premises network. We strongly recommend that you schedule maintenance to deploy a Route Server in your production environment.
88
88
89
+
### Why do I face connectivity issues when assigning a Standard v2 Public IP for my Route Server deployment?
90
+
91
+
Azure Route Server requires Standard SKU Public IP addresses. Standard v2 SKU Public IPs are not supported.
92
+
89
93
## Control plane issues
90
94
91
95
### Why does my on-premises network connected to Azure VPN gateway not receive the default route advertised by the Route Server?
0 commit comments