Johor Bahru

Johor Bahru 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 route servers:

rs1103.119.235.252
2403:4ac0:2::953e:a:1
rs2103.119.235.253
2403:4ac0:2::953e:a:2
AS38206
RIR macro (AS-SET)IPv4: AS-DECIX-JHB
IPv6: AS-DECIX-JHB-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 section "DE-CIX side".

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-JHBAS-SETs of all DE-CIX JHB customers (IPv4)
AS-DECIX-JHB-V6AS-SETs of all DE-CIX JHB customers (IPv6)
AS-DECIX-JHB-CONNECTEDASNs of all DE-CIX JHB customers

DE-CIX side

At DE-CIX, the 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 filter
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 Johor Bahru consists of two machines. The software utilized to provide the route server service is BIRD. Only one of the two conventional route servers 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 '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.

Route server prefix information

Informational BGP communities are used to signal various information about redistributed prefixes. The DE-CIX route servers tag all prefixes with certain BGP communities to indicate their origin. You can use this information to determine where a certain prefix has been injected into the DE-CIX switching platform. This gives you the possibility to filter routes learned from the route servers based on geographical location. 

More information can be found here.

Route server session types

We offer two session types:

Standard/public session (default)

  • We re-distribute all your announcements to other peers while honoring the BGP Communities which allow you to restrict your announcements
     
  • We advertise all announcements from other peers to you while honoring the BGP Communities which allow others peers to restrict their announcements

Monitor session

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