This chapter introduces you to and prepares you for SSH product installation, configuration, startup, and testing. It is for the OpenVMS system manager or technician responsible for product installation and configuration.
To get SSH up and working, you must perform the following steps:
Table 1-1 Getting SSH Up and Running
|
1 |
Load the license pack. | |
|
2 |
Install the software. |
See Chapter2, Installing SSH for OpenVMS |
|
3 |
Configure the SSH for OpenVMS environment. |
See Chapter3, Configuring SSH for OpenVMS |
|
4 |
Configure the SSH for OpenVMS SSH V1 server. |
See Chapter4 Configuring the Secure Shell (SSH) V1 Server |
|
5 |
Configure the SSH for OpenVMS SSH V2 server. |
See Chapter5, Configuring the Secure Shell (SSH) V2 Server |
|
6 |
Configure the SSH for OpenVMS client. |
See Chapter6, Accessing Remote Systems with the Secure Shell (SSH) Utilities |
SSH for OpenVMS installation involves using the VMSINSTAL procedure. Preparing for installation involves:
• Understanding the hardware and software requirements
• Determining if you have sufficient disk space and global pages for the installation
• Determining where to install the software
SSH for OpenVMS has no special hardware requirements beyond those stated in the Software Product Description for HP’s TCP/IP Services.
SSH for OpenVMS supports OpenVMS/VAX version 6.2, 7.0, 7.1, 7.2, 7.3; OpenVMS Alpha version 6.2, 7.0, 7.1, 7.2-1, 7.2-2, 7.3; UCX version 4.2 and later, and TCP/IP Services version 5.0 and later.
The destination device for your SSH for OpenVMS software must have enough disk space so that you can install and run the software. If you plan to install every SSH for OpenVMS component, your system must have approximately the following values.
|
System |
Number of Blocks Needed to Install SSH for OpenVMS |
Number of Blocks Needed After Installation |
|
VAX |
200,000 |
about 34,000 |
|
Alpha |
200,000 |
about 46,000 |
The runtime values are slightly higher once you configure and start SSH for OpenVMS.
You should also have at least 50,000 free global pages (GBLPAGES) on your system before installing SSH for OpenVMS. Use SHOW GBLPAGES in the SYSGEN utility to determine the parameter value and change it using SET GBLPAGES if necessary.
Insufficient GBLPAGES can abort the installation and leave your system command tables disconnected. The only way to recover is through a system reboot.
Check at this point that you:
• Have OPER, SYSPRV, or BYPASS privileges
• Can log in to the system manager's account
• Are the only user logged in (recommended)
• Backed up your system disk on a known, good, current, full backup (recommended)
• Need to reinstall SSH for OpenVMS after performing a major VMS upgrade
• If SSH for OpenVMS is currently running, shut it down. This is mandatory.
• Ensure TCP/IP Services (or UCX) is currently running.
Install SSH for OpenVMS in a location depending on the following:
• Generally, on your system disk, but you can install SSH for OpenVMS anywhere, just answer the question when it appears. This is also where you would keep your "common" files. Node-specific files should always be on your system disk.
• If the machine is in a single platform cluster, on a common disk.
• If the machine is in a mixed platform cluster, once on the Alpha system disk (or disks) and once on the VAX common system disk.
The SSH for OpenVMS Release Notes provide important information on the current release. If you are installing from CD-ROM, you can access the Release Notes and the full SSH for OpenVMS documentation as PDF files. They are in the [DOCUMENTATION] directory. The Release Notes for this product are in the file SSH010.RELEASE_NOTES. The other file (MULTINET044.RELEASE_NOTES) may be ignored.
• If you are installing from disk, you can read or print the Release Notes as a text file, which you can obtain in one of three ways:
– By performing a partial installation
– During the full installation
– After the installation
To perform a partial installation (see Example 1-1):
1 Invoke VMSINSTAL at the system prompt:
$ @SYS$UPDATE:VMSINSTAL MULTINET044 device OPTIONS N
The device is the mount location of the distribution volumes.
2 Press Return at the prompt
Are you satisfied with the backup of your system disk [YES]?.
3 Select the option by number as to whether you want to display or print the Release Notes, or both.
4 If you requested a printout, enter the queue name for the printer. The default is SYS$PRINT.
5 Press Return at the prompt
Do you want to continue the installation [NO]?:.
(Note that if you enter YES at the prompt, you proceed with the full installation.)
6 You see the message
Product's release notes have been moved to SYS$HELP.
7 If you want to read or print the Release Notes after you exit the installation, you can access the MULTINET044.RELEASE_NOTES and SSH010.RELEASE_NOTES files in the SYS$HELP directory, as in:
$ TYPE SYS$HELP:MULTINET044.RELEASE_NOTES
or
$ TYPE SYS$HELP:SSH010.RELEASE_NOTES
Note! For this command to work as desired, do not redefine the SYS$HELP directory logical.
Example 1-1 Performing a Partial Installation to Obtain the Release Notes
$ @SYS$UPDATE:VMSINSTAL MULTINET044 DKA300: OPTIONS N [1]
OpenVMS AXP Software Product Installation Procedure V7.1
It is 3-JUNE-2002 at 11:01.
Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]? Return [2]
The following products will be processed:
MULTINET V4.4
Beginning installation of MULTINET V4.4 at 11:01
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
Release notes included with this kit are always copied to SYS$HELP.
Additional Release Notes Options:
1. Display release notes
2. Print release notes
3. Both 1 and 2
4. None of the above
* Select option [2]: Return [3]
* Queue name [SYS$PRINT]: Return [4]
Job MULTINET044 (queue SYS$PRINT, entry 1) started on SYS$PRINT
* Do you want to continue the installation [NO]? Return [5]
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
VMSINSTAL procedure done at 11:02
.
.
.
$ TYPE SYS$HELP:MULTINET044.RELEASE_NOTES [6]
$TYPE SYS$HELP:SSH010.RELEASE_NOTES [7]