This topic provides step-by-step instructions for replacing the
SSH key pair.
Context
Note: - If you change the SSH keys that will be used by the master console to
communicate with the SAN Volume Controller Console you will have to store
the client SSH private key in the SAN Volume Controller Console software as
described previously and then store the client SSH public key on the SAN Volume
Controller cluster.
- If you change the IP address of your SAN Volume Controller cluster after
you have added the cluster to SAN Volume Controller Console, the SAN Volume
Controller Console will not be aware of the existence of the cluster.
To correct this, remove the cluster from the SAN Volume Controller
Console and add it back again. Perform the following steps:
Steps
- Start the SAN Volume Controller Console by clicking on the desktop
icon or by using your Web browser to go to http://IP_address:9080/ica,
where IP_address is the IP address of the master console. The Signon
window is displayed. This might take a few moments to open.
- Enter the user ID superuser and the password passw0rd. The Welcome
window is displayed.
- Click Clusters from the portfolio.
- Check the Select box for the cluster for which you wish
to replace the key.
- Click Remove a cluster in the selection box
- Click Go.
- Click Clusters from the portfolio.
- Click Add a cluster in the selection box.
- Input the IP address of the cluster.
- Do not check the Create (Initialize Cluster) box.
- Click OK.
- Enter the user name and password. When you see the pop-up window,
enter the network password and click OK.
- Add the SSH client public key to the SAN Volume Controller cluster:
- Click Browse... for the key file to upload and locate
the public key or input the key in the Key (direct input) field
- Type an identifier in the ID field, which uniquely identifies
the key to the cluster.
- Select the Administrator radio button.
- Click Add Key.
- Click Clusters from the portfolio to check the status
of the cluster. If the cluster status remains SSH Key Refused, you
do not have a good key pair. You can reset the SAN Volume Controller Console
private SSH key. However, if you have successfully contacted other clusters,
you will break that connectivity.