Tectia Server can be installed on VMware ESX in two ways:
directly on the VMware ESX Server's Service Console; this section gives instructions for this case.
on a VMware guest host running a supported version of the operating system; see the platform-specific installation instructions above.
Tectia functionality has been tested on VMware ESX Server's Service Console as a replacement of OpenSSH.
Keep in mind that Tectia Server software may need to be re-installed after every VMware ESX upgrade.
When installing Tectia Server directly on the VMware ESX Service Console, use the Tectia Linux installation package for the x86 platform architecture. The downloaded online installation package contains the RPM installation files.
On the installation disk, the installation packages for Linux are located in the
Two packages are always required: one for the common components of Tectia Client and Server, and one for the specific components of Tectia Server.
To install Tectia Server on the VMware ESX Service Console, follow the instructions below:
Unpack the downloaded
Make sure no other software is using port 22 (Tectia Server default listen port). Stop any competing server software or change their listen port.
You have the following installation packages:
In the commands,
<version>indicates the product release version and the current build number (for example,
Install the packages with root privileges:
# 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 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 restart 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 following command:
# /etc/init.d/ssh-server-g3 start