Once the 'Initial set up' has been completed the following tests will validate that the new connection to HSCN is successful.
Note - the results of the following tests should be recorded in the test report spreadsheet, which you should have received from your CNSP with their section completed.
HSCN connectivity tests
1. From a command prompt ping the HSCN DNS servers. For example:

Figure 2 – Command Prompt: ping DNS IP example
2. From a command prompt conduct a trace route to the HSCN DNS servers. For example:

Figure 3 – Command Prompt: tracert DNS IP example
Trace will show the hops from the test connection, across the CNSP network, transverse the peering exchange into the TN and navigation to the end DNS servers on the TN.
3. Open a browser and connect to a site on TN that is available to all users on HSCN/TN. The following sites are three such examples.
https://nww.sft.nhs.uk

https://nww.openexeter.nhs.uk/nhsia/index.jsp

https://login.cqrs.nhs.uk/cas/login

HSCN internet connectivity tests (where applicable)
This section only applies to consumers who intend to connect to the internet over HSCN.
1. From a command prompt ping www.bbc.co.uk. For example:

Figure 4 – Command Prompt: ping BBC URL example
2. Conduct a trace route to www.bbc.co.uk

Figure 5 – Command Prompt: trace to the BBC URL example
The trace will show a connection route from the test connection, across the CNSP network to the Advanced Network Monitoring (ANM) service and out to the internet.
ANM is a central service which provides internet filtering, firewall controls, a reporting capability and associated monitoring services.
Note: ANM does not provide an echo response to a User Datagram Protocol (UDP) traceroute.
The trace will still reach the destination however and confirm connectivity. For a full end-to-end trace response Transmission Control Protocol (TCP) traceroute must be used.
3. Open a browser and browse to a common site on the internet, such as www.bbc.co.uk. The BBC website should load in the browser.