Skip to content
Merged
Show file tree
Hide file tree
Changes from 150 commits
Commits
Show all changes
152 commits
Select commit Hold shift + click to select a range
20271bb
added render
marciocloudflare Oct 10, 2025
d5ea50d
created get started partial
marciocloudflare Oct 10, 2025
3cb6dc9
added params
marciocloudflare Oct 10, 2025
2a6b191
removed explicit name
marciocloudflare Oct 10, 2025
eb2afce
added params
marciocloudflare Oct 10, 2025
07ae018
added params
marciocloudflare Oct 10, 2025
6be6caf
added vars
marciocloudflare Oct 10, 2025
7e9306a
added vars
marciocloudflare Oct 13, 2025
44ee420
added vars to virtual conn prereqs
marciocloudflare Oct 13, 2025
1268e0e
ternary render
marciocloudflare Oct 13, 2025
742e43c
added ternary
marciocloudflare Oct 13, 2025
67a8d6d
vars
marciocloudflare Oct 13, 2025
4fb33e3
added vars
marciocloudflare Oct 13, 2025
f007cb4
added vars
marciocloudflare Oct 13, 2025
f80000c
added vars
marciocloudflare Oct 13, 2025
eb25a64
ternary option
marciocloudflare Oct 13, 2025
00e6d17
removed vars
marciocloudflare Oct 13, 2025
e8e7337
added ternary
marciocloudflare Oct 13, 2025
c43de97
name var
marciocloudflare Oct 13, 2025
8ca0ba0
network segmentation var
marciocloudflare Oct 13, 2025
114a5cd
dhcp vars
marciocloudflare Oct 13, 2025
8b3cd1a
ternary var
marciocloudflare Oct 13, 2025
6d56cd0
added spf to partial
marciocloudflare Oct 13, 2025
66952f1
name var
marciocloudflare Oct 13, 2025
ef7d55a
added vars
marciocloudflare Oct 13, 2025
7278c1c
added vars
marciocloudflare Oct 13, 2025
0cdf8f0
added var names
marciocloudflare Oct 13, 2025
258ddc5
added hcConfigsURL
marciocloudflare Oct 13, 2025
30870b4
added next steps vars
marciocloudflare Oct 13, 2025
7f14ba9
moved overview to partial
marciocloudflare Oct 13, 2025
ffa6d75
added vars
marciocloudflare Oct 13, 2025
b11b43f
added vars
marciocloudflare Oct 13, 2025
0b083ce
added vars
marciocloudflare Oct 13, 2025
fbc0041
dhcp relay to partial
marciocloudflare Oct 13, 2025
a4067f1
name var and pre class mermaid
marciocloudflare Oct 14, 2025
32c5b29
naming vars
marciocloudflare Oct 14, 2025
b02264d
dhcp server partial
marciocloudflare Oct 14, 2025
6587018
productname var
marciocloudflare Oct 14, 2025
3c87921
dhcp static address to partial
marciocloudflare Oct 14, 2025
c23e5ad
moved partials to network options
marciocloudflare Oct 14, 2025
b7f1d93
corrected path
marciocloudflare Oct 14, 2025
6b000c7
nat partial
marciocloudflare Oct 14, 2025
f60a320
added vars
marciocloudflare Oct 14, 2025
35e2dc7
network segmentation partial
marciocloudflare Oct 14, 2025
5ce1c21
name var
marciocloudflare Oct 14, 2025
862841c
pre class to mermaid
marciocloudflare Oct 14, 2025
efb1bfb
name var
marciocloudflare Oct 14, 2025
86c41c5
added vars
marciocloudflare Oct 14, 2025
d77021c
var name
marciocloudflare Oct 14, 2025
5368a75
routed subnets partial
marciocloudflare Oct 14, 2025
49b798b
added partial
marciocloudflare Oct 14, 2025
5ac71c1
added vars
marciocloudflare Oct 14, 2025
4c53b5b
moved appliance to folder
marciocloudflare Oct 14, 2025
4868330
corrected path
marciocloudflare Oct 14, 2025
6c01591
url vars
marciocloudflare Oct 14, 2025
3f7b8be
basic info partial
marciocloudflare Oct 14, 2025
23f3b62
add remove mconn partial
marciocloudflare Oct 14, 2025
6c33d8f
network settings partial
marciocloudflare Oct 14, 2025
8cb6dc4
traffic steering
marciocloudflare Oct 14, 2025
1fbfc7c
sites partial
marciocloudflare Oct 14, 2025
e058abf
deactivate partial
marciocloudflare Oct 14, 2025
302c6f2
default pass partial
marciocloudflare Oct 14, 2025
fadfeb9
heartbeat partial
marciocloudflare Oct 14, 2025
280307c
service window partial
marciocloudflare Oct 14, 2025
ede3d91
device metrics partial
marciocloudflare Oct 14, 2025
7320d9d
var name
marciocloudflare Oct 14, 2025
90df52b
mconn ref partial
marciocloudflare Oct 14, 2025
14bf307
added params
marciocloudflare Oct 14, 2025
837bf87
name var
marciocloudflare Oct 14, 2025
cbfdba1
added vars
marciocloudflare Oct 14, 2025
babeaf4
vars
marciocloudflare Oct 14, 2025
9b69ae3
ha var
marciocloudflare Oct 14, 2025
be8253f
vars
marciocloudflare Oct 14, 2025
1ed51b5
wan partial params
marciocloudflare Oct 14, 2025
b1f0896
ecmp var
marciocloudflare Oct 14, 2025
2271a3a
ecmp var
marciocloudflare Oct 14, 2025
6dbc24c
var
marciocloudflare Oct 14, 2025
93a46c3
multiple wans var
marciocloudflare Oct 14, 2025
6be0659
var
marciocloudflare Oct 14, 2025
4450e44
sfp var
marciocloudflare Oct 14, 2025
8b35075
vars
marciocloudflare Oct 14, 2025
7ddb6bb
vlanid var
marciocloudflare Oct 14, 2025
3d3867a
traffic steering var
marciocloudflare Oct 14, 2025
e0353bd
tunnel hc var
marciocloudflare Oct 14, 2025
655d4c5
vars
marciocloudflare Oct 14, 2025
0fc94b2
dhcp url
marciocloudflare Oct 14, 2025
0f83ece
routed subnets var
marciocloudflare Oct 14, 2025
c8eb548
network segmentation var
marciocloudflare Oct 14, 2025
458e4ac
refactored troubleshooting
marciocloudflare Oct 14, 2025
89a98d4
var name
marciocloudflare Oct 14, 2025
2d2e5b7
name vars
marciocloudflare Oct 14, 2025
e4723cf
activaef var
marciocloudflare Oct 14, 2025
82a084d
vars
marciocloudflare Oct 14, 2025
380293c
vars
marciocloudflare Oct 14, 2025
65d9428
vars
marciocloudflare Oct 14, 2025
6f93cb7
traceroute partial
marciocloudflare Oct 14, 2025
37a5654
gre url var
marciocloudflare Oct 14, 2025
e555596
added vars
marciocloudflare Oct 14, 2025
9a39aeb
vars
marciocloudflare Oct 14, 2025
0bb921a
moved sites brief
marciocloudflare Oct 14, 2025
93755ab
sites partial
marciocloudflare Oct 14, 2025
5df1ad6
added vars
marciocloudflare Oct 14, 2025
b5ef8c9
cni var
marciocloudflare Oct 14, 2025
b351118
vars
marciocloudflare Oct 14, 2025
394c970
vars
marciocloudflare Oct 14, 2025
ff3da63
changed h3
marciocloudflare Oct 14, 2025
bff68d2
added vars
marciocloudflare Oct 14, 2025
d4cf470
removed partial from 3rd party
marciocloudflare Oct 14, 2025
b3aab9f
created mconn heartbeat health partial
marciocloudflare Oct 15, 2025
a720101
added vars
marciocloudflare Oct 15, 2025
afdd6f4
custom ike partial
marciocloudflare Oct 15, 2025
fdf0b1f
added vars
marciocloudflare Oct 15, 2025
e261529
security filters partial
marciocloudflare Oct 15, 2025
98513ed
vars
marciocloudflare Oct 15, 2025
9972e15
moved partials
marciocloudflare Oct 15, 2025
3d2bbdd
zt overview partial
marciocloudflare Oct 15, 2025
f8f732e
vars
marciocloudflare Oct 15, 2025
b968684
gateway partial and vars
marciocloudflare Oct 15, 2025
c1dc191
vars
marciocloudflare Oct 15, 2025
bb1fe6b
vars class mermaid
marciocloudflare Oct 15, 2025
6e103cf
vars
marciocloudflare Oct 15, 2025
107ed78
traceroute partial
marciocloudflare Oct 15, 2025
15d7371
vars
marciocloudflare Oct 15, 2025
2f551ed
tunnel partial
marciocloudflare Oct 15, 2025
f19af2f
content
marciocloudflare Oct 15, 2025
b11ffaf
vars
marciocloudflare Oct 15, 2025
bc481ba
vars
marciocloudflare Oct 15, 2025
4717f7f
vars
marciocloudflare Oct 15, 2025
97daa3f
warp partial
marciocloudflare Oct 15, 2025
f6ab762
content
marciocloudflare Oct 15, 2025
0ba1f5d
vars
marciocloudflare Oct 15, 2025
d8d8919
vars
marciocloudflare Oct 15, 2025
2bfc26d
vars
marciocloudflare Oct 15, 2025
1b7579e
vars
marciocloudflare Oct 15, 2025
02500ca
vars
marciocloudflare Oct 15, 2025
04a06a2
vars
marciocloudflare Oct 15, 2025
1c724ab
vars
marciocloudflare Oct 15, 2025
381a3dd
load balancing partial
marciocloudflare Oct 15, 2025
81d4d5c
vars
marciocloudflare Oct 15, 2025
5659c89
changed partial name
marciocloudflare Oct 15, 2025
4c91061
mwan net analytics partial
marciocloudflare Oct 15, 2025
3acaff5
vars
marciocloudflare Oct 15, 2025
980d920
bandwidth partial and vars
marciocloudflare Oct 15, 2025
284c5f1
vars
marciocloudflare Oct 15, 2025
d4860b7
vars
marciocloudflare Oct 15, 2025
a7c21d9
vars
marciocloudflare Oct 15, 2025
17dc212
corrected path
marciocloudflare Oct 15, 2025
e6847a5
vars
marciocloudflare Oct 15, 2025
bf77b79
vars
marciocloudflare Oct 15, 2025
3479ef6
made cftunnel optional
marciocloudflare Oct 15, 2025
9fcdfa1
Update src/content/partials/networking-services/mconn/maintenance/hea…
marciocloudflare Oct 15, 2025
d64b544
Update src/content/partials/networking-services/mconn/maintenance/int…
marciocloudflare Oct 15, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion src/content/docs/magic-transit/analytics/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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/"
}}
/>
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" />
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down
3 changes: 2 additions & 1 deletion src/content/docs/magic-wan/analytics/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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/"
}}
/>
23 changes: 6 additions & 17 deletions src/content/docs/magic-wan/analytics/network-analytics.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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" />
}}
/>
7 changes: 5 additions & 2 deletions src/content/docs/magic-wan/analytics/site-analytics.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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" />
Original file line number Diff line number Diff line change
Expand Up @@ -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/"
}}
/>
Original file line number Diff line number Diff line change
Expand Up @@ -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",
}}
/>
Original file line number Diff line number Diff line change
Expand Up @@ -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/"
}}
/>
Original file line number Diff line number Diff line change
Expand Up @@ -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/"
}} />
Original file line number Diff line number Diff line change
Expand Up @@ -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",
}} />
Original file line number Diff line number Diff line change
Expand Up @@ -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/"
}} />
Loading
Loading