Skip to content

Commit 8f5194a

Browse files
cdraper-cloudflaremarciocloudflare
cdraper-cloudflare
and
marciocloudflare
authored
New docs for Magic WAN custom IKE IDs plus changelog for custom IKE IDs and bidirectional health check update (cloudflare#25047)
* Write new doc on custom IKE IDs for IPsec in Magic WAN. Write changelog for custom IKE and health check updates. * Fix side bar ordering for other documents in the Magic WAN common settings page * Apply suggestions from code review --------- Co-authored-by: marciocloudflare <[email protected]>
1 parent c715315 commit 8f5194a

File tree

9 files changed

+80
-22
lines changed

9 files changed

+80
-22
lines changed

‎src/content/changelog/magic-wan/2025-09-05-bidirectional-health-check-any-on-ramp.mdx‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
title: Bidirectional tunnel health checks are compatible with all Magic on-ramps
3+
description: Bidirectional tunnel health check return packets are accepted by any Magic on-ramp
4+
date: 2025-09-05
5+
---
6+
7+
All bidirectional tunnel health check return packets are accepted by any Magic on-ramp.
8+
9+
Previously, when a Magic tunnel had a bidirectional health check configured, the bidirectional health check would pass when the return packets came back to Cloudflare over the same tunnel that was traversed by the forward packets.
10+
11+
There are SD-WAN devices, like VeloCloud, that do not offer controls to steer traffic over one tunnel versus another in a high availability tunnel configuration.
12+
13+
Now, when a Magic tunnel has a bidirectional health check configured, the bidirectional health check will pass when the return packet traverses over any tunnel in a high availability configuration.

‎src/content/changelog/magic-wan/2025-09-08-custom-ike-id-ipsec-tunnels.mdx‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
---
2+
title: Custom IKE ID for IPsec Tunnels
3+
description: Customers can now set a custom IKE ID for their IPsec Tunnels
4+
date: 2025-09-08
5+
---
6+
7+
Now, Magic WAN customers can configure a custom IKE ID for their IPsec tunnels. Customers that are using Magic WAN and a VeloCloud SD-WAN device together can utilize this new feature to create a high availability configuration.
8+
9+
This feature is available via API only. Customers can read the Magic WAN documentation to learn more about the [Custom IKE ID feature and the API call to configure it](/magic-wan/configuration/common-settings/custom-ike-id-ipsec/).

‎src/content/docs/magic-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
pcx_content_type: how-to
33
title: Check tunnel health in the dashboard
44
sidebar:
5-
order: 3
5+
order: 2
66
---
77

88
import { Render } from "~/components";
@@ -11,18 +11,20 @@ import { Render } from "~/components";
1111
file="tunnel-health/check-tunnel-healthchecks-dash"
1212
product="networking-services"
1313
params={{
14-
dashInfo: "The dashboard shows the view of tunnel health as measured from each Cloudflare location where your traffic is likely to land.",
14+
dashInfo:
15+
"The dashboard shows the view of tunnel health as measured from each Cloudflare location where your traffic is likely to land.",
1516
productPath: "**Magic WAN** > **Network health**",
1617
graphQL: "/magic-wan/analytics/query-tunnel-health/",
17-
notificationsPath: "[notifications wizard](/magic-wan/configuration/common-settings/configure-magic-tunnel-health-alerts/)"
18+
notificationsPath:
19+
"[notifications wizard](/magic-wan/configuration/common-settings/configure-magic-tunnel-health-alerts/)",
1820
}}
1921
/>
2022

2123
<Render
2224
file="tunnel-health/health-checks-compatible-cmb-eu"
2325
product="networking-services"
2426
params={{
25-
productName: "Magic WAN"
27+
productName: "Magic WAN",
2628
}}
2729
/>
2830

‎src/content/docs/magic-wan/configuration/common-settings/configure-magic-tunnel-health-alerts.mdx‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@ pcx_content_type: how-to
33
title: Configure Magic Tunnel health alerts
44
head: []
55
description: Use the API to set up and configure Magic Tunnel health alerts
6+
sidebar:
7+
order: 4
68
---
79

810
import { Render } from "~/components";
@@ -13,8 +15,9 @@ import { Render } from "~/components";
1315
params={{
1416
magicWord: "Magic WAN",
1517
productName: "Magic WAN",
16-
magicTunnelHealthCheckCalculation: "/magic-wan/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/",
18+
magicTunnelHealthCheckCalculation:
19+
"/magic-wan/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/",
1720
networkAnalyticsPath: "/magic-wan/analytics/network-analytics/",
1821
healthChecks: "/magic-wan/reference/tunnel-health-checks/",
1922
}}
20-
/>
23+
/>

‎src/content/docs/magic-wan/configuration/common-settings/custom-ike-id-ipsec.mdx‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
pcx_content_type: how-to
3+
title: Custom IKE ID for IPsec
4+
sidebar:
5+
order: 6
6+
---
7+
8+
Magic WAN customers can configure a custom IKE ID for their IPsec tunnels. Customers that are using Magic WAN and a VeloCloud SD-WAN device together should utilize this option to create a high availability configuration.
9+
10+
:::note
11+
This feature is only available via API. There are no configuration options for a custom IKE ID for an IPsec tunnel in the Cloudflare dashboard.
12+
:::
13+
14+
VeloCloud has a high availability mechanism that allows customers to specify one set of IKE parameters (like IKE ID) and multiple remote IPs. Customers create an IKE ID, and then assign the same custom IKE ID to their primary IPsec tunnel and their backup IPsec tunnel. FQDN is the only supported type for custom IKE IDs.
15+
16+
Magic WAN customers can set a custom IKE ID for an IPsec tunnel using the following API call. Customers will need to fill in the appropriate values for &lt;account_id&gt;, &lt;tunnel_id&gt;, and the FQDN wildcard before running the API call.
17+
18+
```txt
19+
% cloudflared access curl
20+
https://conduit-api.cfdata.org/accounts/<account_id>/ipsec_tunnels/<tunnel_id>
21+
-XPUT -d '{"custom_remote_identities": {"fqdn_id": "*.<account_id>.custom.ipsec.cloudflare.com"}}'
22+
```

‎src/content/docs/magic-wan/configuration/common-settings/enable-magic-roles.mdx‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,10 @@ title: Enable Magic user roles
44
head: []
55
description: You can determine which users have, or do not have, configuration
66
edit access for Magic products.
7-
7+
sidebar:
8+
order: 5
89
---
910

10-
import { Render } from "~/components"
11+
import { Render } from "~/components";
1112

1213
<Render file="magic-user-role" product="networking-services" />

‎src/content/docs/magic-wan/configuration/common-settings/index.mdx‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Common settings
33
pcx_content_type: navigation
4+
head: []
45
sidebar:
56
order: 4
6-
77
---
88

9-
import { DirectoryListing } from "~/components"
9+
import { DirectoryListing } from "~/components";
1010

11-
Review this section to learn about the settings shared between the Magic WAN Connector and the manual setup process for Magic WAN.
11+
Review this section to learn about the common settings that apply to both the Magic WAN Connector setup process and the manual setup process for Magic WAN.
1212

1313
<DirectoryListing />

‎src/content/docs/magic-wan/configuration/common-settings/sites.mdx‎

Lines changed: 14 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,12 @@
22
title: Set up a site
33
pcx_content_type: how-to
44
sidebar:
5-
order: 2
5+
order: 1
66
badge:
77
text: Beta
88
---
99

10-
import { Render } from "~/components"
10+
import { Render } from "~/components";
1111

1212
Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to check, at a glance, the state of your on-ramps and set up health alert settings so that you get notified when there are issues with the site's on-ramps.
1313

@@ -24,17 +24,21 @@ To use a site, start by setting up your on-ramps. These can be [GRE or IPsec tun
2424
7. Select **Continue**.
2525
8. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
2626
9. In **Magic WAN Health Check Alert** > **Notification name**, enter a name for the site's alert.
27-
9. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
28-
10. In **Alert sensitivity level** define the threshold for Magic Tunnel health alerts to be fired. Refer to [How Cloudflare calculates Magic Tunnel health alerts](/magic-wan/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information.
29-
11. Select **Complete setup** to finish setting up your site.
27+
10. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
28+
11. In **Alert sensitivity level** define the threshold for Magic Tunnel health alerts to be fired. Refer to [How Cloudflare calculates Magic Tunnel health alerts](/magic-wan/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information.
29+
12. Select **Complete setup** to finish setting up your site.
3030

3131
Your site is now set up. If you have other sites you need to set up, repeat the steps above. If you did not set up alerts, we strongly recommend that you do it. Otherwise you will not be notified when there is a problem with one of your on-ramps.
3232

3333
---
3434

3535
## Site analytics
3636

37-
<Render file="analytics/site-analytics" product="networking-services" params={{ instructions: "" }}/>
37+
<Render
38+
file="analytics/site-analytics"
39+
product="networking-services"
40+
params={{ instructions: "" }}
41+
/>
3842

3943
---
4044

@@ -60,4 +64,7 @@ If you add geographic coordinates to your site, it will show up in the Network m
6064

6165
### Set thresholds for Magic WAN site health
6266

63-
<Render file="analytics/set-thresholds-site-health" product="networking-services" />
67+
<Render
68+
file="analytics/set-thresholds-site-health"
69+
product="networking-services"
70+
/>

‎src/content/docs/magic-wan/configuration/common-settings/update-tunnel-health-checks-frequency.mdx‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
pcx_content_type: how-to
33
title: Update tunnel health checks frequency
44
sidebar:
5-
order: 4
5+
order: 3
66
---
77

88
import { Render } from "~/components";
@@ -14,14 +14,15 @@ import { Render } from "~/components";
1414
magicProduct: "Magic WAN",
1515
productName: "Magic WAN",
1616
healthChecksUrl: "/magic-wan/reference/tunnel-health-checks/",
17-
addTunnelsPath: "/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/#add-tunnels"
17+
addTunnelsPath:
18+
"/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/#add-tunnels",
1819
}}
1920
/>
2021

2122
<Render
2223
file="tunnel-health/health-checks-compatible-cmb-eu"
2324
product="networking-services"
2425
params={{
25-
productName: "Magic WAN"
26+
productName: "Magic WAN",
2627
}}
27-
/>
28+
/>

0 commit comments

Comments
 (0)