|Set LOCAL_PREF to 80
|Set LOCAL_PREF to 90
|Set LOCAL_PREF to 100
|Set LOCAL_PREF to 110
The communities that control route announcement to peers and transits are only available to customers. The x specifies what the action for the said target is:
0 Announce as is ..
1 Announce with 6667 prepended to as-path ...
2 Announce with 6667 6667 prepended to as-path ...
3 Announce with 6667 6667 6667 prepended to as-path ...
9 Don't announce ... (default and takes precedence if present)
We will also let external communities through from customers. This will enable customers to use similar communities of our peers and transits. Some pages describing these communities have been collected at the end of the page.
|to all AS6667 customers
|to all transits
|to AS3356 Level3
|to AS3549 Global Crossing
|to AS3320 T-Systems
|to AS1239 Sprint Nextel
|to AS1273 Cable&Wireless
|to AS702 Verizon
|to all peers
|to peers in Helsinki Finland and at Ficix
|to peers in Stockholm Sweden and at Netnod
|to peers in London United Kingdom and as LINX
|to peers in Frankfurt Germany and at DECIX
|to peers in Copenhagen Denmark and at DIX
|to peers in Oslo Norway and at NIX
|to peers in Amsterdam The Netherlands and at AMS-IX
|to peers in New York USA and at NYIIX
These communities are tagged on all routes to distinguish their origins. They are sent to everyone but not excepted from outside. They are there to let customers filter routes based on route source.
Standard customers announce all their routes to us with communities 6667:900, 6667:1000 and 6667:2000. When Elisa receives the routes, they are tagged with 6667:300x and the local location community (6667:4xxx.)
|Internal or customer
|London United Kingdom
|Amsterdam The Netherlands
|New York USA