Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.

SSH Tectia

Installing on VMware ESX

SSH Tectia Client 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]Note

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

When installing SSH Tectia Client 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 CD-ROM, the installation packages for Linux are located in the /install/linux/ directory.

Two packages are required: one for the common components of SSH Tectia Client and Server, and one for the specific components of SSH Tectia Client.

To install SSH Tectia Client on the VMware ESX Service Console, follow the instructions below:

  1. Download the installation packages:

    ssh-tectia-common-<version>-linux-x86.rpm
    ssh-tectia-client-<version>-linux-x86.rpm
    

    In the commands, <version> indicates the product release version and the current build number (for example, 6.0.10.123).

  2. Install the packages with root privileges:

    # rpm -Uvh ssh-tectia-common-<version>-linux-x86.rpm
    # rpm -Uvh ssh-tectia-client-<version>-linux-x86.rpm
    
  3. Copy the license file to the /etc/ssh2/licenses directory. (This is not necessary in "third-digit" maintenance updates.) See also Licensing.

===AUTO_SCHEMA_MARKUP===