BGP Community String for Telecomplete AS6320

   March 15, 2007  Leave a comment

Attention

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

BGP COMMUNITIES FOR AS6320 TRANSIT CUSTOMERS


BGP Community String

6320:1000x Announce to all
6320:1100x Announce to all peers
6320:1110x Announce to all peers in London
6320:1111x Announce to all private peers in London
6320:1112x Announce to all peers at LINX
6320:1113x Announce to all peers at XCHANGEPOINT
6320:1114x Announce to all peers at LIPEX
6320:1115x Announce to all peers at XchangePoint-LoNAP Shared LAN
6320:1120x Announce to all peers in Manchester
6320:1121x Announce to all private peers in Manchester
6320:1122x Announce to all peers at MaNAP
6320:1123x Announce to all peers at MCIX
6320:1131x Announce to all peers at AMS-IX
6320:1132x Announce to all peers at FreeIX
6320:1141x Announce to all peers at NYIIX
6320:1197x Announce to all peering with 3549
6320:1198x Announce to all peering with 6453
6320:1199x Announce to all peering with 7911
6320:1200x Announce to all transit
6320:1210x Announce to all transit in London
6320:1211x Announce to all transit with Telia
6320:1212x Announce to all transit with Teleglobe
6320:1220x Announce to all transit in Manchester
6320:1221x Announce to all transit with Level3


**Where x is prepend 0,1,2 or do NOT announce x = 9

BGP COMMUNITIES APPLIED AT INGRESS


BGP Communities Ingress

6320:21000 – Peer
6320:21100 – Peers in London
6320:21110 – Peers in London Private
6320:21120 – Peers in LINX
6320:21130 – Peers in XCHANGEPOINT
6320:21140 – Peers in LIPEX
6320:21150 – Peers in XCHANGEPOINT-LoNAP Shared LAN
6320:21200 – Peers in Manchester
6320:21210 – Peers in Manchester Private
6320:21230 – Peers in MCIX
6320:21310 – Peers in AMS-IX
6320:21320 – Peers in FreeIX
6320:21410 – Peers in NYIIX
6320:22000 – Transit
6320:22100 – Transit in London
6320:22110 – Transit Telia
6320:22120 – Transit Teleglobe
6320:22200 – Transit Manchester
6320:22210 – Transit Level3
6320:23000 – Customer
6320:23010 – Customer All Routes
6320:23020 – Customer Partial Routes
6320:24000 – Local

** ABUSE ** Please send to [email protected]

Please ensure before sending in abuse emails that we are responsible for the source netblock


** PEERING ** Please send to [email protected]

** Trouble ** [email protected]


Telecomplete may peer with any non-customer network at the following locations:

LINX (LAN1) – 195.66.224.139
(LAN2) – 195.66.226.139
(LAN2) 195.66.226.115
XchangePoint – 217.79.160.58
217.79.161.58
XPE/LoNAP – 195.47.243.71
Lipex – 193.109.219.110
MCIX – 85.159.209.17
AMSIX – 195.69.144.178
FreeIX – 213.228.3.164
NYIIX – 198.32.160.125

We may also private peer, please email for info.

 

 


Applying BGP Community string with sample configuration

 

1. Get the latest BGP community string from your ISP/upstream provider or check www.ShowipBGP.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

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.

 

Leave a Reply