BGP COMMUNITY STRING ACCEPTED FROM AS15756 CUSTOMERS

BGP Community String Action

15756:666 Route traffic to Null
15756:699 Set blackhole community for uplinks
15756:911 Set local pref to 50 (backup)
15756:200x Set prepend for russian peers
16756:300x Set prepend for uplinks

Where x is number of prepends (x=1,2,4,6) or do NOT announce (x=9).

 

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

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

Phone: +7 095 3632252
Fax : +7 095 3632252

Trouble:

Routing and peering issues: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
SPAM issues: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Mail and News issues: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Customer support: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Hosting information: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

Add as favourites (33) | Views: 249 | 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 ;