diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx index e1e6f32bf672f58..07665bdd836da01 100644 --- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx +++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx @@ -18,6 +18,7 @@ import { Render } from "~/components" routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization", chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes", publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.", - productGatewayOrEgress: "Magic Transit with Egress" + productGatewayOrEgress: "Magic Transit with Egress", + dashButtonPath: "/?to=/:account/magic-transit/configuration" }} /> \ No newline at end of file diff --git a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx index 942793759694b69..491c24752fb72f1 100644 --- a/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx +++ b/src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-tunnels.mdx @@ -16,7 +16,8 @@ import { GlossaryTooltip, Render } from "~/components"; ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters", antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/", cniLink: "/magic-transit/network-interconnect/", - productPathDash: "Magic Transit > Configuration", + targetPageName: "Configuration", + dashButtonPath: "/?to=/:account/magic-transit/configuration", updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/", tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/", antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/", diff --git a/src/content/docs/magic-transit/analytics/traceroutes.mdx b/src/content/docs/magic-transit/analytics/traceroutes.mdx index 85099bd60a684b1..101d798d56eb7df 100644 --- a/src/content/docs/magic-transit/analytics/traceroutes.mdx +++ b/src/content/docs/magic-transit/analytics/traceroutes.mdx @@ -10,5 +10,8 @@ import { Render } from "~/components"; diff --git a/src/content/docs/magic-transit/how-to/configure-routes.mdx b/src/content/docs/magic-transit/how-to/configure-routes.mdx index c29a3600e7e1f93..1241b7b724bbd8a 100644 --- a/src/content/docs/magic-transit/how-to/configure-routes.mdx +++ b/src/content/docs/magic-transit/how-to/configure-routes.mdx @@ -21,6 +21,7 @@ import { Render } from "~/components" routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization", chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes", publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.", - productGatewayOrEgress: "Magic Transit with Egress" + productGatewayOrEgress: "Magic Transit with Egress", + dashButtonPath: "/?to=/:account/magic-transit/configuration" }} /> \ No newline at end of file diff --git a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx index 3d81caec61b0ef5..2a77037172b2cb4 100644 --- a/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx +++ b/src/content/docs/magic-transit/how-to/configure-tunnel-endpoints.mdx @@ -20,7 +20,8 @@ import { Render } from "~/components"; ciphersPagePath: "/magic-transit/reference/gre-ipsec-tunnels/#supported-configuration-parameters", antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/", cniLink: "/magic-transit/network-interconnect/", - productPathDash: "Magic Transit > Configuration", + targetPageName: "Configuration", + dashButtonPath: "/?to=/:account/magic-transit/configuration", updateHCFrequencyPage: "/magic-transit/network-health/update-tunnel-health-checks-frequency/", tunnelHealthChecksPage: "/magic-transit/reference/tunnel-health-checks/", antiReplayPagePath: "/magic-transit/reference/anti-replay-protection/", diff --git a/src/content/docs/magic-wan/analytics/traceroutes.mdx b/src/content/docs/magic-wan/analytics/traceroutes.mdx index 0c9e1e1a437c1b8..8bf1a6f765d5c42 100644 --- a/src/content/docs/magic-wan/analytics/traceroutes.mdx +++ b/src/content/docs/magic-wan/analytics/traceroutes.mdx @@ -7,7 +7,11 @@ sidebar: import { Render } from "~/components"; - diff --git a/src/content/docs/magic-wan/configuration/manually/how-to/configure-routes.mdx b/src/content/docs/magic-wan/configuration/manually/how-to/configure-routes.mdx index 40e80c2a86c5d71..314e78e2e6bc306 100644 --- a/src/content/docs/magic-wan/configuration/manually/how-to/configure-routes.mdx +++ b/src/content/docs/magic-wan/configuration/manually/how-to/configure-routes.mdx @@ -21,7 +21,8 @@ import { Render } from "~/components" routePrioritization: "/magic-wan/reference/traffic-steering/#route-prioritization", chooseWeights: "/magic-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes", publicAsnMT: " ", - productGatewayOrEgress: "Magic WAN with Gateway" + productGatewayOrEgress: "Magic WAN with Gateway", + dashButtonPath: "/?to=/:account/magic-wan/configuration" }} /> diff --git a/src/content/docs/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints.mdx b/src/content/docs/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints.mdx index 6f90014d6b2cea5..d242db9611e4d33 100644 --- a/src/content/docs/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints.mdx +++ b/src/content/docs/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints.mdx @@ -20,7 +20,8 @@ import { GlossaryTooltip, Render } from "~/components"; ciphersPagePath: "/magic-wan/reference/gre-ipsec-tunnels/#supported-configuration-parameters", antiReplayPagePath: "/magic-wan/reference/anti-replay-protection/", cniLink: "/magic-wan/network-interconnect/", - productPathDash: "Magic WAN > Configuration", + targetPageName: "Configuration", + dashButtonPath: "/?to=/:account/magic-wan/configuration", updateHCFrequencyPage: "/magic-wan/configuration/common-settings/tunnel-health-checks-frequency/", tunnelHealthChecksPage: "/magic-wan/reference/tunnel-health-checks/", antiReplayPagePath: "/magic-wan/reference/anti-replay-protection/", diff --git a/src/content/partials/networking-services/analytics/traceroutes.mdx b/src/content/partials/networking-services/analytics/traceroutes.mdx index 08d49129f605ca2..6d459c27b1cd512 100644 --- a/src/content/partials/networking-services/analytics/traceroutes.mdx +++ b/src/content/partials/networking-services/analytics/traceroutes.mdx @@ -1,18 +1,21 @@ --- params: - productName + - dashButtonPath --- -import { Markdown } from "~/components"; +import { DashButton } from "~/components"; Magic {props.productName} customers can run traceroutes to understand the hop by hop Internet path and latencies from Cloudflare's network to their own network. To run a traceroute from a specific Cloudflare data center to your network: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. Go to **Magic {props.productName}** > **Tunnel Health**. -3. Expand a Magic Tunnel, and find the Cloudflare data center where the traceroute will be run from. -4. Select **Traceroute for details**. +1. In the Cloudflare dashboard, go to Magic {props.productName}'s **Network health** page. + + + +2. Expand a Magic Tunnel, and find the Cloudflare data center where the traceroute will be run from. +3. Select **Traceroute for details**. You can access detailed data from the traceroute, including: diff --git a/src/content/partials/networking-services/magic-user-role.mdx b/src/content/partials/networking-services/magic-user-role.mdx index edf17c1052ab775..f4ab2ce4f54b2d9 100644 --- a/src/content/partials/networking-services/magic-user-role.mdx +++ b/src/content/partials/networking-services/magic-user-role.mdx @@ -3,17 +3,21 @@ --- +import { DashButton } from "~/components"; + You can determine which users have, or do not have, configuration edit access for Magic products, including Magic Transit, Magic WAN, and Magic Firewall. For example, if you have multiple Cloudflare products managed by different teams on the same account, you may want to provide select users with edit access and other users with read-only access. ## Assign permissions -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. -2. From your Account Home, go to **Manage Account** > **Members**. -3. Under **Members**, enter an existing user's name and select **Search**. -4. Expand the menu at the end of the user row. -5. From the list, locate **Network Services (Magic)**. -6. Select one of two options: +1. In the Cloudflare dashboard, go to the **Members** page. + + + +2. Under **Members**, enter an existing user's name and select **Search**. +3. Expand the menu at the end of the user row. +4. From the list, locate **Network Services (Magic)**. +5. Select one of two options: - **Network Services (Magic)** - Enables users to view and edit Magic configurations. - **Network Services (Magic, Read-Only)** - Enables users to view but not modify Magic configurations. diff --git a/src/content/partials/networking-services/mconn/configure-connectors.mdx b/src/content/partials/networking-services/mconn/configure-connectors.mdx index caeee0dd3efab74..2dd5c346b6a503b 100644 --- a/src/content/partials/networking-services/mconn/configure-connectors.mdx +++ b/src/content/partials/networking-services/mconn/configure-connectors.mdx @@ -10,7 +10,18 @@ params: - finalInstructions --- -import { AnchorHeading, Aside, Card, Code, GlossaryTooltip, Markdown, Render, Tabs, TabItem } from "~/components"; +import { + AnchorHeading, + Aside, + Card, + Code, + GlossaryTooltip, + Markdown, + Render, + Tabs, + TabItem, + DashButton, +} from "~/components"; { props.magicWord === "virtual" && ( <> @@ -513,8 +524,11 @@ After finishing your Connector configuration, you need to add it to a site. **Configuration** > **Connectors**. +1. In the Cloudflare dashboard, go to Magic WAN's **Configuration** page. + + + +2. Go to **Connectors**. 3. Find the Connector you want to activate, select the three dots next to it > **Edit**. Make sure you verify the serial number to choose the right connector you want to activate. 4. In the new window, the **Status** dropdown will show as **Deactivated**. Select it to change the status to **Activated**. 5. The **Interrupt window** is the time period when the Magic WAN Connector software can update, which may result in interruption to existing connections. Choose a time period to minimize disruption to your sites. Refer to [Interrupt window](/magic-wan/configuration/connector/maintenance/interrupt-service-window/) for more details on how to define when the Connector can update its systems. @@ -769,10 +783,13 @@ Magic WAN Connector automatically creates [IPsec tunnels](/magic-wan/reference/g To check the IPsec tunnels and static routes created by your Magic WAN Connector: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. Go to **Magic WAN** > **Sites**. -3. Select the name of the site for which you want to check the Connector's IPsec tunnels and static routes, and select **Edit**. -4. Select **Tunnels** to check IPsec tunnels, and **Routes** for the static routes. +1. In the Cloudflare dashboard, go to the **Sites** page. + + + +2. Select the name of the site for which you want to check the Connector's IPsec tunnels and static routes, and select **Edit**. + +3. Select **Tunnels** to check IPsec tunnels, and **Routes** for the static routes. --- diff --git a/src/content/partials/networking-services/mconn/register-hardware-appliance.mdx b/src/content/partials/networking-services/mconn/register-hardware-appliance.mdx index b173fdf4ffddfcb..29480c4a84aa00a 100644 --- a/src/content/partials/networking-services/mconn/register-hardware-appliance.mdx +++ b/src/content/partials/networking-services/mconn/register-hardware-appliance.mdx @@ -2,11 +2,15 @@ {} --- -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. Go to **Magic WAN** > **Configuration**. -3. Under **Connectors**, select **Register your appliance**. -4. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Magic WAN Connector you are adding to the dashboard. -5. (Optional) Select **Add** below **Serial number** to add multiple Magic WAN Connectors at once to your account. -6. Select **Register appliance**. - -Your device is now registered with your account. Select **Add on-ramps** to continue with the setup process, or **Return to connections** to check your newly added Connector. \ No newline at end of file +import { DashButton } from "~/components"; + +1. In the Cloudflare dashboard, go to Magic WAN's **Configuration** page. + + + +2. Under **Connectors**, select **Register your appliance**. +3. In **Appliance details** > **Serial number**, insert the serial number for your device. You can optionally add notes about the Magic WAN Connector you are adding to the dashboard. +4. (Optional) Select **Add** below **Serial number** to add multiple Magic WAN Connectors at once to your account. +5. Select **Register appliance**. + +Your device is now registered with your account. Select **Add on-ramps** to continue with the setup process, or **Return to connections** to check your newly added Connector. diff --git a/src/content/partials/networking-services/routing/configure-routes.mdx b/src/content/partials/networking-services/routing/configure-routes.mdx index f1aefbd6b934d40..13e74e7484bfd49 100644 --- a/src/content/partials/networking-services/routing/configure-routes.mdx +++ b/src/content/partials/networking-services/routing/configure-routes.mdx @@ -8,9 +8,10 @@ params: - routePrioritization - chooseWeights - productGatewayOrEgress + - dashButtonPath --- -import { Aside, APIRequest, Markdown, Render, TabItem, Tabs } from "~/components"; +import { Aside, APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components"; Magic Networking uses a routing table to steer your traffic via next-hop from Cloudflare's global network to your connected networks. Entries can be added to the Magic routing table via static route configuration or via routes learned through BGP peering (only available over Direct CNI). @@ -32,20 +33,22 @@ Refer to Traffic Steering for more infor -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. -2. Go to **{props.productName}** > **Configuration**. -3. From the **Routes** tab, select **Create** to add a new route. -4. Enter a descriptive name for your route in **Description**. -5. In **Prefix**, enter your range of IP addresses. For example, `10.10.10.100/24`. -6. In **Tunnel/Next hop** select which tunnel you want your route to go through. Choose from the tunnels you have created in Configure tunnel endpoints. -7. Choose the **Priority** for your route. Lower numbers have higher priorities. +1. In the Cloudflare dashboard, go to {props.productName}'s **Configuration** page. + + + +2. From the **Routes** tab, select **Create** to add a new route. +3. Enter a descriptive name for your route in **Description**. +4. In **Prefix**, enter your range of IP addresses. For example, `10.10.10.100/24`. +5. In **Tunnel/Next hop** select which tunnel you want your route to go through. Choose from the tunnels you have created in Configure tunnel endpoints. +6. Choose the **Priority** for your route. Lower numbers have higher priorities. :::note Have this in mind when configuring priorities for your routes. Refer to Route prioritization for more information. ::: -8. (Optional) Choose a **Weight** for your route. Refer to Set priority and weights for static routes for examples. -9. (Optional) If you need to scope your route to a specific region, you can do it in **Region code**. -10. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**. -11. Select **Add routes** when you are done. +7. (Optional) Choose a **Weight** for your route. Refer to Set priority and weights for static routes for examples. +8. (Optional) If you need to scope your route to a specific region, you can do it in **Region code**. +9. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**. +10. Select **Add routes** when you are done. @@ -263,8 +266,11 @@ The Magic routing table is managed by the customer, who can select both the Clou By default, each BGP peering session will use the same Cloudflare-side ASN to represent peering with the {props.productName} routing table. This ASN is called the **CF Account ASN** and is set to `13335`. This can be configured to a private 2-byte ASN (for example, any values between `64512` and `65534`). To set this ASN: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account. -2. Go to **{props.productName}** > **Configuration** > **BGP**. +1. In the Cloudflare dashboard, go to {props.productName}'s **Configuration** page. + + + +2. Go to **BGP configuration**. 3. In **CF Account ASN**, enter Cloudflare's ASN. 4. Select **Update**. @@ -313,8 +319,11 @@ You need to configure two ASNs: If you already have set up your Cloudflare account ASN, you can skip steps two and three below. -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. -2. Go to **{props.productName}** > **Configuration** > **BGP configuration**. +1. In the Cloudflare dashboard, go to {props.productName}'s **Configuration** page. + + + +2. Go to **BGP configuration**. 3. In **CF Account ASN**, enter Cloudflare's ASN. 4. Go to **Interconnects**. 5. Find the Direct CNI interconnect you want to configure with BGP > select the **three dots** next to it > **Configure BGP**. diff --git a/src/content/partials/networking-services/routing/configure-tunnels.mdx b/src/content/partials/networking-services/routing/configure-tunnels.mdx index 0d95bab8c7937dd..a927799dc785513 100644 --- a/src/content/partials/networking-services/routing/configure-tunnels.mdx +++ b/src/content/partials/networking-services/routing/configure-tunnels.mdx @@ -7,7 +7,8 @@ params: - ciphersPagePath - antiReplayPagePath - cniLink - - productPathDash + - targetPageName + - dashButtonPath - updateHCFrequencyPage - tunnelHealthChecksPage - antiReplayPagePath @@ -16,7 +17,7 @@ params: - biVsUniHealthCheckDefaults --- -import { APIRequest, CURL, Details, GlossaryTooltip, Render, TabItem, Tabs } from "~/components"; +import { APIRequest, CURL, Details, GlossaryTooltip, Render, TabItem, Tabs, DashButton } from "~/components"; Cloudflare recommends two tunnels for each ISP and network location router combination, one per Cloudflare endpoint. Shortly after your onboarding kickoff call, Cloudflare will assign two Cloudflare endpoint addresses that you can use as the tunnel destinations on your network location's routers/endpoints. @@ -74,48 +75,49 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. -2. Select **{props.productPathDash}**. -3. From the **Tunnels** tab, select **Create**. -4. On the **Add tunnels** page, choose either a **GRE tunnel** or **IPsec tunnel**. +1. In the Cloudflare dashboard, go to {props.productName}'s **{props.targetPageName}** page. + + +2. From the **Tunnels** tab, select **Create**. +3. On the **Add tunnels** page, choose either a **GRE tunnel** or **IPsec tunnel**.
-5. In **Name**, give your tunnel a descriptive name. This name must be unique, must not contain spaces or special characters, and must be 15 or fewer characters. Hover the mouse over `i` in the dashboard for more information. -6. Give your tunnel a description in **Description**. You do not have character restrictions here. -7. In **IPv4 Interface address**, enter the internal IP address for your tunnel along with the interface's prefix length (either `/31` or `/30`). This is used to route traffic through the tunnel on the Cloudflare side. We recommend using an RFC1918 address scheme with a `/31` netmask, as it provides the most efficient use of IP address space. -8. In **Customer GRE endpoint**, enter your router's public IP address. This value is not needed if you intend to use a physical or virtual connection like Cloudflare Network Interconnect because Cloudflare will provide it. -9. In **Cloudflare GRE endpoint**, enter the anycast address you received from your account team. -10. Leave the default values for **TTL** and **MTU**. -11. _(Optional)_ **Tunnel health checks** are enabled by default. If you disable Tunnel health checks, your tunnels will appear 100% down in your tunnel health dashboard even when working. Cloudflare will keep sending traffic through the tunnel, without the means to detect if the tunnel goes down. You will have to set up your own system to detect down tunnels, as Cloudflare will not be able to warn you about down tunnels. Refer to Tunnel health checks for more information. -12. _(Optional)_ If you keep **Tunnel health checks** enabled, choose the **Health check rate** for your tunnel. Available options are _Low_, _Medium_, and _High_. -13. The **Health check type** defaults to _Reply_ and to creating an ICMP reply. If your firewall drops this type of packet for assuming it is a type of attack, change this option to _Request_ which will create an ICMP request. Refer to Tunnel health checks for more information. -14. The **Health check direction** defaults to **{props.biVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details. -15. _(Optional)_ **Health check target** is the customer end of the tunnel. This field is only visible when the **Health check direction** is set to _Unidirectional_. -16. _(Optional)_ We recommend you test your tunnel before officially adding it. To test the tunnel, select **Test tunnels**. -17. To add multiple tunnels, select **Add GRE tunnel** for each new tunnel. -18. After adding your tunnel information, select **Add tunnels** to save your changes. +4. In **Name**, give your tunnel a descriptive name. This name must be unique, must not contain spaces or special characters, and must be 15 or fewer characters. Hover the mouse over `i` in the dashboard for more information. +5. Give your tunnel a description in **Description**. You do not have character restrictions here. +6. In **IPv4 Interface address**, enter the internal IP address for your tunnel along with the interface's prefix length (either `/31` or `/30`). This is used to route traffic through the tunnel on the Cloudflare side. We recommend using an RFC1918 address scheme with a `/31` netmask, as it provides the most efficient use of IP address space. +7. In **Customer GRE endpoint**, enter your router's public IP address. This value is not needed if you intend to use a physical or virtual connection like Cloudflare Network Interconnect because Cloudflare will provide it. +8. In **Cloudflare GRE endpoint**, enter the anycast address you received from your account team. +9. Leave the default values for **TTL** and **MTU**. +10. _(Optional)_ **Tunnel health checks** are enabled by default. If you disable Tunnel health checks, your tunnels will appear 100% down in your tunnel health dashboard even when working. Cloudflare will keep sending traffic through the tunnel, without the means to detect if the tunnel goes down. You will have to set up your own system to detect down tunnels, as Cloudflare will not be able to warn you about down tunnels. Refer to Tunnel health checks for more information. +11. _(Optional)_ If you keep **Tunnel health checks** enabled, choose the **Health check rate** for your tunnel. Available options are _Low_, _Medium_, and _High_. +12. The **Health check type** defaults to _Reply_ and to creating an ICMP reply. If your firewall drops this type of packet for assuming it is a type of attack, change this option to _Request_ which will create an ICMP request. Refer to Tunnel health checks for more information. +13. The **Health check direction** defaults to **{props.biVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details. +14. _(Optional)_ **Health check target** is the customer end of the tunnel. This field is only visible when the **Health check direction** is set to _Unidirectional_. +15. _(Optional)_ We recommend you test your tunnel before officially adding it. To test the tunnel, select **Test tunnels**. +16. To add multiple tunnels, select **Add GRE tunnel** for each new tunnel. +17. After adding your tunnel information, select **Add tunnels** to save your changes.
-5. In **Name**, give your tunnel a descriptive name. This name must be unique, must not contain spaces or special characters, and must be 15 or fewer characters. Hover the mouse over `i` in the dashboard for more information. -6. Give your tunnel a description in **Description**. You do not have character restrictions here. -7. In **IPv4 Interface address**, enter the internal IP address for your tunnel along with the interface's prefix length (either `/31` or `/30`). This is used to route traffic through the tunnel on the Cloudflare side. We recommend using an RFC1918 address scheme with a `/31` netmask, as it provides the most efficient use of IP address space. -8. In **Customer endpoint**, enter your router's public IP address. This value is only required if your router is using an IKE ID of type `ID_IPV4_ADDR`. -9. In **Cloudflare endpoint**, enter the anycast address you received from your account team. -10. _(Optional)_ **Tunnel health checks** are enabled by default. If you disable Tunnel health checks, your tunnels will appear 100% down in your tunnel health dashboard even when working. Cloudflare will keep sending traffic through the tunnel, without the means to detect if the tunnel goes down. You will have to set up your own system to detect down tunnels, as Cloudflare will not be able to warn you about down tunnels. Refer to Tunnel health checks for more information. -11. _(Optional)_ If you keep **Tunnel health checks** enabled, choose the **Health check rate** for your tunnel. Available options are _Low_, _Medium_ and _High_. -12. _(Optional)_ The **Health check type** defaults to _Reply_ and to creating an ICMP reply. If your firewall drops this type of packet for assuming it is a type of attack, change this option to _Request_ which will create an ICMP request. Refer to Tunnel health checks for more information. -13. _(Optional)_ The **Health check direction** defaults to **{props.biVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details. -14. _(Optional)_ **Health check target** is the customer end of the tunnel. This field is only visible when the **Health check direction** is set to _Unidirectional_. +4. In **Name**, give your tunnel a descriptive name. This name must be unique, must not contain spaces or special characters, and must be 15 or fewer characters. Hover the mouse over `i` in the dashboard for more information. +5. Give your tunnel a description in **Description**. You do not have character restrictions here. +6. In **IPv4 Interface address**, enter the internal IP address for your tunnel along with the interface's prefix length (either `/31` or `/30`). This is used to route traffic through the tunnel on the Cloudflare side. We recommend using an RFC1918 address scheme with a `/31` netmask, as it provides the most efficient use of IP address space. +7. In **Customer endpoint**, enter your router's public IP address. This value is only required if your router is using an IKE ID of type `ID_IPV4_ADDR`. +8. In **Cloudflare endpoint**, enter the anycast address you received from your account team. +9. _(Optional)_ **Tunnel health checks** are enabled by default. If you disable Tunnel health checks, your tunnels will appear 100% down in your tunnel health dashboard even when working. Cloudflare will keep sending traffic through the tunnel, without the means to detect if the tunnel goes down. You will have to set up your own system to detect down tunnels, as Cloudflare will not be able to warn you about down tunnels. Refer to Tunnel health checks for more information. +10. _(Optional)_ If you keep **Tunnel health checks** enabled, choose the **Health check rate** for your tunnel. Available options are _Low_, _Medium_ and _High_. +11. _(Optional)_ The **Health check type** defaults to _Reply_ and to creating an ICMP reply. If your firewall drops this type of packet for assuming it is a type of attack, change this option to _Request_ which will create an ICMP request. Refer to Tunnel health checks for more information. +12. _(Optional)_ The **Health check direction** defaults to **{props.biVsUniHealthCheck}** for {props.productName}. Refer to [Bidirectional vs unidirectional health checks](#bidirectional-vs-unidirectional-health-checks) for more details. +13. _(Optional)_ **Health check target** is the customer end of the tunnel. This field is only visible when the **Health check direction** is set to _Unidirectional_. :::note IPsec tunnels will not function without a pre-shared key (PSK). ::: -15. If you do not have a pre-shared key yet: +14. If you do not have a pre-shared key yet: 1. Select **Add pre-shared key later**. 2. _(Optional)_ We recommend you test your tunnel configuration before officially adding it. To test the tunnel, select **Test tunnels**. @@ -123,14 +125,14 @@ Beyond GRE and IPsec tunnels, you can also use Network Interconnect (CNI) to onb 4. The Cloudflare dashboard will load the list of tunnels you have configured. The IPsec tunnel you have just created will be listed with a warning in the form of a triangle to let you know it is not yet functional. Select **Edit**. 5. Choose **Generate a new pre-shared key** > **Update and generate a pre-shared key**. Save the key to a safe place, and select **Done**. -16. If you already have a pre-shared key: +15. If you already have a pre-shared key: 1. Select **Use my own pre-shared key**. 2. Paste your key in **Your pre-shared key**. 3. _(Optional)_ We recommend you test your tunnel before officially adding it. To test the tunnel, select **Test tunnels**. 4. Select **Add tunnels**. -17. (Optional) Enable **Replay protection** if you have devices that do not support disabling it. Refer to Anti-replay protection for more information. +16. (Optional) Enable **Replay protection** if you have devices that do not support disabling it. Refer to Anti-replay protection for more information.
diff --git a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx index 4a33a26b16c8421..05ce6820c049132 100644 --- a/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx +++ b/src/content/partials/networking-services/tunnel-health/magic-tunnel-health-alerts.mdx @@ -7,7 +7,16 @@ params: - healthChecks --- -import { APIRequest, Code, Details, GlossaryTooltip, Render, Tabs, TabItem } from "~/components"; +import { + APIRequest, + Code, + Details, + GlossaryTooltip, + Render, + Tabs, + TabItem, + DashButton, +} from "~/components"; {props.productName} customers can configure Magic Tunnel health alerts to receive email, webhook, and PagerDuty notifications when the percentage of successful health checks for a Magic Tunnel drops below the selected service-level objective (SLO). @@ -51,8 +60,11 @@ Refer to How Cloudflare calcul -1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account. -2. Select **Notifications** > **Add**. +1. In the Cloudflare dashboard, go to the **Notifications** page. + + + +2. Select **Add**. 3. From the **Product** drop-down menu, select **{props.productName}**. 4. Select **Magic Tunnel Health Check Alert** > **Select** to add a notification. You can add alerts by tunnel or by data center (beta). diff --git a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx index e69187ffd66ad3b..7673fe4e2806b6a 100644 --- a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx +++ b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx @@ -6,7 +6,15 @@ params: - addTunnelsPath --- -import { CURL, AnchorHeading, GlossaryTooltip, Markdown, TabItem, Tabs } from "~/components"; +import { + CURL, + AnchorHeading, + GlossaryTooltip, + Markdown, + TabItem, + Tabs, + DashButton, +} from "~/components"; By default, Cloudflare servers send health checks to each GRE, CNI, or IPsec tunnel endpoint you configure to receive traffic from {props.productName}. @@ -51,10 +59,9 @@ Below is an example of how to adjust tunnel health check frequency to `low`. Not url="https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/ipsec_tunnels/{ipsec_tunnel_id}" method="PUT" json={{ - "health_check": - { - "rate": "low" - } + health_check: { + rate: "low", + }, }} /> @@ -62,21 +69,20 @@ Below is an example of how to adjust tunnel health check frequency to `low`. Not { props.magicProduct === "Magic WAN" && ( + <> - - **Sites**. - 3. Select your site > **Edit**. - 4. In **Network** > **WAN configuration** > select your WAN > **Edit** - 5. Change the **Health check rate** to your desire rate. - 6. Select **Save**. - `} - inline={false} - /> - +
    +

  1. In the Cloudflare dashboard, go to the Sites page.

    + +
    2. + +
  2. Select your site > Edit.
    3. +
  3. In Network > WAN configuration > select your WAN > Edit.
    4. +
  4. Change the Health check rate to your desire rate.
    5. +
  5. Select Save.
    6. +
- ) -} \ No newline at end of file + + ) +}