This topic describes the DR process for ITC market data.
Normal Production Processing ITC Format
The following figure displays a simplified diagram of the ITC architecture in the Normal Production Processing environment.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
In this state:
- Both feeds are available.
- TCP Replay is available.
DR Event - ITC Format
As quickly as feasible, GCC will declare a DR event using the notification procedure.
Transition to DR Environment ITC Format
After the DR event, the architecture changes during the Transition to DR Environment stage depicted in the following figure.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
In this state:
- Feeds A and B are not available.
- TCP Replay requests are not available.
- GCC will communicate DR event status and timeline to begin the Pre-Open activities in the DR environment 45 minutes in advance of the Market Opening.
Connection & Trading in DR Environment - ITC Format
After moving to Connection & Trading in the DR Environment, the architecture is depicted in the following figure.
| Gliffy | ||||||
|---|---|---|---|---|---|---|
|
In this state:
- Resume listening to Feed A and Feed B.
- The Feed A and Feed B source IP addresses will remain the same.
- The connection starts with Beginning of Week processing.
- Sequence numbers are reset.
- Instrument definitions are sent.
- TCP Replay and Market Recovery are available in the DR environment.
- TCP Replay and Market Recovery are not available for Pre-DR event Market Data.
- Multicast groups will remain the same.
Return to Production - ITC Format
GCC will notify customers when the DR event is resolved and the timeframe for re-establishing the ITC connection back to the Production environment. This reconnection to the CME Globex Production environment will be a scheduled procedure with sufficient notification time.