[Static / BGP Routes] Consolidates and reorganizes info (#21782)

* edited static routes partial

* added bgp

* deleted bgp peering partial

* changed partial from static routes to routes

* changed name to configure routes

* added bgp

* ecmp

* content

* scoping routes

* mt info

* bgp subsection

* refined text

* added content

* changed partial name

* deleted bgp peering pages

* changed path

* added params

* corrected param

* added links

* added links

* removed text

* imported components

* added vars

* removed var

* removed var

* indentation

* removed extra imports

* corrected param

* added info

* corrected params

* refined anchor

* removed extra space

* added param

* corrected link

* refined text

* refined params

* refined link

* refined text

* corrected link

* corrected links

* monospaced

* corrected link

* corrected link

* changed order

* corrected link

* corrected link

* corrected links

* corrected links

* refined allowed ip ranges

* added mt redirects

* mwan redirects

* corrected static routes links

* bgp links

* refined description

* added new limitation

* removed extra space

* added link

* reordered graph texts

* refined names

* corrected link

Author: marciocloudflare

public/__redirects

@@ -804,7 +804,7 @@
 # magic-transit
 /magic-transit/magic-firewall/ /magic-firewall/ 301
 /magic-transit/set-up/onboarding/ /magic-transit/get-started/ 301
-/magic-transit/set-up/provide-configuration-data/assign-tunnel-route-priorities/ /magic-transit/how-to/configure-static-routes/ 301
+/magic-transit/set-up/provide-configuration-data/assign-tunnel-route-priorities/ /magic-transit/how-to/configure-routes/ 301
 /magic-transit/set-up/requirements/ /magic-transit/get-started/ 301
 /magic-transit/get-started/configure-tunnels/specify-gre-tunnel-endpoints/ /magic-transit/how-to/configure-tunnels/ 301
 /magic-transit/about/health-checks/ /magic-transit/reference/tunnel-health-checks/ 301
@@ -814,6 +814,8 @@
 /magic-transit/prerequisites/ /magic-transit/get-started/ 301
 /magic-transit/how-to/ /magic-transit/how-to/configure-tunnels/ 301
 /magic-transit/reference/ /magic-transit/reference/anti-replay-protection/ 301
+/magic-transit/how-to/configure-static-routes/ /magic-transit/how-to/configure-routes/ 301
+/magic-transit/how-to/bgp-peering/ /magic-transit/how-to/configure-routes/ 301
 
 # magic-wan
 /magic-wan/tutorials/ipsec/ /magic-wan/reference/tunnels/#ipsec-tunnels 301
@@ -837,6 +839,8 @@
 /magic-wan/configuration/common-settings/view-analytics/ /magic-wan/analytics/ 301
 /magic-wan/prerequisites/ /magic-wan/get-started/ 301
 /magic-wan/configuration/common-settings/check-tunnel-health-dashboard/ /magic-wan/configuration/common-settings/tunnel-health-checks/ 301
+/magic-wan/configuration/manually/how-to/configure-static-routes/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
+/magic-wan/configuration/manually/how-to/bgp-peering/ /magic-wan/configuration/manually/how-to/configure-routes/ 301
 
 # notifications
 /fundamentals/notifications/ /notifications/ 301

src/content/docs/magic-transit/cloudflare-ips.mdx

@@ -13,7 +13,7 @@ In addition to using Magic Transit with your own IP address, you can use Magic T
 To protect your network using a Cloudflare IP address, contact your account manager. After receiving your IP address, you will need to:
 
 - [Create a tunnel](/magic-transit/how-to/configure-tunnels/).
-- [Set up static routes](/magic-transit/how-to/configure-static-routes) or [BGP peering](/magic-transit/how-to/bgp-peering/).
+- [Set up static routes](/magic-transit/how-to/configure-routes/#configure-static-routes) or [BGP peering](/magic-transit/how-to/configure-routes/#configure-bgp-routes).
 - [Configure health checks](/magic-transit/how-to/run-endpoint-health-checks).
 - Confirm [tunnel](/magic-transit/how-to/tunnel-health-checks/) and endpoint health checks were properly configured.
 - Update your infrastructure at your own pace to use the allocated Cloudflare IPs.

src/content/docs/magic-transit/get-started.mdx

@@ -99,7 +99,7 @@ Refer to [Maximum transmission unit and maximum segment size](/magic-transit/ref
 
 ## 4. Configure static routes or BGP peering
 
-Configure [static routes](/magic-transit/how-to/configure-static-routes/) or [BGP peering](/magic-transit/how-to/bgp-peering/) to route traffic from Cloudflare's global network to your locations.
+Configure [static routes](/magic-transit/how-to/configure-routes/#configure-static-routes) or [BGP peering](/magic-transit/how-to/configure-routes/#configure-bgp-routes) to route traffic from Cloudflare's global network to your locations.
 
 ## 5. Run pre-flight checks
 

src/content/docs/magic-transit/how-to/advertise-prefixes.mdx

@@ -89,12 +89,12 @@ When you withdraw a prefix using BGP, you must ensure the prefix is withdrawn ac
 
 ### BGP peering
 
-If you use Direct CNI as a way to on-ramp your network traffic to Magic Transit, refer to [BGP peering](/magic-transit/how-to/bgp-peering/) to learn how to use BGP to handle traffic routing between Cloudflare and your network. Note that this is a different option to using BGP as a means to control the advertisement status of your prefix.
+If you use Direct CNI as a way to on-ramp your network traffic to Magic Transit, refer to [BGP information](/magic-transit/reference/traffic-steering/#bgp-information) to learn how to use BGP to handle traffic routing between Cloudflare and your network. Note that this is a different option to using BGP as a means to control the advertisement status of your prefix.
 
 
 ### Regional settings
 
-Magic Transit requires static routing to steer traffic from Cloudflare's network over one of your configured tunnel off-ramps (for GRE and IPsec tunnels). For CNI, both static routing and [BGP](/magic-transit/how-to/bgp-peering/) options are available. Currently, advertisement of routes for traffic engineering purposes is not supported. As a best practice to reduce last-hop latency, you should consider scoping your routes regionally. The default setting for static route regions is **All Regions**. Refer to [Configure static routes](/magic-transit/how-to/configure-static-routes/) for more information.
+Magic Transit requires static routing to steer traffic from Cloudflare's network over one of your configured tunnel off-ramps (for GRE and IPsec tunnels). For CNI, both static routing and BGP options are available. Currently, advertisement of routes for traffic engineering purposes is not supported. As a best practice to reduce last-hop latency, you should consider scoping your routes regionally. The default setting for static route regions is **All Regions**. Refer to [Scoping routes to specific regions](/magic-transit/reference/traffic-steering/#scoping-routes-to-specific-regions) for more information.
 
 ## Example router configurations
 

src/content/docs/magic-transit/how-to/bgp-peering.mdx

@@ -0,0 +1,25 @@
+---
+pcx_content_type: how-to
+title: Configure routes
+sidebar:
+  order: 2
+head: []
+description: Magic Transit uses a static configuration to route your traffic through anycast tunnels from Cloudflare's global network to your locations. If you are connected through Direct CNI you also have access to BGP peering. Learn how to configure routing.
+
+---
+
+import { Render } from "~/components"
+
+<Render
+	file="routing/configure-routes"
+	product="networking-services"
+	params={{
+		magicWord: "Magic Transit",
+		trafficSteeringPage: "/magic-transit/reference/traffic-steering/",
+		productName: "Magic Transit",
+		tunnelEndpoints: "/magic-transit/how-to/configure-tunnels/",
+		chooseWeights: "/magic-transit/reference/traffic-steering/#set-priority-and-weights-for-static-routes",
+		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.",
+		productGatewayOrEgress: "Magic Transit with Egress"
+	}}
+/>

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

@@ -31,6 +31,4 @@ import { GlossaryTooltip, Render } from "~/components";
 
 ## Next steps
 
-Now that you have set up your tunnel endpoints, you need to configure <GlossaryTooltip term="static route" link="/magic-transit/how-to/configure-static-routes/">static routes</GlossaryTooltip> to route your traffic through Cloudflare.
-
-If you are connecting to Cloudflare through a [Direct CNI connection](/network-interconnect/express-cni/), you can [configure BGP routing](/magic-transit/how-to/bgp-peering/) instead.
+Now that you have set up your tunnel endpoints, you need to configure routes to route your traffic through Cloudflare. Refer to [Configure routes](/magic-transit/how-to/configure-routes/) to learn more about static routing and BGP peering (only available through Direct CNI connection).

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

@@ -39,7 +39,7 @@ Magic Transit steers traffic along tunnel routes based on priorities you define
 Use Cloudflare-owned IP addresses if you want to protect a smaller network and do not meet Magic Transit's `/24` prefix length requirements.
 </Feature>
 
-<Feature header="BGP peering" href="/magic-transit/how-to/bgp-peering/">
+<Feature header="BGP peering" href="/magic-transit/how-to/configure-routes/#configure-static-routes">
 Use BGP peering between your networks and Cloudflare to automate the process of adding or removing networks and subnets, and take advantage of failure detection and session recovery features.
 </Feature>
 

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

@@ -14,9 +14,13 @@ import { Render } from "~/components";
 	file="reference/traffic-steering"
 	product="networking-services"
 	params={{
-		productName: "Magic Transit",
-		greURL: "/magic-transit/reference/tunnels/",
-		staticRoutesURL: "/magic-transit/how-to/configure-static-routes/",
-		ipsecURL: "/magic-transit/reference/tunnels/#ipsec-tunnels",
+  	magicWord: "Magic Transit",
+  	productName: "Magic Transit",
+  	greIpsecReferenceURL: "/magic-transit/reference/tunnels/",
+  	createStaticRoute: "/magic-transit/how-to/configure-routes/#create-a-static-route",
+  	editStaticRoute: "/magic-transit/how-to/configure-routes/#edit-a-static-route",
+  	setupBgpPeering: "/magic-transit/how-to/configure-routes/#set-up-bgp-peering",
+		legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-bidirectional-health-checks",
+		tunnelHCsPage: "/magic-transit/reference/tunnel-health-checks/"
 	}}
 />