Skip to content

Commit b231cc3

Browse files
marciocloudflareMaddy-Cloudflare
marciocloudflare
and
Maddy-Cloudflare
authored
[MWAN] Prepares for cf1 (#25850)
* added render * created get started partial * added params * removed explicit name * added params * added params * added vars * added vars * added vars to virtual conn prereqs * ternary render * added ternary * vars * added vars * added vars * added vars * ternary option * removed vars * added ternary * name var * network segmentation var * dhcp vars * ternary var * added spf to partial * name var * added vars * added vars * added var names * added hcConfigsURL * added next steps vars * moved overview to partial * added vars * added vars * added vars * dhcp relay to partial * name var and pre class mermaid * naming vars * dhcp server partial * productname var * dhcp static address to partial * moved partials to network options * corrected path * nat partial * added vars * network segmentation partial * name var * pre class to mermaid * name var * added vars * var name * routed subnets partial * added partial * added vars * moved appliance to folder * corrected path * url vars * basic info partial * add remove mconn partial * network settings partial * traffic steering * sites partial * deactivate partial * default pass partial * heartbeat partial * service window partial * device metrics partial * var name * mconn ref partial * added params * name var * added vars * vars * ha var * vars * wan partial params * ecmp var * ecmp var * var * multiple wans var * var * sfp var * vars * vlanid var * traffic steering var * tunnel hc var * vars * dhcp url * routed subnets var * network segmentation var * refactored troubleshooting * var name * name vars * activaef var * vars * vars * vars * traceroute partial * gre url var * added vars * vars * moved sites brief * sites partial * added vars * cni var * vars * vars * changed h3 * added vars * removed partial from 3rd party * created mconn heartbeat health partial * added vars * custom ike partial * added vars * security filters partial * vars * moved partials * zt overview partial * vars * gateway partial and vars * vars * vars class mermaid * vars * traceroute partial * vars * tunnel partial * content * vars * vars * vars * warp partial * content * vars * vars * vars * vars * vars * vars * vars * load balancing partial * vars * changed partial name * mwan net analytics partial * vars * bandwidth partial and vars * vars * vars * vars * corrected path * vars * vars * made cftunnel optional * Update src/content/partials/networking-services/mconn/maintenance/heartbeat.mdx Co-authored-by: Maddy <[email protected]> * Update src/content/partials/networking-services/mconn/maintenance/interrupt-service-window.mdx Co-authored-by: Maddy <[email protected]> --------- Co-authored-by: Maddy <[email protected]>
1 parent 6e3009b commit b231cc3

File tree

103 files changed

+2364
-1566
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

103 files changed

+2364
-1566
lines changed

‎src/content/docs/magic-transit/analytics/index.mdx‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ import { Render } from "~/components";
1818
analyticsAnchorHeading: "#magic-transit-network-analytics",
1919
networkAnalyticsURL: "/magic-transit/analytics/network-analytics/",
2020
traceRoutes: "/magic-transit/analytics/traceroutes/",
21-
graphQl: "/magic-transit/"
21+
graphQlTunnelBandwidthURL: "/magic-transit/analytics/query-bandwidth/",
22+
graphQlTunnelHealthURL: "/magic-transit/analytics/query-tunnel-health/"
2223
}}
2324
/>

‎src/content/docs/magic-transit/analytics/network-analytics.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,4 @@ Refer to [Network Analytics](/analytics/network-analytics/) documentation to lea
2727

2828
## Access Magic Tunnel traffic analytics
2929

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

‎src/content/docs/magic-transit/reference/traffic-steering.mdx‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,12 @@ import { Render } from "~/components";
1818
params={{
1919
magicWord: "Magic Transit",
2020
productName: "Magic Transit",
21+
mFirewallName: "Magic Firewall",
22+
mFirewallURL: "/magic-firewall/",
23+
warpClientURL: "/cloudflare-one/connections/connect-devices/warp/",
24+
remoteBrowserURL: "/cloudflare-one/policies/browser-isolation/",
25+
accessURL: "/cloudflare-one/policies/access/",
26+
gatewayURL: "/cloudflare-one/policies/gateway/",
2127
greIpsecReferenceURL: "/magic-transit/reference/gre-ipsec-tunnels/",
2228
createStaticRoute: "/magic-transit/how-to/configure-routes/#create-a-static-route",
2329
editStaticRoute: "/magic-transit/how-to/configure-routes/#edit-a-static-route",

‎src/content/docs/magic-wan/analytics/index.mdx‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ import { Render } from "~/components";
1919
analyticsAnchorHeading: "#magic-wan-network-analytics",
2020
networkAnalyticsURL: "/magic-wan/analytics/network-analytics/",
2121
traceRoutes: "/magic-wan/analytics/traceroutes/",
22-
graphQl: "/magic-wan/"
22+
graphQlTunnelBandwidthURL: "/magic-wan/analytics/query-bandwidth/",
23+
graphQlTunnelHealthURL: "/magic-wan/analytics/query-tunnel-health/"
2324
}}
2425
/>

‎src/content/docs/magic-wan/analytics/network-analytics.mdx‎

Lines changed: 6 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,25 +6,14 @@ sidebar:
66
head:
77
- tag: title
88
content: Magic WAN Network Analytics
9-
109
---
1110

12-
import { GlossaryTooltip, Render } from "~/components"
13-
14-
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.
15-
16-
<Render file="analytics/network-analytics-data-averages" product="networking-services" />
11+
import { Render } from "~/components";
1712

18-
Refer to [Network Analytics](/analytics/network-analytics/) documentation to learn more.
19-
20-
## Network traffic data filters
21-
22-
<Render
23-
file="analytics/network-traffic-filters"
13+
<Render file="magic-wan/analytics/network-analytics"
2414
product="networking-services"
25-
params={{ magicProduct: "Magic WAN" }}
26-
/>
27-
28-
## Access Magic Tunnel traffic analytics
15+
params={{
16+
productName: "Magic WAN"
2917

30-
<Render file="analytics/network-analytics" product="networking-services" />
18+
}}
19+
/>

‎src/content/docs/magic-wan/analytics/site-analytics.mdx‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,13 @@ import { Render } from "~/components"
1515
file="analytics/site-analytics"
1616
product="networking-services"
1717
params={{
18-
instructions: "Refer to [Set up a site](/magic-wan/configuration/common-settings/sites/) for more information on how to set up a site."
18+
instructions: "Refer to [Set up a site](/magic-wan/configuration/common-settings/sites/) for more information on how to set up a site.",
19+
productName: "Magic WAN",
20+
magicTunnelHcsURL: "/magic-wan/configuration/common-settings/configure-magic-tunnel-health-alerts/",
21+
setGeoCoordinatesURL: "/magic-wan/configuration/common-settings/sites/#set-geographic-coordinates"
1922
}}
2023
/>
2124

22-
### Set thresholds for Magic WAN site health
25+
### Set thresholds for site health
2326

2427
<Render file="analytics/set-thresholds-site-health" product="networking-services" />

‎src/content/docs/magic-wan/configuration/common-settings/check-tunnel-health-dashboard.mdx‎

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,11 @@ import { Render } from "~/components";
3232

3333
## Magic WAN Connector
3434

35-
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.
36-
37-
Refer to [Heartbeat](/magic-wan/configuration/connector/maintenance/heartbeat/) to learn more.
35+
<Render
36+
file="tunnel-health/mconn-heartbeat-health"
37+
product="networking-services"
38+
params={{
39+
productName: "Magic WAN Connector",
40+
heartbeatURL: "/magic-wan/configuration/connector/maintenance/heartbeat/"
41+
}}
42+
/>

‎src/content/docs/magic-wan/configuration/common-settings/custom-ike-id-ipsec.mdx‎

Lines changed: 8 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -5,23 +5,12 @@ sidebar:
55
order: 6
66
---
77

8-
import { CURL } from "~/components";
8+
import { Render } from "~/components";
99

10-
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.
11-
12-
:::note
13-
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.
14-
:::
15-
16-
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.
17-
18-
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.
19-
20-
<CURL
21-
url="https://api.cloudflare.com/client/v4/accounts/ACCOUNT_ID/ipsec_tunnels/TUNNEL_ID"
22-
method="PATCH"
23-
json={{
24-
"custom_remote_identities":
25-
{"fqdn_id": "<your_custom_label>.<account_id>.custom.ipsec.cloudflare.com"}
26-
}}
27-
/>
10+
<Render
11+
file="magic-wan/custom-ike-id-ipsec"
12+
product="networking-services"
13+
params={{
14+
productName: "Magic WAN",
15+
}}
16+
/>

‎src/content/docs/magic-wan/configuration/common-settings/sites.mdx‎

Lines changed: 7 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -9,62 +9,12 @@ sidebar:
99

1010
import { Render } from "~/components";
1111

12-
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.
13-
14-
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.
15-
16-
## Add a site
17-
18-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
19-
2. Go to **Magic WAN** > **Network overview (beta)**.
20-
3. Select **Add site**.
21-
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.
22-
5. Select **Create and continue**.
23-
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.
24-
7. Select **Continue**.
25-
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.
26-
9. In **Magic WAN Health Check Alert** > **Notification name**, enter a name for the site's alert.
27-
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.
28-
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.
29-
12. Select **Complete setup** to finish setting up your site.
30-
31-
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.
32-
33-
---
34-
35-
## Site analytics
36-
37-
<Render
38-
file="analytics/site-analytics"
39-
product="networking-services"
40-
params={{ instructions: "" }}
41-
/>
42-
43-
---
44-
45-
## Edit a site
46-
47-
### Add or remove on-ramps
48-
49-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
50-
2. Go to **Magic WAN** > **Network overview (beta)**.
51-
3. Find your site in **Traffic overview** > select the three dots in front of it > **Edit**.
52-
4. Select **On-ramps**.
53-
5. Select **Add** to add a new on-ramp.
54-
6. If you want to remove an on-ramp, select the three dots in front of your on-ramp > **Remove**.
55-
56-
### Set geographic coordinates
57-
58-
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:
59-
60-
1. Go to **Magic WAN** > **Network overview (beta)**.
61-
2. Find your site in **Traffic overview** > select the three dots in front of it > **Edit**.
62-
3. In **Basic information**, edit your site's **Latitude** and **Longitude** coordinates.
63-
4. Select **Save**.
64-
65-
### Set thresholds for Magic WAN site health
66-
6712
<Render
68-
file="analytics/set-thresholds-site-health"
13+
file="sites/sites"
6914
product="networking-services"
70-
/>
15+
params={{
16+
greIpsecTunnelsURL: "/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/",
17+
connectorURL: "/magic-wan/configuration/connector/",
18+
cniURL: "/magic-wan/network-interconnect/"
19+
}}
20+
/>

‎src/content/docs/magic-wan/configuration/connector/configure-hardware-connector/index.mdx‎

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,24 @@ import { Render } from "~/components";
1313
params={{
1414
magicWord: "hardware",
1515
productName: "Magic WAN Connector",
16+
maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
17+
productOriginalName: "Magic WAN",
18+
sfpURL: "/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/",
1619
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.",
1720
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.",
1821
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.",
22+
networkSegmentationURL: "/magic-wan/configuration/connector/network-options/network-segmentation/",
23+
dhcpServerURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-server/",
24+
dhcpRelayURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-relay/",
25+
reserveIpAddressesURL: "/magic-wan/configuration/connector/network-options/dhcp/dhcp-static-address-reservation/",
1926
shippedLanguage: "The Magic WAN Connector is shipped to you deactivated",
2027
hardSoftConn: "You need to deploy two Connectors in your premises before you can set up a site in high availability.",
21-
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."
28+
hcConfigsURL: "/magic-wan/configuration/connector/reference/#high-availability-configurations",
29+
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.",
30+
ipsecTunnelsRefURL: "/magic-wan/reference/gre-ipsec-tunnels/#ipsec-tunnels",
31+
staticRoutesRefURL: "/magic-wan/reference/traffic-steering/",
32+
networkOptionsURL: "/magic-wan/configuration/connector/network-options/",
33+
maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
34+
referenceInformationURL: "/magic-wan/configuration/connector/reference/",
35+
troubleshootingURL: "/magic-wan/configuration/connector/troubleshooting/"
2236
}} />

0 commit comments

Comments
 (0)