Document Version June 2012 First Issue 3

Transcription

1 Service and Technical Description Third Party Connectivity - Network Service Providers (NSPs) Issue 1 September 2012

2 Contents Third Party Connectivity - Network Service Providers (NSP)... 1 Contents... 2 Document Version Introduction Purpose of this document Overview of the service Associated Documentation Third Party markets and services a Network Service Provider can provide Differences between NSP and Vendor Access Network (VAN) Principles and High Level implementation process Principles The NSP Agreement and Questionnaire NSP Implementation flow NSP Design NSP Connectivity Requirements Configuration options for Extranex Extranex Technical Configuration Configuration options for Exchange Hosting Hosting Connectivity to Exchange Services (North de) - Summary Hosting 10Gb Network Diagram North de Hosting - 10Gb Network - Multicast Connectivity End Customer IP Addressing Accreditation Process Test Requirements Introduction Pre-Test Intra Test Post Test Customer Enablement Process Timescales and Pricing Connectivity Pricing Accreditation and NSP service charge pricing Timescales Customer Support Client Technology Group Network Service Provider Product Management CTS UK Helpdesk Borsa Italiana Milan Service Desk Turquoise UK Helpdesk Oslo Bors

3 Document Version June 2012 First Issue 3

4 1. Introduction The Exchange s Network Service Provider ( NSP ) initiative is intended to encourage direct connectivity from customers through the accreditation of financial extranet providers as official Exchange Network Service Providers. With the addition of new markets and continuing organic growth, there is a clear requirement for increased methods of access to support access to all London Stock Exchange platforms and services Purpose of this document The purpose of this document is to provide prospective and existing Network Service Providers (NSPs) with an overview of the Network Service Provider Service (the Service ). This document provides details on the service and its introduction, including the delivery timescales, and details of the technical configuration. This publication constitutes an amendment to the Technical Specifications published by London Stock Exchange Plc Overview of the service Customers can use an accredited NSP to connect to the same Exchange markets and services that can be accessed directly through the Exchange s proprietary Extranex network. These financial extranet providers are themselves connected directly to the Exchange through Extranex or Exchange Hosting connections between the NSP infrastructure and the Exchange. Customers have a contractual relationship with the NSP for the provision of a communications service or link to connect them to the Exchange via the NSP infrastructure. Customers have a separate contractual relationship with the Exchange for those Exchange services provided over the NSP infrastructure. 4

5 1.3. Associated Documentation The Exchange has a range of technical documentation to help Network Service Providers with their implementation of a link to the Exchange and this is available on the Exchange website or can be obtained from Exchange staff. This document describes the guiding principles, technical considerations and operational processes by which a customer can connect to the Exchange via an NSP. Each NSP has a different network and there will be differences in the way customers interact with each NSP and also through the NSP with the Exchange. Further information on each of these services can be found in a range of documents from the Exchange s website: Millennium Exchange Technical Specifications Market Data Bandwidth Profiles This document provides details on the bandwidth requirements for customers and NSPs: Hosting The Exchange Hosting service and Technical Description provide details on the Exchange Hosting Service and is available on request from: [email protected] 1.4. Third Party markets and services via a Network Service Provider The Exchange is able to provide access to third party markets and services through an NSP connection. It is the responsibility of the NSP to obtain any agreements or contractual requirements to provide access to these third party markets and services, and copies of these agreements must be provided to the Exchange prior to activation. Examples of the current services available are shown below: Borsa Italiana BIt Clearing Station (BCS) BIt Trading Station (BTS) 5

6 Borsa Italiana Millennium Exchange DDM+ IDEM SOLA IDEM CLICK FIX Gateway London Stock Exchange FIX Gateway hub Oslo Børs Oslo Børs derivatives SOLA Oslo Børs TradElect/Infolect Oslo Børs Millennium Exchange Turquoise Turquoise Millennium Exchange Turquoise SOLA Derivatives The latest markets and services available over NSP can be found on the Exchange website Differences between NSP and Vendor Access Network (VAN) The Vendor Access Network (VAN) model and Network Service Provider (NSP) are very similar in structure; however the points below aim to clarify the key difference between the two services: VAN providers give end customers an end to end service which includes shared connectivity to the Exchange, as well as accredited software for customers to use. This effectively removes the need for software and network management for the end customer. NSP provide end customers with network access only the Exchange s services. The end customer can use whatever network equipment and end software they wish to use once the NSP has provided them with access. 6

7 2. Principles and High Level implementation process 2.1. Principles The following basic principles dictate the operation of the NSP service model The NSP has a network with access equipment (routers or switches) under their management located at potential customer sites. The NSP has robust and resilient connectivity to two separate sites to ensure customer connectivity in the event of a site failure. The NSP must have sufficient bandwidth, in line with Exchange bandwidth recommendations to ensure it can provide services at all times without risk of delays and loss of data. Prior to design discussions, the NSP would have signed the Network Service Provider Agreement, along with any required communications agreements (available on request) Exchange-managed Extranex or Exchange Hosting links connect the NSP network to the Exchange. The NSP network carries traffic between Extranex and the customers connected off the NSP network. NSPs manage the equipment at the customer site to enable/control customer access to Exchange Services. Each NSP is pre-allocated 32 sets of IP addresses for their customers, should these all be used more will be allocated The NSP s connections are pre-configured during the implementation and accreditation phase to pass traffic to/from this range of customer IP addresses. The customer will order access to a service from the Exchange, and will request configuration of services from their NSP in parallel. 2.2 The NSP Agreement and Questionnaire Prior to ordering any necessary connectivity, the NSP must sign the NSP agreement, and complete the NSP questionnaire which details how their service will function. This will then be reviewed by the Exchange, any required changes discussed and agreed, before being countersigned and returned to the NSP provider. A copy of the NSP agreement and Questionnaire is available on request from: [email protected] 7

8 2.3.NSP Implementation flow The steps below detail at a high level the discussions and key steps involved in accreditation and go-live for a new NSP: 8

9 3. NSP Design 3.1. NSP Connectivity Requirements Network Service Providers must have resilient and robust connectivity from the Exchange s primary and secondary data centre to two NSP sites. This provides two available options to prospective NSP s to connect: Option 1: Extranex Only Option 2: Extranex and Exchange Hosting 9

10 Prior to ordering connectivity, technical discussions can be had with our internal network teams, and service partners to discuss the technical requirements of a new NSP configuration. Please note that while Border Gateway Protocol (BGP) can be used on an Extranex only configuration between two sites, this cannot be achieved on an Extranex/Hosting configuration. This should be taken in to consideration during design discussions Configuration options for Extranex During design discussions, the flow of traffic and failover requirements will be agreed on by the NSP and the Exchange, the exchange ordinarily gives two options for NSP network configuration, as shown in the diagrams below: Community of Interest Network A/B Configuration Primary DC Distribution Node PROD UNICAST TSR4 MC PROD UNICAST TSR4 MC A Feed/HVS CDS A&B CTS/TEST TEST UNICAST /21 LSEG Core Network TEST UNICAST A Feed/HVS Secondary DC Distribution Node A Feed/HVS A Feed/HVS TEST UNICAST CDS A&B CTS/TEST LSEG 1Gbps PROD UNICAST TSR4 MC 1Gbps CDS A CTS/TEST TEST UNICAST A Feed/HVS CDS B CTS/TEST TEST UNICAST PROD UNICAST A Feed/HVS TSR4 MC 1Gbps 1Gbps Primary lse1-xxx a SAP6X0001 PDC AS:65010 SAP6X SDC T1/50 T1/50 T1/50 T1/50 G1/48 G1/48 lse1-xxx b lse1-xxx a G1/48 G1/48 T1/52 T1/52 Gx/x Gx/x AS:XXXX Secondary Primary T1/52 Gx/x AS:65010 lse1-xxx b T1/52 Gx/x AS:XXXX Secondary Customer Switch-A Customer Switch-B Customer Switch-A Customer Switch-B COIN-A NSP Network Production: x.0/21 Test: x.0/21 COIN-B NSP Network Production: x.0/21 Test: x.0/21 10

11 ngle Point configuration Primary DC Distribution Node PROD UNICAST TSR4 MC PROD UNICAST TSR4 MC A Feed/HVS CDS A&B CTS/TEST TEST UNICAST /21 LSEG Core Network TEST UNICAST Secondary DC Distribution Node A Feed/HVS TEST UNICAST CDS A&B CTS/TEST LSEG 1Gbps PROD UNICAST TSR4 MC A Feed/HVS 1Gbps CDS A&B CTS/TEST TEST UNICAST CDS A&B CTS/TEST TEST UNICAST PROD UNICAST A Feed/HVS TSR4 MC 1Gbps 1Gbps Primary lse1-xxx a SAP6X0001 PDC T1/50 T1/50 T1/52 Gx/x G1/48 G1/48 lse1-xxx b lse1-xxx a G1/48 G1/48 T1/52 Gx/x AS:65010 AS:XXXX Tertiary Secondary T1/52 Gx/x T1/50 SAP6X SDC T1/50 lse1-xxx b T1/52 Gx/x AS:65010 AS:XXXX Quaternary Customer Switch-A Customer Switch-B Customer Switch-A Customer Switch-B NSP Network Production: x.0/21 Test: x.0/ Extranex Technical Configuration Physical Connection The Extranex service will be delivered by fibre optic cable directly to customer sites. The fibre optic path is optimized for high throughput through the use of DWDM / CWDM coloured optics. This approach allows higher bandwidth services to be delivered over the same fibre optic pair. The DWDM / CWDM equipment is provided by Cube Optics and is electrically passive. The network service access point at the Network Layer will typically be a pair of Cisco Catalyst 4948E switches per site. The Cisco devices provide the option to have the delivery of the site hand-off as: Copper 1Gb/s ngle Mode Fibre 1Gb/s Multi Mode Fibre 1 Gb/s Network Service Providers can select which hand-off interface they require at the point of ordering the service. The Physical SAP service connection is delivered; Over copper, using the standard RJ45 physical socket, auto MDI/MDI-X or; 11

12 Over single mode fibre, using the standard LC(PC) duplex interface, or; Over multimode fibre, using the standard LC(PC) duplex interface. The Logical SAP service logical interface is; AND over copper, at 1Gb/s only 1 IEEE standard 802.3ab / 1000baseT or; over single mode fibre, at 1Gb/s only IEEE standard 802.3z / 1000baseLX/LH, or; over multi mode fibre, at 1Gb/s only IEEE standard 802.3z / 1000baseSX. Over all of the above interfaces, 802.1Q tagged frames to distinguish VLANs. Physical Cabling and Connectivity The equipment that is installed within the client site includes transmission and Internet Protocol (IP) equipment. The actual location of the equipment may vary depending on what is already installed at a customer site and what accommodation is available at the site; however the actual connectivity between the IP devices doesn t really change Configuration options for Exchange Hosting This section sets out the market connectivity between the Customer Equipment and the relevant Exchange Group Markets (North de Connectivity). In addition, this section identifies the connectivity for dedicated management traffic from the Customer Equipment to the Customer s own location (South de Connectivity) via either the Customer s own chosen carriers (utilising the Management Connectivity Service) or via the Exchange-provided 1Mb VPN Internet connection. This section also details the internal structured cabling which can be utilised for purposes such as distribution of market data, order routing and service management activities by Trading and Non-Trading Participants. It is important to note that all configuration changes to the Exchange Hosting environment and infrastructure are completed during the identified change window 18:00 to 22:00 each weekday (excludes UK public holidays and weekends) Hosting Connectivity to Exchange Services (North de) - Summary The network design that has been implemented provides customers with a 10Gb network (multi-mode fibre) service which provides very low latency connectivity while ensuring maintaining a high level of security and operational standards. For access to the markets, customers are provided with a Customer Switch to Exchange Switch Configuration - connectivity via Customer provided primary and secondary switches connecting to Exchange primary and secondary Hosting access switches. To access the network, clients are provided with a set of 4x switch ports, to be used in the following way: 12

13 - 1x port for Unicast link on primary Exchange switch - 1x port for Multicast link on primary Exchange switch - 1x port for Unicast link on secondary Exchange switch - 1x port for Multicast link on secondary Exchange switch Customers should expect the market data A feed to have lowest latency over the Exchange s primary switch. The market data B feed will have the lowest latency over the secondary switch. The Exchange will provide access to the 10Gb Hosting Network environment via a pair of Unicast cross-connect fibre interfaces and a pair of Multicast cross-connect fibre interfaces (four physical cross-connect interfaces in total). These interfaces will be presented on a local Multimode fibre patch panel within the Customers cabinet in a preagreed U position. Customers will be required to provide their own Layer 3 and 10Gb capable access switches in order to connect to the Exchange Unicast and Multicast cross-connect interfaces. Customers should take care when deciding on the model of switches to be used, to ensure compatibility with the Exchange logical and physical design, available power and space requirements. In order to ensure the lowest possible latency, all Multicast traffic will be delivered to the Customer via the Multicast interfaces only. All Unicast traffic will traverse the Unicast interfaces only. The new Exchange 10Gb Hosting Network does not provide direct Server to Switch connectivity. Please be aware that the 10Gb Hosting Architecture only permits a single pair of Customer switches to directly connect to the Exchange 10Gb Hosting Switches Hosting 10Gb Network Diagram North de The following diagram identifies the market connectivity between the Customer equipment and the Exchange s Millennium Exchange, TradElect and Infolect services. 13

14 Network Diagram Notes Setup Requirements and Information Layer 3 capable switches. The Exchange recommends that the Customer deploys 2 switches for this setup. Connections to Exchange via 10Gbps multimode fibre. Unicast and Multicast interfaces must be physically separate & cannot be trunked. BDPU messages must be disabled. Unicast and Multicast interfaces must be routed interfaces (Layer3). Any Layer2 connectivity will be done via the Exchange switches. Exchange will provide the Customer with 4 x 10Gbps Multimode fibre connections (2 per switch) Exchange utilises IGMP static joins to ensure that the Customer always receives their subscribed groups. For Unicast traffic, Customer points their Unicast gateway to the Exchange VRRP address. Exchange requires the Customer to configure HSRP/VRRP on their Unicast interface. For Infolect Multicast traffic, the Customer sees the same Multicast groups on both of their primary and secondary switches. 14

15 For Millennium Exchange Multicast traffic, the Customer sees both Multicast A- Feed and B-Feed traffic on both of their primary and secondary switches. Exchange switches do not form a PIM neighbours with the Customer switches Hosting - 10Gb Network - Multicast Connectivity In order to provide resilience, the Primary Exchange Switch will provide the first Multicast cross-connect interface and the Secondary Exchange Switch will provide the second Multicast cross-connect interface. Each provided Multicast interface will be a member of a different point-to-point link between the Customer Switch and the Exchange Switch. The pair of Multicast cross-connect interfaces are for the Customer to receive all their subscribed Multicast groups. This includes all subscribed Millennium Exchange groups and Infolect groups. The Exchange will configure the Customers Multicast cross-connect interfaces with the appropriate IGMP static-groups to facilitate the automatic delivery of Multicast group traffic to the Customer. Customers will not need to (or be able to) use IGMP Join messages in order to request membership of the subscribed Multicast groups. The Exchange will not form a PIM neighbourship with the Customer switches. Customer Multicast re-request and replay messages will be sent and received via the Unicast cross-connect interfaces, not via the Multicast cross-connect interfaces End Customer IP Addressing A new NSP will be allocated IP addressing for 32 customers, each with the following addressing available: /26 For all Production Services /26 For all Testing Services For Extranex only configuration, it is possible for NSP s to provide their customers with publically registered IP addressing for their Extranex links, however the following rules apply: The NSP provided IP address subnets have to be a public range and registered to their company e.g. on RIPE database. The registered subnet for production has to be a minimum of a /26 per customer. The registered subnet for Customer Testing has to be a minimum of a /27. A contiguous subnet has to be provided for each service i.e. Production and Customer Testing. The subnets should support growth within the NSP network to avoid running out of host addresses. The subnet is dedicated to a ngle customer SAP and cannot be used elsewhere on the LSE network or via another customer SAP. 15

16 4. Accreditation Process 4.1. Test Requirements Introduction Prior to being confirmed as an accredited Network Service Provider, an NSP must complete tests to ensure that their solution can reach and receive all required sets of data, and can meet failure scenarios with minimal disruption to end customers. Tests are booked through the NSP product manager, and require 1 week notice Pre-Test Prior to a testing session being booked, the Exchange will configure Multicast and Unicast services for any markets or services which the NSP is going to provide to end customers. This will allow the NSP to see real data perform any pre-test checks that may be required within their own network. As part of this configuration, the Exchange will provide the NSP with details of the IP addressing used for Multicast and Unicast services. The NSP will need to be able to confirm receipt of Multicast data from the Exchange, and submit Unicast requests to the interactive gateways to confirm they are able to reach them; therefore the NSP will need to ensure they have suitable network tools to perform this task. Multicast confirmation Prior to testing, the NSP will be asked to confirm they are able to see messages for ALL Multicast channels they are subscribed to for their customers. Written confirmation must be provided to the Exchange that this is the case prior to accreditation being given Intra Test The accreditation test takes place after 5pm between Monday-Thursday; the Exchange will provide a conference bridge number for all parties to dial in. Ordinarily the NSP Product Manager, Network Engineer/s and NSP are present on the call. Unicast Confirmation The NSP will test to confirm they can reach all required Unicast addresses, written confirmation will be provided to the Exchange to confirm that this is the case, and will be verified by network engineers on the conference call. 16

17 Failover and Recovery Testing Network Engineers will then simulate the failure of network components to ensure that the NSP is still able to receive Multicast and reach Unicast services. The network components will then be restored and the test repeated Post Test Once the test is successfully completed, and the NSP has notified the exchange that they can see all required Multicast/Unicast services, the Exchange will then confirm to the NSP in writing that they are accredited. 17

18 5. Customer Enablement Process The diagram below explains at a high level how a customer is enabled: The customer should contact the relevant market they require access to directly to arrange enablement, as well as notifying their NSP. 18

19 6. Timescales and Pricing 6.1. Connectivity Pricing Pricing for Extranex and Exchange Hosting connectivity are available on request: Tel: +44 (0) NSP service charge pricing Pricing for accreditation and service charges for Network Service Providers can be found on the Exchange website: Timescales Installation of Extranex lines is approximately 12 weeks from point of order. Installation of a hosting rack configuration is approximately 4 weeks. Usual time for accreditation test once lines have been handed over is approximately 2 weeks. NSPsshould factor these timescales into any project delivery plan. 19

20 7. Customer Support 7.1. Client Technology Group The Client Technology Group will provide technical support and advice via: The Technical Information Desk on +44 (0) , STX The Client Technology Group via 7.2. Network Service Provider Product Management Client Technology Services (CTS) UK Service Desk am-6pm (UK Time) 7.4. Client Technology Services (CTS) Italy-Service Desk / [email protected] 7.30 am pm (CET) 7.5. Turquoise UK Helpdesk Equities [email protected] 7am-5.30pm (UK Time) Derivatives [email protected] 7am-5.30pm (UK Time) 7.6. Oslo Bors [email protected] 20

21 Copyright September 2012 London Stock Exchange plc. Registered in England and Wales No London Stock Exchange plc has used all reasonable efforts to ensure that the information contained in this publication is correct at the time of going to press, but shall not be liable for decisions made in reliance on it. London Stock Exchange and the coat of arms device are registered trade marks of London Stock Exchange plc. London Stock Exchange 10 Paternoster Square London EC4M 7LS Telephone: +44 (0)