You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
Copy file name to clipboardExpand all lines: src/content/docs/magic-wan/configuration/manually/third-party/azure.mdx
+11-19Lines changed: 11 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ This configuration guide applies to Azure Virtual Network Gateway which includes
35
35
1. Create a Virtual Network Gateway.
36
36
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.
37
37
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**.
39
39
5. Select **Create**.
40
40
41
41
:::note
@@ -85,9 +85,13 @@ To configure the Address Space for the Local Network Gateway to support Tunnel H
85
85
86
86
1. Edit the Local Network Gateway configured in the previous section.
87
87
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)**.
89
89
4. Select **Save**.
90
90
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
+
91
95
### 5. Create an IPsec VPN Connection
92
96
93
97
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
165
169
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`.
166
170
4.**Health check rate**: Leave the default option (Medium) selected.
167
171
5.**Health check type**: Leave the default option (Reply) selected.
@@ -355,20 +361,6 @@ curl --location --request PUT \
355
361
356
362
6. Leave the replay protection setting checked in the Cloudflare dashboard, and wait several minutes before validating connectivity again.
357
363
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
-
372
364
:::note
373
365
Tunnel Health Check percentages are calculated over a one hour period.
0 commit comments