CiscoNet.com - BGP Community String for TELE2UTA AS8437

Home

Routing

BGP Community Attributes List

BGP Community String for TELE2UTA AS8437

Google Translation

Main Menu

Login Form

Yahoo Network

Merchant Solutions

Latest Articles

BGP Communities tagged on inbound routes

8437:1000 Customer Routes send peering requests to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it

TELE2UTA - Network Operation Center
mail: This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
phone: +43 1 9009 3333 or 0800-882 662
fax: +43 1 9009 3599

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, OTHER VIOLATIONS, SCANS,PROBES, SPAM, ETC.

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 (38) | Views: 286 | E-mail