Tweet

Attention

This BGP Community string information might be outdated. Please contact Radio-MSU AS2683 to get more recent one. This BGP communites is ONLY for the customer who has BGP with Radio-MSU AS2683. ipbalance.com is not maintaining this BGP Community string.

BGP Community String

BGP Communities usage on outgoing announcements

 

BGP Community String	Description
2683:1000	Don’t announce to M9-IX
2683:1010	Announce to M9-IX with +1 prepend
2683:1020	Announce to M9-IX with +2 prepend
2683:1050	Announce to M9-IX with +5 prepend
2683:2000	Don’t announce to RBNet
2683:2010	Announce to RBNet with +1 prepend
2683:2020	Announce to RBNet with +2 prepend
2683:2050	Announce to RBNet with +5 prepend
2683:3000	Don’t announce to DFN
2683:3010	Announce to DFN with +1 prepend
2683:3020	Announce to DFN with +2 prepend
2683:3050	Announce to DFN with +5 prepend

Contact Info

phone: +7 095 9328880
phone: +7 095 9395877
fax-no: +7 095 9328974

trouble: Radio-MSU NOC is reachable 09:00-21:00 on MSK working days.
trouble: For problems with routing contact (5 x 12):
trouble: Radio-MSU Network Operation Center:
trouble: – [email protected]
remarks: trouble: – +7 095 932-88-80
trouble: – +7 495 932-88-80
remarks: trouble: – +7 095 939-58-77
trouble: – +7 495 939-58-77
http://www.radio-msu.net
modified for Russian phone area changes
phone: +7 095 932 8974
phone: +7 095 939 5877
fax-no: +7 095 932 8974
modified for Russian phone area changes

 

 

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