Once a HSCN customer has received its final 'Readiness Certificate' from their CNSP they should consider carrying out the following steps (typically, under DPS as part of milestone M1.2. - regardless of the procurement mechanism there should still be confirmation of readiness):
- Each CNSP has been issued test IP addresses at their disposal. Check that the CNSP has requested some test IPs from NHS Digital Internet Protocol address management (IPAM).
- Address will typically be 10.120.x.0/24 (where x is specific to a CNSP).
- The test IP address range can be used for testing prior to migration but should not be used for production traffic.
- Request that their CNSP sets up a test port in the CPE router, configured with the IP allocated test IP range (subnet such as /30, IP for router port and IP for test laptop or /29 for a resilient link).
- Prior to migration day the CNSP is required to disable/remove the test connection from the customer CPE.
- The HSCN customer’s test laptop/device to be configured to point to the TN Domain Name System (DNS) servers
Other DNS server definitions will work, however connectivity to the HSCN DNS service is crucial for resolving connectivity to internal services available on TN/HSCN (for example, connecting to nww.xxx.nhs.uk services).
The HSCN customer’s test laptop/device network interface is configured - as per the example below:
Figure 1 - network interface configuration example
The HSCN customer can then connect their test device to the new HSCN test port on the CPE and begin their HSCN readiness confirmation tests.