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.
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.
[Windows Manager]
>"Installation_folder\SVROR\Manager\bin\rcxadm" mgrctl stop "Installation_folder\SVROR\Manager\bin\rcxadm" certctl list
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl stop # /opt/FJSVrcvmr/bin/rcxadm certctl list
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: -------------- Keystore type: jks Keystore provider: SUN The key store includes four entries. client2,May,10,2007, trustedCertEntry, Certificate fingerprint (MD5): 0F:4E:1C:DB:19:AE:3B:82:9D:74:93:6C:46:D8:7C:D2 client1,May,10,2007, trustedCertEntry, Certificate fingerprint (MD5): 9D:99:ED:88:C0:8F:32:26:60:FA:4C:96:A2:34:5A:45 server4,May,11,2007, trustedCertEntry, Certificate fingerprint (MD5): DC:E3:19:59:08:6D:C4:AD:B4:C7:F6:5C:E1:52:0A:1A (*1) server3,May,11,2007, trustedCertEntry, Certificate fingerprint (MD5): 9B:EB:94:58:90:E8:09:BE:BD:FA:14:83:9D:87:3A:E4 ... Keystore: -------------- Keystore type: jks Keystore provider: SUN The key store includes two entries. client, 2007/05/11, keyEntry, Certificate fingerprint (MD5): AA:55:85:54:6B:57:80:4F:8C:6E:2E:AA:7C:77:DB:F6 (*2) server, 2007/05/11, keyEntry, Certificate fingerprint (MD5): 14:48:31:68:C9:CA:66:E1:E0:34:8A:FC:1C:17:19:EF |
[Windows]
>"Installation_folder\Agent\bin\rcxadm" agtctl stop "Installation_folder\Agent\bin\rcxadm" certctl list
[Linux]
# /opt/FJSVrcxat/bin/rcxadm agtctl stop # /opt/FJSVrcxat/bin/rcxadm certctl list
[Solaris]
# /opt/FJSVrcvat/bin/rcxadm agtctl stop # /opt/FJSVrcvat/bin/rcxadm certctl list
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: -------------- Keystore type: jks Keystore provider: SUN The keystore includes one entry. client1, 2007/05/11, trustedCertEntry, Certificate fingerprint (MD5): AA:55:85:54:6B:57:80:4F:8C:6E:2E:AA:7C:77:DB:F6 (*2) ... Keystore: -------------- Keystore type: jks Keystore provider: SUN The keystore includes one entry. server, 2007/05/11, keyEntry, Certificate fingerprint (MD5): DC:E3:19:59:08:6D:C4:AD:B4:C7:F6:5C:E1:52:0A:1A (*1) |
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.
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.
[Windows]
"Installation_folder\Agent\bin\rcxadm" certctl init "Installation_folder\Agent\bin\rcxadm" agtctl start
[Linux]
# /opt/FJSVrcxat/bin/rcxadm certctl init # /opt/FJSVrcxat/bin/rcxadm agtctl start
[Solaris]
# /opt/FJSVrcvat/bin/rcxadm certctl init # /opt/FJSVrcvat/bin/rcxadm agtctl start
[Windows Manager]
"Installation_folder\SVROR\Manager\bin\rcxadm" mgrctl start
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl start