This section explains how to troubleshoot cloning issues that occur after re-installing the manager.
When performing a cloning image operation (collection or deployment) on a managed server that was already registered on the manager before re-installation, the following problem may occur. The manager and agent certificates may not match, resulting in the admin server being unable to communicate with its managed server. In such a case, trying to deploy or collect an image to or from the managed server will fail. This problem occurs when the following conditions are met.
The manager was re-installed, but its certificate store was not properly backed up, as described in "11.1.2 Uninstallation [Windows Manager]" or "11.1.3 Uninstallation [Linux Manager]" in the "Setup Guide VE"
Both the manager and agent were re-installed (and their certificates renewed), but a cloning image that was collected before the re-installation has been deployed, thus restoring an outdated agent certificate on the managed server
Use the following procedure to correct the problem.
To avoid the same certificate problem, recollect the cloning images which include the cause of the problem after the problem has been corrected.
Checking the Certificates
How to check certificates
Stop the manager and then display SSL certificate data by executing the following commands on the admin server.
[Windows Manager]
>"Installation_folder\SVROR\Manager\bin\rcxadm" mgrctl stop <RETURN> |
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl stop <RETURN> |
For details on the command, refer to "5.4 rcxadm certctl" or "5.11 rcxadm mgrctl" in the "Reference Guide (Command) VE".
Example Results
Truststore: |
Stop the agent and display SSL certificate data by executing the following commands on the managed server where the error occurred.
[Windows]
>"Installation_folder\Agent\bin\rcxadm" agtctl stop <RETURN> |
[Linux]
# /opt/FJSVrcxat/bin/rcxadm agtctl stop <RETURN> |
[Solaris]
# /opt/FJSVrcvat/bin/rcxadm agtctl stop <RETURN> |
For details on the command, refer to "5.2 rcxadm agtctl" or "5.4 rcxadm certctl" in the "Reference Guide (Command) VE".
Example Results
Truststore: |
Check the fingerprint that is contained in the agent Keystore.
As shown in the example in (*1), check that the fingerprint that is contained in the agent Keystore is also contained in the manager Truststore that is shown in "Example Results" of step 1.
If it is not, refer to "Corrective Action" to take proper corrective action.
Check the fingerprint that is contained in the agent Truststore.
As shown in the example in (*2), check that the fingerprint that is contained in the agent Truststore is also contained in the manager Keystore that is shown in "Example Results" of step 1.
If it is not, refer to "Corrective Action" to take proper corrective action.
Corrective Action
Execute the following commands on the managed server for which the problem occurred to re-initialize its SSL certificate, and restart its agent.
[Windows]
>"Installation_folder\Agent\bin\rcxadm" certctl init <RETURN> |
[Linux]
# /opt/FJSVrcxat/bin/rcxadm certctl init <RETURN> |
[Solaris]
# /opt/FJSVrcvat/bin/rcxadm certctl init <RETURN> |
Execute the following command on the admin server to start the manager.
[Windows Manager]
>"Installation_folder\SVROR\Manager\bin\rcxadm" mgrctl start <RETURN> |
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl start <RETURN> |
