cloudflare · marciocloudflare · Oct 15, 2025 · Oct 10, 2025 · Oct 10, 2025 · Oct 10, 2025
@@ -18,6 +18,7 @@ import { Render } from "~/components";
 		analyticsAnchorHeading: "#magic-transit-network-analytics",
 		networkAnalyticsURL: "/magic-transit/analytics/network-analytics/",
 		traceRoutes: "/magic-transit/analytics/traceroutes/",
-		graphQl: "/magic-transit/"
+		graphQlTunnelBandwidthURL: "/magic-transit/analytics/query-bandwidth/",
+		graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/"
 		 }}
 />
@@ -27,4 +27,4 @@ Refer to [Network Analytics](/analytics/network-analytics/) documentation to lea
 
 ## Access Magic Tunnel traffic analytics
 
-<Render file="analytics/network-analytics" product="networking-services" />
+<Render file="analytics/magic-tunnel-traffic-analytics" product="networking-services" />
@@ -18,6 +18,12 @@ import { Render } from "~/components";
 	params={{
   	magicWord: "Magic Transit",
   	productName: "Magic Transit",
+		mFirewallName: "Magic Firewall",
+		mFirewallURL: "/magic-firewall/",
+		warpClientURL: "/cloudflare-one/connections/connect-devices/warp/",
+		remoteBrowserURL: "/cloudflare-one/policies/browser-isolation/",
+		accessURL: "/cloudflare-one/policies/access/",
+		gatewayURL: "/cloudflare-one/policies/gateway/",
   	greIpsecReferenceURL: "/magic-transit/reference/gre-ipsec-tunnels/",
   	createStaticRoute: "/magic-transit/how-to/configure-routes/#create-a-static-route",
   	editStaticRoute: "/magic-transit/how-to/configure-routes/#edit-a-static-route",

@@ -19,6 +19,7 @@ import { Render } from "~/components";
 		analyticsAnchorHeading: "#magic-wan-network-analytics",
 		networkAnalyticsURL: "/magic-wan/analytics/network-analytics/",
 		traceRoutes: "/magic-wan/analytics/traceroutes/",
-		graphQl: "/magic-wan/"
+		graphQlTunnelBandwidthURL: "/magic-wan/analytics/query-bandwidth/",
+		graphQlTunnelHealthURL: "/magic-wan/analytics/query-tunnel-health/"
 		 }}
 />
@@ -6,25 +6,14 @@ sidebar:
 head:
   - tag: title
     content: Magic WAN Network Analytics
-
 ---
 
-import { GlossaryTooltip, Render } from "~/components"
-
-Magic WAN customers can view their real-time and historical network data in Network Analytics. Customers can see their network data in a time series that shows Magic WAN traffic (in <GlossaryTooltip term="data packet">packets</GlossaryTooltip> or bytes) over time, and can filter the time series data by different types of [packet](https://www.cloudflare.com/learning/network-layer/what-is-a-packet/) characteristics.
-
-<Render file="analytics/network-analytics-data-averages" product="networking-services" />
+import { Render } from "~/components";
 
-Refer to [Network Analytics](/analytics/network-analytics/) documentation to learn more.
-
-## Network traffic data filters
-
-<Render
-	file="analytics/network-traffic-filters"
+<Render file="magic-wan/analytics/network-analytics"
 	product="networking-services"
-	params={{ magicProduct: "Magic WAN" }}
-/>
-
-## Access Magic Tunnel traffic analytics
+	params={{
+		productName: "Magic WAN"
 
-<Render file="analytics/network-analytics" product="networking-services" />
+		 }}
+/>
@@ -15,10 +15,13 @@ import { Render } from "~/components"
 	file="analytics/site-analytics"
 	product="networking-services"
 	params={{
-		instructions: "Refer to [Set up a site](/magic-wan/configuration/common-settings/sites/) for more information on how to set up a site."
+		instructions: "Refer to [Set up a site](/magic-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
+		productName: "Magic WAN",
+		magicTunnelHcsURL: "/magic-wan/configuration/common-settings/configure-magic-tunnel-health-alerts/",
+		setGeoCoordinatesURL: "/magic-wan/configuration/common-settings/sites/#set-geographic-coordinates"
 		}}
 />
 
-### Set thresholds for Magic WAN site health
+### Set thresholds for site health
 
 <Render file="analytics/set-thresholds-site-health"	product="networking-services" />
@@ -32,6 +32,11 @@ import { Render } from "~/components";
 
 ## Magic WAN Connector
 
-Magic WAN Connector also includes a heartbeat function, an additional way of communicating its health status which does not depend on successfully setting up any tunnels. The heartbeat function communicates periodically with Cloudflare via HTTPS and lets Cloudflare know that the Connector in question is connected to the Internet and reachable.
-
-Refer to [Heartbeat](/magic-wan/configuration/connector/maintenance/heartbeat/) to learn more.
+<Render
+	file="tunnel-health/mconn-heartbeat-health"
+	product="networking-services"
+	params={{
+		productName: "Magic WAN Connector",
+		heartbeatURL: "/magic-wan/configuration/connector/maintenance/heartbeat/"
+	}}
+/>
@@ -5,23 +5,12 @@ sidebar:
   order: 6
 ---
 
-import { CURL } from "~/components";
+import { Render } from "~/components";
 
-Magic WAN customers can configure a custom IKE ID for their IPsec tunnels. Customers that are using Magic WAN and a VeloCloud SD-WAN device together should utilize this option to create a high availability configuration.
-
-:::note
-This feature is only available via API. There are no configuration options for a custom IKE ID for an IPsec tunnel in the Cloudflare dashboard.
-:::
-
-VeloCloud has a high availability mechanism that allows customers to specify one set of IKE parameters (like IKE ID) and multiple remote IPs. Customers create an IKE ID, and then assign the same custom IKE ID to their primary IPsec tunnel and their backup IPsec tunnel. FQDN is the only supported type for custom IKE IDs.
-
-Magic WAN customers can set a custom IKE ID for an IPsec tunnel using the following API call. Customers will need to fill in the appropriate values for `<account_id>`, `<tunnel_id>`, and the FQDN wildcard before running the API call.
-
-<CURL
-  url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
-  method="PATCH"
-  json={{
-    "custom_remote_identities":
-			{"fqdn_id": "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com"}
-  }}
-/>
+<Render
+	file="magic-wan/custom-ike-id-ipsec"
+	product="networking-services"
+	params={{
+		productName: "Magic WAN",
+	}}
+/>
@@ -9,62 +9,12 @@ sidebar:
 
 import { Render } from "~/components";
 
-Sites represent the local network of a data center, office, or other physical location, and combine all on-ramps available there. Sites also allow you to check, at a glance, the state of your on-ramps and set up health alert settings so that you get notified when there are issues with the site's on-ramps.
-
-To use a site, start by setting up your on-ramps. These can be [GRE or IPsec tunnels](/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/), a [Magic WAN Connector](/magic-wan/configuration/connector/), or a direct [CNI link](/magic-wan/network-interconnect/). When you are finished setting these up, refer to the steps below to learn how to set up a site.
-
-## Add a site
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **Magic WAN** > **Network overview (beta)**.
-3. Select **Add site**.
-4. Add a name and description for your new site. Optionally, you can also add the geographical coordinates for your site in **Latitude** and **Longitude**. If you add geographical coordinates, once created your site's location will show in the map.
-5. Select **Create and continue**.
-6. Choose one or more on-ramps for your site from the list. Remember to only choose the on-ramps available to that particular site, as the list might show on-ramps available on other locations.
-7. Select **Continue**.
-8. In **Define alert settings** you set up alerts to notify you when there are issues with your site's on-ramps. If you want to set up alerts later, select **Skip this for now** to complete your setup. Otherwise, continue reading.
-9. In **Magic WAN Health Check Alert** > **Notification name**, enter a name for the site's alert.
-10. Under **Alert settings**, choose how you want to be notified when there is an issue. You can add webhooks as well as email addresses.
-11. In **Alert sensitivity level** define the threshold for Magic Tunnel health alerts to be fired. Refer to [How Cloudflare calculates Magic Tunnel health alerts](/magic-wan/reference/how-cloudflare-calculates-magic-tunnel-health-alerts/) for more information.
-12. Select **Complete setup** to finish setting up your site.
-
-Your site is now set up. If you have other sites you need to set up, repeat the steps above. If you did not set up alerts, we strongly recommend that you do it. Otherwise you will not be notified when there is a problem with one of your on-ramps.
-
----
-
-## Site analytics
-
-<Render
-	file="analytics/site-analytics"
-	product="networking-services"
-	params={{ instructions: "" }}
-/>
-
----
-
-## Edit a site
-
-### Add or remove on-ramps
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **Magic WAN** > **Network overview (beta)**.
-3. Find your site in **Traffic overview** > select the three dots in front of it > **Edit**.
-4. Select **On-ramps**.
-5. Select **Add** to add a new on-ramp.
-6. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
-
-### Set geographic coordinates
-
-If you add geographic coordinates to your site, it will show up in the Network map. To set up or edit geographic coordinates to an existing site:
-
-1. Go to **Magic WAN** > **Network overview (beta)**.
-2. Find your site in **Traffic overview** > select the three dots in front of it > **Edit**.
-3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates.
-4. Select **Save**.
-
-### Set thresholds for Magic WAN site health
-
 <Render
-	file="analytics/set-thresholds-site-health"
+	file="sites/sites"
 	product="networking-services"
-/>
+	params={{
+		greIpsecTunnelsURL: "/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/",
+		connectorURL: "/magic-wan/configuration/connector/",
+		cniURL: "/magic-wan/network-interconnect/"
+	}}
+	/>
@@ -13,10 +13,24 @@ import { Render } from "~/components";
 	params={{
 	magicWord: "hardware",
 	productName: "Magic WAN Connector",
+	maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
+	productOriginalName: "Magic WAN",
+	sfpURL: "/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/",
 	wan: "refers to the physical Magic WAN Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> 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 WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> 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.",
+	networkSegmentationURL: "/magic-wan/configuration/connector/network-options/network-segmentation/",
+	dhcpServerURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation/",
 	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."
+	hcConfigsURL: "/magic-wan/configuration/connector/reference/#high-availability-configurations",
+	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.",
+	ipsecTunnelsRefURL: "/magic-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	staticRoutesRefURL: "/magic-wan/reference/traffic-steering/",
+	networkOptionsURL: "/magic-wan/configuration/connector/network-options/",
+  maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
+  referenceInformationURL: "/magic-wan/configuration/connector/reference/",
+  troubleshootingURL: "/magic-wan/configuration/connector/troubleshooting/"
 	}} />
@@ -4,44 +4,11 @@ title: SFP+ port information
 
 ---
 
-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. These ports can be configured as either a WAN or a LAN port, like all of the 1G RJ45 ports in the machine. Because a 10G WAN uplink will often be bottlenecked by IPsec tunnel speeds, the SFP+ ports are most useful for configuring high speed LANs, and for using fiber connections.
-
-:::note[Virtual Connector and SFP+ ports]
-Since you decide and set up the hardware where Magic WAN Virtual Connector runs, you can ignore the information on this page.
-:::
-
-## Port configuration
-
-SFP+ ports are next to the regular LAN ports. They are represented as follows in the dashboard:
-
-- SFP+ **port 1** is represented by **port 7** in the dashboard
-- SFP+ **port 2** is represented by **port 8** in the dashboard
-
-![The left port, SFP+ 1, is port 7. The right port, SFP+ 2, is port 8.](~/assets/images/magic-wan/connector/sfp-ports.png)
-
-_The left port, SFP+ 1, is port 7. The right port, SFP+ 2, is port 8._
-
-## SFP+ module compatibility
-
-The Magic WAN Connector only supports 10Gbps SFP+ modules, including RJ45, DAC, and fiber, among others. Many 1 Gbps modules are incompatible with the Intel driver used internally, and thus are not supported.
-
-Cloudflare supports the following SFP+ inputs:
-
-- 10 Gbps Intel-compatible optics using 10GBase-SR, LR, ER. This includes Intel-compatible active optical cables (AOC) cables at 10 Gbps.
-- 10 Gbps DAC Twinax cables, compatible with SFF-8431 v4.1 and SFF-8472 v10.4
-- 10GBASE-T RJ45 converter modules
-
-Cloudflare successfully deployed commonly available 10G modules that are also compatible across many vendors:
-
-- StarTech Dell EMC Twinax SFP+ DAC
-- Ubiquiti multi-mode, duplex, 10 Gbps fiber transceiver modules
-
-Keep in mind that SFP+ modules/cables have to be compatible at both ends, that is, both sides of the connection should be 10 Gbps, and it should really be the same module/cable that is compatible with both hardware stacks. The choice of module/optic/cable ultimately depends on your specific interoperability needs, and it is much less of a "plug and play" situation as one expects from RJ45.
-
-## Recover from unsupported SFP+ inputs
-
-SFP+ modules should be installed and tested prior to deploying a Connector into production usage.
-
-An unsupported SFP+ input is indicated by the interface failing to come up (that is, the Connector has no status lights), and also by the port (7 or 8) going offline until the hardware is rebooted.
-
-When an unsupported module is plugged, the module should be removed and then the Connector rebooted by removing power for five seconds. The module should not remain plugged during reboot, or the Connector will have to be rebooted again after the module is removed.
+import { Render } from "~/components";
+
+<Render file="mconn/spf-port-info"
+	product="networking-services"
+	params={{
+	productName: "Magic WAN Connector",
+	productNameVirtual: "Virtual Connector",
+	}} />
@@ -12,11 +12,25 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 	magicWord: "virtual",
-	productName: "Virtual Connector",
+	productName: "Magic WAN Connector",
+	productNameVirtual: "Virtual Connector",
+	maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
+	productOriginalName: "Magic WAN",
 	wan: "needs to correspond to the virtual network interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
 	lan: "needs to correspond to the virtual LAN interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
 	noConnectorShows: "For a Virtual Connector to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Connector Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",
+	networkSegmentationURL: "/magic-wan/configuration/connector/network-options/network-segmentation/",
+	dhcpServerURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/",
+  dhcpRelayURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay/",
+  reserveIpAddressesURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation/",
 	shippedLanguage: "Virtual Magic WAN Connector is deactivated after you install it",
 	hardSoftConn: "You need to install two Virtual Connectors before you can set up a site in high availability.",
-	finalInstructions:  "Follow the instructions in [Activate Connector](#activate-connector) to finish setting up your Connectors."
+	hcConfigsURL: "/magic-wan/configuration/connector/reference/#high-availability-configurations",
+	finalInstructions:  "Follow the instructions in [Activate Connector](#activate-connector) to finish setting up your Connectors.",
+	ipsecTunnelsRefURL: "/magic-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
+	staticRoutesRefURL: "/magic-wan/reference/traffic-steering/",
+	networkOptionsURL: "/magic-wan/configuration/connector/network-options/",
+  maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
+  referenceInformationURL: "/magic-wan/configuration/connector/reference/",
+  troubleshootingURL: "/magic-wan/configuration/connector/troubleshooting/"
 	}} />
Original file line number	Diff line number	Diff line change
Expand Up		@@ -27,4 +27,4 @@ Refer to [Network Analytics](/analytics/network-analytics/) documentation to lea

		## Access Magic Tunnel traffic analytics

		<Render file="analytics/network-analytics" product="networking-services" />
		<Render file="analytics/magic-tunnel-traffic-analytics" product="networking-services" />