Installing on VMware ESX

SSH 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.

SSH Tectia functionality has been tested on VMware ESX Server's Service Console as a replacement of OpenSSH.

	Note
	Keep in mind that SSH Tectia Server software may need to be re-installed after every VMware ESX upgrade.

When installing SSH Tectia Server directly on the VMware ESX Service Console, use the SSH 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 /install/linux/ directory.

Two packages are always 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 the VMware ESX Service Console, 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.
Download the installation packages:
```
ssh-tectia-common-<version>-linux-x86.rpm
ssh-tectia-server-<version>-linux-x86.rpm
```
In the commands, <version> indicates the product release version and the current build number (for example, 6.1.9.123).
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/licenses directory. (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 restart the server manually after copying the license file.

The installation should (re)start the server automatically.

Note

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