Skip to content

Commit a802fe5

Browse files
[Magic WAN] update Azure instructions
This updates the Azure instructions to: - use the Active/Active configuration on the Azure Virtual Gateway - use bidirectional health checks with a custom target equal to the Customer endpoint These changes are unlocked by the completion of RM-19633. (The work is done, and shipped, even if the RM is not yet closed)
1 parent 145455a commit a802fe5

File tree

1 file changed

+11
-19
lines changed
  • src/content/docs/magic-wan/configuration/manually/third-party

1 file changed

+11
-19
lines changed

src/content/docs/magic-wan/configuration/manually/third-party/azure.mdx

Lines changed: 11 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ This configuration guide applies to Azure Virtual Network Gateway which includes
3535
1. Create a Virtual Network Gateway.
3636
2. Create a new public IP address or use an existing IP. Take note of the public IP address assigned to the Virtual Network Gateway as this will be the **Customer endpoint** for Magic WAN's IPsec tunnels configuration.
3737
3. Select the resource group and VNET you have already created.
38-
4. In **Configuration**, disable **Active-active mode** and **Gateway Private IPs**.
38+
4. In **Configuration**, enable **Active-active mode** and disable **Gateway Private IPs**.
3939
5. Select **Create**.
4040

4141
:::note
@@ -85,9 +85,13 @@ To configure the Address Space for the Local Network Gateway to support Tunnel H
8585

8686
1. Edit the Local Network Gateway configured in the previous section.
8787
2. Select **Connections**.
88-
3. Add the`/31` subnet in CIDR notation (for example, `10.252.3.54/31`) under **Address Space(s)**.
88+
3. Add the Interface Address of the Magic IPsec Tunnel from the Cloudflare Dashboard in CIDR notation (for example, `10.252.3.55/32`) under **Address Space(s)**.
8989
4. Select **Save**.
9090

91+
:::note
92+
The Magic IPsec Tunnel Interface Address should be entered as a `/31` in the Cloudflare Dashboard, but as a `/32` when configuring the Local Network Gateway Address Space(s) in the Azure portal.
93+
:::
94+
9195
### 5. Create an IPsec VPN Connection
9296

9397
Choose the following settings when creating your VPN Connection:
@@ -165,9 +169,11 @@ ICMP (ping/traceroute) will work to remote Magic WAN sites, but is not forwarded
165169
3. **Cloudflare endpoint**: Use the Cloudflare anycast address you have received from your account team. This will also be the IP address corresponding to the Local Network Gateway in Azure. For example, `162.xxx.xxx.xxx`.
166170
4. **Health check rate**: Leave the default option (Medium) selected.
167171
5. **Health check type**: Leave the default option (Reply) selected.
168-
6. **Health check direction**: Leave default option.
169-
7. **Add pre-shared key later**: Select this option to create a PSK that will be used later in Azure.
170-
8. **Replay protection**: **Enable**.
172+
6. **Health check direction**: Leave default option (Bidirectional) selected.
173+
7. **Health check target**: Select **Custom**.
174+
8. **Target address**: Enter the same address that is used in the **Customer endpoint** field.
175+
9. **Add pre-shared key later**: Select this option to create a PSK that will be used later in Azure.
176+
10. **Replay protection**: **Enable**.
171177
3. Create static routes for your Azure Virtual Network subnets, specifying the newly created tunnel as the next hop.
172178

173179
## Validate connectivity and disable Azure Virtual Network Gateway anti-replay protection
@@ -355,20 +361,6 @@ curl --location --request PUT \
355361

356362
6. Leave the replay protection setting checked in the Cloudflare dashboard, and wait several minutes before validating connectivity again.
357363

358-
## Tunnel health checks and Azure
359-
360-
We have identified cases where the IPsec Tunnels configured on the Azure Virtual Network Gateway need to be restarted one time before the tunnel health checks start passing.
361-
362-
### Restart Azure tunnels
363-
364-
1. Open the Virtual Network Gateway.
365-
2. Go to **Settings** > **Connections**.
366-
3. Open the properties of the tunnel.
367-
4. Go to **Help** > **Reset**.
368-
5. Select **Reset**.
369-
370-
It may take several minutes for the tunnels to reset from the Azure side. Monitor the [tunnel health checks section](/magic-wan/configuration/common-settings/check-tunnel-health-dashboard/) in the Cloudflare dashboard to determine the status.
371-
372364
:::note
373365
Tunnel Health Check percentages are calculated over a one hour period.
374366
:::

0 commit comments

Comments
 (0)