You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/partials/networking-services/magic-transit/get-started.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -145,7 +145,7 @@ Refer to [Maximum transmission unit and maximum segment size](/magic-transit/ref
145
145
{props.magicWord==="Learning Path"&& (
146
146
<>
147
147
<AnchorHeadingtitle="BGP for Magic Transit prefix advertisement control (optional)"depth={2} />
148
-
<p>If you want to use BGP for prefix advertisement control then you need to let the account team know the IPs and ASN for your customer premises equipment (CPE) to use for the BGP peerings. You should allow around five working days for Cloudflare to add this to our Route Reflectors.</p>
148
+
<p>If you want to use <ahref="/magic-transit/how-to/advertise-prefixes/#border-gateway-protocol-bgp-control-for-advertisements-optional">BGP for prefix advertisement control</a> then you need to let the account team know the IPs and ASN for your customer premises equipment (CPE) to use for the BGP peerings. You should allow around five working days for Cloudflare to add this to our Route Reflectors.</p>
0 commit comments