ServerCentral supports an industry-leading range of Border Gateway Protocol (BGP) communities that allow you to have extensive routing control.
BGP communities are 32-bit values which are attached to a BGP route in order to carry additional information about that route. In common usage, this 32-bit value is split into two 16-bit values seperated by a colon (:). The first half typically represents the ASN—the globally unique number used to identify an Autonomous System—that the community "belongs to" or "targets." The second half typically represents the proprietary data.
Informational Communities are BGP communities added by ServerCentral, in order to convey information about how and where the route was initially learned by our network. These communities will always have 5 digits in the second half, and are constructed in the following format:
23352:TCRPP
T - The type of relationship that the route was learned through.
C - The continent where the route was learned.
R - The region of the continent where the route was learned.
PP - The POP code (city) where the route was learned.
| Value | Relationship | Continent | Region |
| 0 | - | All | All |
| 1 | Transit | North America | North-West |
| 2 | Public Peer | Europe | North |
| 3 | Private Peer | Asia | North-East |
| 4 | Customer | Australia | West |
| 5 | Internet | South America | Central |
| 6 | - | Africa | East |
| 7 | - | Middle East | South-West |
| 8 | - | - | South |
| 9 | - | - | South-East |
| City Code | City/POP Identifier | City State/Province, Country | |
| 11 | IAD | Ashburn VA, United States | |
| 12 | NYC | New York NY, United States | |
| 13 | SJC | San Jose CA, United States | |
| 14 | PAO | Palo Alto CA, United States | |
| 15 | SFO | San Francisco CA, United States | |
| 16 | ORD | Chicago IL, United States | |
| 17 | DFW | Dallas/Forth Worth TX, United States | |
| 18 | LAX | Los Angeles CA, United States | |
| 19 | EWR | Newark NJ, United States | |
| 20 | AMS | Amsterdam, Netherlands | |
| 21 | TKO | Tokyo, Japan | |
| 22 | LHR | London, United Kingdom | |
| 23 | ATL | Atlanta GA, United States | |
| 24 | PHX | Phoenix AZ, United States | |
| 25 | MTL | Montreal QC, Canada | |
| 26 | TOR | Toronto ON, Canada | |
| 27 | IAH | Houston TX, United States | |
| 28 | SEA | Seattle WA, United States | |
| 29 | DEN | Denver CO, United States | |
| 30 | MIA | Miami FL, United States | |
| 31 | SLC | Salt Lake City UT, United States | |
| 32 | FRA | Frankfurt, Germany | |
| 33 | CDG | Paris, France | |
| 34 | BOS | Boston MA, United States | |
Action Communities are optional communities which may be added by ServerCentral customers, to control route attributes or to control how routes are exported to other networks. These communities may also be targetted to specific peer ASNs, specific locations (by continent, region, or city), or specific classes of neighbors (transits, peers, or customers). Action Communities are always 4 digits in length in the second half and have the following structure:
#####:A0CR
-or-
#####:A1PP
##### The Target ASN
A - The action code to be performed
C - The target continent (same table as above)
R - The target region (same table as above)
PP - The target POP (city code, same table as above)
| Action Code | Action |
| 1 | Prepend AS-PATH with 23352 on export |
| 2 | Prepend AS-PATH with 23352 23352 on export |
| 3 | Prepend AS-PATH with 23352 23352 23352 on export |
| 4 | Prepend AS-PATH with 23352 23352 23352 23352 on export |
| 5 | Set Multi-Exit Discriminator (MED) to 0 on export |
| 6 | Do not export |
| 9 | Override a Do Not Export (action code 6) |
| Target ASN | Meaning |
| 23352 | Apply action to all neighbor ASNs |
| ##### | Apply action to a specific ASN ##### |
| 65001 | Apply action to all Transits |
| 65002 | Apply action to all Peers |
| 65003 | Apply action to all Customers |
Action Community Examples
The following examples illustrate how to use Action Community tags with multiple criteria:
| Community | Meaning |
| 23352:1000 | Prepend once to all BGP neighbors globally |
| 23352:2010 | Prepend twice to all BGP neighbors in North America |
| 23352:3111 | Prepend three times to all BGP neighbors in Ashburn VA |
| 3549:6000 | Do not export to AS3549/Global Crossing globally |
| 65001:6020 | Do not export to any IP Transit neighbors in Europe |
Local Preference Communities are values which influence the best-path selection of BGP prefixes. The local-preference attribute is not transitive, so this applies only to path selection within the ServerCentral network. A value of 50 will create a "backup route" that is never used or propagated to the rest of the Internet, so long as any other path is heard for the prefix in question. This route will only become active if no other route is heard.
| Community | Local Preference Setting |
Notes |
| 23352:50 | Set local-preference to 50 | Backup route only |
| 23352:100 | Set local-preference to 100 | Default transit route |
| 23352:150 | Set local-preference to 150 | Less than peer, more than transit |
| 23352:200 | Set local-preference to 200 | Default peer route |
| 23352:250 | Set local-preference to 250 | Less than customer, more than peer |
| 23352:300 | Set local-preference to 300 | Default customer route |
| 23352:350 | Set local-preference to 350 | Preferred above other customers |
These are miscellaneous communities which do not fit into any of the formats above. The Multihomed Customer Advisory Tag is used to automatically indicate any known issues, such as congestion or routing problems, so that multihomed customers can match this community and divert traffic to another path, if possible.
| Community | Meaning |
| 23352:69 | Multihomed Customer Advisory Tag |
| 23352:666 | Null route all traffic to this prefix (requires a pre-established session with a BGP blackhole server) |
| 23352:998 | Within the ServerCentral network, do not export the prefix outside of the current continent |
| 23352:999 | Within the ServerCentral network, do not export the prefix outside of the current region |
| 23352:5000 | Anycast |