Where Configuration Data Is Stored; Migration Considerations; Installation Of Sftpapi; Quick Start And Guided Tour - HP NonStop SSH 544701-014 Reference Manual

In case the new version of SSH2 creates unexpected problems, revert to the old object files.

Where configuration data is stored

Other than any macros you have created, there are two data files which you want to keep in order to keep your existing
database/configuration entries: HOSTKEY stores the host key SSHCTL stores all users and configuration done through
SSHCOM.

Migration Considerations

When migrating from one NSK system to another, the original configuration can be preserved by porting the SHCTL
database, the HOSTKEY file, and the SSH configuration file to the SSH subvolume $system.zssh. The migration should
only be done for SSH2 processes associated with non-maintenance LANs. Note that the configuration file SSHCFG is a
template and will be overwritten by DSM/SCM when a new SPR is installed. Therefore, the ported configuration file
should be named differently, and the startup message in the SCF input file for persistent processes (or the startup obey
file) changed to point to the correct configuration file. Also take note that if a license file existed in the original
configuration, but not required any longer in the target system (SPRs >= T0801^AAQ), the customer name from the
license file must be placed as a value for parameter CUSTOMER in the configuration file.

Installation of SFTPAPI

SFTPAPI is a separately licensed module offering a programmatic interface to SFTP similar to FTPAPI for FTP.
In June, 2011, HP started to offer the SFTPAPI product which requires a special license. It enables users to easily
convert existing FTP scripts/programs to switch over to SFTP. The minimum SPR supporting this feature is
T0801^AAQ for H/J series, and T0801^AAT for G-series. The HP NonStop SFTP API Reference Manual, part number
659755-nnn, describes the API in detail. Support for it is built into the SFTP client, which must be placed together with
the license into a dedicated subvolume.
Currently it is not possible to use the SSH home subvolume $SYSTEM.ZSSH because of conflicts in the license naming
and license checking. To simplify the installation process, starting with TCF T0801^AAY (H/J series) and T0801^AAZ
(G-series), the SFTP client will be distributed in $SYSTEM.SYSnn (as before) and in $SYSTEM.ZSFTPAPI. The user
needs to place the SFTPAPI license (named "LICENSE") into the $SYSTEM.ZSFTPAPI subvolume where the
additional copy of the SFTP object is located. In the program that makes the FTP API calls, the variable FTPPGM
pointing to the FTP client must be modified to point to the SFTP client $SYSTEM.ZSFTPAPI.SFTP.

Quick Start and Guided Tour

This section offers a brief example illustrating how to start SSH2. In addition, we will provide a guided tour that
illustrates how to perform various SSH related tasks with a remote SSH system.
We will base this section on some assumptions:
•
OpenSSH is installed on the remote system, with sshd listening on port 22.
•
The IP address of the NonStop system is 10.0.0.199.
•
The IP address of the remote system is 10.0.0.201.
•
The SSH2 server will listen on port 22
Some of the steps illustrated here are only covered briefly; however these steps are covered in detail in subsequent
sections of this documentation.
HP NonStop SSH Reference Manual
Installation & Quick Start • 35