Skip to content

Commit 234e7d3

Browse files
added as prepending
1 parent e0a6369 commit 234e7d3

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

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

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,31 @@ When BGP advertises a route, it is automatically added to the Magic routing tabl
5757

5858
Additionally, when multiple BGP routes exist with the same prefix length and priority, traffic is distributed across them using <a href={props.ecmp}>equal-cost multi-path (ECMP) routing</a>.
5959

60+
### BGP communities and AS prepending
61+
62+
Cloudflare supports traffic engineering via BGP communities and AS prepending. You can use these traffic routing techniques to set route priorities and perform traffic engineering across multiple interconnects.
63+
64+
The default BGP route priority is `100`. This base priority can be adjusted using communities. For example, when a route is tagged with the community `13335:60010` its priority is set to `10`. This makes it a higher priority than the default of `100` because lower numeric values are preferred. This operates similarly to local preference communities. However, unlike local preference, these combine numerically with AS prepends as follows.
65+
66+
Additionally, for each AS prepending — where the customer ASN is added multiple times to the AS Path — an additional `10` is added to the route's base priority. By increasing the priority number, the route is less preferred.
67+
68+
In summary:
69+
70+
- Default BGP priority is `100`
71+
- You can use communities to influence routing priorities
72+
- When using AS prepending with communities, Cloudflare combines both values to determine the new route priority. For example, if a route is tagged with `13335:60010`, the base priority is set to `10`. If you prepend your ASN twice, Cloudflare adds `10` for each prepend, resulting in a final route priority of `30`.
73+
74+
The community values supported for setting base route priority are:
75+
- `13335:60010` — set base Magic route priority to `10`
76+
- `13335:60050` — set base Magic route priority to `50`
77+
- `UNSET` — set base Magic route priority to `100`
78+
- `13335:60150` — set base Magic route priority to `150`
79+
- `13335:60200` — set base Magic route priority to `200`
80+
- `13335:60901` — set base Magic route priority to `501000`
81+
- `13335:60902` — set baseMagic route priority to `1001000`
82+
83+
It is considered a misconfiguration to set multiple base priority communities in the same prefix update message. In this situation the highest priority (lowest integer value) is preferred.
84+
6085
## BGP timers and settings
6186

6287
Cloudflare uses the timers as described below. These are not configurable:

0 commit comments

Comments
 (0)