New York

New York route server guide

Route server information

DE-CIX operates so-called route server systems (see RFC7947 for a detailed description) to facilitate the exchange of BGP announcements between peers at DE-CIX. Each peer needs only to set up a BGP connection to the route server in order to receive the BGP announcements of all other peers with a BGP connection to the route server.

BGP session parameters

This section provides a brief overview of the BGP session parameters to connect to the conventional and Blackholing route servers:

rs1206.82.104.254
2001:504:36::f63a:afc:1
rs2206.82.106.254
2001:504:36::f63a:afd:1
AS63034
RIR macro (AS-SET)IPv4: AS-DECIX-NYC
IPv6: AS-DECIX-NYC-V6
Recommended prefix limit rs1/rs2 (your side):IPv4: 250,000
IPv6: 70,000

BGP announcement filtering

This section describes the filtering mechanism that can be used to filter BGP announcements.

Your side

You can safely accept any BGP announcements received via the route servers, as DE-CIX filters all incoming BGP announcements from all peers. The filtering mechanism is described below in the "DE-CIX side" section.

If you additionally want to filter on your side based on AS-SETs, you can do so by using one or more of the following AS-SETs registered in the RIPE database:

RIR macro (AS-SET)Purpose
AS-DECIX-NYCAS-SETs of all DE-CIX NYC customers (IPv4)
AS-DECIX-NYC-V6AS-SETs of all DE-CIX NYC customers (IPv6)
AS-DECIX-NYC-CONNECTEDASNs of all DE-CIX NYC customers

DE-CIX side

At DE-CIX, the conventional and Blackholing route servers filter based on AS path as well as IP prefixes. The BGP announcements that a route server receives from a peer are checked against the AS-SET the peer has provided. The AS-SET can be changed by contacting the DE-CIX Customer Service team.

How and what the route servers filters
The DE-CIX filters are updated every 6 hours. Don't forget to register your IP prefixes in the IRR database well in advance (at least 24h before announcing the first time).

Bogon and Martian filtering
Please make sure not to announce routes that

  • are > /24 (IPv4) and > /48 (IPv6) (RFC7454)
  • have a different BGP next-hop to the IP of your own router
  • are bogons/martians (private and reserved IP prefixes as defined by RFC1918, RFC2544, RFC3927RFC 5735RFC5737RFC6598 and RFC6890)
  • are a DE-CIX peering LAN (please also do not announce any of our peering LANs in the DFZ!)
  • contain bogon ASNs in the BGP AS path (private and reserved ASN numbers as defined by RFC7607RFC6793RFC5398, RFC6996RFC7300)
  • differ in the leftmost ASN in the AS path from your own ASN
  • have an AS path length > 32
  • are < /8 (IPv4) and < /19 (IPv6) (RFC7454)

We will drop these kinds of routes.

Check the status of your routes
You can check the status of your announced routes to us in the DE-CIX Looking Glass – the reason why a route is filtered is also shown, as is a hint on how to fix the issue.

You can find more info on how to use the DE-CIX Looking Glass here.

IRR and RPKI validation
Any routes you announce will also be RPKI (RFC6811, RFC7115) validated and checked against Internet Routing Registry (IRR) data. The AS-SET you provide to us will be recursively resolved. Then filtering is executed as follows:

  • The origin ASN needs to be in the customer cone (make sure that your AS-SET is well maintained and that all your downstreams are included)
  • Is the route a blackhole (RFC7999)?
    • If not, the route undergoes strict RPKI validation filtering (both origin and maxLength):
      • If the result is RPKI Valid, the route is accepted (a missing route object will have no implication in this case).
      • If the result is RPKI Invalid, the route is rejected.
      • If the result is RPKI NotFound/Unknown, we check if the route is resolvable for its origin ASN (this will be the case if a proper route object exists) and it might get accepted or rejected depending on the result.**
         
    • If it is, the route undergoes loose RPKI validation filtering (origin only):
      • If the result is RPKI Valid, the route is accepted.
      • if the result is RPKI Invalid, the route is rejected.
      • If the result is RPKI NotFound/Unknown, we check if the route is resolvable for its origin ASN (this will be the case if a proper route object exists) and it might get accepted or rejected depending on the result.**
Route server filters

**Loose filtering on IRRDB route objects
We perform loose filtering on IRRDB route objects. For example: If you have a route object for 46.31.120.0/21, we will also accept e.g. 46.31.120.0/22 and other more specifics (up to /24 and up to /32 for blackholes). If this is not a desired behavior, we strongly encourage you to create a ROA and set the maxLength attribute accordingly. As RPKI validation is performed before the IRRDB route object check, it will render all undesired more specifics as RPKI Invalid, which will result in rejection of these. Please note that this method only works for non-blackholes as we perform loose RPKI validation on blackholes (i.e. ignore maxLength).

Route server setup

The route server setup at DE-CIX New York consists of three machines, two conventional route servers and a blackhole route server. The software utilized to provide the route server service is BIRD. Of the two conventional route servers only one is required. However, in order to use the route server service, every peer is requested to connect to both machines for redundancy purposes, so that if one machine is out of order (e.g. maintenance), the route server service can still be used.

If the route servers system receive a BGP announcement marked as a Blackhole, the NO-EXPORT community and the BLACKHOLE Community are added if these communities are not already present. This makes sure each BGP announcement marked as Blackhole can be easily filtered and does not spread widely in the Internet routing system.

Route server control

Operational BGP Communities can be used to control various functions of the route server. With these communities, you can:

  • control the redistribution of advertised prefixes,
  • prepend your own AS up to three times,
  • trigger the calculation of a new alternate path (if available) for your advertised prefixes before commencing any maintenance tasks.From an operational point of view, we advise setting up BGP sessions to both route servers, even if you do not want to peer with (i.e. advertise prefixes to) the route servers. This helps DE-CIX staff to quickly monitor the availability of each peer.

Please note that you are required to set up BGP sessions with (but don't need to advertise prefixes to) the DE-CIX route servers to be able to claim credits for the GlobePEER service. Otherwise DE-CIX may not be able to comply with its SLA (please see DE-CIX GlobePEER Technical Service Description - III. IP LAYER CONFIGURATION (ISO/OSI LAYER 3) - Interface configuration).

If your decision not to establish BGP sessions with the route servers was made due to your peering policy, please contact us to establish a monitoring-only session. You don’t have to advertise any prefixes and you won’t receive any prefixes from us during that session.

Sample configurations

The following section contains configuration examples for different router operating systems:

    1. !
    2. ! Config example for Cisco IOS
    3. ! Peer and session templates, (S)AFI format and some basic filtering
    4. ! DE-CIX route servers rs1, rs2
    5. ! Your example ASN: 64500 (replace with your real ASN)
    6. ! Local preference route servers: 125
    7. !
    8. router bgp 64500
    9. bgp router-id <YOUR_ROUTER_ID>
    10. ! Requires all your sessions to reset to take effect (if not already enabled)
    11. bgp graceful-restart
    12. bgp graceful-restart restart-time 120
    13. bgp graceful-restart stalepath-time 360
    14. template peer-policy PP_DECIX_ROUTE_SERVERS_COMMON
    15. ! Optional: Keep a pre-ingress-route-map copy of the peer table (if you have the memory; useful for debugging)
    16. soft-reconfiguration inbound
    17. ! Strip private ASNs from BGP AS-PATH
    18. remove-private-as
    19. ! Send standard and extended BGP communities
    20. send-community both
    21. exit-peer-policy
    22. !
    23. template peer-policy PP_DECIX_ROUTE_SERVERS_4
    24. ! Apply ingress route map
    25. route-map RM_DECIX_ROUTE_SERVERS_IN in
    26. ! Apply egress IPv4 route map
    27. route-map RM_DECIX_ROUTE_SERVERS_OUT_4 out
    28. ! Please accept up to 250,000 IPv4 prefixes from us
    29. maximum-prefix 250000
    30. inherit peer-policy PP_DECIX_ROUTE_SERVERS_COMMON 1
    31. exit-peer-policy
    32. !
    33. template peer-policy PP_DECIX_ROUTE_SERVERS_6
    34. ! Apply ingress route map
    35. route-map RM_DECIX_ROUTE_SERVERS_IN in
    36. ! Apply egress IPv6 route map
    37. route-map RM_DECIX_ROUTE_SERVERS_OUT_6 out
    38. ! Please accept up to 70,000 IPv6 prefixes from us
    39. maximum-prefix 70000
    40. inherit peer-policy PP_DECIX_ROUTE_SERVERS_COMMON 1
    41. exit-peer-policy
    42. !
    43. template peer-session PS_DECIX_ROUTE_SERVERS
    44. ! ASN of DE-CIX route servers
    45. remote-as 63034
    46. ! The route servers are passive and waiting for you side to initiate the sessions
    47. transport connection-mode active
    48. ! Use BGP version 4 and skip version negotiation
    49. version 4
    50. ! Please do not use aggressive timers (60/180 should be fine) to reduce the risk of flapping sessions
    51. timers 60 180
    52. exit-peer-session
    53. !
    54. ! Our route servers are transparent: Ignore first AS in AS path not being your peer AS (i.e. 63034)
    55. no bgp enforce-first-as
    56. bgp log-neighbor-changes
    57. neighbor 206.82.104.254 inherit peer-session PS_DECIX_ROUTE_SERVERS
    58. neighbor 206.82.104.254 description RS1.NYC.DE-CIX.NET
    59. neighbor 2001:504:36::f63a:afc:1 inherit peer-session PS_DECIX_ROUTE_SERVERS
    60. neighbor 2001:504:36::f63a:afc:1 description RS1.NYC.DE-CIX.NET
    61. neighbor 206.82.106.254 inherit peer-session PS_DECIX_ROUTE_SERVERS
    62. neighbor 206.82.106.254 description RS2.NYC.DE-CIX.NET
    63. neighbor 2001:504:36::f63a:afd:1 inherit peer-session PS_DECIX_ROUTE_SERVERS
    64. neighbor 2001:504:36::f63a:afd:1 description RS2.NYC.DE-CIX.NET
    65. !
    66. address-family ipv4 unicast
    67. ! Some example IPv4 prefixes to announce
    68. network 192.0.2.0
    69. network 198.51.100.0
    70. network 203.0.113.0
    71. ! We do not support IPv6 over IPv4 transport
    72. no neighbor 2001:504:36::f63a:afc:1 activate
    73. no neighbor 2001:504:36::f63a:afd:1 activate
    74. neighbor 206.82.104.254 activate
    75. neighbor 206.82.104.254 inherit peer-policy PP_DECIX_ROUTE_SERVERS_4
    76. neighbor 206.82.106.254 activate
    77. neighbor 206.82.106.254 inherit peer-policy PP_DECIX_ROUTE_SERVERS_4
    78. exit-address-family
    79. !
    80. address-family ipv6 unicast
    81. ! Some example IPv6 prefixes to announce
    82. network 2001:DB8:1234::/48
    83. network 2001:DB8:ABCD::/48
    84. network 2001:DB8:FFFF::/48
    85. neighbor 2001:504:36::f63a:afc:1 activate
    86. neighbor 2001:504:36::f63a:afc:1 inherit peer-policy PP_DECIX_ROUTE_SERVERS_6
    87. neighbor 2001:504:36::f63a:afd:1 activate
    88. neighbor 2001:504:36::f63a:afd:1 inherit peer-policy PP_DECIX_ROUTE_SERVERS_6
    89. exit-address-family
    90. !
    91. ! Use new BGP community format
    92. ip bgp-community new-format
    93. !
    94. ! We will not advertise IPv4 prefixes less specific than /8 and more specific than /24
    95. ! Exception: Blackhole next-hop and/or BLACKHOLE Community is set.
    96. ! Please allow up to /32 if you wish to receive all blackholed prefixes from the route servers
    97. ! Prefix list example: Allow every IPv4 prefix up to /32 from the route servers
    98. ip prefix-list PL_DECIX_ROUTE_SERVERS_IN_4 seq 5 permit 0.0.0.0/0 le 32
    99. !
    100. ! We will not advertise IPv6 prefixes less specific than /19 and more specific than /48
    101. ! Exception: Blackhole next-hop and/or BLACKHOLE Community is set.
    102. ! Please allow up to /128 if you wish to receive all blackholed prefixes from the route servers
    103. ! Prefix list example: Allow every IPv6 prefix up to /128 from the route servers
    104. ipv6 prefix-list PL_DECIX_ROUTE_SERVERS_IN_6 seq 5 permit ::/0 le 128
    105. !
    106. ! We do not accept IPv4 prefixes less specific than /8 and more specific than /24
    107. ! Exception: Up to /32 allowed when Blackhole next-hop and/or BLACKHOLE Community is set
    108. ! Prefix list example: Make sure to only advertise your own IPv4 prefixes/those of your customers
    109. ip prefix-list PL_DECIX_ROUTE_SERVERS_OUT_4 seq 5 permit 192.0.2.0/24
    110. ip prefix-list PL_DECIX_ROUTE_SERVERS_OUT_4 seq 10 permit 203.0.113.0/24
    111. !
    112. ! We do not accept IPv6 prefixes less specific than /19 and more specific than /48
    113. ! Exception: Up to /128 allowed when Blackhole next-hop and/or BLACKHOLE Community is set
    114. ! Prefix list example: Make sure to only advertise your own IPv6 prefixes/those of your customers
    115. ipv6 prefix-list PL_DECIX_ROUTE_SERVERS_OUT_6 seq 5 permit 2001:DB8:1234::/48
    116. ipv6 prefix-list PL_DECIX_ROUTE_SERVERS_OUT_6 seq 10 permit 2001:DB8:FFFF::/48
    117. !
    118. ! Prefix list example: IPv4 prefixes to blackhole
    119. ip prefix-list PL_DECIX_BLACKHOLE_OUT_4 seq 5 permit 198.51.100.0/24
    120. !
    121. ! Prefix list example: IPv6 prefixes to blackhole
    122. ipv6 prefix-list PL_DECIX_BLACKHOLE_OUT_6 seq 5 permit 2001:DB8:ABCD::/48
    123. !
    124. ! Route-Map example: Set local-preference for route servers to 125
    125. route-map RM_DECIX_ROUTE_SERVERS_IN permit 10
    126. match ip address prefix-list PL_DECIX_ROUTE_SERVERS_IN_4
    127. match ipv6 address prefix-list PL_DECIX_ROUTE_SERVERS_IN_6
    128. set local-preference 125
    129. !
    130. ! Route-Map example:
    131. ! Use community 0:64501 for not allowing AS64501 to receive your prefixes
    132. ! Use extended community rt 0:65550 for not allowing AS65550 (4 byte ASN) to receive your prefixes
    133. ! Use community 63034:63034 for allowing the route servers to advertise your prefixes to all (other) peers
    134. ! For all available communities, please see "Route Server Control"
    135. route-map RM_DECIX_ROUTE_SERVERS_OUT_4 permit 10
    136. match ip address prefix-list PL_DECIX_ROUTE_SERVERS_OUT_4
    137. set community 63034:63034 0:64501 additive
    138. set extcommunity rt 0:65550 additive
    139. !
    140. ! Route-Map example: Blackhole IPv4 prefixes
    141. route-map RM_DECIX_ROUTE_SERVERS_OUT_4 permit 20
    142. match ip address prefix-list PL_DECIX_BLACKHOLE_OUT_4
    143. set community 63034:63034 additive
    144. set community 65535:666 additive
    145. !
    146. ! Route-Map example:
    147. ! Use community 0:63034 in combination with 63034:65550 to allow no one except AS65550 to receive your IPv6 prefixes
    148. route-map RM_DECIX_ROUTE_SERVERS_OUT_6 permit 10
    149. match ipv6 address prefix-list PL_DECIX_ROUTE_SERVERS_OUT_6
    150. set community 0:63034 additive
    151. set extcommunity rt 63034:65550 additive
    152. !
    153. ! Route-Map example: Blackhole IPv6 prefixes
    154. route-map RM_DECIX_ROUTE_SERVERS_OUT_6 permit 20
    155. match ipv6 address prefix-list PL_DECIX_BLACKHOLE_OUT_6
    156. set community 63034:63034 additive
    157. set community 65535:666 additive
    158. !
    1. !!
    2. !! Config example for Cisco IOS XR
    3. !! Session-, AF- and neighbor groups as well as some basic filtering
    4. !! DE-CIX route servers rs1, rs2
    5. !! Your example ASN: 64500 (replace with your real ASN)
    6. !! Local preference route servers: 125
    7. !!
    8. !
    9. !! We do not accept IPv4 prefixes less specific than /8 and more specific than /24
    10. !! Exception: Up to /32 allowed when Blackhole next-hop and/or BLACKHOLE Community is set
    11. !! Prefix set example: Make sure to only advertise your own IPv4 prefixes/those of your customers
    12. prefix-set PS_DECIX_ROUTE_SERVERS_OUT_4
    13. 192.0.2.0/24,
    14. 203.0.113.0/24
    15. end-set
    16. !
    17. !! We do not accept IPv6 prefixes less specific than /19 and more specific than /48
    18. !! Exception: Up to /128 allowed when Blackhole next-hop and/or BLACKHOLE Community is set
    19. !! Prefix set example: Make sure to only advertise your own IPv6 prefixes/those of your customers
    20. prefix-set PS_DECIX_ROUTE_SERVERS_OUT_6
    21. 2001:db8:1234::/48,
    22. 2001:db8:ffff::/48
    23. end-set
    24. !
    25. !! Prefix set example: IPv4 prefixes to blackhole
    26. prefix-set PS_DECIX_BLACKHOLE_OUT_4
    27. 198.51.100.0/24
    28. end-set
    29. !
    30. !! Prefix set example: IPv6 prefixes to blackhole
    31. prefix-set PS_DECIX_BLACKHOLE_OUT_6
    32. 2001:db8:abcd::/48
    33. end-set
    34. !
    35. !! Use this community for allowing the route servers to advertise your prefixes to all peers
    36. !! For all available communities, please see "Route Server Control"
    37. !! Community set example: Community set for DE-CIX "advertise to all peers" community
    38. community-set CS_DECIX_ADVERTISE_TO_ALL_PEERS
    39. 63034:63034
    40. end-set
    41. !
    42. community-set CS_DECIX_BLACKHOLE
    43. 65535:666
    44. end-set
    45. !
    46. !! We will not advertise IPv4 prefixes less specific than /8 and more specific than /24
    47. !! Exception: Blackhole next-hop and/or BLACKHOLE Community is set
    48. !! Please allow up to /32 if you wish to receive all blackholed prefixes from the route servers
    49. !! Route Policy example: Allow every IPv4 prefix from the route servers and set local preference to 125
    50. route-policy RPL_DECIX_ROUTE_SERVERS_IN_4
    51. set local-preference 125
    52. pass
    53. end-policy
    54. !
    55. !! We will not advertise IPv6 prefixes less specific than /19 and more specific than /48
    56. !! Exception: Blackhole next-hop and/or BLACKHOLE Community is set
    57. !! Please allow up to /128 if you wish to receive all blackholed prefixes from the route servers
    58. !! Route Policy example: Allow every IPv6 prefix from the route servers and set local preference to 125
    59. route-policy RPL_DECIX_ROUTE_SERVERS_IN_6
    60. set local-preference 125
    61. pass
    62. end-policy
    63. !
    64. !! Route Policy example:
    65. !! Advertise IPv4 prefixes from prefix sets PS_DECIX_ROUTE_SERVERS_OUT_4 and PS_DECIX_BLACKHOLE_OUT_4 (prefixes to blackhole)
    66. !! Use community 0:64501 for not allowing AS64501 to receive your prefixes
    67. !! Use extended community rt 0:65550 for not allowing AS65550 (4 byte ASN) to receive your prefixes
    68. !! Use community 63034:63034 for allowing the route servers to advertise your prefixes to all (other) peers
    69. !! Set DE-CIX BLACKHOLE Community
    70. !! For all available communities, please see "Route Server Control"
    71. route-policy RPL_DECIX_ROUTE_SERVERS_OUT_4
    72. if destination in PS_DECIX_ROUTE_SERVERS_OUT_4 then
    73. set community CS_DECIX_ADVERTISE_TO_ALL_PEERS additive
    74. set community (0:64501) additive
    75. set extcommunity rt (0:65550) additive
    76. pass
    77. !! Blackhole IPv4 prefixes
    78. elseif destination in PS_DECIX_BLACKHOLE_OUT_4 then
    79. !! Allow all peers to receive your blackholed prefixes
    80. set community CS_DECIX_ADVERTISE_TO_ALL_PEERS additive
    81. !! Set BLACKHOLE Community
    82. set community CS_DECIX_BLACKHOLE additive
    83. pass
    84. else
    85. drop
    86. endif
    87. end-policy
    88. !
    89. !! Route Policy example:
    90. !! Advertise IPv6 prefixes from prefix sets PS_DECIX_ROUTE_SERVERS_OUT_6 and PS_DECIX_BLACKHOLE_OUT_6 (prefixes to blackhole)
    91. !! Use community 0:63034 in combination with 63034:65550 to allow no one except AS65550 to receive your IPv6 prefixes
    92. !! Set DE-CIX BLACKHOLE Community
    93. route-policy RPL_DECIX_ROUTE_SERVERS_OUT_6
    94. if destination in PS_DECIX_ROUTE_SERVERS_OUT_6 then
    95. set community (0:63034) additive
    96. set extcommunity rt (63034:65550) additive
    97. pass
    98. !! Blackhole IPv6 prefixes
    99. elseif destination in PS_DECIX_BLACKHOLE_OUT_6 then
    100. !! Allow all peers to receive your blackholed prefixes
    101. set community CS_DECIX_ADVERTISE_TO_ALL_PEERS additive
    102. !! Set BLACKHOLE Community
    103. set community CS_DECIX_BLACKHOLE additive
    104. pass
    105. else
    106. drop
    107. endif
    108. end-policy
    109. !
    110. router bgp 64500
    111. bgp router-id <YOUR_ROUTER_ID>
    112. bgp graceful-restart
    113. address-family ipv4 unicast
    114. !! Some example IPv4 prefixes to announce
    115. network 192.0.2.0/24
    116. network 198.51.100.0/24
    117. network 203.0.113.0/24
    118. !
    119. address-family ipv6 unicast
    120. !! Some example IPv6 prefixes to announce
    121. network 2001:db8:1234::/48
    122. network 2001:db8:abcd::/48
    123. network 2001:db8:ffff::/48
    124. !
    125. af-group AG_DECIX_ROUTE_SERVERS_4 address-family ipv4 unicast
    126. !! Allow sending of BGP standard and extended communities to control advertising of your prefixes
    127. !! For available communities, please see "Route Server Control"
    128. send-community-ebgp
    129. send-extended-community-ebgp
    130. !! Inbound IPv4 policy
    131. route-policy RPL_DECIX_ROUTE_SERVERS_IN_4 in
    132. !! Outbound IPv4 policy
    133. route-policy RPL_DECIX_ROUTE_SERVERS_OUT_4 out
    134. !! Please accept up to 250,000 IPv4 prefixes from us
    135. maximum-prefix 250000 75
    136. !! Strip private ASNs from BGP AS-PATH
    137. remove-private-AS
    138. !! Optional: Keep a pre-ingress-route-map copy of the peer table even if route refresh is supported (if you have the memory; useful for debugging)
    139. soft-reconfiguration inbound always
    140. !
    141. af-group AG_DECIX_ROUTE_SERVERS_6 address-family ipv6 unicast
    142. !! Allow sending of BGP standard and extended communities to control advertising of your prefixes
    143. !! For available communities, please see "Route Server Control"
    144. send-community-ebgp
    145. send-extended-community-ebgp
    146. !! Inbound IPv6 policy
    147. route-policy RPL_DECIX_ROUTE_SERVERS_IN_6 in
    148. !! Outbound IPv6 policy
    149. route-policy RPL_DECIX_ROUTE_SERVERS_OUT_6 out
    150. !! Please accept up to 70,000 IPv6 prefixes from us
    151. maximum-prefix 70000 75
    152. !! Strip private ASNs from BGP AS-PATH
    153. remove-private-AS
    154. !! Optional: Keep a pre-ingress-route-map copy of the peer table even if route refresh is supported (if you have the memory; useful for debugging)
    155. soft-reconfiguration inbound always
    156. !
    157. session-group SG_DECIX_ROUTE_SERVERS
    158. !! ASN of DE-CIX route servers
    159. remote-as 63034
    160. !! Please do not use aggressive timers (60/180 should be fine) to reduce the risk of flapping sessions
    161. timers 60 180
    162. !! Our route servers are transparent: Ignore first AS in AS path not being your peer AS (i.e. 63034)
    163. enforce-first-as disable
    164. !! Allow BGP graceful restart
    165. graceful-restart
    166. !! The route servers are passive and waiting for you side to initiate the sessions
    167. session-open-mode active-only
    168. !
    169. neighbor-group NG_DECIX_ROUTE_SERVERS_4
    170. use session-group SG_DECIX_ROUTE_SERVERS
    171. address-family ipv4 unicast
    172. use af-group AG_DECIX_ROUTE_SERVERS_4
    173. !
    174. !
    175. neighbor-group NG_DECIX_ROUTE_SERVERS_6
    176. use session-group SG_DECIX_ROUTE_SERVERS
    177. address-family ipv6 unicast
    178. use af-group AG_DECIX_ROUTE_SERVERS_6
    179. !
    180. !
    181. neighbor 206.82.104.254
    182. use neighbor-group NG_DECIX_ROUTE_SERVERS_4
    183. description RS1.NYC.DE-CIX.NET
    184. !
    185. neighbor 2001:504:36::f63a:afc:1
    186. use neighbor-group NG_DECIX_ROUTE_SERVERS_6
    187. description RS1.NYC.DE-CIX.NET
    188. !
    189. neighbor 206.82.106.254
    190. use neighbor-group NG_DECIX_ROUTE_SERVERS_4
    191. description RS2.NYC.DE-CIX.NET
    192. !
    193. neighbor 2001:504:36::f63a:afd:1
    194. use neighbor-group NG_DECIX_ROUTE_SERVERS_6
    195. description RS2.NYC.DE-CIX.NET
    196. !
    197. !
    198. end