What BGP communities do the FD-IX route servers support?

What BGP communities do the FD-IX route servers support?

Announcement control via BGP communities

Routes tagged with the NO_EXPORT or NO_ADVERTISE communities received by the route server are

propagated to other clients with those communities unaltered.


Function 

Standard 

Extended 

Large

Do not announce to any client 

0:13681 

rt:0:13681 

13681:0:13681


Announce to peer, even if tagged with the previous community

13681:peer_as 

rt:13681:peer_as 

13681:13681:peer_as

Do not announce to peer 

0:peer_as 

rt:0:peer_as 

13681:0:peer_as


Prepend the announcing ASN once to peer 

65504:peer_as 

rt:65504:peer_as 

13681:65504:peer_as


Prepend the announcing ASN twice to peer 

65505:peer_as 

rt:65505:peer_as 

13681:65505:peer_as


Prepend the announcing ASN thrice to peer 

65506:peer_as 

rt:65506:peer_as 

13681:65506:peer_as


Prepend the announcing ASN once to any 

65501:13681 

rt:65501:13681 

13681:65501:13681


Prepend the announcing ASN twice to any 

65502:13681 

rt:65502:13681 

13681:65502:13681


Prepend the announcing ASN thrice to any 

65503:13681 

rt:65503:13681 

13681:65503:13681


Add NO_EXPORT to any 

65507:13681 

rt:65507:13681 

13681:65507:13681


Add NO_ADVERTISE to any 

65508:13681 

rt:65508:13681 

13681:65508:13681


Function Standard Extended Large

Add NO_EXPORT to peer Add NO_ADVERTISE to peer 65509:peer_as rt:65509:peer_as 13681:65509:peer_as

65510:peer_as rt:65510:peer_as 13681:65510:peer_as

    • Related Articles

    • Indianapolis FD-IX Connection Guide

      Table of Contents 1. Overview 2. Prerequisites 3. Connection Process 3.1 Order Cross-Connect 3.2 IP Assignment 3.3 Interface Configuration 4. BGP Configuration 4.1 Route Server Details 4.2 Cisco Configuration 4.3 Juniper Configuration 4.4 Arista ...

    • Route Server general behaviors

      The following are two of the route server general behaviors. Route server ASN is not prepended to the AS_PATH of routes announced to clients (RFC7947 section 2.2.2.1 (https://tools.ietf.org/html/rfc7947#section-2.2.2.1)). Route server does implement ...

    • What are the Reject reasons BGP is not working correctly?

      Reject reasons The following values are used to identify the reason for which routes are rejected. This is mostly used for troubleshooting, internal reporting purposes, looking glasses or in the route server log files. ID Reason 0 Generic code: the ...

    • Filtering Policy: AS_PATH attribute

      AS_PATH attribute Routes whose AS_PATH is longer than 24 ASNs are rejected. The left-most ASN in the AS_PATH of any route announced to the route server must be the ASN of the announcing client. Routes whose AS_PATH contains private or invalid ASNs ...

    • What a LOA Is in a Data Center

      If you order a cross-connect in a data center, you will hear one term fast: LOA. LOA stands for Letter of Authorization. It is the data center’s written proof that you approve a physical connection between two parties. Think of it as the bouncer at ...