You can reset the SSH fingerprint for a cluster that is managed by the SAN Volume Controller Console for your configuration by using the Resetting the SSH Fingerprint panel.
You must have superuser administrator authority to perform the following procedure.
If you have changed the name of the master console, you must also change the master console host name in the IBM WebSphere Application Server files.
The communication between the SAN Volume Controller Console and the cluster is through the Secure Shell (SSH) protocol. In this protocol, the SAN Volume Controller Console acts as the SSH client and the cluster acts as the SSH host server. The SSH protocol requires that credentials are exchanged when communication between the SSH client and server begins. The SSH client places the accepted SSH host server fingerprint in cache. Any change to the SSH server fingerprint in future exchanges results in a challenge to the end user to accept the new fingerprint. When a new code load is performed on the cluster, new SSH server keys can be produced which result in the SSH client flagging the SSH host fingerprint as changed and, therefore, no longer valid.
The SAN Volume Controller Console displays the status of the cluster SSH server key in the Availability Status column of the Viewing Clusters panel.
Perform the following steps to reset the SSH fingerprint:
| Attention: Select a cluster that has an availability status of Invalid SSH Fingerprint. In some cases this availability status results from a software upgrade that disrupts normal user operations. In the case of a disruptive software upgrade, follow the procedure for Recovering from a Disruptive Software Upgrade. |
Availability status is changed to OK