BGP Community String for LINX AS8714

Tweet

Attention

This BGP Community string information might be outdated. Please contact LINX AS8714 to get more recent one. This BGP communites is ONLY for the customer who has BGP with LINX AS8714. www.ipbalance.com is not maintaining this BGP Community string.

AS8714 is used for the LINX Route Server.
For LINX members to connect to the route server use of BGP Communities must be employed to control outgoing information via the route server. For members to enforce policy routes must be
tagged with either of the following :

This AS has no route policy registered due the nature of how the route servers operate

For more information pleasae contact [email protected]

Please DO NOT send spam or hack complaints to us where a trace to the source (but not the Received: headers) reveals one of: 195.66.224.x or 195.66.226.x
As we are not the origin of the spam/hack or the owner of these routers, we CANNOT usually take any action. Please DO NOT just e-mail all contacts or we’ll all ignore it. Complaints go to the ISP at the source network, not us.
Please see: https://www.linx.net/help/faq/

 

 

Applying BGP Community string with sample configuration

2. Pick the best BGP community string for your traffic shaping plan (mainly incoming traffic). Most of ISPs are providing BGP community string with local preference and AS prepending option. Cannot tell which one is better than the other. It will depend on your global traffic shaping plan.

3. Follow the below commands ( Cisco only )

The below Sample configuration will tag the 10.0.0.0/24 route with [ISP AS]:120 or [ISP AS]:3 and will not tag any other routes.

router#config t
router(config)#ip bgp-community new-format
router(config)#access-list 10 permit 10.0.0.0 0.0.0.255
router(config)#access-list 10 deny any

router(config)#route-map [to-ISP] permit 10
router(config-route-map)#match ip address 10
router(config-route-map)#set community [ISP AS]:120 <—- using Local Preference

or

router(config-route-map)#set community [ISP AS]:3 <——- using AS prepending
router(config-route-map)#route-map [to-ISP] permit 20
router(config-route-map)#exit

router(config)#router bgp [xxxx] <——————————- xxxx = customer’s ASN
router(config-router)#neighbor x.x.x.x send-community
router(config-router)#neighbor x.x.x.x route-map [to-ISP] out
router(config-router)#exit
router(config)#exit
router#copy running-config startup-config

4. And then, go to www.RouteServer.org and pick one of route server on the map to see your announcement. If you are using AS prepending option, you will see your AS prepends on route servers. Sometime you might not see your route with particular ISP path.
In most of case it might not be any routing problem, just the route path was dropped at somewhere by BGP best path selection scheme. Try Oregon route server, if you can see your route. The Oregon route server is providing many possible and available paths between BGP speakers and neighbors.
If you don’t see your route on there? check other route servers and also check your
BGP configuration. You might need to contact your upstream provider to check what they are learning BGP route from you.