Skip to content

Commit 4727a81

Browse files
added wan tunnels steps
1 parent 4c5ca14 commit 4727a81

File tree

4 files changed

+42
-13
lines changed

4 files changed

+42
-13
lines changed

src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/analytics/traceroutes.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,8 @@ import { Render } from "~/components";
1111
file="analytics/traceroutes"
1212
product="networking-services"
1313
params={{
14-
productName: "WAN",
14+
productName: "WAN Tunnels",
1515
dashButtonPath: "/?to=/:account/magic-wan/tunnel-healthchecks",
16+
magicWord: "wan-tunnels",
1617
}}
1718
/>

src/content/docs/magic-transit/analytics/traceroutes.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,8 @@ import { Render } from "~/components";
1111
file="analytics/traceroutes"
1212
product="networking-services"
1313
params={{
14-
productName: "Transit",
14+
productName: "Magic Transit",
1515
dashButtonPath: "/?to=/:account/magic-transit/tunnel-healthchecks",
16+
magicWord: "magic-transit",
1617
}}
1718
/>

src/content/docs/magic-wan/analytics/traceroutes.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,8 @@ import { Render } from "~/components";
1111
file="analytics/traceroutes"
1212
product="networking-services"
1313
params={{
14-
productName: "WAN",
14+
productName: "Magic WAN",
1515
dashButtonPath: "/?to=/:account/magic-wan/tunnel-healthchecks",
16+
magicWord: "magic-wan",
1617
}}
1718
/>

src/content/partials/networking-services/analytics/traceroutes.mdx

Lines changed: 36 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,46 @@
22
params:
33
- productName
44
- dashButtonPath
5+
- magicWord
56
---
67

7-
import { DashButton } from "~/components";
8-
9-
Magic {props.productName} customers can run traceroutes to understand the hop by hop Internet path and latencies from Cloudflare's network to their own network.
10-
11-
To run a traceroute from a specific Cloudflare data center to your network:
12-
13-
1. In the Cloudflare dashboard, go to Magic {props.productName}'s **Network health** page.
14-
15-
<DashButton url={props.dashButtonPath} />
16-
8+
import { DashButton, Markdown } from "~/components";
9+
10+
{props.productName} customers can run traceroutes to understand the hop by hop Internet path and latencies from Cloudflare's network to their own network.
11+
12+
{ props.magicWord === "wan-tunnels" && (
13+
<>
14+
<Markdown
15+
text={`
16+
## To run a traceroute from a specific Cloudflare data center to your network:
17+
18+
1. Log in to [Cloudflare One](https://one.dash.cloudflare.com/) > **Insights**.
19+
2. Go to **Network visibility** > **WAN connector health**.
20+
3. Select the tunnel you want to run the traceroute on.
21+
4. Select the three dots > **Traceroute details**.
22+
`}
23+
/>
24+
</>
25+
)}
26+
27+
{ props.magicWord !== "wan-tunnels" && (
28+
<>
29+
<Markdown
30+
text={`
31+
## To run a traceroute from a specific Cloudflare data center to your network:
32+
33+
1. In the Cloudflare dashboard, go to ${props.productName}'s **Network health** page.
34+
`}
35+
/>
36+
<DashButton url={props.dashButtonPath} />
37+
<Markdown
38+
text={`
1739
2. Expand a Magic Tunnel, and find the Cloudflare data center where the traceroute will be run from.
1840
3. Select **Traceroute for details**.
41+
`}
42+
/>
43+
</>
44+
)}
1945

2046
You can access detailed data from the traceroute, including:
2147

0 commit comments

Comments
 (0)