vars

Author: marciocloudflare

src/content/docs/magic-wan/configuration/manually/third-party/aruba-edgeconnect.mdx

@@ -9,5 +9,8 @@ import { Render } from "~/components";
 <Render file="magic-wan/third-party/aruba-edgeconnect"
   product="networking-services"
   params={{
-    productName: "Magic WAN"
+    productName: "Magic WAN",
+		tunnelHealthCheckUrl: "/magic-wan/reference/tunnel-health-checks/",
+		magicFirewallUrl: "/magic-firewall/",
+		gatewayUrl: "/cloudflare-one/policies/gateway/"
   }} />

src/content/partials/networking-services/magic-wan/third-party/aruba-edgeconnect.mdx

@@ -1,6 +1,9 @@
 ---
 params:
   - productName
+  - tunnelHealthCheckUrl
+  - magicFirewallUrl
+  - gatewayUrl
 ---
 
 import { Details } from "~/components"
@@ -83,7 +86,7 @@ We use Aruba Orchestrator's Business Intent Overlays to create intuitive policie
 
 <Details header="GRE tunnel configuration">
 
-Cloudflare's [tunnel health checks](/magic-transit/reference/tunnel-health-checks/) are ping reply packets encapsulated in GRE packets. The source IP is the Edgeconnect WAN interface used to establish a tunnel, and the destination IP is Cloudflare servers. These packets need to be sent directly from the WAN interface and not through the established tunnels.
+Cloudflare's <a href={props.tunnelHealthCheckUrl}>tunnel health checks</a>] are ping reply packets encapsulated in GRE packets. The source IP is the Edgeconnect WAN interface used to establish a tunnel, and the destination IP is Cloudflare servers. These packets need to be sent directly from the WAN interface and not through the established tunnels.
 
 To create the overlay policy:
 
@@ -102,7 +105,7 @@ The service name used to send traffic through the tunnel created in the next ste
 
 <Details header="IPsec tunnel configuration">
 
-Cloudflare's [tunnel health checks](/magic-transit/reference/tunnel-health-checks/) are ping reply packets encapsulated in IPsec packets. The source IP is the Edgeconnect WAN interface used to establish a tunnel, and the destination IP is Cloudflare servers. These packets need to be sent directly from the WAN interface and not through the established tunnels.
+Cloudflare's <a href={props.tunnelHealthCheckUrl}>tunnel health checks</a>] are ping reply packets encapsulated in IPsec packets. The source IP is the Edgeconnect WAN interface used to establish a tunnel, and the destination IP is Cloudflare servers. These packets need to be sent directly from the WAN interface and not through the established tunnels.
 
 To create the overlay policy:
 
@@ -356,4 +359,4 @@ This validates the east-west traffic flow through Cloudflare {props.productName}
 
 At this point, the GRE or IPsec tunnels should be connected from the EdgeConnect appliances to Cloudflare's global network, and traffic is scoped to route over the tunnels using the EdgeConnect Business Intent Overlays.
 
-To begin filtering traffic and gathering analytics, refer to the [Magic Firewall documentation](/magic-firewall/) to learn how to create filters for east-west inter-branch traffic and the [Secure Web Gateway documentation](/cloudflare-one/policies/gateway/) to learn how to configure Gateway policies if you decide to send traffic from your local private subnets to the Internet through Cloudflare Gateway.
+To begin filtering traffic and gathering analytics, refer to the <a href={prps.magicFirewallUrl}>Magic Firewall documentation</a> to learn how to create filters for east-west inter-branch traffic and the <a href={prps.gatewayUrl}>Secure Web Gateway documentation</a> to learn how to configure Gateway policies if you decide to send traffic from your local private subnets to the Internet through Cloudflare Gateway.