Try TT Now

Recovery Behavior: Secondary MX Gateway

Overview

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

Note

You can use secondary MX 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 MX Gateways, this member cannot have two sessions active at a time (one on each gateway).

When you set up secondary MX Gateways on a network, traders can log into another MX Gateway to continue trading if the MX 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 MX 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 MX -A and MX-B, he can use the same Member ID for MX-A and MX-B, which are both active in the trading network. However, trader Jim cannot be logged in to both MX -A and MX-B simultaneously -- a Membership can have only one active SAIL session at a time.

Gateway Failover Behavior

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

Secondary Gateway Recovery: Hardware

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

Example 2: Recovery Scenario

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