Notes from MS Learn AZ-700 Module 3: Design and Implement Azure ExpressRoute – Unit 9: Improve Data Path Performance Between Networks with ExpressRoute FastPath
FastPath is intended to improve path performance between on-prem and virtual network. Enabling has FastPath send traffic straight to VMs bypassing the gateway
- Circuits
- FastPath is available on all ExpressRoute Circuits
- Gateways
- FastPath still needs Virtual Network Gateway to exchange route between virtual and on-prem networks
- Gateway requirements for ExpressRoute FastPath
- Configuration – Virtual Network Gateway must be
- Ultra-Performance
- ErGw3AZ
- If planned use for IPv6 private peering must be this SKU only available for ExpressRoute Direct circuits
- Limitations
- Does not support
- UDR on gateway subnet: UDR has 0 impact on traffic FastPath sends from on-prem to VMs in a VNet
- Private link: If connecting private endpoint in VNet to on-prem it goes through virtual network gateway
- Does not support
- Configuration – Virtual Network Gateway must be
- Configure ExpressRoute FastPath
- Requirements/Worekflow
- Active ExpressRoute Circuit required
- Follow instruction for ExpressRoute circuit and have provider enable
- Make sure Azure private peering configured for circuit
- Make sure Azure private peering configured and successful BGP between network and MS
- Make sure VNet and Virtual Network Gateway fully provisioned using GatewayType ‘ExpressRoute’
- Possible to link up to 10 VNets on standard SKU. All VNets in same geopolitical region when using standard
- Single VNet links up to 16 ExpressRoute Circuits
- If ExpressRoute premium, can link VNets outside of geopolitical region of circuit.
- Allows for more than 10 VNets based on chosen bandwidtch
- To create from ExpressRoute Circuit to target ExpressRoute Virtual Network Gateway
- Address spaces advertised from local/peered VNet must be = or < 200
- Once success can add up to 1000 address spaces
- Requirements/Worekflow