Upload
others
View
12
Download
0
Embed Size (px)
Citation preview
Attachment 2
HSN Network Commissioning Test Plan for
New HSN Network
HKEX Service Network
Version 7.1
Date : 5 JUL 2019
HKEX Service Network Commissioning Test
Classification: Confidential Page 2 of 31
Document Control
Change History
Version Issue Date Record of Changes
7.1 4 JUL 2019 - Simplified commissioning test procedures for HSN
Hardware Replacement Connectivity Test
HKEX Service Network Commissioning Test
Classification: Confidential Page 3 of 31
Table of Content
1 INTRODUCTION 5
2 TEST OBJECTIVES 5
3 SUBMISSION 5
4 TESTING TOOLS 5
5 NETWORK CONNECTIVITY TEST ENVIRONMENT 7
6 NETWORK COMMISSIONING VERIFICATION PROCEDURES 8
6.1 BGP PEER AND ADVERTISEMENT STATUS VERIFICATION FOR NEW HSN 8
6.2 HKEX UNICAST HOST CONNECTIVITY VERIFICATION 8
6.3 MULTICAST TRAFFIC VERIFICATION UNDER NORMAL SCENARIO 9
6.4 HSN UPLINK FAILOVER VERIFICATION 14
7 APPENDIX A-1 MULTICAST GROUP AND PORT NUMBER FOR OMD-C &
OMD-CC NETWORK COMMISSIONING TEST 21
8 APPENDIX A-2 MULTICAST GROUP AND PORT NUMBER FOR OMD-D
NETWORK COMMISSIONING TEST 24
9 APPENDIX B MULTICAST TESTING INDEX 30
HKEX Service Network Commissioning Test
Classification: Confidential Page 4 of 31
Disclaimer
HKEX and/or its subsidiaries endeavour to ensure the accuracy and
reliability of the information provided, but do not guarantee its accuracy and
reliability and accept no liability (whether in tort or contract or otherwise) for
any loss or damage arising from any inaccuracy or omission or from any
decision, action or non-action based on or in reliance upon information
contained in this information sheet.
© Copyright 2018 HKEX
All Rights Reserved
HKEX Service Network Commissioning Test
Classification: Confidential Page 5 of 31
1 Introduction
The purpose of this document is to describe the process, currently deployed by
HKEX, for network connectivity test to the HKEX Service Network (HSN).
2 Test Objectives
This HSN Network Commissioning Test is to assist the subscriber layer 3 switches
interoperable with HSN. It should be noted that performance test is beyond the
scope of this test.
Subscriber has responsibility to perform all the tests on the subscribed services.
Subscriber can skip those tests which are not subscribed.
HKEX strongly recommends EP/IVs to perform all tests whenever applicable since
change has been made to the Subscriber layer 3 switches.
HKEX reserves the right to decline the HSN port connectivity if any one of the test
in section 6 is failed or incompletion.
3 Submission
Upon completion of all test cases, subscriber should fill in the test result table in
“HSN Connectivity Test Result Confirmation Form”
4 Testing Tools
Hosting Subscriber is responsible for the following testing devices:
a. 2 fully configured Layer 3 Switches in subscriber rack(s) based on the IP address
and BGP parameters provided by HKEX.
HKEX Service Network Commissioning Test
Classification: Confidential Page 6 of 31
b. At least 1 PC workstation or laptop computer running in Windows platform which
connecting to the subscriber switch to perform PING and multicast receiving
testing.
Subscriber should use the IP address within the server/client subnet to simulate
the real production server/client. For detail IP address assignment format,
please refer to the Hosting Services Interface Specification.
c. To assist subscriber to test OMD-C, OMD-CC and OMD-D multicast, subscriber
may contact Hosting Help Desk to get a script client program which is running
in 64bits Windows.
d. The testing notebook / laptop should be installed with Perl and VC distribution
(vc_redist.x86.exe or vc_redist.x64.exe).
e. Subscriber can use their own multicast testing program but detail log should be
provided to HKEX after test was successfully completed. HKEX will not take any
responsibility to verify such test results. Instead, subscriber has his/her own
responsibility to prove the results which comply all technical requirement in the
Hosting Services Interface Specification.
f. For IIS testing, IP address for the testing client should be x.x.x.200 of that
specific subnet.
g. For OCG & CCCG testing, IP address for the testing client should be x.x.x.240
of that specific subnet.
h. For HKATS (Genium CG & NG, PTRM) testing, IP address for the testing client
should be x.x.x.240 of that specific subnet.
HKEX Service Network Commissioning Test
Classification: Confidential Page 7 of 31
i. For OMD-C & OMD-CC testing, subscriber should use the 15th IP address of the
specific subnet. For example, if the subscriber has 10.121.0.0/27, the IP address
of the testing client should be 10.121.0.15.
j. For OMD-D testing, subscriber should use the 15th IP address of the specific
subnet. For example, if the subscriber has 10.123.0.0/27, the IP address of the
testing client should be 10.123.0.15.
k. For those testing client in ASP OMD-C, OMD-CC or OMD-D, since IP subnet is
24bit, IP address for testing client should be x.x.x.202.
l. To speed up the testing, subscriber may consider to use multiple clients at the
same time to simulate different clients in different VLANs.
5 Network Connectivity Test Environment
Below diagram shows the high level network topology for commissioning testing.
HSN
Subscriber Switch 1 Subscriber Switch 2
Subscriber LAN
iBGP Peer
EBGP Peer for Unicast EBGP Peer for UnicastEBGP Peer for Multicast
EBGP Peer for Multicast
100M/1G/10G100M/1G/10G
Multicast Server 2Multicast Server 1
Multicast Stream 1Multicast Stream 2
Testing PC/Notebook
HKEX Service Network Commissioning Test
Classification: Confidential Page 8 of 31
6 Network Commissioning Verification Procedures
This section describes how to perform network verification for HSN.
6.1 BGP Peer and Advertisement Status Verification for New HSN
a. Objective
To verify BGP is properly peering to the new HSN.
b. Test Procedures
- After the HSN ports were switched to the new HSN by HKEX, subscriber is
advised to check the BGP peering status and prefixes, which should be the
same before the HSN migration.
c. Expected Results
All BGP peers status should be in established state as list below:
- Subscriber Switch 1 to HSN
- Subscriber Switch 2 to HSN
- Subscriber should receive the same prefixes before the HSN switch over.
d. Actual Result
Subscriber should fill in the test result in the “HSN Connectivity Test Result
Confirmation Form”
6.2 HKEX Unicast Host Connectivity Verification
a. Objective
To confirm the Unicast connectivity between hosting subscriber network and HSN
is properly configured.
b. Test Procedures
Subscriber should select the test according to the subscribed services.
HKEX Service Network Commissioning Test
Classification: Confidential Page 9 of 31
i. Test Procedures
- Ping to the HKEX host IP address
- Capture the PING log result.
- It is suggested to use multiple Windows prompts to speed up the test.
c. Expected Result
- Ping should be successful without any packets lost
d. Actual Result
Subscriber should fill in the test result in the “HSN Connectivity Test Result
Confirmation Form”
6.3 Multicast Traffic Verification under Normal Scenario
This section is applicable to OMD-C, OMD-CC and OMD-D Subscriber only.
Subscriber should select the test according to the subscribed services.
Source Destination
HKATS Genium
INT NG / CG
Testing client in
HKATS VLAN
10.151.5.241 (primary)
10.152.5.241 (secondary)
HKATS PTRM Testing client in
HKATS VLAN
10.151.14.254 (primary)
10.152.14.254 (secondary)
OCG Testing client in
OCG VLAN
10.1.93.231 (primary)
10.2.93.231 (secondary)
CCCG Testing client in
CCCG VLAN
10.1.145.231 (primary)
10.2.145.231 (secondary)
OMD-C & OMD-CC Testing client in
OMD-C VLAN
10.1.90.32 (primary)
10.2.90.32 (secondary)
OMD-D Testing client in
OMD-D VLAN
10.170.3.241 (primary)
10.170.13.241 (secondary)
IIS Testing client in IIS
VLAN
192.168.228.11 (primary)
192.168.229.11 (primary)
192.168.233.11 (secondary)
HKEX Service Network Commissioning Test
Classification: Confidential Page 10 of 31
a. Objective
To confirm the Multicast Traffic can successfully disseminate from HSN to
hosting subscriber network from both primary and secondary uplink at the same
time.
b. Highlights
It should be noted that the multicast group addresses and port number used in
this test are NOT real production multicast group addresses.
Please refer to the Interface Specification and OMD connectivity guide for actual
production multicast group addresses.
c. Test Procedures for OMD-C, OMD-CC & OMD-D
i. In the Windows command prompt, enter the following command:
> checkomd1 40 60
Wait around 5 minutes for the result. Within this 5 mins, the test client
program will collect all the multicast group packets in all the subscribed
OMD-C, OMD-CC & OMD-D services in both primary and secondary
port.
HKEX Service Network Commissioning Test
Classification: Confidential Page 11 of 31
After 3 minutes, the client program will finish as below.
The “200” in the screen dump is a sample number of packet received in
the specific subscribed multicast group which will be greater than 0.
ii. Launch another script in the Windows command prompt to verify the
test result:
> perl chk_pmc7-1.pl hsn_result.txt hsn_check.txt xx+xx+xx
HKEX Service Network Commissioning Test
Classification: Confidential Page 12 of 31
Please refer to the appendix C for the meaning of xx.
For example :
A Subscriber booked “OMD-C Product: Securities FullTick(sf),
Conflated Broker Queue(cbq), Odd Lot Order(olo)” & “OMD-D Product:
Derivatives FullTick – Non-SOM(dfn), Derivatives FullTick – SOM(dfs)”.
The command is as below:
> perl chk_pmc7-1.pl hsn_result.txt hsn_check.txt sf+cbq+olo+dfn+dfs
Highlights:
Subscriber must enter all the subscribed OMD-C, OMD-CC & OMD-D
services. Test will be failed if anyone is missing
This script will verify all the multicast channels datafeed collection in
step i., according to the inputted subscription.
Please refer to the appendix C for the result meaning
HKEX Service Network Commissioning Test
Classification: Confidential Page 13 of 31
iii. Capture multicast logs “hsn_result.txt” & results “hsn_check.txt” from the
folder.
d. Expect Result
- For OMD-C, OMD-CC & OMD-D subscriber, a “==== OK ====” message
should be prompted on the screen after verification script in above section iii.
e. Actual Result
Subscriber should fill in the test result in the “HSN Connectivity Test Result
Confirmation Form”
HKEX Service Network Commissioning Test
Classification: Confidential Page 14 of 31
6.4 HSN Uplink Failover Verification
6.4.1 Primary Link Failover Verification
HSN
Subscriber Switch 1 Subscriber Switch 2
Subscriber LAN
iBGP Peer
EBGP Peer for Unicast EBGP Peer for UnicastEBGP Peer for Multicast
EBGP Peer for Multicast
100M/1G/10G100M/1G/10G
Multicast Server 2Multicast Server 1
Multicast Stream 1Multicast Stream 2
Testing PC/Notebook
a. Objective
To confirm subscriber network is fully compatible with new HSN network upon
primary HSN uplink port failure.
b. Testing Procedures
The Unicast and Multicast test should be performed simultaneously.
Subscriber should select the test according to the subscribed services.
1. Unicast Connectivity Test Verification
Continuously Ping to HKEX hosts as below, whenever applicable to the
subscribed services.
Source Destination
HKATS Genium
INT NG / CG
Testing client in
HKATS VLAN
10.151.5.241 (primary)
10.152.5.241 (secondary)
HKEX Service Network Commissioning Test
Classification: Confidential Page 15 of 31
2. Subscriber disables/disconnects the HSN PRIMARY uplink port in the
primary switch.
3. Routing Table Verification
Verify the routing table in the PRIMARY switch to show that the
Subscriber switch can still receive routes via the secondary switch
4. Multicast Connectivity Test Verification
Verify the test result to receive the secondary multicast streams by
adding “ro” in the end of the command
> perl chk_pmc7-1.pl hsn_result_link_ro.txt hsn_check_link_ro.txt
xx+xx+xx+ro
,where xx is the product type in Appendix C
“ro” must be entered since it is used to verify the secondary multicast
streams.
HKATS PTRM Testing client in
HKATS VLAN
10.151.14.254 (primary)
10.152.14.254 (secondary)
OCG Testing client in
OCG VLAN
10.1.93.231 (primary)
10.2.93.231 (secondary)
CCCG Testing client in
CCCG VLAN
10.1.145.231 (primary)
10.2.145.231 (secondary)
OMD-C & OMD-CC Testing client in
OMD-C VLAN
10.1.90.32 (primary)
10.2.90.32 (secondary)
OMD-D Testing client in
OMD-D VLAN
10.170.3.241 (primary)
10.170.13.241 (secondary)
IIS Testing client in IIS
VLAN
192.168.228.11 (primary)
192.168.229.11 (primary)
192.168.233.11 (secondary)
HKEX Service Network Commissioning Test
Classification: Confidential Page 16 of 31
This script will verify all the multicast channels according to the inputted
subscription.
Subscriber must select all the subscribed OMD-C, OMD-CC & OMD-D
services. Test will be failed if anyone is missing.
Capture multicast logs “hsn_result_link_ro.txt” & results
“hsn_check_link_ro.txt” from the folder.
Subscriber enables/reconnects the switch HSN uplink port and wait for the BGP
peers to become established status.
c. Expect Results
- Unicast traffic (Ping Traffic) switchover to secondary link and resume
automatically.
- a “==== OK ====” message should be prompted on the screen after
verification script in above section.
d. Actual Result
HKEX Service Network Commissioning Test
Classification: Confidential Page 17 of 31
Subscriber should fill in the test result in the “HSN Connectivity Test Result
Confirmation Form”
6.4.2 Secondary Link Failover Verification
HSN
Subscriber Switch 1 Subscriber Switch 2
Subscriber LAN
iBGP Peer
EBGP Peer for Unicast EBGP Peer for UnicastEBGP Peer for Multicast
EBGP Peer for Multicast
100M/1G/10G100M/1G/10G
Multicast Server 2Multicast Server 1
Multicast Stream 1Multicast Stream 2
Testing PC/Notebook
a. Objective
To confirm subscriber network is fully compatible with new HSN network upon
Secondary HSN uplink port failure.
b. Testing Procedures
The Unicast and Multicast test should be performed simultaneously.
Subscriber can select any test in this section according to the subscribed
services.
1. Unicast Connectivity Test Verification
Continuously Ping to HKEX hosts as below, whenever applicable to the
subscribed services.
HKEX Service Network Commissioning Test
Classification: Confidential Page 18 of 31
2. Subscriber disables/disconnects the HSN SECONDARY uplink port in the
secondary switch
3. Routing Table Verification
Verify the routing tables in the secondary switch to show that the Subscriber
switch can still receive routes via the primary switch
4. Multicast Connectivity Test Verification
For OMD-C, OMD-CC & OMD-D, as similar as 6.3, perform multicast testing
by using the
> perl chk_pmc7-1.pl hsn_result_link_lo.txt hsn_check_link_lo.txt
xx+xx+xx+lo”
where xx is the product type in Appendix C:
“lo” must be entered since it is used to verify the primary multicast
Source Destination
HKATS Genium
INT NG / CG
Testing client in
HKATS VLAN
10.151.5.241 (primary)
10.152.5.241 (secondary)
HKATS PTRM Testing client in
HKATS VLAN
10.151.14.254 (primary)
10.152.14.254 (secondary)
OCG Testing client in
OCG VLAN
10.1.93.231 (primary)
10.2.93.231 (secondary)
CCCG Testing client in
CCCG VLAN
10.1.145.231 (primary)
10.2.145.231 (secondary)
OMD-C & OMD-CC Testing client in
OMD-C VLAN
10.1.90.32 (primary)
10.2.90.32 (secondary)
OMD-D Testing client in
OMD-D VLAN
10.170.3.241 (primary)
10.170.13.241 (secondary)
IIS Testing client in IIS
VLAN
192.168.228.11 (primary)
192.168.229.11 (primary)
192.168.233.11 (secondary)
HKEX Service Network Commissioning Test
Classification: Confidential Page 19 of 31
streams.
For example:
a subscriber booked “OMD-C Product: Securities FullTick(sf),
Conflated Broker Queue(cbq), Odd Lot Order(olo)” & “OMD-D Product:
Derivatives FullTick – Non-SOM(dfn), Derivatives FullTick –
SOM(dfs)”.
The command is as below:
perl chk_pmc7-1.pl hsn_result_link_lo.txt hsn_check_link_lo.txt
sf+cbq+olo+dfn+dfs+lo
This script will verify all the multicast channels according to the
inputted subscription.
Subscriber must select all the subscribed OMD-C, OMD-CC & OMD-D
services. Test will be failed if anyone is missing.
Capture multicast logs “hsn_result_link_lo.txt” & results
“hsn_check_link_lo.txt” from the folder.
HKEX Service Network Commissioning Test
Classification: Confidential Page 20 of 31
Subscriber enables/reconnects the switch HSN uplink port and wait for the BGP peers
to become established status.
c. Expect Result
- There should be no Ping lost
- For OMD-C, OMD-CC & OMD-D subscriber, a “==== OK ====” message
should be prompted on the screen after verification script in above section ii.
d. Actual Result
Subscriber should fill in the test result in the “HSN Connectivity Test Result
Confirmation Form”
HKEX Service Network Commissioning Test
Classification: Confidential Page 21 of 31
7 Appendix A-1 Multicast group and port number for OMD-C &
OMD-CC Network Commissioning Test
The multicast groups and port numbers used for OMD-C & OMD-CC Network Commissioning Test
is shown in the following table. Hosting Subscriber should aware that the port numbers used for
Network Commissioning test are different from the one use in Production Environment and the HKEX
OMD-C & OMD-CC multicast client for Network Commissioning Test is configured with ports number
shown in the table.
There is no difference to the multicast group IP address. The HKEX OMD-C & OMD-CC multicast
client is already configured with such ports which is transparent to the subscribers.
source multicast group port SS SP SF IDX CBQ OLO SCM SSE SZSE
10.1.8.32 239.1.1.1 3001 Y Y Y
10.1.9.32 239.1.127.1 3001 Y Y Y
10.1.8.32 239.1.1.11 3011 Y Y Y
10.1.9.32 239.1.127.11 3011 Y Y Y
10.1.8.32 239.1.1.2 3002 Y
10.1.9.32 239.1.127.2 3002 Y
10.1.8.32 239.1.1.12 3012 Y
10.1.9.32 239.1.127.12 3012 Y
10.1.8.32 239.1.1.3 3003 Y
10.1.9.32 239.1.127.3 3003 Y
10.1.8.32 239.1.1.13 3013 Y
10.1.9.32 239.1.127.13 3013 Y
10.1.8.32 239.1.1.4 3004 Y
10.1.9.32 239.1.127.4 3004 Y
10.1.8.32 239.1.1.14 3014 Y
10.1.9.32 239.1.127.14 3014 Y
10.1.8.32 239.1.1.5 3005 Y
10.1.9.32 239.1.127.5 3005 Y
10.1.8.32 239.1.1.15 3015 Y
10.1.9.32 239.1.127.15 3015 Y
10.1.8.32 239.1.1.6 3006 Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 22 of 31
10.1.9.32 239.1.127.6 3006 Y
10.1.8.32 239.1.1.16 3016 Y
10.1.9.32 239.1.127.16 3016 Y
10.1.8.32 239.1.1.7 3007 Y
10.1.9.32 239.1.127.7 3007 Y
10.1.8.32 239.1.1.17 3017 Y
10.1.9.32 239.1.127.17 3017 Y
10.1.8.32 239.1.1.8 3008 Y
10.1.9.32 239.1.127.8 3008 Y
10.1.8.32 239.1.1.18 3018 Y
10.1.9.32 239.1.127.18 3018 Y
10.1.8.32 239.1.1.9 3009 Y
10.1.9.32 239.1.127.9 3009 Y
10.1.8.32 239.1.1.19 3019 Y
10.1.9.32 239.1.127.19 3019 Y
10.2.8.32 239.1.1.1 6001 Y Y Y
10.2.9.32 239.1.127.1 6001 Y Y Y
10.2.8.32 239.1.1.11 6011 Y Y Y
10.2.9.32 239.1.127.11 6011 Y Y Y
10.2.8.32 239.1.1.2 6002 Y
10.2.9.32 239.1.127.2 6002 Y
10.2.8.32 239.1.1.12 6012 Y
10.2.9.32 239.1.127.12 6012 Y
10.2.8.32 239.1.1.3 6003 Y
10.2.9.32 239.1.127.3 6003 Y
10.2.8.32 239.1.1.13 6013 Y
10.2.9.32 239.1.127.13 6013 Y
10.2.8.32 239.1.1.4 6004
Y
10.2.9.32 239.1.127.4 6004 Y
10.2.8.32 239.1.1.14 6014 Y
10.2.9.32 239.1.127.14 6014 Y
10.2.8.32 239.1.1.5 6005 Y
10.2.9.32 239.1.127.5 6005 Y
10.2.8.32 239.1.1.15 6015 Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 23 of 31
10.2.9.32 239.1.127.15 6015 Y
10.2.8.32 239.1.1.6 6006 Y
10.2.9.32 239.1.127.6 6006 Y
10.2.8.32 239.1.1.16 6016 Y
10.2.9.32 239.1.127.16 6016 Y
10.2.8.32 239.1.1.7 6007 Y
10.2.9.32 239.1.127.7 6007 Y
10.2.8.32 239.1.1.17 6017 Y
10.2.9.32 239.1.127.17 6017 Y
10.2.8.32 239.1.1.8 6008 Y
10.2.9.32 239.1.127.8 6008 Y
10.2.8.32 239.1.1.18 6018 Y
10.2.9.32 239.1.127.18 6018 Y
10.2.8.32 239.1.1.9 6009 Y
10.2.9.32 239.1.127.9 6009 Y
10.2.8.32 239.1.1.19 6019 Y
10.2.9.32 239.1.127.19 6019 Y
10.1.8.32 239.1.1.101 3101 Y
10.1.9.32 239.1.127.101 3101 Y
10.1.8.32 239.1.1.105 3105 Y Y
10.1.9.32 239.1.127.105 3105 Y Y
10.1.8.32 239.1.1.111 3111 Y
10.1.9.32 239.1.127.111 3111 Y
10.1.8.32 239.1.1.121 3121 Y
10.1.9.32 239.1.127.121 3121 Y
10.2.8.32 239.1.1.101 6101 Y
10.2.9.32 239.1.127.101 6101 Y
10.2.8.32 239.1.1.105 6105 Y Y
10.2.9.32 239.1.127.105 6105 Y Y
10.2.8.32 239.1.1.111 6111 Y
10.2.9.32 239.1.127.111 6111 Y
10.2.8.32 239.1.1.121 6121 Y
10.2.9.32 239.1.127.121 6121 Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 24 of 31
8 Appendix A-2 Multicast group and port number for OMD-D
Network Commissioning Test
The multicast groups and port numbers used for OMD-D Network Commissioning Test is shown in
the following table. Hosting Subscriber should aware that the port numbers used for Network
Commissioning test are different from the one use in Production Environment and the HKEX OMD-
D multicast client for Network Commissioning Test is configured with ports number shown in the table.
There is no difference to the multicast group IP address. The HKEX OMD-D multicast client is
already configured with such ports which is transparent to the subscribers.
source multicast group port
DS-
Non-
SOM
DS-
SOM
DP-
Non-
SOM
DP-
SOM
DF-
Non-
SOM
DF-
SOM
DT-
Non-
SOM
DT-
SOM
DL-
Non-
SOM
DL-
SOM
DO-
Non-
SOM
10.1.8.32 239.1.1.128 3001 Y Y Y Y
10.1.9.32 239.1.127.128 3001 Y Y Y Y
10.1.8.32 239.1.1.129 3001 Y
10.1.9.32 239.1.127.129 3001 Y
10.1.8.32 239.1.1.130 3001 Y
10.1.9.32 239.1.127.130 3001 Y
10.1.8.32 239.1.1.131 3001 Y
10.1.9.32 239.1.127.131 3001 Y
10.1.8.32 239.1.1.132 3001 Y
10.1.9.32 239.1.127.132 3001 Y
10.1.8.32 239.1.1.133 3001 Y Y Y Y
10.1.9.32 239.1.127.133 3001 Y Y Y Y
10.1.8.32 239.1.1.134 3001 Y
10.1.9.32 239.1.127.134 3001 Y
10.1.8.32 239.1.1.135 3001 Y
10.1.9.32 239.1.127.135 3001 Y
10.1.8.32 239.1.1.136 3001 Y
10.1.9.32 239.1.127.136 3001 Y
10.1.8.32 239.1.1.137 3001 Y
10.1.9.32 239.1.127.137 3001 Y
10.1.8.32 239.1.1.139 3001 Y Y Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 25 of 31
10.1.9.32 239.1.127.139 3001 Y Y Y
10.1.8.32 239.1.1.140 3001 Y Y Y
10.1.9.32 239.1.127.140 3001 Y Y Y
10.1.8.32 239.1.1.141 3001 Y
10.1.9.32 239.1.127.141 3001 Y
10.1.8.32 239.1.1.142 3001 Y
10.1.9.32 239.1.127.142 3001 Y
10.1.8.32 239.1.1.143 3001 Y Y Y Y Y Y
10.1.9.32 239.1.127.143 3001 Y Y Y Y Y Y
10.1.8.32 239.1.1.144 3001 Y Y Y Y Y Y Y Y
10.1.9.32 239.1.127.144 3001 Y Y Y Y Y Y Y Y
10.1.8.32 239.1.1.149 3001 Y Y Y
10.1.9.32 239.1.127.149 3001 Y Y Y
10.1.8.32 239.1.1.150 3001 Y Y Y
10.1.9.32 239.1.127.150 3001 Y Y Y
10.1.8.32 239.1.1.151 3001 Y
10.1.9.32 239.1.127.151 3001 Y
10.1.8.32 239.1.1.152 3001 Y
10.1.9.32 239.1.127.152 3001 Y
10.2.8.32 239.1.1.153 3001 Y Y Y
10.2.9.32 239.1.127.153 3001 Y Y Y
10.2.8.32 239.1.1.154 3001 Y
10.2.9.32 239.1.127.154 3001 Y
10.2.8.32 239.1.1.155 3001 Y
10.2.9.32 239.1.127.155 3001 Y
10.2.8.32 239.1.1.156 3001 Y
10.2.9.32 239.1.127.156 3001 Y
10.2.8.32 239.1.1.157 3001 Y
10.2.9.32 239.1.127.157 3001 Y
10.2.8.32 239.1.1.158 3001 Y Y Y
10.2.9.32 239.1.127.158 3001 Y Y Y
10.2.8.32 239.1.1.159 3001 Y
10.2.9.32 239.1.127.159 3001 Y
10.2.8.32 239.1.1.160 3001 Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 26 of 31
10.2.9.32 239.1.127.160 3001 Y
10.2.8.32 239.1.1.161 3001 Y
10.2.9.32 239.1.127.161 3001 Y
10.2.8.32 239.1.1.162 3001 Y
10.2.9.32 239.1.127.162 3001 Y
10.2.8.32 239.1.1.166 3001 Y
10.2.9.32 239.1.127.166 3001 Y
10.2.8.32 239.1.1.167 3001 Y
10.2.9.32 239.1.127.167 3001 Y
10.2.8.32 239.1.1.168 3001 Y Y Y Y Y Y
10.2.9.32 239.1.127.168 3001 Y Y Y Y Y Y
10.2.8.32 239.1.1.169 3001 Y Y Y Y Y Y Y Y
10.2.9.32 239.1.127.169 3001 Y Y Y Y Y Y Y Y
10.2.8.32 239.1.1.174 3001 Y Y
10.2.9.32 239.1.127.174 3001 Y Y
10.2.8.32 239.1.1.175 3001 Y Y
10.2.9.32 239.1.127.175 3001 Y Y
10.2.8.32 239.1.1.176 3001 Y
10.2.9.32 239.1.127.176 3001 Y
10.2.8.32 239.1.1.177 3001 Y
10.2.9.32 239.1.127.177 3001 Y
10.2.8.32 239.1.1.178 3001 Y
10.2.9.32 239.1.127.178 3001 Y
10.2.8.32 239.1.1.179 3001 Y
10.2.9.32 239.1.127.179 3001 Y
10.2.8.32 239.1.1.180 3001 Y
10.2.9.32 239.1.127.180 3001 Y
10.2.8.32 239.1.1.181 3001 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
10.2.9.32 239.1.127.181 3001 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
10.1.8.32 239.1.1.128 6001 Y Y Y Y
10.1.9.32 239.1.127.128 6001 Y Y Y Y
10.1.8.32 239.1.1.129 6001 Y
10.1.9.32 239.1.127.129 6001 Y
10.1.8.32 239.1.1.130 6001 Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 27 of 31
10.1.9.32 239.1.127.130 6001 Y
10.1.8.32 239.1.1.131 6001 Y
10.1.9.32 239.1.127.131 6001 Y
10.1.8.32 239.1.1.132 6001 Y
10.1.9.32 239.1.127.132 6001 Y
10.1.8.32 239.1.1.133 6001 Y Y Y Y
10.1.9.32 239.1.127.133 6001 Y Y Y Y
10.1.8.32 239.1.1.134 6001 Y
10.1.9.32 239.1.127.134 6001 Y
10.1.8.32 239.1.1.135 6001 Y
10.1.9.32 239.1.127.135 6001 Y
10.1.8.32 239.1.1.136 6001 Y
10.1.9.32 239.1.127.136 6001 Y
10.1.8.32 239.1.1.137 6001 Y
10.1.9.32 239.1.127.137 6001 Y
10.1.8.32 239.1.1.139 6001 Y Y Y
10.1.9.32 239.1.127.139 6001 Y Y Y
10.1.8.32 239.1.1.140 6001 Y Y Y
10.1.9.32 239.1.127.140 6001 Y Y Y
10.1.8.32 239.1.1.141 6001 Y
10.1.9.32 239.1.127.141 6001 Y
10.1.8.32 239.1.1.142 6001 Y
10.1.9.32 239.1.127.142 6001 Y
10.1.8.32 239.1.1.143 6001 Y Y Y Y Y Y
10.1.9.32 239.1.127.143 6001 Y Y Y Y Y Y
10.1.8.32 239.1.1.144 6001 Y Y Y Y Y Y Y Y
10.1.9.32 239.1.127.144 6001 Y Y Y Y Y Y Y Y
10.1.8.32 239.1.1.149 6001 Y Y Y
10.1.9.32 239.1.127.149 6001 Y Y Y
10.1.8.32 239.1.1.150 6001 Y Y Y
10.1.9.32 239.1.127.150 6001 Y Y Y
10.1.8.32 239.1.1.151 6001 Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 28 of 31
10.1.9.32 239.1.127.151 6001 Y
10.1.8.32 239.1.1.152 6001 Y
10.1.9.32 239.1.127.152 6001 Y
10.2.8.32 239.1.1.153 6001 Y Y Y
10.2.9.32 239.1.127.153 6001 Y Y Y
10.2.8.32 239.1.1.154 6001 Y
10.2.9.32 239.1.127.154 6001 Y
10.2.8.32 239.1.1.155 6001 Y
10.2.9.32 239.1.127.155 6001 Y
10.2.8.32 239.1.1.156 6001 Y
10.2.9.32 239.1.127.156 6001 Y
10.2.8.32 239.1.1.157 6001 Y
10.2.9.32 239.1.127.157 6001 Y
10.2.8.32 239.1.1.158 6001 Y Y Y
10.2.9.32 239.1.127.158 6001 Y Y Y
10.2.8.32 239.1.1.159 6001 Y
10.2.9.32 239.1.127.159 6001 Y
10.2.8.32 239.1.1.160 6001 Y
10.2.9.32 239.1.127.160 6001 Y
10.2.8.32 239.1.1.161 6001 Y
10.2.9.32 239.1.127.161 6001 Y
10.2.8.32 239.1.1.162 6001 Y
10.2.9.32 239.1.127.162 6001 Y
10.2.8.32 239.1.1.166 6001 Y
10.2.9.32 239.1.127.166 6001 Y
10.2.8.32 239.1.1.167 6001 Y
10.2.9.32 239.1.127.167 6001 Y
10.2.8.32 239.1.1.168 6001 Y Y Y Y Y Y
10.2.9.32 239.1.127.168 6001 Y Y Y Y Y Y
10.2.8.32 239.1.1.169 6001 Y Y Y Y Y Y Y Y
10.2.9.32 239.1.127.169 6001 Y Y Y Y Y Y Y Y
10.2.8.32 239.1.1.174 6001 Y Y
HKEX Service Network Commissioning Test
Classification: Confidential Page 29 of 31
10.2.9.32 239.1.127.174 6001 Y Y
10.2.8.32 239.1.1.175 6001 Y Y
10.2.9.32 239.1.127.175 6001 Y Y
10.2.8.32 239.1.1.176 6001 Y
10.2.9.32 239.1.127.176 6001 Y
10.2.8.32 239.1.1.177 6001 Y
10.2.9.32 239.1.127.177 6001 Y
10.2.8.32 239.1.1.178 6001 Y
10.2.9.32 239.1.127.178 6001 Y
10.2.8.32 239.1.1.179 6001 Y
10.2.9.32 239.1.127.179 6001 Y
10.2.8.32 239.1.1.180 6001 Y
10.2.9.32 239.1.127.180 6001 Y
10.2.8.32 239.1.1.181 6001 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
10.2.9.32 239.1.127.181 6001 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
HKEX Service Network Commissioning Test
Classification: Confidential Page 30 of 31
9 Appendix B Multicast Testing Index
OMD-C Product
ss = Securities Standard
sp = Securities Premium
sf = Securities FullTick
idx = Index Feed
cbq = Conflated Broker Queue
olo = Odd Lot Order
scm = Stock Connection Market Data Feed
OMD-CC Product
sse = Shanghai Stock Exchange
szse = Shenzhen Stock Exchange
OMD-D Product
dsn = Derivatives Standard – Non-SOM
dss = Derivatives Standard – SOM
dpn = Derivatives Premium – Non-SOM
dps = Derivatives Premium – SOM
dfn = Derivatives FullTick – Non-SOM
dfs = Derivatives FullTick – SOM
dtn = Derivatives TradeTick – Non-SOM
dts = Derivatives TradeTick – SOM
dln = Derivatives Lite Price Depth Feed – Non-SOM
dls = Derivatives Lite Price Depth Feed -- SOM
don = Derivatives Lite Order Feed
HKEX Service Network Commissioning Test
Classification: Confidential Page 31 of 31
Script result meaning
Output Meaning
Got_Packet There is packet received from the specific multicast group.
No_Packet There is no packet received from the specific multicast group
OK - Got_Packet” is normal since the subscribed multicast group can
receive data.
- “No_Packet” is normal since the specific multicast group is not
subscribed.
Fail: Should receive
packets
There is no data received from the specific multicast group which is
subscribed.
Fail: Should be no
packets
There should be no data received from the specific multicast group
but got data during the testing.
==== OK ==== If test is passed, a result message” ==== OK ==== “should be
displayed in the last row
==== Fail ==== If the test is failed, “==== Fail ====” will be displayed in the last
row.