There are several deployment options for {props.productName}. {props.productName} can act like a DHCP server for your local network, or integrate with your local setup and have static IP addresses assigned to it.
@@ -461,8 +461,8 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
{`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)
+ accTitle: ${props.productName} set up as a DHCP server, and connecting to the Internet.
+ a(${props.productName})--> b(Internet) --> c(Cloudflare)
subgraph Customer site
d[LAN 1] --> a
@@ -477,8 +477,8 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
{`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)
+ accTitle: ${props.productName} connects to the router in the site, and only some of the LANs connect to Connector.
+ a(${props.productName})--> b((Site's router)) --> c(Internet) --> i(Cloudflare)
subgraph Customer site
d[LAN 1] --> a
@@ -491,7 +491,7 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
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.
+ Refer to {props.productName} 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 {props.productName}, configure the firewall to allow the following traffic:
@@ -547,7 +547,7 @@ When you are ready to connect your { props.magicWord === "virtual" ? props.produ
2. Go to **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.
+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](/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" && (
@@ -795,9 +795,9 @@ To set up a high availability configuration:
## IPsec tunnels and static routes
-Magic WAN Connector automatically creates IPsec tunnels and static routes for you. You cannot configure these manually.
+{ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } automatically creates IPsec tunnels and static routes for you. You cannot configure these manually.
-To check the IPsec tunnels and static routes created by your Magic WAN Connector:
+To check the IPsec tunnels and static routes created by your { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }:
1. In the Cloudflare dashboard, go to the **Sites** page.
diff --git a/src/content/partials/networking-services/mconn/licence-keys.mdx b/src/content/partials/networking-services/mconn/licence-keys.mdx
index 6f09bfda9b9b1cd..762bbc9168a849d 100644
--- a/src/content/partials/networking-services/mconn/licence-keys.mdx
+++ b/src/content/partials/networking-services/mconn/licence-keys.mdx
@@ -1,9 +1,10 @@
---
-{}
+params:
+ - virtualConnectorName
---
:::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.
+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 {props.virtualConnectorName}.
:::
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
index 5638ee828d2e463..4e4dd6b071ee22d 100644
--- a/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
+++ b/src/content/partials/networking-services/mconn/maintenance/default-password.mdx
@@ -13,6 +13,6 @@ Your Connector's default password is the serial number (also known as a Service
## Default password to access {props.virtualConnectorName}
-Your Virtual Connector's default password is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
+Your {props.virtualConnectorName}'s default password is the last seven characters of your license key, all uppercase, plus an `!` (exclamation mark).
For example, if your license key is `mconn-abcdefghijklmnopqrstuvwxyz`, your default password will be `TUVWXYZ!`.
\ No newline at end of file
diff --git a/src/content/partials/networking-services/mconn/mconn-reference.mdx b/src/content/partials/networking-services/mconn/mconn-reference.mdx
index 09be3efd21d98f1..bfad0b74521f82e 100644
--- a/src/content/partials/networking-services/mconn/mconn-reference.mdx
+++ b/src/content/partials/networking-services/mconn/mconn-reference.mdx
@@ -94,7 +94,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.
-
If you are using {props.virtualProductName}, this needs to correspond to the virtual network interface on the {props.virtualProductName} instance you have set up in VMware.
-- **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your Magic WAN Connector. Refer to VLAN ID for more information.
+- **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your {props.productName}. Refer to VLAN ID for more information.
- **Priority**: Assigns a priority to the WAN interface. Lower numbers have higher priority. Refer to Traffic steering to learn more about how Cloudflare calculates priorities.
- **Health check rate:** Configures the health check frequency for your WAN. Options are low, mid, and high. Refer to Update tunnel health checks frequency for more information.
- **Addressing:** Configures the {props.productName} to work in a DHCP or static IP environment.
@@ -120,7 +120,7 @@ If you do not have more than one anycast IP configured in your account, and you
## LAN settings
- **Interface number:** When using the hardware version of {props.productName}, this refers to the Ethernet port that you are using for your LAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to SFP+ port information for more information on the hardware supported.
If you are using the {props.virtualProductName}, this needs to correspond to the virtual LAN interface on the {props.virtualProductName} instance you have set up in VMware.
-- **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your Magic WAN Connector. Refer to VLAN ID for more information.
+- **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your {props.productName}. Refer to VLAN ID for more information.
- **Static addressing:** Configures the type of IP addressing for your Connector. Depending on your use case, this is where you configure your LAN interface IP address, or enable DHCP server or DHCP relay. Refer to DHCP options to learn more.
- **Static NAT prefix**: Enable NAT (network address translation). This is an optional setting.
- **Routed subnets:** Configures additional subnets behind a layer 3 router. Refer to Routed subnets for more information.
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 05e3fc09dab4370..81094688c2ed489 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,6 +5,7 @@ params:
- featureName
- trafficSteeringURL?
- whatHappensApp
+ - mwanName
---
import { APIRequest, Aside, AnchorHeading, CURL, Markdown, Render, TabItem, Tabs } from "~/components";
@@ -228,8 +229,8 @@ You need to delete {props.featureName} applications for each of your existing si
file="mconn/network-options/app-aware-policies/warp-traffic"
product="networking-services"
params={{
- connectorName: "Magic WAN Connector",
- mwanName: "Magic WAN",
+ connectorName: props.productName,
+ mwanName: props.mwanName,
warpFirewallURL: "/cloudflare-one/connections/connect-devices/warp/deployment/firewall/"
}}
/>
diff --git a/src/content/partials/networking-services/mconn/overview.mdx b/src/content/partials/networking-services/mconn/overview.mdx
index b76cea1bc8de29f..a8b00459aaaf1cf 100644
--- a/src/content/partials/networking-services/mconn/overview.mdx
+++ b/src/content/partials/networking-services/mconn/overview.mdx
@@ -9,14 +9,14 @@ params:
import { DirectoryListing, GlossaryTooltip } from "~/components";
-The {props.hardwareProductName} is a lightweight appliance you can install in corporate network locations to automatically connect, steer , and shape any IP traffic through secure IPsec tunnels. Magic WAN Connector is the easiest way to onboard your network locations to Cloudflare One. It is managed remotely through the Cloudflare dashboard, so you do not require an onsite IT team.
+The {props.hardwareProductName} is a lightweight appliance you can install in corporate network locations to automatically connect, steer , and shape any IP traffic through secure IPsec tunnels. {props.hardwareProductName} is the easiest way to onboard your network locations to Cloudflare One. It is managed remotely through the Cloudflare dashboard, so you do not require an onsite IT team.
You can purchase {props.hardwareProductName} software pre-installed on a Cloudflare-certified device, or download and deploy {props.virtualProductName} in your own infrastructure.
Either option ensures the best possible connectivity to the closest Cloudflare network location, where Cloudflare will apply security controls and send traffic on an optimized route to its destination.
-Magic WAN Connector has the same type of support process as other Cloudflare Enterprise products. Contact your team account manager to learn more.
+{props.hardwareProductName} has the same type of support process as other Cloudflare Enterprise products. Contact your team account manager to learn more.
-Review this section to learn how to configure and deploy Magic WAN Connector.
+Review this section to learn how to configure and deploy {props.hardwareProductName}.
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).
+You can also configure subinterfaces on the {props.virtualConnectorName} 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