Skip to content

Commit ed04ae8

Browse files
committed
Update partial routing/configure-routes.mdx and its references
1 parent da873a0 commit ed04ae8

File tree

4 files changed

+31
-19
lines changed

4 files changed

+31
-19
lines changed

src/content/docs/learning-paths/data-center-protection/configure-tunnels-routes/configure-routes.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ import { Render } from "~/components"
1818
routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
1919
chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
2020
publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
21-
productGatewayOrEgress: "Magic Transit with Egress"
21+
productGatewayOrEgress: "Magic Transit with Egress",
22+
dashButtonPath: "/?to=/:account/magic-transit/configuration"
2223
}}
2324
/>

src/content/docs/magic-transit/how-to/configure-routes.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ import { Render } from "~/components"
2121
routePrioritization: "/magic-transit/reference/traffic-steering/#route-prioritization",
2222
chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
2323
publicAsnMT: "[Public ASNs used for Magic Transit](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn) are verified during the onboarding process.",
24-
productGatewayOrEgress: "Magic Transit with Egress"
24+
productGatewayOrEgress: "Magic Transit with Egress",
25+
dashButtonPath: "/?to=/:account/magic-transit/configuration"
2526
}}
2627
/>

src/content/docs/magic-wan/configuration/manually/how-to/configure-routes.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,8 @@ import { Render } from "~/components"
2121
routePrioritization: "/magic-wan/reference/traffic-steering/#route-prioritization",
2222
chooseWeights: "/magic-wan/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
2323
publicAsnMT: " ",
24-
productGatewayOrEgress: "Magic WAN with Gateway"
24+
productGatewayOrEgress: "Magic WAN with Gateway",
25+
dashButtonPath: "/?to=/:account/magic-wan/configuration"
2526
}}
2627
/>
2728

src/content/partials/networking-services/routing/configure-routes.mdx

Lines changed: 25 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,10 @@ params:
88
- routePrioritization
99
- chooseWeights
1010
- productGatewayOrEgress
11+
- dashButtonPath
1112
---
1213

13-
import { Aside, APIRequest, Markdown, Render, TabItem, Tabs } from "~/components";
14+
import { Aside, APIRequest, Markdown, Render, TabItem, Tabs, DashButton } from "~/components";
1415

1516
Magic Networking uses a routing table to steer your traffic via next-hop from Cloudflare's global network to your connected networks. Entries can be added to the Magic routing table via static route configuration or via routes learned through BGP peering (only available over Direct CNI).
1617

@@ -32,20 +33,22 @@ Refer to <a href={props.trafficSteeringPage}>Traffic Steering</a> for more infor
3233

3334
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
3435

35-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
36-
2. Go to **{props.productName}** > **Configuration**.
37-
3. From the **Routes** tab, select **Create** to add a new route.
38-
4. Enter a descriptive name for your route in **Description**.
39-
5. In **Prefix**, enter your range of IP addresses. For example, `10.10.10.100/24`.
40-
6. In **Tunnel/Next hop** select which tunnel you want your route to go through. Choose from the tunnels you have created in <a href={props.tunnelEndpoints}>Configure tunnel endpoints</a>.
41-
7. Choose the **Priority** for your route. Lower numbers have higher priorities.
36+
1. In the Cloudflare dashboard, go to {props.productName}'s **Configuration** page.
37+
38+
<DashButton url={props.dashButtonPath} />
39+
40+
2. From the **Routes** tab, select **Create** to add a new route.
41+
3. Enter a descriptive name for your route in **Description**.
42+
4. In **Prefix**, enter your range of IP addresses. For example, `10.10.10.100/24`.
43+
5. In **Tunnel/Next hop** select which tunnel you want your route to go through. Choose from the tunnels you have created in <a href={props.tunnelEndpoints}>Configure tunnel endpoints</a>.
44+
6. Choose the **Priority** for your route. Lower numbers have higher priorities.
4245
:::note
4346
<Render file="longest-prefix-match" product="networking-services/reference" /> Have this in mind when configuring priorities for your routes. Refer to <a href={props.routePrioritization}>Route prioritization</a> for more information.
4447
:::
45-
8. (Optional) Choose a **Weight** for your route. Refer to <a href={props.chooseWeights}>Set priority and weights for static routes</a> for examples.
46-
9. (Optional) If you need to scope your route to a specific region, you can do it in **Region code**.
47-
10. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**.
48-
11. Select **Add routes** when you are done.
48+
7. (Optional) Choose a **Weight** for your route. Refer to <a href={props.chooseWeights}>Set priority and weights for static routes</a> for examples.
49+
8. (Optional) If you need to scope your route to a specific region, you can do it in **Region code**.
50+
9. (Optional) We highly recommend testing your route before adding it by selecting **Test routes**.
51+
10. Select **Add routes** when you are done.
4952

5053
</TabItem> <TabItem label="API">
5154

@@ -263,8 +266,11 @@ The Magic routing table is managed by the customer, who can select both the Clou
263266

264267
By default, each BGP peering session will use the same Cloudflare-side ASN to represent peering with the {props.productName} routing table. This ASN is called the **CF Account ASN** and is set to `13335`. This can be configured to a private 2-byte ASN (for example, any values between `64512` and `65534`). To set this ASN:
265268

266-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
267-
2. Go to **{props.productName}** > **Configuration** > **BGP**.
269+
1. In the Cloudflare dashboard, go to {props.productName}'s **Configuration** page.
270+
271+
<DashButton url={props.dashButtonPath} />
272+
273+
2. Go to **BGP configuration**.
268274
3. In **CF Account ASN**, enter Cloudflare's ASN.
269275
4. Select **Update**.
270276

@@ -313,8 +319,11 @@ You need to configure two ASNs:
313319

314320
If you already have set up your Cloudflare account ASN, you can skip steps two and three below.
315321

316-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
317-
2. Go to **{props.productName}** > **Configuration** > **BGP configuration**.
322+
1. In the Cloudflare dashboard, go to {props.productName}'s **Configuration** page.
323+
324+
<DashButton url={props.dashButtonPath} />
325+
326+
2. Go to **BGP configuration**.
318327
3. In **CF Account ASN**, enter Cloudflare's ASN.
319328
4. Go to **Interconnects**.
320329
5. Find the Direct CNI interconnect you want to configure with BGP > select the **three dots** next to it > **Configure BGP**.

0 commit comments

Comments
 (0)