Skip to content

Commit 9c4d7bf

Browse files
authored
Clarifying the statement about the default route
The statement that the default route will not be honored is incorrect. It is only for private destinations that it will not be honored, I understand (for public IPs it will be honored alright)
1 parent 9639e80 commit 9c4d7bf

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-vmware/concepts-network-design-considerations.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,11 +33,11 @@ Use either 2-byte or 4-byte public ASN numbers, and make sure that they're compa
3333
## Management VMs and default routes from on-premises
3434

3535
> [!IMPORTANT]
36-
> Azure VMware Solution management virtual machines (VMs) won't honor a default route from on-premises.
36+
> Azure VMware Solution management virtual machines (VMs) won't honor a default route from on-premises for RFC1918 destinations.
3737
38-
If you're routing back to your on-premises networks by using only a default route advertised toward Azure, vCenter Server and NSX-T Manager VMs won't be compatible with that route.
38+
If you're routing back to your on-premises networks by using only a default route advertised toward Azure, traffic from vCenter Server and NSX-T Manager VMs towards on-premises destinations with private IP addresses won't follow that route.
3939

40-
To reach vCenter Server and NSX-T Manager, provide specific routes from on-premises to allow traffic to have a return path to those networks.
40+
To reach vCenter Server and NSX-T Manager from on-premises, provide specific routes to allow traffic to have a return path to those networks. For example, advertise the RFC1918 summaries (10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16).
4141

4242
## Default route to Azure VMware Solution for internet traffic inspection
4343

0 commit comments

Comments
 (0)