This topic describes various DR failover scenarios. Some of these scenarios require customer configuration changes and some do not.
API solutions have separate IPs and Ports to connect to Production or Disaster Recovery environments. CME Group will issue both Production and DR IPs and ports to client during initial setup.
Clients must manage their own connections to the acting production environment IPs and ports.
Please review the full DR Process overview, then see below for specifics for Scenario 3 impacts on network connectivity and all client-facing solutions. In Scenario 3, both the Production trading platform and co-location services are unavailable. The trading platform is failed over to the DR data center. Co-located clients must use alternative network connectivity to access the DR trading platform.
In Scenario 1, the Production trading platform is unavailable but co-location services are still operable. Co-located clients can use their Production network connection to access the DR trading platform. All other impacts are the same for Scenarios 1 and 3.
Details on Scenario 2 are available here.
Contents
Disaster Recovery Scenarios
The Production data centers house CME Globex Production and Co-Location services. More information on network connectivity impacts for all scenarios is documented here.
The following table details each of the three scenarios for which customers must be prepared.
Disaster Scenarios | Applicable Data Centers | Availability | Description | CME Group Responsibility | Client Responsibility |
|---|---|---|---|---|---|
Scenario 1 | NY5 LD4.2 TY5 |
| Co-Location Services are operable, but CME Globex Production is inoperable. | CME Group initiates DR procedures. | GLink and CME Globex Hub - TY5 are available in this scenario. Client must update their network configuration to route to the EBS Market on CME Globex DR environment(s). |
Scenario 2 | NY5 LD4.2 TY5 |
| Customer has lost connectivity to CME Globex Production within Co-Location facility. | None | Co-location services in the impacted production data center (GLink-Slough, GLink-Secaucus, or CME Globex Hub - TY5) are NOT available in this scenario Customer initiates their internal DR strategy to connect to the Production environment. CME Group strongly recommends all Co-Located clients establish alternative/back-up connectivity in case of connectivity issues. |
Scenario 3 | NY5 LD4.2 TY5 |
| Site failure; Co-Location Services and CME Globex Production are inoperable. | CME Group initiates DR procedures. | GLink and/or CME Globex Hub - TY5 are NOT available in this scenario. Customer initiates their internal DR strategy to connect to the DR environment. CME Group strongly recommends all Co-Located clients establish alternative/back-up connectivity in case of connectivity issues. |
Scenario 3 Overview
In these scenarios, the Production data center and co-location services for a region are inoperable. EBS Market and eFix trading moves from the Production to the DR trading platform. Co-location services in the Production data center cannot be used to access the DR data center.
NY5 Failover
In this scenario, the NY5 Production data center and all co-location services in NY5 (GLink-Secaucus) are inoperable. EBS Market and eFix trading moves from NY5 to the DR trading platform in Slough LD4.2. The NY5 Co-Location service is not available.
New York FX Spot, New York Metals and New York eFix products trade in the NY5 Production Data Center.
| Service | NY Customer Actions for DR | London Customer Actions for DR | Tokyo Region Customer Actions for DR |
|---|---|---|---|
Network | GLink-Secaucus customers need to use an alternative network connection to access the DR trading platform in LD4.2. | London customers can use their LD4.2 network connection to access the DR trading platform in LD4.2. | Tokyo customers can use their network connection to access the DR trading platform in LD4.2. |
EBS Central Post Trade FIX | EBS Central Post Trade customers must use an LD4.2 or TY5 EBS Central Post Trade session, remove any duplicates, and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. |
EBS Central Post Trade TOF | EBS Central Post Trade customers must use an LD4.2 or TY5 EBS Central Post Trade session and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. |
MSGW | MSGW customers can use their NY5 Production sessions to connect to the DR MSGW in LD4.2, using the DR IPs and ports. | ||
| OESGW for MSGW | OESGW for MSGW customers can use their NY5 Production sessions to connect to the DR OESGW in LD4.2, using the DR IPs and ports. | ||
Drop Copy MSGW | |||
CGW | CGW customers must use an LD4.2 CGW session. Any LD4.2 CGW session will route orders to the New York EBS Market and eFix instruments in DR. | LD4.2 CGW sessions are not impacted and will route orders to the New York EBS Market and eFix instruments in DR. | TY5 CGW sessions are not impacted and will route orders to the New York EBS Market and eFix instruments in DR. |
| OESGW for CGWs | OESGW for CGW customers must use an LD4.2 OESGW for CGW session. Any LD4.2 OESGW for CGW session can register Party Details for use in the New York EBS Market and eFix instruments in DR. | No impact. | No impact. |
Drop Copy CGW | Drop Copy CGW customers must use an LD4.2 CGW session. | No impact. | No impact. |
MDP3 TCP Channels | Customers can use their NY5 Production sessions to connect to the TCP gateway in London, using the London IPs and ports. | No impact. | No impact. |
MDP3 Multicast UDP Channels | Customers can consume A and B feeds using the DR multicast addresses with DR IPs and ports | ||
EBS Workstation | EBS Workstation customers must use the London URL and login using their Production credentials. | No impact. | No impact. |
| EBS Ai | EBS Ai customers in New York can use their Production APi IDs and connect to one of the IP/Ports in either London or Tokyo. | LD4.2 EBS Ai sessions are not impacted and will route orders and publish market data for the New York EBS Market and eFix instruments in DR. | TY5 EBS Ai sessions are not impacted and will route orders and publish market data for the New York EBS Market and eFix instruments in DR. |
LD4.2 Failover
In this scenario, the LD4.2 Production data center and all co-location services in LD4.2 (GLink-Slough) are inoperable. EBS Market and eFix trading moves from LD4.2 to the DR trading platform in New York NY5. The LD4.2 Co-Location service is not available.
London FX Spot, London ON SEF/ON MTF NDFs, London OFF SEF/OFF MTF NDFs and London eFix products trade in the LD4.2 Production data center.
| Service | London Customer Actions for DR | NY Customer Actions for DR | Tokyo Region Customer Actions for DR |
|---|---|---|---|
Network | GLink-Slough customers need to use an alternative network connection to access the DR trading platform in NY5. | NY customers can use their NY5 network connection to access the DR trading platform in NY5. | Tokyo customers can use their network connection to access the DR trading platform in NY5. |
EBS Central Post Trade FIX | EBS Central Post Trade customers must use an NY5 or TY5 EBS Central Post Trade session, remove any duplicates, and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. |
EBS Central Post Trade TOF | EBS Central Post Trade customers must use an NY5 or TY5 EBS Central Post Trade session and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. | Stay connected to Production EBS Central Post Trade and reconcile executed trades. |
MSGW | MSGW customers can use their LD4.2 Production sessions to connect to the DR MSGW in NY5, using the DR IPs and ports. | ||
OESGW for MSGW | OESGW for MSGW customers can use their LD4.2 Production sessions to connect to the DR OESGW in NY5, using the DR IPs and ports. | ||
Drop Copy MSGW | Drop Copy MSGW customers can use their LD4.2 Production sessions to connect to the DR Drop Copy MSGW in NY5, using the DR IPs and ports. | ||
CGW | CGW customers must use an NY5 CGW session. Any NY5 CGW session will route orders to the London EBS Market and eFix instruments in DR. | NY5 CGW sessions are not impacted and will route orders to the London EBS Market and eFix instruments in DR. | TY5 CGW sessions are not impacted and will route orders to the London EBS Market and eFix instruments in DR. |
OESGW for CGWs | OESGW for CGW customers must use an NY5 OESGW for CGW session. Any NY5 OESGW for CGW session can register Party Details for use in the London EBS Market and eFix instruments in DR. | No impact. | No impact. |
Drop Copy CGW | Drop Copy CGW customers must use an NY5 Drop Copy CGW session. | No impact. | No impact. |
MDP3 TCP Channels | Customers can use their LD4.2 Production sessions to connect to the TCP gateway in New York, using the New York IPs and ports. | No impact. | No impact. |
MDP3 Multicast UDP Channels | Customers can consume A and B feeds using the DR multicast addresses with DR IPs and ports | ||
EBS Workstation | EBS Workstation customers must use the New York URL and login using their Production credentials. | No impact. | No impact. |
EBS Ai | EBS Ai customers in London can use their Production APi IDs and connect to one of the IP/Ports in either New York or Tokyo. | NY5 EBS Ai sessions are not impacted and will route orders and publish market data for the London EBS Market and eFix instruments in DR. | TY5 EBS Ai sessions are not impacted and will route orders and publish market data for the London EBS Market and eFix instruments in DR. |
TY5 Failover
In this scenario, the TY5 Production data center and all co-location services in TY5 (CME Globex Hub-TY5) are inoperable. Because there is no trading platform in TY5, no markets move to DR. However, the TY5 Co-Location service is not available.
No products trade in TY5. TY5 hosts order entry and market data services only.
| Service | Tokyo Region Customer Actions for DR | NY Customer Actions for DR | London Customer Actions for DR |
|---|---|---|---|
Network | CME Globex Hub-TY5 customers need to use an alternative network connection to access NY5 and/or LD4.2 directly. | No impact. | No impact. |
EBS Central Post Trade FIX | EBS Central Post Trade customers must use an LD4.2 or NY5 EBS Central Post Trade session, remove any duplicates, and reconcile executed trades. | ||
EBS Central Post Trade TOF | EBS Central Post Trade customers must use an LD4.2 or NY5 EBS Central Post Trade session and reconcile executed trades. | ||
MSGW | N/A | ||
CGW | CGW customers must use an LD4.2 or NY5 CGW session. Any LD4.2 or NY5 CGW session will route orders to both New York and London markets. | ||
OESGW for CGWs | OESGW for CGW customers must use an LD4.2 or NY5 OESGW for CGW session. Any LD4.2 or NY5 OESGW for CGW session can register Party Details for use in both the New York and London markets. | ||
Drop Copy CGW | CGW customers must use an LD4.2 or NY5 CGW session. | ||
MDP3 TCP Channels | Customers will be able to use their TY5 Production session to connect to a TCP gateway in NY5 or LD4.2. | ||
MDP3 Multicast UDP Channels | Customers can consume A and B feeds on the normal multicast addresses and with the same source IPs. | ||
EBS Workstation | EBS Workstation customers must use the New York URL and login using their Production credentials. | ||
| EBS Ai | EBS Ai customers in Tokyo can use their Production APi IDs and connect to one of the IP/Ports in either New York or London. |
DC3 Failover
Post trade processing and Credit and Risk Management solutions are operated from the DC3 Production data center in Illinois. In the event of a DR, these services will be failed over to their DR data center at NYDC. EBS Market and eFix Matching Service in both London and New York will be halted during the DR failover.
Customers do not need to take any action during this recovery scenario except to re-login to applications after recovery.
The following solutions are operated from the DC3 data center:
- EBS Risk Manager services
- CME FirmSoft