Reduce operational complexity by managing a small number of route server sessions instead of a growing full-mesh design.
000 / ESTABLISHING SESSION
TurkIX Route Servers simplify multilateral peering by reducing the need for a separate BGP session with each network. Members can exchange routes with multiple networks through a small number of sessions, subject to the applicable routing policies.
Reduce operational complexity by managing a small number of route server sessions instead of a growing full-mesh design.
Use two route server nodes for a more resilient peering setup and better continuity during maintenance windows.
Connect to the TurkIX route server platform and exchange routes with a broader member base more efficiently.
Members announce prefixes to the route servers and receive routes accepted under policy from other connected networks. This reduces the number of sessions needed to manage new peering relationships.
Use the following endpoints when establishing BGP sessions to the TurkIX route server platform.
The route server architecture removes the need to create separate bilateral sessions with every participant on the exchange.
Each network builds bilateral sessions with every other network. This becomes harder to scale as the number of participants increases.
Each network peers with the TurkIX route servers and reaches the wider ecosystem through a more practical and scalable design.
TurkIX Route Servers simplify multilateral peering by reducing the need for a separate BGP session with each network. Members can exchange routes with multiple networks through a small number of sessions, subject to the applicable routing policies.
211877:0:PEER_ASN
211877:1:PEER_ASN
211877:0:0
211877:1:0
211877:101:PEER_ASN
211877:102:PEER_ASN
211877:103:PEER_ASN
Close distribution to everyone first, then explicitly allow the selected peers.
211877:0:0
211877:1:65001
211877:1:65002Use a single deny community to exclude one participant while keeping global route server distribution.
211877:0:65010Recommended model for Bird v2 and modern 32-bit ASN environments.
211877:0:0
211877:1:65001Use peer-specific prepend communities to influence path selection toward a single participant.
211877:102:65020For stronger availability, participants can establish sessions to both route server instances and keep peering more stable during maintenance or node events.
Route servers simplify the exchange of accepted routes and the management of routing policies.
As the number of peers increases, the route server approach keeps day-to-day peering management far more practical than a full bilateral mesh.
Contact our team or send your application to plan the right connection model and activation path for your network.
Fixnet Telekom Ltd. Sti.
test
24/7 NOC — noc@turkix.com.tr
Sales — info@turkix.com.tr
05400822222
Contact →
test
PoPs →