DATAHUB-IX
Docs

BGP config snippets.

Vendor-specific examples for the DATAHUB-IX route servers (AS202192). Replace 65500 with your ASN, the MD5 with the value from your onboarding email, and 192.0.2.1 with your peering interface IP.

Route-server peering (Falkenstein, IPv4)

The snippets below set up a session against both Falkenstein route servers. Replicate per-PoP for Helsinki (185.1.42.17 / .18) and Zurich (185.1.42.33 / .34).

router bgp 65500
 address-family ipv4 unicast
  maximum-paths ebgp 8
 !
 address-family ipv6 unicast
  maximum-paths ebgp 8
 !
 neighbor-group DATAHUB-IX-RS-V4
  remote-as 202192
  description DATAHUB-IX route server (v4)
  password encrypted YOUR_MD5_HERE
  ttl-security
  bfd minimum-interval 300
  address-family ipv4 unicast
   route-policy DATAHUB-IX-IN in
   route-policy DATAHUB-IX-OUT out
   maximum-prefix 1000 90 warning-only
 !
 neighbor 185.1.42.1
  use neighbor-group DATAHUB-IX-RS-V4
  description rs1.fks.datahub-ix.net
 !
 neighbor 185.1.42.2
  use neighbor-group DATAHUB-IX-RS-V4
  description rs2.fks.datahub-ix.net

IPv6

Configure the same neighbours in their IPv6 address-family using the v6 RS addresses (e.g. 2001:7f8:f::1, 2001:7f8:f::2). Default max-prefix is 200.

Common requirements

  • BGP MD5 authentication is recommended; the password is delivered out-of-band during onboarding.
  • Send only your own and customer-cone prefixes — register an AS-SET in IRR (AS-YOURASN).
  • Drop bogons inbound. Drop RPKI-invalid inbound (the route server already does this).
  • Set next-hop self on egress — required by the route servers.
  • Use BFD 300×3 for sub-second convergence.

Looking Glass quick checks

# After turn-up, sanity-check from your side
show bgp ipv4 unicast neighbor 185.1.42.1 advertised-routes
show bgp ipv4 unicast neighbor 185.1.42.1 received-routes
show bgp ipv4 unicast summary | i 202192

# The DATAHUB-IX Looking Glass supports:
#   - show route <prefix>
#   - show neighbors
#   - traceroute / ping from any PoP