diff --git a/src/content/partials/networking-services/magic-wan/third-party/viptela.mdx b/src/content/partials/networking-services/magic-wan/third-party/viptela.mdx
index e451b01e41383c3..97ac7127626c161 100644
--- a/src/content/partials/networking-services/magic-wan/third-party/viptela.mdx
+++ b/src/content/partials/networking-services/magic-wan/third-party/viptela.mdx
@@ -1,6 +1,5 @@
---
params:
- - productName
- configureTunnelEndpointsUrl
- configureStaticRoutesUrl
- ciscoIosXeUrl
@@ -12,9 +11,9 @@ Cloudflare partners with Cisco's SD-WAN solution to provide users with an integr
Before setting up a connection between Cisco SD-WAN and Cloudflare, you must have:
-- Purchased {props.productName} and Secure Web Gateway.
-- Cloudflare provision {props.productName} and Secure Web Gateway.
-- Received two Cloudflare tunnel endpoints (anycast IP address) assigned to {props.productName}.
+- Purchased Magic WAN and Secure Web Gateway.
+- Cloudflare provision Magic WAN and Secure Web Gateway.
+- Received two Cloudflare tunnel endpoints (anycast IP address) assigned to Magic WAN.
- Cisco SD-WAN appliances (physical or virtual). This ensures specific Internet-bound traffic from the sites' private networks is routed over the anycast GRE tunnels to Secure Web Gateway to enforce a user's specific web access policies.
- A static IP pair to use with the tunnel endpoints. The static IPs should be `/31` addresses separate from the IPs used in the subnet deployment.
- Release 20.6 Controllers and vEdge Device Builds. You should also pair them with devices that are on at least version Cisco IOS XE SD-WAN 17.6. Refer to [Cisco documentation](https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/215676-cisco-tac-and-bu-recommended-sd-wan-soft.html) to learn more Cisco softweare versions.
diff --git a/src/content/partials/networking-services/magic-wan/zero-trust/warp.mdx b/src/content/partials/networking-services/magic-wan/zero-trust/warp.mdx
index f5eba99d6deb649..d197879c8dc34dd 100644
--- a/src/content/partials/networking-services/magic-wan/zero-trust/warp.mdx
+++ b/src/content/partials/networking-services/magic-wan/zero-trust/warp.mdx
@@ -97,8 +97,6 @@ To learn which IP addresses and UDP ports you should exclude to accomplish this,
file="mconn/network-options/app-aware-policies/warp-traffic"
product="networking-services"
params={{
- connectorName: props.mwanConnectorName,
- mwanName: props.productName,
warpFirewallURL: "/cloudflare-one/team-and-resources/devices/warp/deployment/firewall/"
}}
/>
diff --git a/src/content/partials/networking-services/mconn/configure-connectors.mdx b/src/content/partials/networking-services/mconn/configure-connectors.mdx
index 2a4a472ce6d962f..0fe0c27b9a6ed1f 100644
--- a/src/content/partials/networking-services/mconn/configure-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/configure-connectors.mdx
@@ -4,7 +4,7 @@ params:
- productName
- productNameVirtual?
- maintenanceURL
- - productOriginalName
+ - dashName
- sfpURL?
- wan
- lan
@@ -27,7 +27,6 @@ params:
- wanSettingsURL
- sitesURL
- networkOptionsURL
- - maintenanceURL
- referenceInformationURL
- troubleshootingURL
---
@@ -58,7 +57,7 @@ In this page you will find instructions on how to configure {props.productName}.
{ props.magicWord === "hardware" && (
<>
- You need to purchase {props.productOriginalName} before you can purchase and use {props.productName}. {props.productName} can function as your primary edge device for your network, or be deployed in-line with existing network gear.
+ You need to purchase Magic WAN before you can purchase and use {props.productName}. {props.productName} can function as your primary edge device for your network, or be deployed in-line with existing network gear.
You also need to purchase {props.productName} before you can start configuring your settings in the Cloudflare dashboard. Contact your account representative to learn more about purchasing options for {props.productName}.
@@ -70,7 +69,7 @@ In this page you will find instructions on how to configure {props.productName}.
<>
-
- To set up and use {props.productOriginalName}, you first need to register it with your account.
+
+ To set up and use Magic WAN, you first need to register it with your account.
@@ -337,7 +336,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
}
{/* WAN Tunnels section */}
-{ props.productOriginalName === "WAN Tunnels" && (
+{ props.dashName === "WAN Tunnels" && (
<>
You need to create a profile for your appliance before connecting it to the Internet.
@@ -352,7 +351,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
}
{/* Magic WAN section */}
-{ props.productOriginalName !== "WAN Tunnels" && (
+{ props.dashName !== "WAN Tunnels" && (
<>
You need to add your { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } to your Cloudflare dashboard and configure its settings before connecting it to the Internet.
@@ -377,7 +376,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
-
+
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 { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } to load balance traffic over WANs of equal priority. It also allows { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } to failover between circuits according to their health. Refer to WAN settings for more details.
:::note
@@ -569,15 +568,15 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
When you are ready to connect your { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } to the Cloudflare network:
{/* Instructions for WAN Tunnels */}
-{ props.productOriginalName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
Cloudflare One, and go to **Networks**.
2. Go to **Connectors** > **Appliances**.
- 3. Find the Appliances you want to activate, select the three dots next to it > **Edit**. Make sure you verify the serial number to choose the right Appliances you want to activate.
+ 3. Find the ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } you want to activate, select the three dots next to it > **Edit**. Make sure you verify the serial number to choose the right ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } 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 ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } 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 for more details on how to define when the Appliances can update its systems.
+ 5. The **Interrupt window** is the time period when the ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } 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 for more details on how to define when the ${ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } can update its systems.
6. Select **Update**.
`}
inline={false}
@@ -639,7 +638,7 @@ When you are ready to connect your { props.magicWord === "virtual" ? props.produ
@@ -851,7 +850,7 @@ inline={false}
To check the IPsec tunnels and static routes created by your { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }:
-{ props.productOriginalName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
hardware version of {props.productName}
+- The hardware version of {props.productName}
- The virtual version of {props.productName}
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx b/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx
index 582eaef45c94486..a0eb0952dec2f18 100644
--- a/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/add-remove-connectors.mdx
@@ -1,14 +1,14 @@
---
params:
- productName
- - wanName
+ - dashName
---
import { Markdown } from "~/components";
To add a new {props.productName} you first need to remove the one associated with the on-ramps. You can only have more than one {props.productName} if you initially enabled high availability on your on-ramp.
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
- Log in to Cloudflare One, and go to Networks.
@@ -20,7 +20,7 @@ To set up and use the hardware version of {props.productName}, you first need to
}
{/* Dashboard steps for Magic WAN (standalone dashboard) */}
-{ props.magicWord !== "WAN Tunnels" && (
+{ props.dashName !== "WAN Tunnels" && (
<>
- In the Cloudflare dashboard, go to Magic WAN's Configuration page.
diff --git a/src/content/partials/networking-services/mconn/mconn-reference.mdx b/src/content/partials/networking-services/mconn/mconn-reference.mdx
index 73a99e264ae903e..33b75082635d54b 100644
--- a/src/content/partials/networking-services/mconn/mconn-reference.mdx
+++ b/src/content/partials/networking-services/mconn/mconn-reference.mdx
@@ -1,7 +1,7 @@
---
params:
- productName
- - productOriginalName
+ - dashName
- virtualProductName
- gatewayURL
- hardConnectorURL
@@ -95,7 +95,7 @@ When a failover occurs, traffic is moved to the new active node. It could take u
This is where you add and configure your WAN connections. Each configured WAN will create one IPsec tunnel, unless you have more than one anycast IP configured in your account.
-
+
When you have multiple WANs you can attribute different priorities to each one. Lower values mean a higher priority. This translates in {props.productName} routing traffic through the higher priority WANs or, more precisely, over the IPsec tunnels established over that interface. On the other hand, if you configure multiple WANs of equal priority, traffic will be distributed over those links through Equal-Cost Multi-Path (ECMP routing).
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
index 469f86c6cc6a2fb..87346f78ac0951b 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/breakout-prioritized.mdx
@@ -5,7 +5,7 @@ params:
- featureName
- trafficSteeringURL?
- whatHappensApp
- - mwanName
+ - dashName
---
import { APIRequest, Aside, AnchorHeading, CURL, Markdown, Render, TabItem, Tabs } from "~/components";
@@ -95,7 +95,7 @@ You need to configure {props.featureName} applications for each of your existing
-{ props.mwanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
-{ props.mwanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
- { props.mwanName === "WAN Tunnels" ? (
+ { props.dashName === "WAN Tunnels" ? (
<>
Cloudflare One dashboard, and go to **Networks**.
2. Go to **Connectors** > **Appliances** > **Profiles**.
- 3. Select the Appliance you want to configure> **Edit**.
+ 3. Select the ${props.productName} you want to configure> **Edit**.
`}
inline={false}
/>
@@ -359,8 +359,6 @@ To pin applications to a WAN port:
file="mconn/network-options/app-aware-policies/warp-traffic"
product="networking-services"
params={{
- connectorName: props.productName,
- mwanName: props.mwanName,
warpFirewallURL: "/cloudflare-one/team-and-resources/devices/warp/deployment/firewall/"
}}
/>
diff --git a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/warp-traffic.mdx b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/warp-traffic.mdx
index c1300a2bb4db40d..826b1729da3033c 100644
--- a/src/content/partials/networking-services/mconn/network-options/app-aware-policies/warp-traffic.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/app-aware-policies/warp-traffic.mdx
@@ -1,11 +1,9 @@
---
params:
- - connectorName
- - mwanName
- warpFirewallURL
---
-If you have {props.connectorName} and WARP clients deployed in your premises, {props.connectorName} automatically routes WARP traffic to the Internet rather than {props.mwanName} IPsec tunnels. This prevents traffic from being encapsulated twice.
+If you have Magic WAN Connector and WARP clients deployed in your premises, Magic WAN Connector automatically routes WARP traffic to the Internet rather than Magic WAN IPsec tunnels. This prevents traffic from being encapsulated twice.
You may need to configure your firewall to allow this new traffic. Make sure to allow the following IPs and ports:
diff --git a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
index a5f8e75a7789582..e5d6bfe5a7022fc 100644
--- a/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
+++ b/src/content/partials/networking-services/mconn/network-options/dhcp/dhcp-relay.mdx
@@ -1,7 +1,7 @@
---
params:
- productName
- - wanName
+ - dashName
- cfTunnelURL
- cfVsCoreDashNamingMwanCni
---
@@ -14,7 +14,7 @@ DHCP Relay provides a way for DHCP clients to communicate with DHCP servers that
{`
flowchart LR
accTitle: An example of Connector in DHCP Relay mode
- a(${props.productName}) <--> b(Cloudflare/${props.wanName}) <--> c(DHCP server)
+ a(${props.productName}) <--> b(Cloudflare/Magic WAN) <--> c(DHCP server)
subgraph Site A
d[LAN 1] <--> a
@@ -39,7 +39,7 @@ To configure DHCP relay:
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
-{ props.wanName === "WAN Tunnels" ? (
+{ props.dashName === "WAN Tunnels" ? (
<>
+
### Performance analytics
@@ -34,7 +34,7 @@ In Performance analytics you can review your {props.productName}'s performance o
To access performance analytics:
-
+
3. Select **Performance analytics**.
### Port analytics
@@ -46,7 +46,7 @@ Port analytics gives you access to information related to the packets sent and r
The dashboard provides this information for all active ports in your {props.productName}. To access port analytics:
-
+
3. Select **Port analytics**.
### Event logs
@@ -72,7 +72,7 @@ Use Event logs to identify general patterns and changes over time. This is usefu
To access event logs:
-
+
3. Select **Events**.
4. You can filter results by specific events, and by time.
@@ -80,7 +80,7 @@ To access event logs:
Refer to the DHCP leasing section to identify DHCP assigned leases and their expiration dates. To access DHCP leasing:
-
+
3. Select **DHCP leasing**.
## Troubleshooting tips
diff --git a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
index 3b40079bb69ee21..3f3cb224324e2ab 100644
--- a/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
+++ b/src/content/partials/networking-services/mconn/wan-two-tunnels.mdx
@@ -1,7 +1,7 @@
---
params:
- productName
- - productOriginalName
+ - dashName
---
-When you have more than one anycast IP configured in your account (set up during your {props.productOriginalName} onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
\ No newline at end of file
+When you have more than one anycast IP configured in your account (set up during your Magic WAN onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/routing/configure-tunnels.mdx b/src/content/partials/networking-services/routing/configure-tunnels.mdx
index 1ba5f814d687844..47a416ef30b850b 100644
--- a/src/content/partials/networking-services/routing/configure-tunnels.mdx
+++ b/src/content/partials/networking-services/routing/configure-tunnels.mdx
@@ -11,7 +11,6 @@ params:
- dashButtonPath?
- updateHCFrequencyPage
- tunnelHealthChecksPage
- - antiReplayPagePath
- biVsUniHealthCheck
- tunnelHealthDash
- biVsUniHealthCheckDefaults
diff --git a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx
index ae32ce395ea78c0..5f05b993d709779 100644
--- a/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx
+++ b/src/content/partials/networking-services/tunnel-health/update-tunnel-health-checks-frequency.mdx
@@ -20,7 +20,7 @@ By default, Cloudflare servers send
-
For {props.magicWord === "Magic WAN" ? "Magic WAN Connector" : "WAN Tunnels Appliances"}, health checks are sent to IPsec tunnel endpoints.
+ For Magic WAN Connector, health checks are sent to IPsec tunnel endpoints.
)
}
@@ -31,7 +31,7 @@ Available options are `low`, `mid`, and `high`.
{ (props.magicWord === "Magic WAN" || props.magicWord === "WAN Tunnels") && (
<>
- To configure health checks frequency in {props.magicWord === "Magic WAN" ? "Magic WAN Connector" : "WAN Tunnels Appliances"}, refer to Configure {props.magicWord === "Magic WAN" ? "Connector" : "Appliances"}
+ To configure health checks frequency in Magic WAN Connector, refer to Configure Connector
)
}
@@ -71,7 +71,7 @@ Below is an example of how to adjust tunnel health check frequency to `low`. Not
{ (props.magicWord === "Magic WAN" || props.magicWord === "WAN Tunnels") && (
<>
-
+
{ props.magicWord === "Magic WAN" ? (
<>