BGP Community String for Ebone France AS13299

Attention

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

 

BGP Community String List

13299:1010 Paris (PAR3)
13299:1020 Bordeaux
13299:1030 Marseille
13299:1040 Lille
13299:1050 Lyon
13299:1060 Strassbourg
13299:1070 Toulouse
13299:1080 Paris (PAR5)
13299:1090 Paris (PAR6)

 

BGP Communities tagged on inbound routes:

BGP Community Definition

13299:666 Route received from other provider with peering agreement with AS13299.
13299:1755 Route received from Ebone upstream.
13299:2010 Route received from peering partner at SFINX

BGP Communities to control traffic (settable by customers.)

13299:1000 Only announce to AS1755 and not beyond
13299:2011 Prepend once to peering partners at SFINX
13299:2012 Prepend twice to peering partners at SFINX
13299:2019 do not announce to peering partners at SFINX

 

 

Applying BGP Community string with sample configuration

 

1. Get the latest BGP community string from your ISP/upstream provider or check www.ShowipBGP.com.

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.


========================================================
Applied Route Flap Damping Policy conformant to RIPE-210
<<<<<http://www.ripe.net/docs/ripe-210.html>>>>>
========================================================
***
*** Ebone/KPNQwest filed for bankruptcy on June 3rd 2002
*** and operations shutdown on July 2nd.
***
*** Queries for changes on RIPE objects related to Ebone
*** will _only_ be answered on EMAIL listed below on
*** a best effort basis. (listed phonenr is bogus)
***

 

peering request: [email protected]
abuse reports: [email protected]

 

 

 

Leave a Reply