Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.0 system

50
Use the following command to remove invalid entries:
mxnodesecurity -r -p protocol.type -n ipaddress of the server
Where:
• dsc_sas = SA
• dsc_rdp = RDP
• dsc_ignite = Ignite
• dsc_custom = VMware AD
Scenario 11: After data migration, the Matrix OE CMS cannot
communicate with SPM
During Data Migration Tool (DMT) operations, the Storage Provisioning Manager service user
certificate is copied from the old CMS to the new CMS. The new CMS has a different, unique
certificate that is used for communication between the CMS and SPM for the service user. However,
the SPM service user certificate was copied from the old CMS. This creates an out-of-sync certificate
scenario where the CMS service user cannot authenticate with SPM and vice versa.
Perform the following sequence of commands to resume functionality between the CMS and SPM.
Check the current certificates for the service user:
1. Change the directory to the following path.
C:\Program Files (x86)\HP\Storage Provisioning Manager\bin
2. Execute the following:
a.
Check the server certificate:
keytool -printcert -file “C:\Program Files\HP\Systems Insight
Manager\bin\server_cert.pem”
Observe and record the SHA1 thumbprint information without “:”’s.
b.
Check the SPM MatrixService1 user certificate:
spmadmin /lcu
c.
Observe the MatrixService1 user and record the associated certificate thumbprint.
Compare the thumbprints without any “:”’s.
3. If the thumbprints do not match, execute the following command:
spmadmin /ucu “MatrixService1” “C:\Program Files\HP\Systems Insight
Manager\bin\server_cert.pem”
4. Recheck the certificates to verify that they now match:
a. Check the server certificate:
keytool -printcert -file “C:\Program Files\HP\Systems Insight
Manager\bin\server_cert.pem”
Observe and record the SHA1 thumbprint information without “:”’s.
b. Check the SPM MatrixService1 user certificate:
spmadmin /lcu
Observe the MatrixService1 user and record the associated certificate thumbprint.
c. Compare the thumbprints without any “:”’s.
5. Repeat steps 1-4 if the SHA1 thumbprints do not match.