Single-region deployment with out World Attain, utilizing Safe Digital WAN Hub with Routing-Intent

This text describes the perfect practices for connectivity and site visitors flows with single-region Azure VMware Answer when utilizing Azure Safe Digital WAN with Routing Intent. You study the design particulars of utilizing Safe Digital WAN with Routing-Intent with out World Attain. This text breaks down Digital WAN with Routing Intent topology from the attitude of an Azure VMware Answer personal cloud, on-premises websites, and Azure native. The implementation and configuration of Safe Digital WAN with Routing Intent are past the scope and are not mentioned on this doc.

In areas with out World Attain help or with a safety requirement to examine site visitors between Azure VMware Answer and on-premises on the hub firewall, a help ticket have to be opened to allow ExpressRoute to ExpressRoute transitivity. ExpressRoute to ExpressRoute transitivity is not supported by default with Digital WAN. – see Transit connectivity between ExpressRoute circuits with routing intent 

Safe Digital WAN with Routing Intent is simply supported with Digital WAN Commonplace SKU. Safe Digital WAN with Routing Intent offers the potential to ship all Web site visitors and Personal community site visitors (RFC 1918) to a safety answer like Azure Firewall, a third-party Community Digital Equipment (NVA), or SaaS answer. Within the situation, we now have a community topology that spans a single area. There’s one Digital WAN with a single hub situated within the Area. The Hub has its personal occasion of an Azure Firewall deployed, primarily making it a Safe Digital WAN Hub. Having a Safe Digital WAN hub is a technical prerequisite to Routing Intent. The Safe Digital WAN Hub has Routing Intent enabled.

The one area additionally has an Azure VMware Answer Personal Cloud and an Azure Digital Community. There’s additionally an on-premises website connecting to the area, which we evaluate in additional element later on this doc.

The next sections cowl site visitors flows and connectivity for Azure VMware Answer, on-premises, Azure Digital Networks, and the Web.

This part focuses on solely the Azure VMware Answer personal cloud. The Azure VMware Answer personal cloud has an ExpressRoute connection to the hub (connections labeled as «D»).

With ExpressRoute to ExpressRoute transitivity enabled on the Safe Hub and Routing-Intent enabled, the Safe Hub sends the default RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to Azure VMware Answer over connection «D». Along with the default RFC 1918 addresses, Azure VMware Answer learns extra particular routes from Azure Digital Networks and Department Networks (S2S VPN, P2S VPN, SDWAN) which might be linked to the hub. Azure VMware Answer does not study particular routes from on-premises networks. For routing site visitors again to on-premises networks, it makes use of the default RFC 1918 addresses that it realized from connection «D». This site visitors transits via the Hub firewall, as proven within the diagram. The Hub firewall has the precise routes for on-premises networks and routes site visitors towards the vacation spot over connection “E”. Visitors from Azure VMware Answer, heading in direction of Digital Networks, will transit the Hub firewall. For extra data, see the site visitors move part.

The diagram illustrates site visitors flows from the attitude of the Azure VMware Answer Personal Cloud.

Visitors Stream Chart

This part focuses solely on the on-premises website. As proven within the diagram, the on-premises website has an ExpressRoute connection to the hub (connection labeled as «E»).

With ExpressRoute to ExpressRoute transitivity enabled on the Safe Hub and Routing-Intent enabled, the Safe Hub sends the default RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to on-premises over connection «E». Along with the default RFC 1918 addresses, on-premises learns extra particular routes from Azure Digital Networks and Department Networks (S2S VPN, P2S VPN, SDWAN) which might be linked to the hub. On-premises does not study particular routes from Azure VMware Answer networks. For routing site visitors again to Azure VMware Answer networks, it makes use of the default RFC 1918 addresses that it realized from connection «E». This site visitors transits via the Hub firewall, as proven within the diagram. The Hub firewall has the precise routes for Azure VMware Answer networks and routes site visitors towards the vacation spot over connection “D”. Visitors from on-premises, heading in direction of Digital Networks, will transit the Hub firewall. For extra data, see the site visitors move part for extra detailed data.

As talked about earlier, once you allow ExpressRoute to ExpressRoute transitivity on the Hub, it sends the default RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to your on-premises community. Subsequently, you should not promote the precise RFC 1918 prefixes (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) again to Azure. Promoting the identical actual routes creates routing issues inside Azure. As a substitute, you must promote extra particular routes again to Azure on your on-premises networks.

Notice
Should you’re at present promoting the default RFC 1918 addresses from on-premises to Azure and want to proceed this apply, that you must cut up every RFC 1918 vary into two equal sub-ranges and promote these sub-ranges again to Azure. The sub-ranges are 10.0.0.0/9, 10.128.0.0/9, 172.16.0.0/13, 172.24.0.0/13, 192.168.0.0/17, and 192.168.128.0/17.

The diagram illustrates site visitors flows from the attitude of on-premises.

Visitors Stream Chart

This part focuses solely on connectivity from an Azure Digital Community perspective. As depicted within the diagram, the Digital Community has a Digital Community peering on to the hub.

The diagram illustrates how all Azure native sources within the Digital Community study routes below their «Efficient Routes». A Safe Hub with Routing Intent enabled at all times sends the default RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to peered Digital Networks. Azure native sources within the Digital Community do not study particular routes from exterior of their Digital Community. With Routing Intent enabled, all sources within the Digital Community at present possess the default RFC 1918 handle and use the hub firewall as the following hop. All site visitors ingressing and egressing the Digital Networks will at all times transit the Hub Firewall. For extra data, see the site visitors move part for extra detailed data.

The diagram illustrates site visitors flows from an Azure Digital Community perspective.

Visitors Stream Chart

This part focuses solely on how web connectivity is offered for Azure native sources in Digital Networks and Azure VMware Answer Personal Clouds in a single area. There are a number of choices to offer web connectivity to Azure VMware Answer. – see Internet Access Concepts for Azure VMware Solution 

Possibility 1: Web Service hosted in Azure
Possibility 2: VMware Answer Managed SNAT
Possibility 3: Azure Public IPv4 handle to NSX-T Information Heart Edge

Though you need to use all three choices with Single Area Safe Digital WAN with Routing Intent, «Possibility 1: Web Service hosted in Azure» is the best choice when utilizing Safe Digital WAN with Routing Intent and is the choice that’s used to offer web connectivity within the situation. The rationale why «Possibility 1» is taken into account the best choice with Safe Digital WAN is because of its ease of safety inspection, deployment, and manageability.

As talked about earlier, once you allow Routing Intent on the Safe Hub, it advertises RFC 1918 to all peered Digital Networks. Nevertheless, you too can promote a default route 0.0.0.0/0 for web connectivity to downstream sources. With Routing Intent, you’ll be able to select to generate a default route from the hub firewall. This default route is marketed to your Digital Community and to Azure VMware Answer. This part is damaged into two sections, one which explains web connectivity from an Azure VMware Answer perspective and one other from the Digital Community perspective.

When Routing Intent is enabled for web site visitors, the default conduct of the Safe Digital WAN Hub is to not promote the default route throughout ExpressRoute circuits. To make sure the default route is propagated to the Azure VMware Answer from the Azure Digital WAN, you need to allow default route propagation in your Azure VMware Answer ExpressRoute circuits – see To advertise default route 0.0.0.0/0 to endpoints. As soon as modifications are full, the default route 0.0.0.0/0 is then marketed through connection “D” from the hub. It’s essential to notice that this setting should not be enabled for on-premises ExpressRoute circuits. As a greatest apply, it is really useful to implement a BGP Filter in your on-premises gear. A BGP Filter in place prevents the inadvertent studying of the default route, provides an additional layer of precaution, and ensures that on-premises web connectivity is not impacted.

When Routing Intent for web entry is enabled, the default route generated from the Safe Digital WAN Hub is robotically marketed to the hub-peered Digital Community connections. You will discover below Efficient Routes for the Digital Machines’ NICs within the Digital Community that the 0.0.0.0/0 subsequent hop is the hub firewall.

For extra data, see the site visitors move part.

The diagram illustrates site visitors flows from a Digital Community and Azure VMware Answer perspective.

Visitors Stream Chart

HCX Mobility Optimized Networking (MON) is an non-compulsory characteristic to allow when utilizing HCX Community Extensions (NE). Mobility Optimized Networking (MON) offers optimum site visitors routing below sure eventualities to forestall community tromboning between the on-premises-based and cloud-based sources on prolonged networks.

Enabling Mobility Optimized Networking (MON) for a particular prolonged community and a digital machine modifications the site visitors move. After implementing Mobility Optimized Networking (MON), egress site visitors from that digital machine doesn’t trombone again to on-premises. As a substitute, it bypasses the Community Extensions (NE) IPSEC tunnel. Visitors for that digital machine will now egress out of the Azure VMware Answer NSX-T Tier-1 Gateway> NSX-T Tier-0 Gateway>Azure Digital WAN.

Enabling Mobility Optimized Networking (MON) for a particular prolonged community and a digital machine ends in a change. From Azure VMware Answer NSX-T, it injects a /32 host route again to Azure Digital WAN. Azure Digital WAN advertises this /32 route again to on-premises, Digital Networks, and Department Networks (S2S VPN, P2S VPN, SDWAN). The aim of this /32 host route is to make sure that site visitors from on-premises, Digital Networks, and Department Networks does not use the Community Extensions (NE) IPSEC tunnel when destined for the Mobility Optimized Networking (MON) enabled Digital Machine. Visitors from supply networks is directed straight to the Mobility Optimized Networking (MON) enabled Digital Machine because of the /32 route that’s realized.

With ExpressRoute to ExpressRoute transitivity enabled on the Safe Hub and Routing-Intent enabled, the Safe Hub sends the default RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to each the on-premises and Azure VMware Answer. Along with the default RFC 1918 addresses, each on-premises and Azure VMware Answer study extra particular routes from Azure Digital Networks and Department Networks (S2S VPN, P2S VPN, SDWAN) which might be linked to the hub. Nevertheless, on-premises networks do not study any particular routes from the Azure VMware Answer, nor does the reverse happen. As a substitute, each environments depend on the default RFC 1918 addresses to facilitate routing again to at least one one other through the Hub firewall. Which means that extra particular routes, reminiscent of HCX Mobility Optimized Networking (MON) Host Routes, aren’t marketed from the Azure VMware Answer ExpressRoute to the on-premises-based ExpressRoute circuit and vice-versa. The lack to study particular routes introduces uneven site visitors flows. Visitors egresses Azure VMware Answer through the NSX-T Tier-0 gateway, however returning site visitors from on-premises returns over the Community Extensions (NE) IPSEC tunnel.

To appropriate any site visitors asymmetry, that you must modify the HCX Mobility Optimized Networking (MON) Coverage Routes. Mobility Optimized Networking (MON) coverage routes decide which site visitors goes again to the on-premises Gateway through an L2 extension. In addition they determine which site visitors is routed via the Azure VMware Answer NSX Tier-0 Gateway.

If a vacation spot IP matches and is ready to «enable» within the Mobility Optimized Networking (MON) coverage configuration, then two actions happen. First, the packet is recognized. Second, it is despatched to the on-premises gateway via the HCX Community Extension equipment.

If a vacation spot IP does not match, or is ready to «deny» within the Mobility Optimized Networking (MON) coverage, the system sends the packet to the Azure VMware Answer Tier-0 for routing.

HCX Coverage Routes