Home BGP Tools BGP Community List FLAG Telecom AS15412

FLAG Telecom AS15412 BGP community Strings

Attention

This BGP Community string information might be outdated. Please contact FLAG Telecom AS15412 to get more recent one.  This BGP communites is ONLY for the customer who has BGP with FLAG Telecom AS15412. Showipbgp.com is not maintaining this BGP Community string.

 

The following BGP policy is common to all Flag customers:
 

Prefixes longer than a /24 are not accepted

Prefixes not matching the specified customer import policy are rejected. We accept Route Objects from any Registry mirrored by RADB.

By default we advertise MED == igp metric

RFC1918 and other reserved networks and subnets are not permitted
The following BGP policy is common to all Flag peers:

Prefixes longer than a /24 are not accepted

A max prefix threshold based upon the number of prefixes received, with a percentage headroom, is applied and updated daily. Sessions dropped for this reason are re-checked every two hours.




===============================================
BGP Communities applied at ingress
===============================================
15412:1xxx PoP
15412:1101 New York
15412:1121 Los Angeles
15412:1301 Tokyo
15412:1311 Hong Kong
15412:1316 Singapore
15412:1321 Seoul
15412:1323 Karachi
15412:1326 Taipei
15412:1401 Cairo
15412:1411 Tehran
15412:1421 Alexandria
15412:1501 London
15412:1511 Paris
15412:1521 Madrid
15412:1531 Frankfurt
15412:1542 Amsterdam
===============================================
15412:7xx Customer
15412:701 Aggregate
15412:702 Statically Routed
15412:703 BGP Routed
15412:705 BGP Routed (Suppress MED to upstreams)
===============================================
15412:8xx Peer
15412:800 PRIVATE PEER
15412:801 PAIX
15412:802 NYIIX
15412:803 JPIX
15412:804 KINX
15412:805 HKIX
15412:806 LINX
15412:807 SFINX
15412:808 LAIX
15412:809 AMSIX
15412:810 DECIX
15412:811 XCHANGEPOINT LONDON
15412:813 JPNAP
15412:814 EQUINIX ASHBURN VA
15412:815 XCHANGEPOINT FRANKFURT
15412:816 EQUINIX TOKYO
15412:817 ANY2
15412:818 TERREMARK IX
===============================================
15412:9xx Upstream
15412:902 LEVEL3 AS3356
15412:903 NTT/VERIO AS2914
15412:904 SPRINT AS1239
===============================================
BGP Communities available to customers for traffic engineering
===============================================
Modify LocalPref

15412:80 = 80
15412:200 = 200 (e.g. backup link)
15412:300 = 300
Default (Customer/Transit/Peer) = 250/100/100
===============================================
Suppression/Prepend
===============================================
15412:4100 Do not announce to any upstream
===============================================
15412:4120 Do not announce to LEVEL3 AS3356
15412:4121 Prepend 15412 to LEVEL3 AS3356
15412:4122 Prepend 15412 15412 to LEVEL3 AS3356
===============================================
15412:4130 Do not announce to NTT/Verio AS2914
15412:4131 Prepend 15412 to NTT/Verio AS2914
15412:4132 Prepend 15412 15412 to NTT/Verio AS2914
===============================================
15412:4140 Do not announce to SPRINT AS1239
15412:4141 Prepend 15412 to SPRINT AS1239
15412:4142 Prepend 15412 15412 to SPRINT AS1239
===============================================
15412:4500 Do not announce to FLAG peers
===============================================
15412:4510 Do not announce to PAIX Peers
15412:4511 Prepend 15412 to PAIX Peers
15412:4512 Prepend 15412 15412 to PAIX Peers
===============================================
15412:4520 Do not announce to NYIIX Peers
15412:4521 Prepend 15412 to NYIIX Peers
15412:4522 Prepend 15412 15412 to NYIIX Peers
===============================================
15412:4530 Do not announce to JPIX Peers
15412:4531 Prepend 15412 to JPIX Peers
15412:4532 Prepend 15412 15412 to JPIX Peers
===============================================
15412:4540 Do not announce to KINX Peers
15412:4541 Prepend 15412 to KINX Peers
15412:4542 Prepend 15412 15412 to KINX Peers
===============================================
15412:4550 Do not announce to HKIX Peers
15412:4551 Prepend 15412 to HKIX Peers
15412:4552 Prepend 15412 15412 to HKIX Peers
===============================================
15412:4560 Do not announce to LINX Peers
15412:4561 Prepend 15412 to LINX Peers
15412:4562 Prepend 15412 15412 to LINX Peers
===============================================
15412:4570 Do not announce to SFINX Peers
15412:4571 Prepend 15412 to SFINX Peers
15412:4572 Prepend 15412 15412 to SFINX Peers
===============================================
15412:4580 Do not announce to LAIX Peers
15412:4581 Prepend 15412 to LAIX Peers
15412:4582 Prepend 15412 15412 to LAIX Peers
===============================================
15412:4590 Do not announce to DECIX Peers
15412:4591 Prepend 15412 to DECIX Peers
15412:4592 Prepend 15412 15412 to DECIX Peers
===============================================
15412:4600 Do not announce to AMSIX Peers
15412:4601 Prepend 15412 to AMSIX Peers
15412:4602 Prepend 15412 15412 to AMSIX Peers
===============================================
15412:4610 Do not announce to EQUINIX ASHBURN peers
15412:4611 Prepend 15412 to EQUINIX ASHBURN peers
15412:4612 Prepend 15412 15412 to EQUINIX ASHBURN peers
===============================================
15412:4620 Do not announce to JPNAP peers
15412:4621 Prepend 15412 to JPNAP peers
15412:4622 Prepend 15412 15412 to JPNAP peers
===============================================
15412:4630 Do not announce to XCHANGEPOINT LONDON peers
15412:4631 Prepend 15412 to XCHANGEPOINT LONDON peers
15412:4632 Prepend 15412 15412 to XCHANGEPOINT LONDON peers
===============================================
15412:4640 Do not announce to EQUINIX SINGAPORE peers
15412:4641 Prepend 15412 to EQUINIX SINGAPORE peers
15412:4642 Prepend 15412 15412 to EQUINIX SINGAPORE peers
===============================================
15412:4650 Do not announce to XCHANGEPOINT FRANKFURT peers
15412:4651 Prepend 15412 to XCHANGEPOINT FRANKFURT peers
15412:4652 Prepend 15412 15412 to XCHANGEPOINT FRANKFURT peers
===============================================
15412:4660 Do not announce to EQUINIX TOKYO peers
15412:4661 Prepend 15412 to EQUINIX TOKYO peers
15412:4662 Prepend 15412 15412 to EQUINIX TOKYO peers
===============================================
15412:4670 Do not announce to ANY2 peers
15412:4671 Prepend 15412 to ANY2 peers
15412:4672 Prepend 15412 15412 to ANY2 peers
===============================================
15412:4680 Do not announce to TERREMARK IX peers
15412:4681 Prepend 15412 to TERREMARK IX peers
15412:4682 Prepend 15412 15412 to TERREMARK IX peers
===============================================
15412:4900 Do not announce to any other customer
===============================================


 



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


 

Looking Glass http://ubs.flagtel.com/lg

abuse reports to ipabuse@flagtelecom.com ipabuse@flagtelecom.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it
peering contact peering@flagtelecom.com peering@flagtelecom.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it
technical support issues noc@flagtelecom.comnoc@flagtelecom.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it
===============================================
trouble: 24 Hour Call +44 208 282 1599
trouble: Report to noc@flagtelecom.comnoc@flagtelecom.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it
peering issues to peering@flagtelecom.com peering@flagtelecom.comThis e-mail address is being protected from spam bots, you need JavaScript enabled to view it
 

 

 

* We do NOT support or maintain any BGP community string
** Contact ISP to get more detail information


 
Google Translation
English Arabic Chinese (Simplified) Czech Dutch French German Italian Korean Portuguese Russian Spanish Filipino Vietnamese Thai Turkish
Statistics
Content View Hits : 549117
Polls
Who is the best ISP?