VDT log for vCenter show [FAIL] SSL Connectivity - Investigate error: [vc:443]:[Errno -2] Name or service not known

Products

• VMware vCenter Server

Issue/Introduction

• vSphere Replication was previously deployed in vSphere but has been decommissioned
• When Using the VCF Diagnostic Tool for vSphere (VDT) it reports the below failure 

          VC Lookup Service Check

            • SSO Site: default-site

                • [PASS]    vCenter.example.com (VC Server or CGW)

                • [FAIL]    192.168.10.10 (vSphere Replication)
                  [FAIL]    SSL Connectivity
                            Investigate error: [192.168.10.10:443]:[Error 113] No route to host

Cause

leftover service registrations on the lookupserivce of the vCenter:

Resolution

Please note ensure you have taken proper snapshots of your SSO domain. This means that you must shut down all VCs or PSCs that are in the SSO domain at the same time, then snapshot them, and power them on again.  If you need to revert to one of these snapshots, shut all the nodes down, and revert all nodes to the snapshot

1. List of the Services  ID registered within the vCenter and using the IP address of the vSphere Replication that is reported in the VDT ,In the below output 3 Service ID are reported
   /usr/lib/vmware-lookupsvc/tools/lstool.py list --url http://localhost:7090/lookupservice/sdk | grep 192.168.10.10 -B 8 | grep "Service ID"
    Service ID: 00f61379-####-####-####-####################_com.vmware.vcHms
    Service ID: h5-dr-####-####-####-####################
    Service ID: d8957e41-####-####-####-####################
2. The below step would need to be completed for each Service ID that is reported, to run it requires the password for [email protected] (default SSO domain)
   /usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url https://localhost/lookupservice/sdk --no-check-cert --id  00f61379-####-####-####-####################_com.vmware.vcHms --user administrator@sso_domain --password 'Example'
3. Once the all the Service ID have been removed restart services on the vCenter 
   service-control --stop --all && service-control --start --all