Trading Continuity During a Failover Event
This section provides the steps required to continue trading during a failover event, and describes the impact to market access and TT Gateway operation.
TT recommends that you review the remainder of this document to increase preparedness for potential service disruptions. Contact your TT Technical Account Manager (TAM), a member of the Customer Support Center or TTNET Operations for guidance on when to follow the procedures and steps listed in the following sections.
Working with TT Support
TTNET customers have access to two lines of support when a disruption to service occurs:
- TTNET Hotline: The main point of contact during a failover and recovery event affecting TTNET customers.
- Customer Support Center (CSC): The front-line to customers’ request for information and assistance. The CSC actively monitors customer contacts for patterns that reflect a disruption to service that affects multiple users.
At the time of a service disruption, TTNET Operations will send a Customer Advisory (CA) indicating which service(s) are impacted and the service’s general state of operation. Subsequent Customer Advisories will be sent to clarify, detail, indicate status, or instruct customers on action they may need to take to minimize impact on their positions.
For intermediate assistance, users may contact the CSC using the contact information listed below.
TTNET Hotline Numbers
The TTNET Hotline serves as the main point of contact during a failover and recovery event.
- Toll-Free (U.S. only): +1 866 558 8638
- Chicago: +1 312 476 1005
- London: +44 (0) 207 621 8139
- Sydney: +61 2 8022 1702
- Singapore: +65 6395 7055
- Tokyo: +81 (0) 3 4577 8345
Customer Support Center (CSC)
The TT CSC provides 24-hour support when the markets are open. CSC phone lines are staffed each week from 12:00pm Sunday to 5:00pm Friday Central Time.
- Toll-Free (U.S. only): +1 877 424 8844
- Americas: +1 312 476 1002
- Europe/Middle East: +44 20 7621 8181
- Asia/Pacific: +65 6395 7002
- Australia: +61 2 8022 1702
- Japan: +81 3 4577 8302
Migrating Users to Backup Gateway
During a Failover Event, you as the administrator must perform the following steps in order to migrate users to the backup TT Gateway.
1. Contact TT at the TTNET Hotline.
The firm must contact TT to coordinate the failover process.
2. Contact BVMF and request that session IDs are logged out of the exchange.
Allows users to login to the exchange with the same session ID via the backup TT Gateway.
3. Verify the backup TT Gateway is “available to user” in TT User Setup
The risk administrator may pre-configure the backup TT Gateway to be available for the user in TT User Setup. If not previously configured, customer administrators need to check "available to user" in TT User Setup for backup gateways.
4. Traders must log out of X_TRADER to fully log out of the primary TT Gateway.
Allows traders to reuse existing logins on the backup gateway.
5. Uncheck the “available to user” setting for the primary TT Gateway in TT User Setup.
Prevents traders from accidentally logging into the problematic TT Gateway.
6. Traders should log into the backup gateway.
Workspaces will be converted to the backup TT Gateway however Algos must be manually updated to reflect the backup TT Gateway flavor (e.g., BVMF-B).
7. If Autotrader and/or RTD links are used, users will need to edit the spreadsheets to use the backup BVMF Gateway Flavor via the find / replace feature in Excel
You must update the exchange-flavor in both Autotrader and Excel.
|8. If Order Routing FIX Adapters are in use via the primary BVMF Gateway, additional actions are necessary.||Refer to the Order Routing FIX Adapter Failover Guide.|
All TTNET price feeds are deployed with local data center redundancy and tertiary backup in a DR data center. Because of the way TTNET distributes market data globally, a failure of the price feed to a DR data center, does not require users necessarily fail over their services to that data center. Failover between the price servers (per market) is configured as hot standby, and requires no customer or user intervention. During a data center outage, TTNET will initiate any price feed failovers as necessary.
Order and Fill Behavior During Failover
The following table highlights the behavior of orders and fills during a failover event.
Non-GTC Orders (including GTD)
Non-GTC orders remain working at the exchange when the primary TT Gateway disconnects. However, working orders on the primary gateway are not visible after a user logs on to and begins using the backup gateway.
WARNING: Users must contact the exchange to determine their current position and status of working orders from the primary Gateway.
GTC Orders (including GTDate)
During a failover event, GTC orders entered on the primary gateway continue working at the exchange. Users must contact the exchange to cancel any working GTC orders.
These orders may appear grayed out or incorrectly remain in their last known state in the X_TRADER® order book. Any action on these orders is rejected by the Gateway while the primary gateway is disconnected.
GTC orders that are filled during the failover event do not appear in the traders’ order and fill books on the secondary gateway and must be reconciled following recovery. In addition, GTC orders placed on the backup gateway cannot be moved to the primary gateway after recovery.
When traders log into the backup BVMF Gateway, they will not have access to working orders or previous fills. This information remains on the failed primary BVMF Gateway.
As all exchanges handle the various working order types differently often depending on the type of disconnect, it is strongly recommended that users contact the exchange to determine which orders are working or not working after a failure incident.
Ensure that all risk settings are the same on the primary and backup gateway. Since previous orders and fills are not available on the backup gateway, all risk limits will reset.
Any P/L based on activity through the primary gateway will not be factored into the users’ overall risk limits on the backup gateway.
If using Autospreader SE, any Autospreader synthetic orders with the primary Gateway designated as one of the spread legs will attempt to delete all of its child quoting orders. Child orders that were in the market prior to the failure could still be working at the exchange. Users should contact the exchange to manage these working orders as needed.
If using Algo SE, any Algo synthetic orders that subscribed to the primary Gateway will be paused. Child orders that were in the market prior to the failure could still be working at the exchange. Users should contact the exchange to manage these working orders as needed.
Synthetic SE orders that were working on the failed, primary gateway behave as follows:
Users should delete Synthetic SE staged and synthetic orders (including native child orders) and may resubmit them on the backup gateway.