Skip to content

Commit 9ba2702

Browse files
author
Patricia McPhee
authored
Update articles/azure-vmware/vmware-hcx-mon-guidance.md
1 parent c9e59ea commit 9ba2702

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-vmware/vmware-hcx-mon-guidance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Throughout the migration cycle, MON optimizes application mobility for:
1919
In this article, you'll learn about the Azure VMware Solution-specific use cases for MON.
2020

2121

22-
## Optimize traffic flows across standard and stretched segments on AVS Private Cloud side
22+
## Optimize traffic flows across standard and stretched segments on the private cloud side
2323

2424
In this scenario, VM1 is migrated to the cloud using the NE, which provides optimal VM to VM latency. As a result, VM1 needs low latency to VM3 on the local Azure VMware Solution segment. We migrate the VM1 gateway from on-premises to Azure VMware Solution (cloud) to ensure an optimal path for traffic (blue line). If the gateway remains on-premises (red line), a tromboning effect and higher latency are observed.
2525

0 commit comments

Comments
 (0)