Try TT Now

Recovery Behavior: Secondary CFE Gateway

Overview

Secondary CFE Gateways offer traders the opportunity to continue trading should one or more routes to the CFE fail. When a CFE Gateway fails in a redundant environment during trading hours, all current orders remain as working orders in the market.

Note

You can use secondary CFE Gateways under the following conditions:

  • Each has a unique Exchange-Flavor.
  • If you repeat the member parameter in any [OrderServerSession_#] sections in the hostinfo.cfg files on other CFE Gateways, this member cannot have two sessions active at a time (one on each gateway).

When you set up secondary CFE Gateways on a network, traders can log into another CFE Gateway to continue trading if the CFE Gateway fails.

After reconnecting to the exchange 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 install secondary CFE Gateways for disaster recovery purposes, traders can use their same Member IDs when logging in to the secondary TT Gateways; however, only one session can be active at a time. For example, if trader Jim wants access to the exchange through CFE -A and CFE-B, he can use the same Member ID for CFE-A and CFE-B, which are both active in the trading network. However, trader Jim cannot be logged in to both CFE -A and CFE-B simultaneously -- a Membership can have only one active session at a time.

Gateway Failover Behavior

After a trader closes and then reopens X_TRADER® and then logs into the alternate CFE 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 CFE 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.

Secondary Gateway Recovery: Software

Refer to Single Gateway Failure for details on CFE Gateway software recovery.

Secondary Gateway Recovery: Hardware

Refer to Single Gateway Failure for details on CFE Gateway hardware recovery.

Example 2: Recovery Scenario

Having recovered from the hard drive crash in the previous Example Scenario 1 – Single CFE Gateway, Quick Financial Services (QFS) now has two CFE Gateways (referred to as A and B) conforming to the setup criteria for Redundant CFE 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.

First, traders document their positions, calls the exchange, and cancels all working orders. They then close X_TRADER®, reopen it, and log into gateway B to continue trading. These traders already have a previously saved workspace on this gateway and are not prompted to convert. When the traders log into gateway B, none of their fills or orders refresh. They do not have access to their historical fills. They resume trading via Gateway B.

The IT staff at QFS restarts Gateway A. Traders can begin logging into Gateway A, and trading continues as normal. However, if traders submit orders on Gateway B, then log off B and into Gateway A, those traders do not have access to trading activity (orders and fills) managed by Gateway B.