Installation Instructions
Table Of Contents
- Installation and Configuration Manual
- Tait Communications Corporate Head Office
- Contents
- Preface
- 1 Introduction
- 2 Installation
- 3 Configuration
- 4 Administrating the SCADA Gateway
- 4.1 Logging on to the SCADA Gateway
- 4.2 Logging on to the SCADA Gateway as ‘root’
- 4.3 Self-Signed SSL Certificates
- 4.4 Using the Certificate from a Certification Authority (CA)
- 4.5 Changing the ‘root’ and ‘taitnet’ Passwords
- 4.6 Stopping/Starting the SCADA Gateway Software
- 4.7 Changing to a Local Time Zone
- 4.8 SCADA Gateway Resource File
- 5 Uploading SCADA Gateway Firmware
- 6 Backing up/Restoring Configuration Files
- Appendix 1: Transferring an ISO Image to a USB Flash Drive
- Appendix 2: Adding an Alternate Interface in CentOS
SCADA Gateway Installation and Configuration Manual Installation 17
© Tait Limited May 2017
./installvm clean
This will remove the Virtual Machine, and thus the SCADA gate-
way, and should place the node in the same state it was in prior to
installation of the Communications Server
2. If Step 1 is unsuccessful, it is necessary to remove the Virtual
Machine manually: use ssh to log into the node as user taitnet,
and then:
VBoxManage controlvm Q9361VM poweroff
VBoxManage unregistervm Q9361VM –delete
Now uninstall the startup script:
rm -f /etc/rc3.d/S90vbox
Now remove the virtual box software:
VBoxManage extpack uninstall “Oracle VM VirtualBox
Extension Pack”
pkgrm -n -a /opt/VirtualBox/autoresponse SUNWvbox
3. If Step 2 is unsuccessful, in a multi node system, change a Switching
Node mode to Control Node and contact Tait Technical Support to
ascertain what steps to take.
2.5 Creating Your Custom ‘ssh’ Login Script
It is recommended that you create a login script. This is the script that is
displayed to the user when they log in from an external device (for
example, using PuTTY).
1. Locate (or write) a file with the login script required (see example
below).
2. Copy this file to the /etc directory, and name it issue:
# mv <path to login script> /etc/issue
3. Change the ownership and group of the file to root:
# chown root:root /etc/issue
4. Check the ownership and permissions:
# ls -l /etc/issue
5. If permissions are not -rw-r--r-- make them so:
# chmod 644 /etc/issue
Sample login script “WARNING! THIS SYSTEM IS RESTRICTED TO AUTHORIZED
USERS ONLY!
If you are not authorized to use this system, you must exit immediately.
Unauthorized users will be subject to criminal penalties, fines, damages
and/or disciplinary action.