BGP Community String for Primorye AS12332

Attention

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

 

BGP Communities applied at ingress

12332:20000 – All Links

12332:21000 – Upstreams
12332:21010 – RTComm
12332:21020 – Transtelecom

12332:22000 – Peers
12332:22010 – Equant
12332:22020 – VNTC
12332:22030 – FESU
12332:22040 – RTK-Primorye

 

BGP Communities for AS12332 Customers

12332:1000x – All Links

12332:1100x – Upstreams
12332:1101x – RTComm AS8342
12332:1102x – Transtelecom AS20485

12332:1200x – Peers
12332:1201x – Equant AS2854
12332:1202x – VNTC AS21332
12332:1203x – FESU AS12999
12332:1204x – RTK-Primorye AS21105


Where x is prepend 12332 0,1,2,4 or 6 times or do NOT announce x = 9
Other 12332:* communities are deleted
We DO pass communities to Upstreams
None of communities are accepted from Upstreams and Peers
AS12332 does not accept or announce prefixes longer than /24 (included)

 

 

Applying BGP Community string with sample configuration

 

1. Get the latest BGP community string from your ISP/upstream provider or check www.ShowipBGP.com.

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


 

Contact for RU.PRIMORYE – Network Operation Center

phone: +7 4232 406040
fax: +7 4232 406029
Abuse contact: [email protected]

Leave a Reply