Skip to content

Commit 5820a84

Browse files
refined language
1 parent c2d7716 commit 5820a84

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/content/partials/network-interconnect/bgp-peering.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,15 @@ BGP peering sessions can advertise reachable prefixes to a peer, and withdraw pr
2121

2222
## Tunnel health checks
2323

24-
You need to enable <a href={props.productPath}>tunnel health checks</a> alongside BGP. This is essential to determine if a specific Cloudflare datacenter is reachable from a customer router or not. Tunnel health checks will modify the route's priorities for dynamically learned BGP routes, like what happens for static routes.
24+
You need to enable <a href={props.productPath}>tunnel health checks</a> alongside BGP. This is essential to determine if a specific Cloudflare datacenter is reachable from a customer router or not. Tunnel health checks will modify the route's priorities for dynamically learned BGP routes.
2525

2626
{props.productName} customers should configure unidirectional health checks.
2727

2828
## How to set up BGP peering
2929

30-
BGP peering if available to Magic WAN/Transit customers with Direct CNI as an on-ramp. If your network is set up with GRE or IPsec tunnels, you cannot use BGP peering
30+
:::caution
31+
BGP peering is only available to Magic WAN/Transit customers with Direct CNI as an on-ramp. If your network is set up with GRE or IPsec tunnels, you cannot use BGP peering.
32+
:::
3133

3234
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
3335
2. Go to **Interconnects**.

0 commit comments

Comments
 (0)