Changes of multicast addresses and partition ID for some ETF instruments currently located on partition 59

Release date: 10 Dec 2019

084/2019 Changes of multicast addresses and partition ID for some ETF instruments currently located on partition 59 Xetra Circular 084/19 Changes of multicast addresses and partition ID for some ETF instruments currently located on partition 59

1.    Introduction

For performance optimisation reasons, Deutsche Börse is planning to move approximately 250 ETF instruments currently located on partition 59 to partition 57. The affected instruments will also receive new multicast addresses for the dissemination of Market Data via the EOBI market data interface. The multicast addresses for the MDI and EMDI market data interfaces will remain unchanged.

The redistribution of the affected instruments to partition 57 and the reconfiguration of the multicast groups for EOBI will become effective in the T7 production environment from Monday, 20 January 2020 onwards. The existing port numbers used for the dissemination of market data will remain unchanged.

Optional connectivity test: 18 January 2020

Production start: 20 January 2020

2.    Required action

Depending on the set-up of a participant, reconfigurations may be required.

3.    Details 

A. Access to the updated reference data prior to the production start

To provide participants with access to the reference data containing all the respective changes prior to the start of trading on Monday, 20 January 2020, the reference data via Reference Data Interface (RDI) and Reference Data File (RDF) on the Common Report Engine (CRE) and in the Member Section will be provided on Saturday, 18 January 2020. In addition, connectivity testing with ETI sessions will also be possible on Saturday, 18 January 2020. More information regarding the availability of the T7 production system will be provided later.

A list of the affected instruments and the new multicast addresses can be found on the Xetra website www.xetra.com under the following link:

B. Possible impact

Please note: Moving products from one partition to another may lead to a scenario where GTC/GTD orders entered and owned by one high-frequency session come to reside on two different partitions. As a high-frequency session login is always partition specific (via a partition specific gateway), the respective owning session needs to login to the new partition to manage orders for products which have been moved. To manage orders for products which have not been moved, the owning session needs to login to the old partition.
 

Further information

Recipients:All Xetra® and Börse Frankfurt Members and Vendors
Target groups:Traders, Technical Contacts, Security Administrators, System Administrators, General
Contact:

Technical Key Account Manager via your VIP number or cts@deutsche-boerse.com

Authorized by:

Bernd Eschenbrücher, Holger Patt

Market Status

XETR

-

-

Parts of the trading system are currently experiencing technical issues

The trading system is currently experiencing technical issues

Xetra newsboard

The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.

Please find further information about incident handling in the Emergency Playbook published on the Xetra webpage under Technology --> T7 trading architecture --> Emergency procedures. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message

We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.


Emergency procedures


An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.