2.5.3 For KVM

(a) Software required on the PFM - RM host

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

Legend:

N: Not installed by default.

(b) RPM packages required on the monitoring-target host

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

Legend:

Y: Installed by default.

(c) 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

(d) 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.

(a) Enabling public key authentication of the SSH server

To enable public key authentication:

1. Log in to the monitoring-target host as the superuser.

2. Open the /etc/ssh/sshd_config file.

3. Change the value of PubkeyAuthentication to yes.

4. Change the value of PermitRootLogin to yes.

5. Save and close the /etc/ssh/sshd_config file.

6. Restart the sshd service by executing the command shown below.

   Note that the command below assumes that the host named targethost1 is set as a monitoring target.

   [root@targethost1.ssh]$ /etc/rc.d/init.d/sshd restart

   Important note

   To allow the superuser to collect information, open the /etc/ssh/sshd_config file, and change the value of PermitRootLogin to yes. Then, restart the sshd service.

(b) Creating keys

The procedure for creating keys is described below.

Keys can be created by logging on to the PFM - RM host, and then by executing PuTTY. Either of two types of keys (for RSA encryption and DSA encryption) can be selected. Because the only difference between two key types is the encryption algorithm, key usage is the same, whichever type is selected. In this subsection, the procedure for creating RSA keys is described. To create RSA keys:

1. From the Windows Start menu, select Programs, PuTTY, and then PuTTYgen.

   PuTTYgen starts, and the PuTTY Key Generator window appears.

2. Under Parameters, confirm that Type of key to generate is SSH-2 RSA, and then click the Generate button.

   The key generation progress bar appears in Key.

   Because PuTTY uses the version 2 of the SSH protocol by default, SSH-2 RSA is selected. However, you might want to change the protocol version to 1. For details about how to change the protocol version to 1, see the PuTTY documentation.

3. Irregularly move the mouse pointer in the dialog box until the progress reaches 100%.

   When the progress reaches 100%, the created random number is displayed in Key, and keys are created.

4. Click the Save private key button to save a private key.

   If no values are entered in Key passphrase and Confirm passphrase, a dialog box appears. In this dialog box, click the Yes button without entering anything in Key passphrase and Confirm passphrase.

5. Click the Save public key button to save a public key.

(c) Deploying the public key (PFM - RM host)

If there are multiple monitoring-target hosts, perform the following procedure on all of the hosts.

[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

(d) Confirming connectivity and registering the fingerprint (PFM - RM host)

To confirm connectivity and register the fingerprint:

1. Log in to the PFM - RM host.

   Make sure that you use the account that was set for HostUserID during setup of the instance environment.

2. Open the Command Prompt window.

3. Execute the PuTTY plink command using the private key that has been created.

   Connection is attempted.

4. Upon achieving the initial connection, register the fingerprint.

   Enter y to register the fingerprint of the public key on the monitoring-target host.

   When y is entered, the prompt of the monitoring-target host is displayed.

5. Log out.

   When the prompt of the monitoring-target host is displayed, enter exit to log out from the host.

6. Execute the PuTTY plink command to reconnect to the monitoring-target host.

   If you are not prompted to enter anything and reconnection succeeds, the connection settings are completed. Enter exit to log out from the monitoring-target host.

   If an error occurs or you are prompted to enter something, check for problems with operations performed by the procedure.

The following shows an example of performing the procedure for checking connectivity:

C:\WINDOWS\system32>"C:\Program Files\PuTTY\plink.exe" -ssh -noagent -i "C:\Program Files\PuTTY\agt8.ppk" -l root -P 22 targethost1
The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
If you trust this host, enter "y" to add the key to PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the connection.
Store key in cache? (y/n) y
Using username "root".
Last login: Wed Aug  4 13:29:55 2010 from xxx.xxx.xxx.xxx
[root@targethost1]$ exit
logout
C:\WINDOWS\system32>"C:\Program Files\PuTTY\plink.exe" -ssh -noagent -i "C:\Program Files\PuTTY\agt8.ppk" -l root -P 22 targethost1
Using username "root".
Last login: Wed Aug  4 13:30:00 2010 from xxx.xxx.xxx.xxx
[root@targethost1]$ exit
logout
C:\WINDOWS\system32>

Important note

PFM - RM for Virtual Machine assumes that fingerprint authentication has already finished. If the fingerprint has not yet been registered before PFM - RM for Virtual Machine connects to the SSH client for the first time, always register the fingerprint at the initial connection.

In a cluster environment, make sure that you also check connectivity and register the fingerprint on the standby node.