Resetting a refused SSH key Clusters Starting statistics collections

This topic provides an overview about resetting a refused SSH key relationship between the SAN Volume Controller Console and the SAN Volume Controller cluster.

Overview

The communication between the SAN Volume Controller Console software and the SAN Volume Controller cluster is through the Secure Shell (SSH) protocol. In this protocol, the SAN Volume Controller Console software acts as the SSH client and the SAN Volume Controller cluster acts as the SSH host server.

As an SSH client, the SAN Volume Controller Console must use an SSH2 RSA key pair composed of a public key and a private key which are coordinated at key generation time. The SSH client public key is stored on each SAN Volume Controller cluster with which the SAN Volume Controller Console communicates. The SSH client private key is known to the SAN Volume Controller Console software by being stored in a specific directory with a specific name. If the SSH protocol detects the key pair is mismatched, the SSH communication fail.

The SAN Volume Controller Console externalizes the status of a mismatched or invalid SAN Volume Controller Console client key pair in the Availability Status column of the Cluster panel.

Because the client SSH key pair must be coordinated across two systems, you might have to take one or more actions to reset the pair of keys. Perform one or more of the following steps to reset the refused client SSH key pair:

(C) Copyright International Business Machines Corporation 2003, 2004