[MWAN] Changed hardcoded names to vars (#25934)

marciocloudflare · web-flow · commit d3be8da71ec2 · 2025-10-20T16:16:40.000+01:00
* connector to var

* changed params

* added vars

* changed to vars

* vars

* vars

* vars

* vars

* vars

* vars
diff --git a/src/content/docs/magic-wan/configuration/common-settings/sites.mdx b/src/content/docs/magic-wan/configuration/common-settings/sites.mdx
@@ -15,6 +15,7 @@ import { Render } from "~/components";
 	params={{
 		greIpsecTunnelsURL: "/magic-wan/configuration/manually/how-to/configure-tunnel-endpoints/",
 		connectorURL: "/magic-wan/configuration/connector/",
-		cniURL: "/magic-wan/network-interconnect/"
+		cniURL: "/magic-wan/network-interconnect/",
+		connectorName: "Magic WAN Connector"
 	}}
 	/>
diff --git a/src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/breakout-traffic.mdx b/src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/breakout-traffic.mdx
@@ -15,5 +15,6 @@ import { Render } from "~/components";
 	productName: "Magic WAN Connector",
 	featureName: "Breakout traffic",
 	trafficSteeringURL: "/magic-wan/reference/traffic-steering/",
-	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering"
+	whatHappensApp: "will now go directly to the Internet and bypass Cloudflare's filtering",
+	mwanName: "Magic WAN"
 	}} />
diff --git a/src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/prioritized-traffic.mdx b/src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/prioritized-traffic.mdx
@@ -14,5 +14,6 @@ import { Render } from "~/components";
 	magicWord: "prioritized",
 	productName: "Magic WAN Connector",
 	featureName: "Prioritized traffic",
-	whatHappensApp: "is now processed first by Connector"
+	whatHappensApp: "is now processed first by Connector",
+	mwanName: "Magic WAN"
 	}} />
diff --git a/src/content/partials/networking-services/magic-wan/get-started.mdx b/src/content/partials/networking-services/magic-wan/get-started.mdx
@@ -38,7 +38,7 @@ Setting up {props.productNameManual} manually is done through a combination of t
 ## Prerequisites
 
 :::note
-The list of prerequisites below is only for customers planning to connect manually to Cloudflare with a third-party device. If you plan on using Magic WAN Connector, skip this section and refer to <a href={props.configureConnectorUrl}>Configure with Connector</a>.
+The list of prerequisites below is only for customers planning to connect manually to Cloudflare with a third-party device. If you plan on using {props.productNameConnector}, skip this section and refer to <a href={props.configureConnectorUrl}>Configure with Connector</a>.
 :::
 
 ### Use compatible tunnel endpoint routers
@@ -54,7 +54,7 @@ Magic WAN relies on <a href={props.greReferenceURL}>GRE</a> and <a href={props.i
 <Render
 	file="prerequisites/maximum-segment-size"
 	product="networking-services"
-	params={{ productName: "Magic WAN" }}
+	params={{ productName: props.productNameManual }}
 />
 
 #### MSS clamping recommendations
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
@@ -97,8 +97,8 @@ 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: "Magic WAN Connector",
-		mwanName: "Magic WAN",
+		connectorName: props.mwanConnectorName,
+		mwanName: props.productName,
 		warpFirewallURL: "/cloudflare-one/connections/connect-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
@@ -206,7 +206,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 		inline={false}
 		/>
 
-		<Render file="mconn/vlan-tagging" product="networking-services" params={{	url: "[VMware's documentation](https://kb.vmware.com/s/article/1003825)" }}/>
+		<Render file="mconn/vlan-tagging" product="networking-services" params={{	url: "[VMware's documentation](https://kb.vmware.com/s/article/1003825)", virtualConnectorName: props.productNameVirtual }}/>
 
 		<Markdown
 		text={`
@@ -250,7 +250,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 		inline={false}
 		/>
 
-		<Render file="mconn/licence-keys" product="networking-services" />
+		<Render file="mconn/licence-keys" product="networking-services" params={{ virtualConnectorName: props.productNameVirtual }} />
 
 		<Markdown
 		text={`
@@ -282,7 +282,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 		inline={false}
 		/>
 
-		<Render file="mconn/licence-keys" product="networking-services" />
+		<Render file="mconn/licence-keys" product="networking-services" params={{ virtualConnectorName: props.productNameVirtual }} />
 
 		<Markdown
 		text={`
@@ -293,7 +293,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 		inline={false}
 		/>
 
-		<Render file="mconn/vlan-tagging" product="networking-services" params={{	url: "[Proxmox documentation](https://www.proxmox.com/en/products/proxmox-virtual-environment/get-started)" }}/>
+		<Render file="mconn/vlan-tagging" product="networking-services" params={{	url: "[Proxmox documentation](https://www.proxmox.com/en/products/proxmox-virtual-environment/get-started)", virtualConnectorName: props.productNameVirtual }}/>
 
 		<Markdown
 		text={`
@@ -349,7 +349,7 @@ To add a { props.magicWord === "virtual" ? props.productNameVirtual : props.prod
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: "Magic WAN Connector" }} />
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.productName }} />
 
 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 <GlossaryTooltip term="IPsec tunnel">IPsec</GlossaryTooltip> 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 Connector to failover between circuits according to their <GlossaryTooltip term="tunnel health-check" link="/magic-wan/reference/tunnel-health-checks/">health</GlossaryTooltip>. Refer to [WAN settings](/magic-wan/configuration/connector/reference/#wan-settings) for more details.
 		:::note
@@ -407,7 +407,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{sit
    - **Next hop**: The address of the L3 router to which the Connector should forward packets for this subnet.
    - **Static NAT prefix**: Optional setting. If you want to enable NAT for a routed subnet, supply an "external" prefix for the overlay-facing side of the NAT to use. It must be the same size as **Prefix**. <br /> Refer to [Routed subnets](/magic-wan/configuration/connector/network-options/routed-subnets/) for more information.
 8. Select **Save**.
-9. Select **Done** to finish your configuration. Tunnels and <GlossaryTooltip term="static route">static routes</GlossaryTooltip> will be automatically created for your Magic WAN Connector, once it boots up.
+9. Select **Done** to finish your configuration. Tunnels and <GlossaryTooltip term="static route">static routes</GlossaryTooltip> will be automatically created for your { props.magicWord === "virtual" ? props.productNameVirtual : props.productName }, once it boots up.
 
 </TabItem> <TabItem label="API">
 
@@ -440,11 +440,11 @@ After setting up your LANs, you can configure your { props.magicWord === "virtua
 
 #### DHCP options
 
-Magic WAN Connector supports different types of DHCP configurations. Connector can:
+{ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } supports different types of DHCP configurations. Connector can:
 
 - Connect to a DHCP server or use a static IP address instead of connecting to a DHCP server.
 - Act as a <a href={props.dhcpServerURL}>DHCP server</a>.
-- Use <a href={props.dhcpRelayURL}>DHCP relay</a> to connect to a DHCP server outside the location your Magic WAN Connector is in.
+- Use <a href={props.dhcpRelayURL}>DHCP relay</a> to connect to a DHCP server outside the location your { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } is in.
 - <a href={props.reserveIpAddressesURL}>Reserve IP addresses</a> for specific devices on your network.
 
 ### Add your Connector to a site
@@ -453,16 +453,16 @@ After finishing your { props.magicWord === "virtual" ? props.productNameVirtual
 
 { props.magicWord === "hardware" && (
   <>
-		<AnchorHeading title="Set up your Magic WAN Connector" depth={2} />
+		<AnchorHeading title={`Set up your ${props.productName}`} depth={2} />
 
 		<AnchorHeading title="Device installation" depth={3} />
 		<p>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.</p>
 		<p>When {props.productName} acts like the WAN router for your site, deployment will be something like this:</p>
 
 		<pre class="mermaid">
 		{`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
 
 		<pre class="mermaid">
 		{`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`}
 		</pre>
 
-		<p>Refer to <a href="/reference-architecture/diagrams/sase/magic-wan-connector-deployment/">Magic WAN Connector deployment options</a> for a high-level explanation of the deployment options that make sense to most environments, as well as a few advanced use cases.</p>
+		<p>Refer to <a href="/reference-architecture/diagrams/sase/magic-wan-connector-deployment/">{props.productName} deployment options</a> for a high-level explanation of the deployment options that make sense to most environments, as well as a few advanced use cases.</p>
 
 		<AnchorHeading title="Firewall settings required" depth={4} />
 		<p>If there is a firewall deployed upstream of the {props.productName}, configure the firewall to allow the following traffic:</p>
@@ -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 <a href={props.ipsecTunnelsRefURL}>IPsec tunnels</a> and <a href={props.staticRoutesRefURL}>static routes</a> for you. You cannot configure these manually.
+{ props.magicWord === "virtual" ? props.productNameVirtual : props.productName } automatically creates <a href={props.ipsecTunnelsRefURL}>IPsec tunnels</a> and <a href={props.staticRoutesRefURL}>static routes</a> 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
@@ -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}.
 :::
diff --git 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!`.
diff --git 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.
 
-<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: "Magic WAN Connector" }} />
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.productName }} />
 
 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 <a href={props.ecmpRoutingURL}>Equal-Cost Multi-Path (ECMP routing)</a>.
 
@@ -112,15 +112,15 @@ If you do not have more than one anycast IP configured in your account, and you
 ### WAN settings
 
 - **Interface number:** When using the hardware version of {props.productName}, this refers to the Ethernet port that you are using for your WAN. If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to <a href={props.sfpURL}>SFP+ port information</a> for more information on the hardware supported. <br />  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 <a href={props.vlanIdURL}>VLAN ID</a> for more information.
+- **VLAN ID**: Allows you to have multiple virtual WANs configured over the same port on your {props.productName}. Refer to <a href={props.vlanIdURL}>VLAN ID</a> for more information.
 - **Priority**: Assigns a priority to the WAN interface. Lower numbers have higher priority. Refer to <a href={props.trafficSteeringURL}>Traffic steering</a> 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 <a href={props.hcFrequencyURL}>Update tunnel health checks frequency</a> for more information.
 - **Addressing:** Configures the {props.productName} to work in a DHCP or static IP environment.
 
 ## 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 <a href={props.sfpURL}>SFP+ port information</a> for more information on the hardware supported. <br />  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 <a href={props.vlanIdURL}>VLAN ID</a> for more information.
+- **VLAN ID**: Allows you to have multiple virtual LANs configured over the same port on your {props.productName}. Refer to <a href={props.vlanIdURL}>VLAN ID</a> 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 <a href={props.dhcpURL}>DHCP options</a> 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 <a href={props.routedSubnetsURL}>Routed subnets</a> 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
@@ -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
@@ -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, <GlossaryTooltip term="traffic steering">steer</GlossaryTooltip>, and shape any IP traffic through <a href={props.ipsecRefUrl}>secure IPsec tunnels</a>. 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, <GlossaryTooltip term="traffic steering">steer</GlossaryTooltip>, and shape any IP traffic through <a href={props.ipsecRefUrl}>secure IPsec tunnels</a>. {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 <a href={props.hardwareUrl}>purchase {props.hardwareProductName}</a> software pre-installed on a Cloudflare-certified device, or download and deploy <a href={props.virtualUrl}>{props.virtualProductName}</a> 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}.
 
 <DirectoryListing />
diff --git a/src/content/partials/networking-services/mconn/vlan-tagging.mdx b/src/content/partials/networking-services/mconn/vlan-tagging.mdx
diff --git a/src/content/partials/networking-services/sites/sites.mdx b/src/content/partials/networking-services/sites/sites.mdx
