BGP Community String definitions

------------------------------------------------

8708:80 Set local preference to 80 inside RDS
8708:120 Set local preference to 120 inside RDS (*)
8708:1000 Advertise the prefix (*)
8708:1001 Prepend 1*8708 when advertising (*)
8708:1002 Prepend 2*8708 when advertising (*)
8708:1003 Prepend 3*8708 when advertising (*)
8708:2001 Prepend 1*8708 when announcing to domestic peers (*)
8708:2002 Prepend 2*8708 when announcing to domestic peers (*)
8708:2003 Prepend 3*8708 when announcing to domestic peers (*)

(*) only customers can use this BGP community

Default local preference

Customer 110
Peers 100
Backup 80
Peering requests at http://www.rdsnet.ro/peering/
We are present at: DE-CIX, AMS-IX, LINX, SFINX, MIX, BIX

Contact Us

Call center (24x7) +40 21 30 10 888
NOC (24x7): This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Peering issues: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

ABUSE CONTACT: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it IN CASE OF HACK ATTACKS,
ILLEGAL ACTIVITY, VIOLATION, SCANS, PROBES, SPAM, ETC.

Questions to the proper department ( This e-mail address is being protected from spam bots, you need JavaScript enabled to view it ) or to your own ISP, police, etc.

<font size="2"><span style="color: rgb(255, 0, 0); font-family: Tahoma;"> 
</span><span style="font-family: Tahoma;"></span>
</font>

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.CiscoNET.com 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.

Add as favourites (35) | Views: 375 | E-mail

Be first to comment this article

Only registered users can write comments.
Please login or register.

Powered by AkoComment Tweaked Special Edition v.1.4.3

---

Please share this article with ;