Page tree
Skip to end of metadata
Go to start of metadata

CME Globex Hub offers clients in UK, Hong Kong, Seoul, Singapore and Tokyo access to the CME Group production environment using Metropolitan Ethernet. Clients connect their Ethernet network to the local CME Group data hubs. CME Group maintains a connection between the local CME Group data hubs and the CME Group production environment.  Diversity is achieved by establishing connections to both local CME Group data hubs using different carriers.

CME Globex Hubs also offers clients in the locations mentioned above connectivity to BrokerTec US and EU markets located in Secaucus, NJ and Slough, UK.  Hub customers are required to have separate connectivity to access CME Group and BrokerTec. 

A new hub has been installed in Aurora providing CME Licensed Space customers convenient access to BrokerTec markets.  There is a separate link highlighting the technical details of this new hub - CME Globex Hub - Aurora.

For more details to trade CME Group products via this connectivity method, contact your Globex Account Manager (GAM).

CME Globex Hub connectivity provides access to:

  • iLink order entry on the CME Globex platform for futures, options, and BrokerTec markets
  • Market data for futures, options, and Brokertec markets on CME Globex disseminated over the CME Market Data Platform (MDP) 
  • CME Clearing House systems for CME Group markets.

Contents

Handoff Specifications

  • 1 Gbps hand-off
  • 10 Gbps hand-off
  • Single Mode Fiber
  • 1G-LR (1GBASE-LH)
  • 10G-LR (10GBASE-LR)
  • 1310nm wavelength

The following diagram illustrates a configuration with carrier diversity.

CME Globex Hub

Requirements

Customers are responsible for establishing connections from their site to each of the local CME Group data hubs.

    • All IP packets destined for CME Group must be sourced from the CME Group-assigned private address space.
    • Should customers decide to place the server behind another network device, they will be responsible for network address translation.
  • CME Group is not responsible for support of CDL WAN circuits since the customer manages the connectivity.
  • CME Group requires connection to both data centers for redundancy.

CME Globex Hub Connectivity Procedures

Upon successful validation of the circuit and site acceptance by CME Group, the customer is responsible for the following procedures:

  • Activating the multicast stream
  • Configuring the customer application on the arbitration server
  • Configuring routers
  • Configuring the rendezvous point’s IP address
  • Configuring a fixed path between each router and corresponding CME data center
  • Validating that the listener server is receiving data from the correct source

Routing Requirements

Customer routers must be capable of using advanced TCP/IP Protocols including BGP and multicast, specifically PIM Sparse Mode.

  • BGP routing must be used on the routers terminating CME Group connections.
  • 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.
  • Multicast PIM Sparse Mode must be used.

Restrictions

The following restrictions apply to connectivity:

  • No site-to-site connectivity.
  • No direct server connectivity into CME Globex.
  • Terminating the circuit on a Layer 2 device is not allowed.
  • CME Group will not accept traffic sourced from any customer’s public IP space.
  • Only one Market Data Platform data feed per router is allowed.
  • Customer hardware must be capable of supporting quote streams (e.g., PIM sparse mode).
  • Customer equipment must be in CME approved space