Ultra electronics HYPERSPIKE HS-18 RAHD, Operation And Maintenance Manual, Page: 16 / 60

HyperSpike ® HS-18 RAHD Operation and Maintenance Manual
Copyright © Ultra Electronics USSI Columbia City, IN 46725 USA
90207A-MAN-HS18RAHD
REV C
11
4. Networking and Device Setup
The HS-18 RAHD is designed to be controlled over a TCP/IP based network equipped with
either a static IP address or a DHCP server. By default, the HS-18 RAHD has a static IP
address of 192.168.123.10/24. If configured as a DHCP client (see Section 5.17.1) the HS-18
RAHD will receive a dynamic IP address when powered on. Take note of the IP address
assigned to your HS-18 RAHD (if your DHCP server also serves DNS, you should be able to
access the RAHD by hostname as well, which is the serial number of the unit). You will need
this information to set up the device. If you do not know how to identify the IP address of your
HS-18 RAHD, consult your network manager.
4.1. Installing the CA Certificate
The HS-18 RAHD signs its encrypted digital communications as its own certificate authority (this
is not the same as a self-signed certificate). This means that a client machine that is accessing
the Command and Control Interface (CCI) can be configured to trust that signature. Without
installing the certificate for the certificate authority, which includes the signature to be trusted,
modern browsers will display a warning and prompt users for whether the webpage should be
trusted. However, once the certificate for the RAHD’s certificate authority is installed in the trust
store of a client machine, the Command and Control Interface (CCI) webpage will register as
having come from a trusted source and will no longer prompt with a warning. In addition, cross-
domain calls from browser environments to the REST API become possible. To install the
certificate in the Windows trust store, follow the steps below:
1.
Request a copy of the certificate from Hyperspike Customer Support
2. Save the received file
– “rahdStaticIpCA.pem” to the client machine
3. On the client machine, open the Microsoft Management Console
– type mmc in the program
search or run box
4. File->Add/Remove Snap-
in…
5. Select
“Certificates” from the “Available snap-ins” menu and use the Add > button to move it to the
“Selected snap-ins” box. Select the OK button
6. Expand the Certificates menu item on the left part of the screen and right-
click “Trusted Root
Certification Authori
ties”. Choose “All Tasks -> Import…”
7.
Use the wizard to navigate to the “rahdStaticIpCA.pem” file.
8.
Select “Finish”
9. There should be a popup indicating the import was successful
10.
The Hyperspike Certificate Authority should now be listed in the “Trusted Root Certification
Authorities” folder.
All RAHDs use the same certificate authority, so importing the certificate to a client machine’s trust
store will cause that machine to trust the CCI of any RAHD that is accessed. Also, the same
“rahdStaticIpCA.pem” file can be used on multiple client machines.