CME RNet is a client-managed connectivity solution providing access to relationship-based trading platforms. This CME RNet topic describes:
RNet services for EBS Direct are available in Secaucus, Slough and Tokyo.
- Equinix IBX Licensed Space customers at Secaucus, Slough and Tokyo can order service and connect to RNet with an Equinix cross-connect.
- Customers can connect to this service using a carrier circuit. The carrier must be a Equinix IBX Licensed Space customer and order the Equinix cross-connect on behalf of their customer.
- CME Group will issue a Letter of Authorization (“LOA”) for each cross-connect. Customer or carrier will submit the LOA to Equinix with their cross-connect request.
RNet service for BrokerTec Stream is available only in Secaucus.
- Equinix IBX Licensed Space customers at Secaucus can order service and connect to RNet with an Equinix cross-connect.
- Customers can connect to this service using a carrier circuit. The carrier must be a Equinix IBX Licensed Space customer at Secaucus and order the Equinix cross-connect on behalf of their customer.
- CME Group will issue a Letter of Authorization (“LOA”). Customer or carrier will submit the LOA to Equinix with their cross-connect request.
Separate RNet services are required to access EBS and BrokerTec supported services.
CME RNet connectivity provides access to the following services:
- EBS Direct 2.0
- EBS Workstation
- CPT 2.0
CME RNet connectivity provides access to the following BrokerTec services:
- BrokerTec Stream 2.0
For more details about trading CME Group products via this connectivity method, contact your Client Integration Services (CIS).
Handoff Specifications
- 10 Gbps hand-off
- Single Mode Fiber
- 10G-LR (10GBASE-LR)
- 1310nm wavelength
Relationship-Based Trading - Secaucus, Slough, Tokyo Connectivity:
CME RNet Connectivity Procedures
Upon successful validation of the cross-connects and site acceptance by CME Group, the customer is responsible for the following procedures:
- Configuring the customer application
- Configuring routers
- Selecting a preferred path between the two X-Connects
Routing Requirements
Customer routers must be capable of using advanced TCP/IP Protocols including BGP.
- CME Group will assign /31 IP Address for the X-Connects
- BGP routing must be used on the routers terminating CME Group connections.
- CME Group will not support BGP timers faster than 3 & 9 seconds
- It is recommended that customers use a routing protocol between their routers to provide automatic failover.
- All IP packets destined for CME Group must be sourced from CME Group-assigned private address space. (/27 block will be assigned to each customer). Customers have the ability to advertise more specific routes on the connections to allow for routing failover and fault tolerance.
- Should customers decide to place the server behind another network device, they will be responsible for network address translation.
- CME Group will advertise CME owned public IP prefixes used for respective CME Group products
- CME Group will assign a private ASN for clients who wish to use private ASN
Restrictions
The following restrictions apply to connectivity:
- No site-to-site connectivity.
- No direct server connectivity into CME Group network gear/environment.
- CME Group does not support asymmetric routing between the X-Connects.
- CME Group will not accept traffic sourced from any customer’s public IP space.