[Impact]
Re-registering SRM/VR would fail with an SSL error.
[Cause]
— Both SRM & VR save the entries of the lookupservice url in their respective DBs under various tables.
— These need to be manually updated with the correct entries of the now embedded VC node’s url & thumbprint.
[DB Tables to review]
Wile re-registering SRM :
- In SRM, look for certificates in the following DB tables:
a. SELECT * FROM pd_sslthumbprintstore;
b. SELECT * FROM pd_localsite;
c. SELECT * FROM pd_remotesite;
d. SELECT * FROM pds_remotesite;
e. SELECT * from pds_solutionuser;
- For vSphere Replication:
a. SELECT * from vmomiserverentity;
[Fix]
Manually update the thumbprint & url information as below (would be the same for both SRM & VR):
update vmomiserverentity set thumbprint = ‘C5:A1:31:FA:1F:A5:90:32:90:DX:3E:5F:49:A3:ED:51:79:4C:F4:A2‘ where dbid = ‘330‘;
where;
C5:A1:31:FA:1F:A5:90:32:90:DX:3E:5F:49:A3:ED:51:79:4C:F4:A2 is the thumbprint of the embedded VC’s machine ssl certificate.
330 is the database id of that particular entry.
I hope this helps!
Virtual SDDC 