Skip to content

Commit cddb58b

Browse files
committed
added updates
1 parent e40562e commit cddb58b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-wan/how-to-routing-policies.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -375,11 +375,11 @@ When private routing policies are configured for dual-role NVAs, Virtual WAN aut
375375

376376
For **active-passive NVA configurations** where only one instance of the NVAs is advertising a route for a specific prefix to Virtual WAN (or the AS-PATH length of routes learnt from one of the instances is always the shortest), Virtual WAN ensures that outbound traffic from an Azure Virtual Network is always routed to the active (or preferred) NVA instance.
377377

378-
:::image type="content" source="./media/routing-policies/active-passive-network-virtual-appliance.png"alt-text="Screenshot showing routing patterns for active-passive NVAs."lightbox="./media/routing-policies/active-passive-nva.png":::
378+
:::image type="content" source="./media/routing-policies/active-passive-network-virtual-appliance.png"alt-text="Screenshot showing routing patterns for active-passive NVAs."lightbox="./media/routing-policies/active-passive-network-virtual-appliance.png":::
379379

380380
For **active-active NVA configurations** (multiple NVA instances advertise the same prefix with the same AS-PATH length), Azure automatically performs ECMP to route traffic from Azure to on-premises. Azure's software-defined networking platform doesn't guarantee flow-level symmetry, meaning the inbound flow to Azure and outbound flow from Azure can land on different instances of the NVA. This results in asymmetric routing which is dropped by stateful firewall inspection. Therefore, it isn't recommended to use active-active connectivity patterns where an NVA is behaving as a dual-role NVA unless the NVA can support asymmetric forwarding or support session sharing/synchronization. For more information on whether your NVA supports asymmetric forwarding or session state sharing/synchronization, reach out to your NVA provider.
381381

382-
:::image type="content" source="./media/routing-policies/active-active-network-virtual-appliance.png"alt-text="Screenshot showing routing patterns for active-active NVAs."lightbox="./media/routing-policies/active-active-nva.png":::
382+
:::image type="content" source="./media/routing-policies/active-active-network-virtual-appliance.png"alt-text="Screenshot showing routing patterns for active-active NVAs."lightbox="./media/routing-policies/active-active-network-virtual-appliance.png":::
383383

384384
## Configuring routing intent through Azure portal
385385

0 commit comments

Comments
 (0)