Use these instructions when you are installing SSH Tectia Server on Linux versions running on the 32-bit x86 and the 64-bit x86-64 platform architecture. For instructions on installing on Linux running on IBM System z, see Installing on Linux on IBM System z.
SSH Tectia Server for Linux platforms is supplied in RPM (Red Hat Package Manager) binary packages for Red Hat Enterprise Linux and SUSE Linux. There are separate packages for Linux versions running on the 32-bit and the 64-bit architecture.
The downloaded online installation package contains the RPM installation files. On the installation CD-ROM, the installation packages for Linux are located in the
Two packages are required: one for the common components of SSH Tectia Client and Server, and one for the specific components of SSH Tectia Server.
To install SSH Tectia Server on Linux, follow the instructions below:
Make sure no other Secure Shell software is using port 22 (SSH Tectia Server default listen port). Stop any competing server software or change their listen port.
Select the installation package according to your Linux version.
When installing on SUSE or Red Hat Enterprise Linux running on the 32-bit x86 architecture, use the following packages:
When installing on SUSE or Red Hat Enterprise Linux versions running on the 64-bit x86-64 architecture, use the following packages:
In the commands,
<version>indicates the product release version and the current build number (for example,
Install the packages with root privileges. In the command examples below, we use the x86 version:
# rpm -Uvh ssh-tectia-common-<version>-linux-x86.rpm # rpm -Uvh ssh-tectia-server-<version>-linux-x86.rpm
The server host key is generated during the installation. The key generation may take several minutes on slow machines.
Copy the license file to the
/etc/ssh2/licensesdirectory. (This is not necessary in "third-digit" maintenance updates.) See Licensing.
If this is the initial installation of SSH Tectia Server, the directory does not yet exist. You can either create it manually or copy the license after the installation. In the latter case, you have to start the server manually after copying the license file.
The installation should (re)start the server automatically.
If the server does not start (for example because of a missing license or because some other secure shell software is running on port 22), you can start it after correcting the problem by issuing the command:
# /etc/init.d/ssh-server-g3 start