vars refine

Author: marciocloudflare

src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/index.mdx

@@ -14,7 +14,7 @@ import { Render } from "~/components";
 	magicWord: "hardware",
 	productName: "Magic WAN Connector",
 	maintenanceURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/",
-	productOriginalName: "WAN Tunnels",
+	dashName: "WAN Tunnels",
 	mwanName: "Magic WAN",
 	sfpURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/sfp-port-information/",
 	wan: "refers to the physical 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](/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.",

src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-virtual-connector.mdx

@@ -15,7 +15,7 @@ import { Render } from "~/components";
 	productName: "Magic WAN Connector",
 	productNameVirtual: "Virtual Connector",
 	maintenanceURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/",
-	productOriginalName: "WAN Tunnels",
+	dashName: "WAN Tunnels",
 	mwanName: "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.",

src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/reference.mdx

@@ -12,7 +12,8 @@ import { Render } from "~/components";
 	product="networking-services"
 	params={{
 		productName: "Magic WAN Connector",
-		productOriginalName: "WAN Tunnels",
+		dashName: "WAN Tunnels",
+		mwanName: "Magic WAN",
 		virtualProductName: "Virtual Connector",
 		gatewayURL: "/cloudflare-one/policies/gateway/",
 		hardConnectorURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/",

src/content/partials/networking-services/mconn/configure-connectors.mdx

@@ -4,7 +4,7 @@ params:
   - productName
   - productNameVirtual?
   - maintenanceURL
-  - productOriginalName
+  - dashName
   - mwanName
   - sfpURL?
   - wan
@@ -330,15 +330,15 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 			file="mconn/maintenance/register-hardware-appliance"
 			product="networking-services"
 			params={{
-				magicWord: props.productOriginalName,
+				magicWord: props.dashName,
 				productName: props.productName
 				}} />
   </>
   )
 }
 
 {/* WAN Tunnels section */}
-{ props.productOriginalName === "WAN Tunnels" && (
+{ props.dashName === "WAN Tunnels" && (
 	<>
 		<AnchorHeading title="Create a new profile" depth={3} />
 		<p>You need to create a profile for your appliance before connecting it to the Internet.</p>
@@ -353,7 +353,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 }
 
 {/* Magic WAN section */}
-{ props.productOriginalName !== "WAN Tunnels" && (
+{ props.dashName !== "WAN Tunnels" && (
 	<>
 		<AnchorHeading title="Add a Connector on-ramp" depth={3} />
 		<p>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.</p>
@@ -378,7 +378,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.magicWord === "virtual" ? props.productNameVirtual : props.productName, productOriginalName: props.productOriginalName }} />
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.magicWord === "virtual" ? props.productNameVirtual : props.productName, dashName: props.dashName, mwanName: props.mwanName }} />
 
 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 { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } to failover between circuits according to their <GlossaryTooltip term="tunnel health-check" link={props.tunnelHealthChecksURL}>health</GlossaryTooltip>. Refer to <a href={props.wanSettingsURL}>WAN settings</a> for more details.
 		:::note
@@ -570,7 +570,7 @@ 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" ? (
 	<>
 		<Markdown
 	text={`
@@ -640,7 +640,7 @@ When you are ready to connect your { props.magicWord === "virtual" ? props.produ
 		<Markdown
 		text={`
 		1. Connect ${props.productName} to a DHCP port with access to the Internet.
-		2. ${props.productOriginalName === "WAN Tunnels" ? "[Create a new profile](#create-a-new-profile)" : "[Add a Connector on-ramp](#add-a-connector-on-ramp)"} in the Cloudflare dashboard.
+		2. ${props.dashName === "WAN Tunnels" ? "[Create a new profile](#create-a-new-profile)" : "[Add a Connector on-ramp](#add-a-connector-on-ramp)"} in the Cloudflare dashboard.
 		3. Create a [DHCP WAN](#create-a-wan).
 		4. [Activate](#activate-appliance) and power on your ${props.productName}.
 		5. Wait 60 seconds.
@@ -665,7 +665,7 @@ When you are ready to connect your { props.magicWord === "virtual" ? props.produ
 		<Markdown
 		text={`
 		1. Connect the machine where you installed the VM with ${props.productNameVirtual} to a DHCP port with access to the Internet.
-		2. ${props.productOriginalName === "WAN Tunnels" ? "[Create a new profile](#create-a-new-profile)" : "[Add a Connector on-ramp](#add-a-connector-on-ramp)"} in the Cloudflare dashboard.
+		2. ${props.dashName === "WAN Tunnels" ? "[Create a new profile](#create-a-new-profile)" : "[Add a Connector on-ramp](#add-a-connector-on-ramp)"} in the Cloudflare dashboard.
 		3. Create a [DHCP WAN](#create-a-wan).
 		4. [Activate](#activate-appliance) and boot your ${props.productNameVirtual}.
 		5. Wait 60 seconds.
@@ -825,7 +825,7 @@ To set up a high availability configuration:
 
 <Markdown
 text={`
-1. Follow the steps in ${props.productOriginalName === "WAN Tunnels" ? "[Create a new profile](#create-a-new-profile)" : "[Add a Connector on-ramp](#add-a-connector-on-ramp)"} up until step 4.
+1. Follow the steps in ${props.dashName === "WAN Tunnels" ? "[Create a new profile](#create-a-new-profile)" : "[Add a Connector on-ramp](#add-a-connector-on-ramp)"} up until step 4.
 `}
 inline={false}
 />
@@ -852,7 +852,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" ? (
 	<>
 		<Markdown
 	text={`

src/content/partials/networking-services/mconn/mconn-reference.mdx

@@ -1,7 +1,8 @@
 ---
 params:
   - productName
-  - productOriginalName
+  - dashName
+  - mwanName
   - virtualProductName
   - gatewayURL
   - hardConnectorURL
@@ -95,7 +96,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: props.productName, productOriginalName: props.productOriginalName }} />
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.productName, dashName: props.dashName, mwanName: props.mwanName }} />
 
 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>.
 

src/content/partials/networking-services/mconn/wan-two-tunnels.mdx

@@ -1,7 +1,8 @@
 ---
 params:
   - productName
-  - productOriginalName
+  - dashName
+  - mwanName
 ---
 
-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.
+When you have more than one anycast IP configured in your account (set up during your {props.mwanName} 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.