2.5.7 SSH connection settings

■ Software required on the PFM - RM host

The table below lists the software that is required for PFM - RM for Virtual Machine to acquire monitoring-target information. For details, see the Release Notes.

Legend:

Y: Installed by default.

N: Not installed by default.

■ RPM packages required on the monitoring-target host

In order for PFM - RM for Virtual Machine to acquire monitoring-target information, the RPM packages listed below are required.

Legend:

Y: Installed by default.

■ Packages and commands required on the monitoring-target host

The command required for record collection differs depending on the record to be collected, and the required RPM package also differs depending on the command. To check the required package for a command, execute the following:

/bin/rpm -qf full-path-name-of-the-prerequisite-command

■ Records and the commands required for collecting the records

The following table lists records and the commands that are required for collecting the records.

The following lists the RPM packages required by the commands that are required for record collection.

Legend:

Y: Installed by default.

N: Not installed by default.

Table 2‒18: RPM packages required by the commands that are required for record collection (For Red Hat Enterprise Linux(R) Server 7)

No.	Command name	Package name	Default
1	/bin/cat	coreutils-8.22-11.el7 or later	Y
2	/bin/date	coreutils-8.22-11.el7 or later	Y
3	/bin/df	coreutils-8.22-11.el7 or later	Y
4	/bin/ps	procps-ng-3.3.10-3.el7 or later	Y
5	/usr/bin/free	procps-ng-3.3.10-3.el7 or later	Y
6	/usr/bin/getconf	glibc-common-2.17-78.el7 or later	Y
7	/usr/bin/iostat	sysstat-10.1.5-7.el7 or later	N
8	/usr/bin/pmap	procps-ng-3.3.10-3.el7 or later	Y
9	/usr/bin/top	procps-ng-3.3.10-3.el7 or later	Y
10	/usr/bin/virsh	libvirt-client-1.2.8-16.el7 or later	N
11	/usr/bin/vmstat	procps-ng-3.3.10-3.el7 or later	Y
12	/bin/hostname	hostname-3.13-3.el7 or later	Y

Legend:

Y: Installed by default.

N: Not installed by default.

Table 2‒19: RPM packages required by the commands that are required for record collection (For Red Hat Enterprise Linux(R) Server 8)

No.	Command name	Package name	Default
1	/bin/cat	coreutils-8.30-6.el8 or later	Y
2	/bin/date	coreutils-8.30-6.el8 or later	Y
3	/bin/df	coreutils-8.30-6.el8 or later	Y
4	/bin/ps	procps-ng-3.3.15-1.el8 or later	Y
5	/usr/bin/free	procps-ng-3.3.15-1.el8 or later	Y
6	/usr/bin/getconf	glibc-common-2.28-42.el8 or later	Y
7	/usr/bin/iostat	sysstat-11.7.3-2.el8 or later	Y
8	/usr/bin/pmap	sysstat-11.7.3-2.el8 or later	Y
9	/usr/bin/top	procps-ng-3.3.15-1.el8 or later	Y
10	/usr/bin/virsh	libvirt-client-4.5.0-23.module+el8+2800+2d311f65 or later	N
11	/usr/bin/vmstat	procps-ng-3.3.15-1.el8 or later	N
12	/bin/hostname	hostname-3.20-6.el8 or later	Y

Legend:

Y: Installed by default.

N: Not installed by default.

■ Software required on the PFM - RM host

Software required by PFM - RM for Virtual Machine to acquire monitoring-target information is the same as that for KVM. See Table 2-15 Software required to acquire monitoring-target information.

■ RPM packages required on the monitoring-target host

In order for PFM - RM for Virtual Machine to acquire monitoring-target information, the RPM packages listed below are required.

Legend:

Y: Installed by default.

■ Packages and commands required on the monitoring-target host

The command required for record collection differs depending on the record to be collected, and the required RPM package also differs depending on the command. To check the required package for a command, execute the following:

/bin/rpm -qf full-path-name-of-the-prerequisite-command

■ Records and the commands required for collecting the records

The following table lists records and the commands that are required for collecting the records.

The following lists the RPM packages required by the commands that are required for record collection.

Legend:

Y: Installed by default.

N: Not installed by default.

■ Transfer the public key

Transfer the public key to the .ssh directory under the home directory on a monitoring-target host. To do this:

1. Log in to the monitoring-target host as the superuser (account specified for UserID during setup of the monitoring target).

2. Use the cd command to move to the .ssh directory under the home directory.

   If the .ssh directory does not exist under the home directory, create the .ssh directory. For the access permission attribute of the .ssh directory, set 700 or 755. For the owner and group, set values that are appropriate for the user specified during setup of the monitoring-target host.

   If the home directory, .ssh directory attribute, owner, and group settings are not correct, SSH connection might fail.

   For details about how to set the directory attribute, see the OS documentation.

3. On the PFM - RM host, open the Command Prompt window, and then execute the following commands.

   If you use PuTTY as the SSH client:

   Navigate to the folder where PuTTY is installed, and then execute the pscp command, which is provided by PuTTY.

   The following shows an example of executing the command when the public key is located in the PuTTY installation directory:

   C:\Program Files\PuTTY>pscp.exe agt8.pub ClientUser@TargetHost:.ssh
   ClientUser@TargetHost's password:password (Enter the superuser's password here.)
   agt8.pub                  | 0 kB |   0.3 kB/s | ETA: 00:00:00 | 100%
   C:\Program Files\PuTTY>

   If a message asking you whether you want to register the fingerprint appears, enter n.

   If you use OpenSSH (which comes with Windows Server 2019) as the SSH client:

   The following shows an example of executing the command when the public key is located in the .ssh directory:

   C:\Users\username\.ssh\>scp.exe id_rsa.pub ClientUser@TargetHost:.ssh
   The authenticity of host 'PFM - RM hostname' can't be established.
   ECDSA key fingerprint is SHA256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.
   Are you sure you want to continue connecting (yes/no)? yes
   Warning: Permanently added xxx.xxx.xxx.xxx (ECDSA) to the list of known hosts.
    
   ClientUser@TargetHost's password:password
   agt8.pub                                     100%  404     0.4KB/s   00:00

■ Registering the public key (monitoring-target host)

Log in to the monitoring-target host as the superuser that was set during setup of the monitoring target (account specified for UserID), and then register the public key. To do this:

1. Log in to the monitoring-target host as the superuser that was set during setup of the monitoring target.

2. Use the cd command to move to the .ssh directory.

3. Execute the following command.

   If you use PuTTY as the SSH client:

   Execute the ssh-keygen command with the -i and -f options specified. When you execute the command, the public key created by PuTTY is converted into the authentication key file format available to OpenSSH.

   If you use OpenSSH (which comes with Windows Server 2019) as the SSH client:

   Execute the cat command with the public key file and the authentication key file as the redirect destination specified. When you execute the command, the contents of the public key file are redirected to the authentication key file. Furthermore, the contents of the received public key are added to the authentication key file.

4. Use the rm command to delete the public key file that was received by the procedure in Transferring the public key.

5. Execute the chmod command to change the attribute of the key authentication file to 600.

The following shows an example of executing the commands in steps 2 through 5:

If you use PuTTY as the SSH client:

[root @targethost1 ~]$ cd .ssh
[root @targethost1 .ssh]$ ssh-keygen -i -f agt8.pub >> authorized_keys
[root @targethost1 .ssh]$ rm agt8.pub
[root @targethost1 .ssh]$ chmod 600 authorized_keys

If you use OpenSSH (which comes with Windows Server 2019) as the SSH client:

[root@targethost1 ]$ cd .ssh
[root@targethost1 .ssh]$ cat id_rsa.pub >> authorized_keys
[root@targethost1 .ssh]$ rm id_rsa.pub
[root@targethost1 .ssh]$ chmod 600 authorized_keys

The name of the key authentication file is set by AuthorizedKeysFile in the /etc/ssh/sshd_config file.

By default, ~/.ssh/ authorized_keys is set.