TT CME Gateway System Administration Manual - Trading ...
TT CME Gateway System Administration Manual - Trading ...
TT CME Gateway System Administration Manual - Trading ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
6 Disaster Recovery<br />
Exchange Host Failure and Recovery<br />
Overview Several types of failures can occur between the customer’s network and the<br />
exchange. Such failures can involve network devices, the <strong>CME</strong> Group price and<br />
order environments, and the exchange matching exchange. Of these failures, this<br />
section discusses three primary types:<br />
• Exchange Host Failure<br />
• MDP Server Failure<br />
• MDP Price Delivery Failure<br />
• iLink Server Failure<br />
Exchange Host Failure In the event that only the <strong>CME</strong> Group exchange host fails, all traders on the <strong>TT</strong><br />
<strong>System</strong> experience the following:<br />
• Orders: <strong>CME</strong> Group rejects all submitted orders.<br />
• Prices: Prices go stale.<br />
However, the <strong>TT</strong> <strong>Gateway</strong> continues to run and remains connected to the <strong>CME</strong><br />
Group’s iLink and MDP servers.<br />
When the exchange host again goes live, the <strong>TT</strong> <strong>Gateway</strong> receives the appropriate<br />
fix messages. Traders can again begin trading normally and prices begin updating<br />
as normal.<br />
MDP Server Failure When an MDP server fails in the <strong>CME</strong> Group’s environment, any Price Servers<br />
connected to it shutdown after the number of seconds set in the<br />
HeartbeatTimeout parameter of the [price_session] section in the<br />
hostinfo.cfg file. These Price Servers appear red (inactive) in Guardian. During<br />
the MDP server failure, all prices remain stale.<br />
MDP Price Delivery<br />
Failure<br />
<strong>CME</strong> <strong>Gateway</strong> <strong>System</strong> <strong>Administration</strong> <strong>Manual</strong> 117<br />
<strong>Trading</strong> Technologies International, Inc.<br />
This section highlights gateway behavior during price transmission failure. The<br />
<strong>CME</strong> Group provides price data along two separate yet identical feeds. The data<br />
packets are transmitted with sequence numbers to help identify missing packets.<br />
If the <strong>TT</strong> <strong>Gateway</strong> discovers a missing sequence number, the Price Server updates<br />
with correct information after receiving the next price update.<br />
When waiting for the next price update, the <strong>CME</strong> <strong>Gateway</strong> may temporarily<br />
remove market data. This information automatically repopulates when a new<br />
price update is received.<br />
You must verify that the price feeds are receiving data. For further information,<br />
refer to the section called Verifying Connectivity on page 43.<br />
iLink Server Failure When a <strong>CME</strong> Group iLink Server fails, all Order Routers that connect to that server<br />
lose their connections. Normally, the Order Routers on the <strong>TT</strong> <strong>Gateway</strong> cycle to<br />
the backup iLink server whose connection information is included in the<br />
hostinfo.cfg file.<br />
However, in the case that both iLink servers fail, Order Routers on the <strong>CME</strong><br />
<strong>Gateway</strong> begin cycling by attempting to connect first to the Primary and then to<br />
the Backup IP addresses listed in the hostinfo.cfg file.<br />
The <strong>CME</strong> Group exchange host may or may not retain orders that reached the<br />
exchange prior to the failure. Traders must call <strong>CME</strong> Group for an accurate<br />
accounting of their orders.<br />
For details on Order Router cycling and recovery, refer to the section<br />
called <strong>Gateway</strong> Recovery: Order Routers on page 111.