diff --git a/src/content/docs/magic-wan/configuration/common-settings/custom-ike-id-ipsec.mdx b/src/content/docs/magic-wan/configuration/common-settings/custom-ike-id-ipsec.mdx index d5327cba7d6188..e92bd80bdd00a8 100644 --- a/src/content/docs/magic-wan/configuration/common-settings/custom-ike-id-ipsec.mdx +++ b/src/content/docs/magic-wan/configuration/common-settings/custom-ike-id-ipsec.mdx @@ -5,6 +5,8 @@ sidebar: order: 6 --- +import { CURL } from "~/components"; + 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. :::note @@ -13,10 +15,13 @@ This feature is only available via API. There are no configuration options for a 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. -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 <account_id>, <tunnel_id>, and the FQDN wildcard before running the API call. +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 ``, ``, and the FQDN wildcard before running the API call. -```txt -% cloudflared access curl -https://conduit-api.cfdata.org/accounts//ipsec_tunnels/ --XPUT -d '{"custom_remote_identities": {"fqdn_id": "*..custom.ipsec.cloudflare.com"}}' -``` +..custom.ipsec.cloudflare.com"} + }} +/>