TT CME Gateway System Administration Manual - Trading ...

6 Disaster Recovery
Failover Behavior: Secondary CME Gateway
Overview Secondary CME Gateways offer traders the opportunity to continue trading should
one or more routes to the CME Group fail. When a CME Gateway fails in a failover
environment during trading hours, all current orders remain as working orders in
the market
Gateway Failover
Behavior
Secondary Gateway
Recovery: Software
Secondary Gateway
Recovery: Hardware
Example 2: Unsuccessful
Failover
CME Gateway System Administration Manual 115
Trading Technologies International, Inc.
Note: You can use secondary, redundant CME Gateways under the following conditions:
• Each has a unique exchange-flavor.
• You do not repeat the member parameter in any [order_session_#] sections in the
hostinfo.cfg files on other CME Gateways.
When you set up secondary CME Gateways on a network, traders can log into
another CME Gateway to continue trading if the CME Gateway fails.
After reconnecting to the CME Group in this manner, traders have no access to
their current working state or position in the market (i.e., historical information).
This information remains on the failed TT Gateway in its log and table files.
Note: If you intend on installing secondary CME Gateways for disaster recovery purposes,
traders must use unique Member IDs when logging into the different TT Gateways. This is a
CME Group restriction. For example, if trader Jim wants access to the exchange through
CME -A and CME-B, he must have a Member ID for CME-A and a different Member ID for
CME-B. In this manner, his login on each TT Gateway is different.
After a trader closes and then reopens X_TRADER ® and then logs into the
alternate CME Gateway, the TT system exhibits the following behavior:
• Fills: X_TRADER ® does not have access to any fills that occurred previous
to the trader connecting to the secondary CME Gateway because the *.bof
files do not hold the fills for the new trader.
• Orders: After traders reconnect, they can submit orders. However, they do
not have access to any active orders that were in the market at the time
of the previous connection being lost. This information is on the failed TT
Gateway.
Refer to the section called Single Gateway Failure on page 111 for details on
CME Gateway software recovery.
Refer to the section called Single Gateway Failure on page 111 for details on
CME Gateway hardware recovery.
Having recovered from the hard drive crash in the previous Example Scenario 1
– Single CME Gateway, Quick Financial Services (QFS) now has two CME
Gateways (referred to as A and B) conforming to the setup criteria for Redundant
CME Gateways. During the day, the exchange connections on gateway A fail.
Gateway A immediately loses its connection to the exchange and shuts down. All
traders on gateway A lose their connection to the exchange and gateway A
displays as red in Guardian across the network. Prices become stale, traders stop
receiving fills, and they are unable to trade.
Jim first documents his position. With his documented position in hand, Jim calls
CME Group and cancels all outstanding orders. He then closes X_TRADER ® ,
reopens it, and logs into gateway B to continue trading. Jim already has
previously saved workspace on this gateway and is not prompted to convert.