[ Ссылка ]
[Pattern 1] [ Ссылка ]
[Pattern 2] [ Ссылка ]
[Pattern 2] [ Ссылка ]
[Pattern 3] [ Ссылка ]
[Pattern 3] [ Ссылка ]
[Pattern 4] [ Ссылка ]
[Pattern 4] It's worth noting, that strictly speaking, the custom-next-hop setting is not required for ER-to-ER, the GatewaySubnet UDR alone would suffice. However it would make sense to reconcile the ARS control-plane with the presented data-plane, if you have other VNets in Azure wanting to reach AVS via Azure Firewall.

NB. This list is not exhaustive. For example, if one side of your ExpressRoute is utilising IPsec encryption (IPsec over Private Peering), then this opens up more pattern options.

Caveat Empor - this is focused on functionality, any production design would naturally have to account for scale, resilience etc

00:00 Intro
02:02 ExpressRoute GlobalReach
04:23 Virtual WAN Routing Intent
08:18 Azure Route Server + NVA
15:03 Azure Route Server + NVA + Azure Firewall

свернуть