BGP Community String for Polish Telecom AS5617

Home

Routing

BGP Community Attributes List

BGP Community String for Polish Telecom AS5617

Google Translation

Main Menu

Login Form

Sections

Latest Articles

BGP Communities used in AS5617

5617:103 - prefix is not announced to foreign peers

We do not accept all RFC1997 BGP communities (no-export etc.)

BGP communities for specific link are 5617:ab0x :

x=0 for "do not advertise"; x=1,2,3 for "prepend 1,2,3 times"

for AS1299 Telia 5617:110x
for AS5511 OpenTransit 5617:120x
for AS3320 T-Systems 5617:130x
for AS8501 POL34: 5617:210x
for AS16283 Lodman: 5617:220x
for AS8308 NASK: 5617:230x
for AS8664 ICM: 5617:240x
not used 5617:250x
for AS8890 Kampus Ochota: 5617:260x
for AS8364 Pozman: 5617:270x
for AS8508 Silweb: 5617:280x
for AS8970 WASK: 5617:290x

Our looking-glass: http://lg.tpnet.pl

In case of routing problems,
please send mail to registry contact.

This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

In case of abuse (intrusion attempts, hacking, spamming or other unaccepted behavior) from TP S.A. address space, please mail only to: abuse-mailbox. Notifications sent to other mailboxes will be left without any action. abuse phone: +48 22 8871788

Applying BGP Community string with sample configuration

1. Get the latest BGP community string from your ISP/upstream provider or check new.CiscoNET.com web site.

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

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 (19) | Views: 306 | E-mail