diff --git a/src/content/docs/magic-wan/configuration/connector/configure-hardware-connector/index.mdx b/src/content/docs/magic-wan/configuration/connector/configure-hardware-connector/index.mdx index 3f7ab16b54776c..d42c7aa88c5f12 100644 --- a/src/content/docs/magic-wan/configuration/connector/configure-hardware-connector/index.mdx +++ b/src/content/docs/magic-wan/configuration/connector/configure-hardware-connector/index.mdx @@ -6,162 +6,16 @@ sidebar: label: Configure hardware Connector --- -import { GlossaryTooltip, Render, Card } from "~/components"; - -## Prerequisites - -You need to purchase [Magic WAN](https://www.cloudflare.com/magic-wan/) before you can purchase and use the Magic WAN Connector. The Magic WAN Connector can function as your primary edge device for your network, or be deployed in-line with existing network gear. - -You also need to purchase a Magic WAN Connector before you can start configuring your settings in the Cloudflare dashboard. After buying a Magic WAN Connector, the device will be registered with your Cloudflare account and show up in your Cloudflare dashboard. - -Contact your account representative to learn more about purchasing options for the Magic WAN Connector device. - ---- - -## Before you begin - - - ---- - -## DHCP vs static IP connections - -Magic WAN Connector uses a DHCP connection at first boot to download your settings and go through the activation process. However, if you need to use a static IP in your Connector, and this is a fresh install: -1. Connect Magic WAN Connector to a DHCP port with access to the Internet. -2. Go through the [setup flow](#set-up-cloudflare-dashboard) below and activate your Connector. -3. Refer to [WAN with a static IP address](#wan-with-a-static-ip-address). - ---- - -## Port speeds - -The hardware version of the Magic WAN connector includes two [SFP+ ports](https://en.wikipedia.org/wiki/Small_Form-factor_Pluggable) that support 10G throughput, as well as six RJ45 ports that support 1G throughput. - -Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for details on this topic. - ---- - -## Set up Cloudflare dashboard - - If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.", - lan: "refers to the physical Magic WAN Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector.
If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.", - noConnectorShows: - "You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.", - }} -/> - -## Set up your Magic WAN Connector - -### Device installation - -There are several deployment options for Magic WAN Connector. Connector can act like a DHCP server for your local network, or integrate with your local setup and have static IP addresses assigned to it. - -When Connector acts like the WAN router for your site, deployment will be something like this: - -```mermaid -flowchart LR -accTitle: Magic WAN Connector set up as a DHCP server, and connecting to the Internet. - a(Magic WAN Connector)--> b(Internet) --> c(Cloudflare) - - subgraph Customer site - d[LAN 1] --> a - e[LAN 2] --> a - end - - classDef orange fill:#f48120,color: black - class a,c orange -``` - -
- -In the example below, the Connector sits behind the WAN router in your site, and on-ramps only some of the existing LANs to Cloudflare. - -
- -```mermaid -flowchart LR -accTitle: Magic WAN Connector connects to the router in the site, and only some of the LANs connect to Connector. - a(Magic WAN Connector)--> b((Site's router)) --> c(Internet) --> i(Cloudflare) - - subgraph Customer site - d[LAN 1] --> a - e[LAN 2] --> a - g(LAN 3) --> b - h(LAN 4) --> b - end - - classDef orange fill:#f48120,color: black - class a,i orange -``` - -Refer to [Magic WAN Connector deployment options](/reference-architecture/diagrams/sase/magic-wan-connector-deployment/) for a high-level explanation of the deployment options that make sense to most environments, as well as a few advanced use cases. - -#### Firewall settings required - -If there is a firewall deployed upstream of the Magic WAN Connector, configure the firewall to allow the following traffic: - -{/* prettier-ignore */} -| Protocol/port | Destination IP/URL | Purpose | -| --- | --- |--- | -| `UDP/53` | DNS destination IP `1.1.1.1` | Needed to allow DNS traffic to Cloudflare DNS servers. Cloudflare uses this port for DNS lookups of control plane API | -| `TCP/443` | - | The Connector will open outbound HTTPS connections over this port for control plane operations. | -| `UDP/4500` | Destination IP `162.159.64.1` | Needed for Connector's initialization and discovery traffic through outbound connections. | -| `UDP/4500` | Destination IP - Cloudflare anycast IPs | Needed for the Cloudflare anycast IPs assigned to your account for tunnel outbound connections. This traffic is tunnel traffic. | -| `TCP/7844`, `UDP/7844` | Outbound connections | This is for debugging facilities in the Connector. | -| `UDP/123` | `http://time.cloudflare.com/` | Needed for Magic WAN Connector to periodically contact Cloudflare's Time Services. | - -## Activate Connector - - - ---- - -## WAN with a static IP address - -After activating your Connector, you can use it in a network configuration with the WAN interface set to a static IP address — that is, an Internet configuration that is not automatically set by DHCP. To use your Connector on a network configuration with a static IP, follow the steps below. - -:::caution -Make sure you complete the setup workflow and activate your Magic WAN Connector before changing the WAN settings to a static IP. -::: - -1. Connect Magic WAN Connector to a DHCP port with access to the Internet. -2. [Add a Connector on-ramp](#1-add-a-connector-on-ramp) in the Cloudflare dashboard. -3. Create a [DHCP WAN](#2-create-a-wan). -4. [Activate](#activate-connector) and power on your Connector. -5. Wait 60 seconds. -6. Make changes to the [WAN settings](#2-create-a-wan) in the Cloudflare dashboard to a static IP set up. -7. Wait 60 seconds again. -8. Magic WAN Connector will go offline. This is normal and expected behavior. -9. Adjust your physical connections as required to match the static configuration. -10. Magic WAN Connector comes back online. - ---- - - - ---- - -## IP sec tunnels and static routes - - - ---- - -## Next steps - - +import { Render } from "~/components"; + + If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.", + lan: "refers to the physical Magic WAN Connector Ethernet port that you are using for your LAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector.
If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.", + noConnectorShows: "You need to have bought a Connector already for it to show up here. Refer to [Prerequisites](#prerequisites) if no Connector shows up in this list.", + shippedLanguage: "The Magic WAN Connector is shipped to you deactivated", + hardSoftConn: "You need to deploy two Connectors in your premises before you can set up a site in high availability.", + finalInstructions: "Follow the instructions in [Set up your Magic WAN Connector](#set-up-your-magic-wan-connector) and [Activate Connector](#activate-connector) to finish setting up your Connectors." + }} /> diff --git a/src/content/docs/magic-wan/configuration/connector/configure-virtual-connector.mdx b/src/content/docs/magic-wan/configuration/connector/configure-virtual-connector.mdx index c43ed53ca36532..1da57d3d018bb4 100644 --- a/src/content/docs/magic-wan/configuration/connector/configure-virtual-connector.mdx +++ b/src/content/docs/magic-wan/configuration/connector/configure-virtual-connector.mdx @@ -7,169 +7,14 @@ sidebar: import { Render } from "~/components"; -Virtual Magic WAN Connector (Virtual Connector) is a virtual appliance alternative to the hardware based Magic WAN Connector appliance. These two versions of Connector are identical otherwise. - -## Prerequisites - -Before you can install Virtual Connector, you need an Enterprise account with Magic WAN enabled. Additionally, you need to have a VMware host with sufficient compute, memory, and storage to run the virtual machine with Virtual Connector. This includes: - -- Intel x86 CPU architecture -- ESXi hypervisor 7.0U1 or higher -- 4 virtual CPUs per virtual connector (We recommend deployment with a 1:1 virtual CPU to physical core allocation to avoid CPU over contention which will cause packet loss.) -- 8 GB of RAM per virtual connector -- 8 GB of disk per virtual connector -- One vSwitch port group or VLAN with access to the Internet (for example, through a WAN) -- One or more vSwitch port group or VLAN that will be the internal LAN - -Refer to [VMware's documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.install.doc/GUID-B2F01BF5-078A-4C7E-B505-5DFFED0B8C38.html) for more information on how to install ESXi and configure a virtual machine. - ---- - -## Before you begin - - - ---- - -## DHCP vs static IP connections - -Virtual Connector uses a DHCP connection at first boot to download your settings and go through the activation process. However, if you need to use a static IP in your Virtual Connector, and this is a fresh install: -1. Connect the machine with your Virtual Connector VM to a DHCP port with access to the Internet. -2. Go through the [setup flow](#set-up-cloudflare-dashboard) below and activate your Connector. -3. Refer to [WAN with a static IP address](#wan-with-a-static-ip-address). - -## Obtain the Virtual Connector image - -Contact your account team at Cloudflare to obtain the Virtual Connector [OVA package](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-AE61948B-C2EE-436E-BAFB-3C7209088552.html) and license keys. The OVA image includes the files required to install and configure the virtual machine (VM) for Virtual Connector with the appropriate settings. - -This image can be deployed multiple times to create several instances of a Virtual Connector, in different locations or on the same ESXi host. - -You will consume one license key for each instance created. For example, if you want to deploy 10 Virtual Connectors you should request 10 license keys, and your account team will create 10 Connector instances in your Cloudflare dashboard. - -## Deploy the Virtual Connector on VMware - -The following instructions assume you already have VMware ESXi hypervisor installed with sufficient resources. Refer to [Prerequisites](#prerequisites) for more information. - -1. When setting up your VMware ESXi, you need to create port groups for Virtual Connector. Go to **Networking** > **Port groups**, and prepare your vSwitch port groups and/or VLANs for your desired network topology. For example, a simple deployment typically has: - - A WAN port group where the Virtual Connector will get an IP address (static or DHCP) that has access to the Internet. - - A LAN port group, where the Virtual Connector will act as default router, and possibly DHCP server. - - A null, or unused, port group for allocating unused virtual interfaces in the Virtual Connector. You can, for example, create a null port group with the name of `Null port group`, and a **VLAN ID** of `999`. - -:::note[VLAN tagging] -Virtual Connector supports creating subinterfaces through the use of [802.1Q VLAN tagging](https://en.wikipedia.org/wiki/IEEE_802.1Q). - -Use VLAN ID `0` when: - -- Connected to a Port Group or Distributed Port Group that is associated with a specific VLAN. -- Connected to a Port Group or Distributed Port Group that is configured as a trunk that requires untagged packets. - -You can also configure subinterfaces on the Virtual Connector by associating the network interface with a Port Group or Distributed Port Group trunk and specifying a VLAN ID in addition to the port associated with the network interface (VLAN ID `1`-`4094`). - -Refer to [VMWare's documentation](https://kb.vmware.com/s/article/1003825) for more information. -::: - -2. Extract the files in the OVA image provided by your Cloudflare account team. For example: - - ```txt - tar -xvf mconn-2024-1-3.ova - ``` - - Take note of the folder where you are extracting the files to, as you will need to refer to that folder when creating the VM. - -3. Go to **Virtual Machines** > **Create/Register VM** wizard to start deploying the Virtual Connector. -4. Select **Deploy a virtual machine from an OVF or OVA file** > **Next**. -5. Choose a descriptive name for your virtual machine. -6. Upload the files you have extracted from the OVA image. These include `mconn.ovf`, `mconn.nvram`, and `mconn.vmdk`. -7. Select where you want to save the files extracted from the OVA image > **Next**. -8. In **Networking mappings**, select assignments for your desired topology according to the port groups you set up previously: - 1. For example, map `eno1` port to `VM Network` to create your WAN, and `eno2` to `LAN0` to act as your LAN port. - 2. Allocate any unused ports to the `null` port group. - 3. Take note of your configuration. You will need this information to configure your network in the Cloudflare dashboard. -9. In **Disk provisioning**, select **Thin**. -10. Before completing the deployment wizard, disable **Power on automatically**. This is important so that you can configure the license key prior to boot. -11. Configure the virtual machine with the license key your account team provided you: - 1. Select the Virtual Connector's VM > **Settings**. - 2. Go to **VM Options** > **Advanced** > **Edit Configuration**. - 3. Select **Add parameter** to add your license key. Scroll down to the last entry (this is where VMware adds the new parameter), and add the following two new entries: - - **Key**: `guestinfo.cloudflare.identity` - - **Value**: `` - -:::note -You cannot use the same license key twice, or reuse a key once the virtual machine has been registered with Cloudflare. You need a new key from your account team for every new Virtual Connector. -::: - -12. Select **Save** to finish configuring your Virtual Connector. -13. Continue set up in your [Cloudflare dashboard](#set-up-cloudflare-dashboard). - -## Set up Cloudflare dashboard - - - -## Activate Connector - - - -## Boot your Virtual Connector - -1. Go to **Virtual Machines** in VMware, and boot up Virtual Connector's VM. -2. The Virtual Connector will make a request to Cloudflare. This is the step where Virtual Connector registers your provided license key and downloads the [configuration you provided](#1-add-a-connector-on-ramp). -3. The Virtual Connector will set up the LAN and WAN connections according to the configuration downloaded from the site you created on the Cloudflare dashboard. The Virtual Connector will also establish IPsec tunnels. -4. If successful, the [tunnel health checks](/magic-wan/configuration/common-settings/check-tunnel-health-dashboard/) will show as healthy. -5. If you do not see a [healthy heartbeat](/magic-wan/configuration/connector/maintenance/heartbeat/) the Cloudflare dashboard, reboot the Virtual Connector's VM in VMware. - ---- - -## WAN with a static IP address - -After activating your Virtual Connector, you can use it in a network configuration with the WAN interface set to a static IP address - that is, an Internet configuration that is not automatically set by DHCP. To use your Virtual Connector on a network configuration with a static IP, follow the steps below. - -:::caution -Make sure you complete the setup workflow and activate your Virtual Connector before changing the WAN settings to a static IP. -::: - -1. Connect the machine where you installed the VM with Virtual Connector to a DHCP port with access to the Internet. -2. [Add a Connector on-ramp](#1-add-a-connector-on-ramp) in the Cloudflare dashboard. -3. Create a [DHCP WAN](#2-create-a-wan). -4. [Activate](#activate-connector) and boot your Virtual Connector. -5. Wait 60 seconds. -6. Make changes to the [WAN settings](#2-create-a-wan) in the Cloudflare dashboard to a static IP set up. -7. Wait 60 seconds again. -8. Modify your [Port Groups](#deploy-the-virtual-connector-on-vmware) as needed to change the source from which the WAN port obtains its IP address. -9. Reboot your virtual machine. - ---- - - - ---- - -## IP sec tunnels and static routes - - - ---- - -## Next steps - - + \ No newline at end of file diff --git a/src/content/partials/magic-wan/connector/activate-connector.mdx b/src/content/partials/magic-wan/connector/activate-connector.mdx deleted file mode 100644 index b8d84c83d905c5..00000000000000 --- a/src/content/partials/magic-wan/connector/activate-connector.mdx +++ /dev/null @@ -1,23 +0,0 @@ ---- -params: - - shippedLanguage ---- - -import { Markdown } from "~/components"; - -{props.shippedLanguage}, and will only establish a connection to the Cloudflare network when it is activated. Cloudflare recommends leaving it deactivated until you finish [setting it up in the dashboard](#1-add-a-connector-on-ramp). - -When the Connector is first activated, one of the ports must be connected to the Internet through a device that supports DHCP. This is required so that the Connector can reach the Cloudflare global network and download the required configurations that you [set up](#1-add-a-connector-on-ramp). - -:::caution -Remember to connect Magic WAN Connector through a route that supports DHCP for its first connection to the Internet. Otherwise, the Connector will not work. -::: - -When you are ready to connect your Magic WAN Connector to the Cloudflare network: - -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. Go to **Magic WAN** > **Configuration** > **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. -6. Select **Update**. diff --git a/src/content/partials/magic-wan/connector/before-you-begin.mdx b/src/content/partials/magic-wan/connector/before-you-begin.mdx deleted file mode 100644 index fe8cbe3f604700..00000000000000 --- a/src/content/partials/magic-wan/connector/before-you-begin.mdx +++ /dev/null @@ -1,25 +0,0 @@ ---- -{} ---- - -import { Card } from "~/components"; - -You can install up to two Magic WAN Connectors for redundancy at each of your sites. If one of your Connectors fail, traffic will fail over to the other Connector ensuring that you never lose connectivity to that site. - -In this type of high availability (HA) configuration, you will choose a reliable LAN interface as the HA link which will be used to monitor the health of the peer connector. HA links can be dedicated links or can be shared with other LAN traffic. - -You must decide the type of configuration you want for your site from the beginning: no redundancy or with redundancy. You cannot add redundancy after finishing configuring your dashboard settings. If, at a later stage, you decide to enable redundancy, you will need to delete your Connector on-ramp in the Cloudflare dashboard, and start again. - - - -- If you need a high availability configuration for your premises, refer to - [About high availability configurations](#about-high-availability-configurations) for more information - and learn how to configure your Connector in this mode. - -- If you do not need a high availability configuration for you premises, proceed to [Set up Cloudflare dashboard](#set-up-cloudflare-dashboard). - - - -:::caution -You cannot enable high availability for an existing Connector on-ramp. To add high availability to an existing Connector on-ramp in the Cloudflare dashboard, you need to delete the on-ramp and start again. Plan accordingly to create a high availability configuration from the start if needed. -::: diff --git a/src/content/partials/magic-wan/connector/configure-connectors.mdx b/src/content/partials/magic-wan/connector/configure-connectors.mdx new file mode 100644 index 00000000000000..0f4b7cb2f04349 --- /dev/null +++ b/src/content/partials/magic-wan/connector/configure-connectors.mdx @@ -0,0 +1,507 @@ +--- +params: + - magicWord + - productName + - productNameType + - wan + - lan + - noConnectorShows + - shippedLanguage + - hardSoftConn + - finalInstructions +--- + +import { AnchorHeading, Aside, Card, Code, GlossaryTooltip, Markdown, Render, TabItem, Tabs } from "~/components"; + +{ props.magicWord === "virtual" && ( + <> +

Virtual Magic WAN Connector (Virtual Connector) is a virtual appliance alternative to the hardware based Magic WAN Connector appliance. These two versions of Connector are identical otherwise.

+ + ) +} + +## Prerequisites + +{ props.magicWord === "hardware" && ( + <> +

You need to purchase Magic WAN before you can purchase and use the Magic WAN Connector. The Magic WAN Connector can function as your primary edge device for your network, or be deployed in-line with existing network gear.

+

You also need to purchase a Magic WAN Connector before you can start configuring your settings in the Cloudflare dashboard. After buying a Magic WAN Connector, the device will be registered with your Cloudflare account and show up in your Cloudflare dashboard.

+

Contact your account representative to learn more about purchasing options for the Magic WAN Connector device.

+ + ) +} + +{ props.magicWord === "virtual" && ( + <> +

Before you can install Virtual Connector, you need an Enterprise account with Magic WAN enabled. Additionally, you need to have a VMware host with sufficient compute, memory, and storage to run the virtual machine with Virtual Connector. This includes:

+
    +
  • Intel x86 CPU architecture
    • +
  • ESXi hypervisor 7.0U1 or higher
    • +
  • 4 virtual CPUs per virtual connector (We recommend deployment with a 1:1 virtual CPU to physical core allocation to avoid CPU over contention which will cause packet loss.)
    • +
  • 8 GB of RAM per virtual connector
    • +
  • 8 GB of disk per virtual connector
    • +
  • One vSwitch port group or VLAN with access to the Internet (for example, through a WAN)
    • +
  • One or more vSwitch port group or VLAN that will be the internal LAN
    • +
+

Refer to VMware's documentation for more information on how to install ESXi and configure a virtual machine.

+ + ) +} + +--- + +## Before you begin + +You can install up to two {props.productName}s for redundancy at each of your sites. If one of your Connectors fail, traffic will fail over to the other Connector ensuring that you never lose connectivity to that site. + +In this type of high availability (HA) configuration, you will choose a reliable LAN interface as the HA link which will be used to monitor the health of the peer connector. HA links can be dedicated links or can be shared with other LAN traffic. + +You must decide the type of configuration you want for your site from the beginning: no redundancy or with redundancy. You cannot add redundancy after finishing configuring your dashboard settings. If, at a later stage, you decide to enable redundancy, you will need to delete your Connector on-ramp in the Cloudflare dashboard, and start again. + + + +- If you need a high availability configuration for your premises, refer to + [About high availability configurations](#about-high-availability-configurations) for more information + and learn how to configure your Connector in this mode. + +- If you do not need a high availability configuration for you premises, proceed to [Set up Cloudflare dashboard](#set-up-cloudflare-dashboard). + + + +:::caution +You cannot enable high availability for an existing Connector on-ramp. To add high availability to an existing Connector on-ramp in the Cloudflare dashboard, you need to delete the on-ramp and start again. Plan accordingly to create a high availability configuration from the start if needed. +::: + +--- + +## DHCP vs static IP connections + +{props.productName} uses a DHCP connection at first boot to download your settings and go through the activation process. However, if you need to use a static IP in your {props.productName}, and this is a fresh install: +1. Connect {props.productNameType} to a DHCP port with access to the Internet. +2. Go through the [setup flow](#set-up-cloudflare-dashboard) below and activate your Connector. +3. Refer to [WAN with a static IP address](#wan-with-a-static-ip-address). + +--- + +{ props.magicWord === "hardware" && ( + <> + +

The hardware version of the Magic WAN connector includes two SFP+ ports that support 10G throughput, as well as six RJ45 ports that support 1G throughput.

+

Refer to SFP+ port information for details on this topic.

+ + ) +} + +{ props.magicWord === "virtual" && ( + <> + + +

Contact your account team at Cloudflare to obtain the Virtual Connector OVA package and license keys. The OVA image includes the files required to install and configure the virtual machine (VM) for Virtual Connector with the appropriate settings.

+

This image can be deployed multiple times to create several instances of a Virtual Connector, in different locations or on the same ESXi host.

+

You will consume one license key for each instance created. For example, if you want to deploy 10 Virtual Connectors you should request 10 license keys, and your account team will create 10 Connector instances in your Cloudflare dashboard.

+ + + +

The following instructions assume you already have VMware ESXi hypervisor installed with sufficient resources. Refer to Prerequisites for more information.

+
    + +
  1. When setting up your VMware ESXi, you need to create port groups for Virtual Connector. Go to Networking {'>'} Port groups, and prepare your vSwitch port groups and/or VLANs for your desired network topology. For example, a simple deployment typically has: +
      +
    • A WAN port group where the Virtual Connector will get an IP address (static or DHCP) that has access to the Internet.
      • +
    • A LAN port group, where the Virtual Connector will act as default router, and possibly DHCP server.
      • +
    • A null, or unused, port group for allocating unused virtual interfaces in the Virtual Connector. You can, for example, create a null port group with the name of Null port group, and a VLAN ID of 999.
      • +
    + +
    2. + +
  2. Extract the files in the OVA image provided by your Cloudflare account team. For example: + + + + Take note of the folder where you are extracting the files to, as you will need to refer to that folder when creating the VM. +
    3. + +
  3. Go to Virtual Machines {`>`} Create/Register VM wizard to start deploying the Virtual Connector.
    4. + +
  4. Select Deploy a virtual machine from an OVF or OVA file {`>`} Next.
    5. + +
  5. Choose a descriptive name for your virtual machine.
    6. + +
  6. Upload the files you have extracted from the OVA image. These include mconn.ovf, mconn.nvram, and mconn.vmdk.
    7. + +
  7. Select where you want to save the files extracted from the OVA image {`>`} Next.
    8. + +
  8. In Networking mappings, select assignments for your desired topology according to the port groups you set up previously:
    9. +
      +
    1. For example, map eno1 port to VM Network to create your WAN, and eno2 to LAN0 to act as your LAN port.
      2. +
    2. Allocate any unused ports to the null port group.
      3. +
    3. Take note of your configuration. You will need this information to configure your network in the Cloudflare dashboard.
      4. +
    + +
  9. In Disk provisioning, select Thin.
    10. + +
  10. Before completing the deployment wizard, disable Power on automatically. This is important so that you can configure the license key prior to boot.
    11. + +
  11. Configure the virtual machine with the license key your account team provided you:
    12. +
      +
    1. Select the Virtual Connector's VM {`>`} Settings.
      2. + +
    2. Go to VM Options {`>`} Advanced {`>`} Edit Configuration.
      3. + +
    3. Select Add parameter to add your license key. Scroll down to the last entry (this is where VMware adds the new parameter), and add the following two new entries:
      4. +
        +
      • Key: guestinfo.cloudflare.identity
        • +
      • Value: {``}
        • +
      +
    + + +
  12. Select Save to finish configuring your Virtual Connector.
    13. + +
  13. Continue setup in your Cloudflare dashboard.
    14. +
+ + + ) +} + +--- + +## Set up Cloudflare dashboard + +### 1. Add a Connector on-ramp + +You need to add your Connector to your Cloudflare dashboard and configure its settings before connecting it to the Internet. + +To add a Connector on-ramp: + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. +2. Go to **Magic WAN** > **Connector on-ramps (beta)**. +3. Select **Add**. +4. In **Name**, enter a descriptive name for your Connector. Optionally, you can also add a description for it. +5. You need to decide if you want to turn on high availability for the Connector. Refer to [About high availability configurations](#about-high-availability-configurations) for more information. +6. Select **Create and continue**. +7. Select **Add Connector**. This will show you a list of Magic WAN Connector devices associated with your account. +8. If you have more than one Connector, choose the one that corresponds to the on-ramp you are creating. Connectors are identified by a serial number, also known as a service tag. Use this information to choose the right Connector. Select **Select Connector** when you are ready to proceed. +9. The Connector will be added to your account with an **Interrupt window** defined. The interrupt window is the time period when the Magic WAN Connector software can update, which may result in interruption to existing connections. You can change this later. 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. +10. Select **Continue** to proceed to creating your WAN and LAN networks. + +### 2. Create a WAN + + + +1. In **WAN configuration**, select **Create**. You can create one or more [wide area networks (WANs)](https://www.cloudflare.com/learning/network-layer/what-is-a-wan/). Configuring multiple WANs will create multiple IPsec tunnels (one IPsec tunnel per WAN port). This allows the Connector to failover between circuits according to their health. +2. In **Interface name**, enter a descriptive name for your WAN. +3. **Interface number** +4. In **VLAN ID**, enter a number between `0` and `4094` to specify a [VLAN ID](/magic-wan/configuration/connector/reference/#vlan-id). +5. In **Priority**, choose the priority for your WAN. Lower numbers have higher priority. Refer to Traffic steering to learn more about how Cloudflare calculates priorities. +6. In **Health check rate** configure the health check frequency for your site. Options are `low`, `mid`, and `high`. Refer to [Update tunnel health checks frequency](/magic-wan/configuration/common-settings/tunnel-health-checks/) for more information. +7. **Addressing**: Select **DHCP**. This is needed the first time you set up your Connector to successfully download all settings to the machine and activate it. If you need a static IP address in your network environment: + 1. Continue the set up flow below to activate your Connector. + 2. Refer to [WAN with a static IP address](#wan-with-a-static-ip-address). If you choose a static IP, you also need to specify the static IP and gateway addresses. + +
+ +![An example of how to configure you Magic WAN Connector WAN](~/assets/images/magic-wan/connector/wan-config.png) + +
+ +8. Select **Save** when you are finished. + + + + + +Make a `POST` request [using the API](/api/resources/magic_transit/subresources/sites/subresources/wans/methods/create/) to create a WAN. + +The `static_addressing` object is optional. Omit it if you are using DHCP. If you are using static addressing, add the `secondary_address` parameter when your site is in high availability (HA) mode. + +Example: + +```bash +curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/wans \ +--header "X-Auth-Email: " \ +--header "X-Auth-Key: " \ +--header "Content-Type: application/json" \ +--data '{ + "name": "", + "physport": 1, + "priority": 0, + "vlan_tag": 0 +}' +``` + + + +### 3. Create a LAN + + + +1. In **LAN configuration**, select **Create**. +2. Enter a descriptive name for your LAN in **Interface name**. +3. **Interface number** +4. In **VLAN ID**, specify a [VLAN ID](/magic-wan/configuration/connector/reference/#vlan-id) to create virtual LANs. +5. In **Static addressing** > **Static address** give your Connector's LAN interface its IP address. You can also enable the following options if they suit your use case: + - **This is a DHCP server**: If your Connector is a [DHCP server](/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/). + - **This is a DHCP relay**: If your Connector is a [DHCP relay](/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay/). +6. (Optional) In **Directly attached subnet** > **Static NAT prefix**, enter a CIDR prefix to enable NAT (network address translation). The prefix you enter here should be the same size as the prefix entered in **Static addressing**. For example, both networks have a subnet mask of `/24`: `192.168.100.0/24` and `10.10.100.0/24`. +7. (Optional) If your LAN contains additional subnets behind a layer 3 router, select **Add routed subnet** under **Routed subnets** to add them: + - **Prefix**: The CIDR prefix for the subnet behind the L3 router. + - **Next hop**: The address of the L3 router to which the Connector should forward packets for this subnet. + - **Static NAT prefix**: Optional setting. If you want to enable NAT for a routed subnet, supply an "external" prefix for the overlay-facing side of the NAT to use. It must be the same size as **Prefix**.
Refer to [Routed subnets](/magic-wan/configuration/connector/network-options/routed-subnets/) for more information. +8. Select **Save**. +9. Select **Done** to finish your configuration. Tunnels and static routes will be automatically created for your Magic WAN Connector, once it boots up. + + + + + +Make a `POST` request [using the API](/api/resources/magic_transit/subresources/sites/subresources/lans/methods/create/) to create a LAN. + +Example: + +```bash +curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/lans \ +--header "X-Auth-Email: " \ +--header "X-Auth-Key: " \ +--header "Content-Type: application/json" \ +--data '{ + "name": "", + "physport": 2, + "static_addressing": { + "address": "172.16.14.0/24" + }, + "vlan_tag": 0 +}' +``` + + + +#### Network segmentation + +After setting up your LANs, you can configure your Connector to enable communication between them without traffic leaving your premises. Refer to [Network segmentation](/magic-wan/configuration/connector/network-options/network-segmentation/) for more information. + +#### DHCP options + +Magic WAN Connector supports different types of DHCP configurations. Connector can: + +- Connect to a DHCP server or use a static IP address instead of connecting to a DHCP server. +- Act as a [DHCP server](/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/). +- Use [DHCP relay](/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay/) to connect to a DHCP server outside the location your Magic WAN Connector is in. +- [Reserve IP addresses](/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation/) for specific devices on your network. + +Refer to [DHCP options](/magic-wan/configuration/connector/network-options/dhcp/) to learn more. + +### 4. Add your Connector to a site + +After finishing your Connector configuration, you need to add it to a site. + +{ props.magicWord === "hardware" && ( + <> + + + +

There are several deployment options for Magic WAN Connector. Connector can act like a DHCP server for your local network, or integrate with your local setup and have static IP addresses assigned to it.

+

When Connector acts like the WAN router for your site, deployment will be something like this:

+ + 
+		{`flowchart LR
+		accTitle: Magic WAN Connector set up as a DHCP server, and connecting to the Internet.
+    a(Magic WAN Connector)--> b(Internet) --> c(Cloudflare)
+
+    subgraph Customer site
+    d[LAN 1] --> a
+    e[LAN 2] --> a
+    end
+
+    classDef orange fill:#f48120,color: black
+    class a,c orange`}
+
+ +

In the example below, the Connector sits behind the WAN router in your site, and on-ramps only some of the existing LANs to Cloudflare.

+ + 
+		{`flowchart LR
+		accTitle: Magic WAN Connector connects to the router in the site, and only some of the LANs connect to Connector.
+    a(Magic WAN Connector)--> b((Site's router)) --> c(Internet) --> i(Cloudflare)
+
+    subgraph Customer site
+    d[LAN 1] --> a
+    e[LAN 2] --> a
+    g(LAN 3) --> b
+    h(LAN 4) --> b
+    end
+
+    classDef orange fill:#f48120,color: black
+    class a,i orange`}
+
+ +

Refer to Magic WAN Connector deployment options for a high-level explanation of the deployment options that make sense to most environments, as well as a few advanced use cases.

+ + +

If there is a firewall deployed upstream of the Magic WAN Connector, configure the firewall to allow the following traffic:

+ + + + + ) +} + +## Activate Connector + +{props.shippedLanguage}, and will only establish a connection to the Cloudflare network when it is activated. Cloudflare recommends leaving it deactivated until you finish [setting it up in the dashboard](#1-add-a-connector-on-ramp). + +When the Connector is first activated, one of the ports must be connected to the Internet through a device that supports DHCP. This is required so that the Connector can reach the Cloudflare global network and download the required configurations that you [set up](#1-add-a-connector-on-ramp). + +:::caution +Remember to connect Magic WAN Connector through a route that supports DHCP for its first connection to the Internet. Otherwise, the Connector will not work. +::: + +When you are ready to connect your Magic WAN Connector to the Cloudflare network: + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. +2. Go to **Magic WAN** > **Configuration** > **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. +6. Select **Update**. + +{ props.magicWord === "virtual" && ( + <> + +
    +
  1. Go to Virtual Machines in VMware, and boot up Virtual Connector's VM.
    2. +
  2. The Virtual Connector will make a request to Cloudflare. This is the step where Virtual Connector registers your provided license key and downloads the configuration you provided.
    3. +
  3. The Virtual Connector will set up the LAN and WAN connections according to the configuration downloaded from the site you created on the Cloudflare dashboard. The Virtual Connector will also establish IPsec tunnels.
    4. +
  4. If successful, the tunnel health checks will show as healthy.
    5. +
  5. If you do not see a healthy heartbeat on the Cloudflare dashboard, reboot the Virtual Connector's VM in VMware.
    6. +
+ + ) +} + +--- + +## WAN with a static IP address + +{ props.magicWord === "hardware" && ( + <> +

After activating your Connector, you can use it in a network configuration with the WAN interface set to a static IP address — that is, an Internet configuration that is not automatically set by DHCP. To use your Connector on a network configuration with a static IP, follow the steps below.

+ + + +
    +
  1. Connect Magic WAN Connector to a DHCP port with access to the Internet.
    2. +
  2. Add a Connector on-ramp in the Cloudflare dashboard.
    3. +
  3. Create a DHCP WAN.
    4. +
  4. Activate and power on your Connector.
    5. +
  5. Wait 60 seconds.
    6. +
  6. Make changes to the WAN settings in the Cloudflare dashboard to a static IP set up.
    7. +
  7. Wait 60 seconds again.
    8. +
  8. Magic WAN Connector will go offline. This is normal and expected behavior.
    9. +
  9. Adjust your physical connections as required to match the static configuration.
    10. +
  10. Magic WAN Connector comes back online.
    11. +
+ + ) +} + +{ props.magicWord === "virtual" && ( + <> +

After activating your Virtual Connector, you can use it in a network configuration with the WAN interface set to a static IP address - that is, an Internet configuration that is not automatically set by DHCP. To use your Virtual Connector on a network configuration with a static IP, follow the steps below.

+ + +
    +
  1. Connect the machine where you installed the VM with Virtual Connector to a DHCP port with access to the Internet.
    2. +
  2. Add a Connector on-ramp in the Cloudflare dashboard.
    3. +
  3. Create a DHCP WAN.
    4. +
  4. Activate and boot your Virtual Connector.
    5. +
  5. Wait 60 seconds.
    6. +
  6. Make changes to the WAN settings in the Cloudflare dashboard to a static IP set up.
    7. +
  7. Wait 60 seconds again.
    8. +
  8. Modify your Port Groups as needed to change the source from which the WAN port obtains its IP address.
    9. +
  9. Reboot your virtual machine.
    10. +
+ + ) +} + +--- + +## About high availability configurations + +{props.hardSoftConn} When you set up a site in high availability, the WANs and LANs in your Connectors have the same configuration but are replicated on two nodes. In case of failure of a Connector, the other Connector becomes the active node, taking over configuration of the LAN gateway IP and allowing traffic to continue without disruption. + +Because Connectors in high availability configurations share a single site, you need to set up: + +- **Static address**: The IP for the primary node in your site. +- **Secondary static address**: The IP for the secondary node in your site. +- **Virtual static address**: The IP that the LAN south of the Connector will forward traffic to, which is the LAN's gateway IP. + +Make sure all IPs are part of the same subnet. + +For detailed information about the expected behavior of high availability configurations, refer to [High availability configurations](/magic-wan/configuration/connector/reference/#high-availability-configurations). + +### Create a high availability configuration + +You cannot enable high availability for an existing site. To add high availability to an existing site in the Cloudflare dashboard, you need to delete the site and start again. + +To set up a high availability configuration: + +1. Follow the steps in [Add a Connector on-ramp](#1-add-a-connector-on-ramp) up until step 4. +2. After naming your site, select **Turn on high availability**. +3. Select **Create and continue**. +4. Select **Add Connector**. +5. From the list, choose your first Connector > **Add Connector**. +6. Back on the previous screen, select **Add secondary Connector**. +7. From the list, choose your second Connector > **Add Connector**. +8. Select **Continue** to [Create a WAN](#2-create-a-wan). If you are configuring a static IP, configure the IP for the primary node as the static address, and the IP for the secondary node as the secondary static address. +9. To create a LAN, follow the steps mentioned above in [Create a LAN](#3-create-a-lan) up until step 4. +10. In **Static address**, enter the IP for the primary node in your site. For example, `192.168.10.1/24`. +11. In **Secondary static address**, enter the IP for the secondary node in your site. For example, `192.168.10.2/24`. +12. In **Virtual static address**, enter the IP that the LAN south of the Connector will forward traffic to. For example, `192.168.10.3/24`. +13. Select **Save**. +14. From the **High availability probing link** drop-down menu, select the port that should be used to monitor the node's health. Cloudflare recommends you choose a reliable interface as the HA probing link. The primary and secondary node's probing link should be connected over a switch, and cannot be a direct connection. +15. + +--- + +## IPsec tunnels and static routes + +Magic WAN Connector automatically creates [IPsec tunnels](/magic-wan/reference/tunnels/#ipsec-tunnels) and [static routes](/magic-wan/reference/traffic-steering/) for you. You cannot configure these manually. + +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. + +--- + +## Next steps + +- [Network options](/magic-wan/configuration/connector/network-options/) +- [Maintenance](/magic-wan/configuration/connector/maintenance/) +- [Reference information](/magic-wan/configuration/connector/reference/) +- [Troubleshooting](/magic-wan/configuration/connector/troubleshooting/) diff --git a/src/content/partials/magic-wan/connector/connector-onramps.mdx b/src/content/partials/magic-wan/connector/connector-onramps.mdx deleted file mode 100644 index a1b6be73657285..00000000000000 --- a/src/content/partials/magic-wan/connector/connector-onramps.mdx +++ /dev/null @@ -1,135 +0,0 @@ ---- -params: - - wan - - lan - - noConnectorShows ---- - -import { GlossaryTooltip, Markdown, Render, TabItem, Tabs } from "~/components"; - -### 1. Add a Connector on-ramp - -You need to add your Connector to your Cloudflare dashboard and configure its settings before connecting it to the Internet. - -To add a Connector on-ramp: - -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. -2. Go to **Magic WAN** > **Connector on-ramps (beta)**. -3. Select **Add**. -4. In **Name**, enter a descriptive name for your Connector. Optionally, you can also add a description for it. -5. You need to decide if you want to turn on high availability for the Connector. Refer to [About high availability configurations](#about-high-availability-configurations) for more information. -6. Select **Create and continue**. -7. Select **Add Connector**. This will show you a list of Magic WAN Connector devices associated with your account. -8. If you have more than one Connector, choose the one that corresponds to the on-ramp you are creating. Connectors are identified by a serial number, also known as a service tag. Use this information to choose the right Connector. Select **Select Connector** when you are ready to proceed. -9. The Connector will be added to your account with an **Interrupt window** defined. The interrupt window is the time period when the Magic WAN Connector software can update, which may result in interruption to existing connections. You can change this later. 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. -10. Select **Continue** to proceed to creating your WAN and LAN networks. - -### 2. Create a WAN - - - -1. In **WAN configuration**, select **Create**. You can create one or more [wide area networks (WANs)](https://www.cloudflare.com/learning/network-layer/what-is-a-wan/). Configuring multiple WANs will create multiple IPsec tunnels (one IPsec tunnel per WAN port). This allows the Connector to failover between circuits according to their health. -2. In **Interface name**, enter a descriptive name for your WAN. -3. **Interface number** -4. In **VLAN ID**, enter a number between `0` and `4094` to specify a [VLAN ID](/magic-wan/configuration/connector/reference/#vlan-id). -5. In **Priority**, choose the priority for your WAN. Lower numbers have higher priority. Refer to Traffic steering to learn more about how Cloudflare calculates priorities. -6. In **Health check rate** configure the health check frequency for your site. Options are `low`, `mid`, and `high`. Refer to [Update tunnel health checks frequency](/magic-wan/configuration/common-settings/tunnel-health-checks/) for more information. -7. **Addressing**: Select **DHCP**. This is needed the first time you set up your Connector to successfully download all settings to the machine and activate it. If you need a static IP address in your network environment: - 1. Continue the set up flow below to activate your Connector. - 2. Refer to [WAN with a static IP address](#wan-with-a-static-ip-address). If you choose a static IP, you also need to specify the static IP and gateway addresses. - -
- -![An example of how to configure you Magic WAN Connector WAN](~/assets/images/magic-wan/connector/wan-config.png) - -
- -8. Select **Save** when you are finished. - - - - - -Create a `POST` request [using the API](/api/resources/magic_transit/subresources/sites/subresources/wans/methods/create/) to create a WAN. - -The `static_addressing` object is optional. Omit it if you are using DHCP. If you are using static addressing, add the `secondary_address` parameter when your site is in high availability (HA) mode. - -Example: - -```bash -curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/wans \ ---header "X-Auth-Email: " \ ---header "X-Auth-Key: " \ ---header "Content-Type: application/json" \ ---data '{ - "name": "", - "physport": 1, - "priority": 0, - "vlan_tag": 0 -}' -``` - - - -### 3. Create a LAN - - - -1. In **LAN configuration**, select **Create**. -2. Enter a descriptive name for your LAN in **Interface name**. -3. **Interface number** -4. In **VLAN ID**, specify a [VLAN ID](/magic-wan/configuration/connector/reference/#vlan-id) to create virtual LANs. -5. In **Static addressing** > **Static address** give your Connector's LAN interface its IP address. You can also enable the following options if they suit your use case: - - **This is a DHCP server**: If your Connector is a [DHCP server](/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/). - - **This is a DHCP relay**: If your Connector is a [DHCP relay](/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay/). -6. (Optional) In **Directly attached subnet** > **Static NAT prefix**, enter a CIDR prefix to enable NAT (network address translation). The prefix you enter here should be the same size as the prefix entered in **Static addressing**. For example, both networks have a subnet mask of `/24`: `192.168.100.0/24` and `10.10.100.0/24`. -7. (Optional) If your LAN contains additional subnets behind a layer 3 router, select **Add routed subnet** under **Routed subnets** to add them: - - **Prefix**: The CIDR prefix for the subnet behind the L3 router. - - **Next hop**: The address of the L3 router to which the Connector should forward packets for this subnet. - - **Static NAT prefix**: Optional setting. If you want to enable NAT for a routed subnet, supply an "external" prefix for the overlay-facing side of the NAT to use. It must be the same size as **Prefix**.
Refer to [Routed subnets](/magic-wan/configuration/connector/network-options/routed-subnets/) for more information. -8. Select **Save**. -9. Select **Done** to finish your configuration. Tunnels and static routes will be automatically created for your Magic WAN Connector, once it boots up. - - - - - -Create a `POST` request [using the API](/api/resources/magic_transit/subresources/sites/subresources/lans/methods/create/) to create a LAN. - -Example: - -```bash -curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/lans \ ---header "X-Auth-Email: " \ ---header "X-Auth-Key: " \ ---header "Content-Type: application/json" \ ---data '{ - "name": "", - "physport": 2, - "static_addressing": { - "address": "172.16.14.0/24" - }, - "vlan_tag": 0 -}' -``` - - - -#### Network segmentation - -After setting up your LANs, you can configure your Connector to enable communication between them without traffic leaving your premises. Refer to [Network segmentation](/magic-wan/configuration/connector/network-options/network-segmentation/) for more information. - -#### DHCP options - -Magic WAN Connector supports different types of DHCP configurations. Connector can: - -- Connect to a DHCP server or use a static IP address instead of connecting to a DHCP server. -- Act as a [DHCP server](/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/). -- Use [DHCP relay](/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay/) to connect to a DHCP server outside the location your Magic WAN Connector is in. -- [Reserve IP addresses](/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation/) for specific devices on your network. - -Refer to [DHCP options](/magic-wan/configuration/connector/network-options/dhcp/) to learn more. - -### 4. Add your Connector to a site - -After finishing your Connector configuration, you need to add it to a site. \ No newline at end of file diff --git a/src/content/partials/magic-wan/connector/ha-configs.mdx b/src/content/partials/magic-wan/connector/ha-configs.mdx deleted file mode 100644 index 4cd0732d688878..00000000000000 --- a/src/content/partials/magic-wan/connector/ha-configs.mdx +++ /dev/null @@ -1,43 +0,0 @@ ---- -params: - - finalInstructions - - hardSoftConn ---- - -import { Markdown } from "~/components"; - -## About high availability configurations - -{props.hardSoftConn} When you set up a site in high availability, the WANs and LANs in your Connectors have the same configuration but are replicated on two nodes. In case of failure of a Connector, the other Connector becomes the active node, taking over configuration of the LAN gateway IP and allowing traffic to continue without disruption. - -Because Connectors in high availability configurations share a single site, you need to set up: - -- **Static address**: The IP for the primary node in your site. -- **Secondary static address**: The IP for the secondary node in your site. -- **Virtual static address**: The IP that the LAN south of the Connector will forward traffic to, which is the LAN's gateway IP. - -Make sure all IPs are part of the same subnet. - -For detailed information about the expected behavior of high availability configurations, refer to [High availability configurations](/magic-wan/configuration/connector/reference/#high-availability-configurations). - -### Create a high availability configuration - -You cannot enable high availability for an existing site. To add high availability to an existing site in the Cloudflare dashboard, you need to delete the site and start again. - -To set up a high availability configuration: - -1. Follow the steps in [Add a Connector on-ramp](#1-add-a-connector-on-ramp) up until step 4. -2. After naming your site, select **Turn on high availability**. -3. Select **Create and continue**. -4. Select **Add Connector**. -5. From the list, choose your first Connector > **Add Connector**. -6. Back on the previous screen, select **Add secondary Connector**. -7. From the list, choose your second Connector > **Add Connector**. -8. Select **Continue** to [Create a WAN](#2-create-a-wan). If you are configuring a static IP, configure the IP for the primary node as the static address, and the IP for the secondary node as the secondary static address. -9. To create a LAN, follow the steps mentioned above in [Create a LAN](#3-create-a-lan) up until step 4. -10. In **Static address**, enter the IP for the primary node in your site. For example, `192.168.10.1/24`. -11. In **Secondary static address**, enter the IP for the secondary node in your site. For example, `192.168.10.2/24`. -12. In **Virtual static address**, enter the IP that the LAN south of the Connector will forward traffic to. For example, `192.168.10.3/24`. -13. Select **Save**. -14. From the **High availability probing link** drop-down menu, select the port that should be used to monitor the node's health. Cloudflare recommends you choose a reliable interface as the HA probing link. The primary and secondary node's probing link should be connected over a switch, and cannot be a direct connection. -15. diff --git a/src/content/partials/magic-wan/connector/ipsec-static-tunnels.mdx b/src/content/partials/magic-wan/connector/ipsec-static-tunnels.mdx deleted file mode 100644 index 99ecb8f793e0a7..00000000000000 --- a/src/content/partials/magic-wan/connector/ipsec-static-tunnels.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -{} - ---- - -Magic WAN Connector automatically creates [IPsec tunnels](/magic-wan/reference/tunnels/#ipsec-tunnels) and [static routes](/magic-wan/reference/traffic-steering/) for you. You cannot configure these manually. - -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. diff --git a/src/content/partials/magic-wan/connector/next-steps.mdx b/src/content/partials/magic-wan/connector/next-steps.mdx deleted file mode 100644 index 2457c22868f793..00000000000000 --- a/src/content/partials/magic-wan/connector/next-steps.mdx +++ /dev/null @@ -1,9 +0,0 @@ ---- -{} - ---- - -- [Network options](/magic-wan/configuration/connector/network-options/) -- [Maintenance](/magic-wan/configuration/connector/maintenance/) -- [Reference information](/magic-wan/configuration/connector/reference/) -- [Troubleshooting](/magic-wan/configuration/connector/troubleshooting/)