Remove stale/duplicate SRM entries from PSC 2.0

Things to know.

  1. SRM solution user should match the VRUI user. See example

/usr/lib/vmidentity/tools/scripts/lstool.py list –url http://localhost:7080/lookupservice/sdk –type VCDR

RESULT SRM-5abc29cb-fc9a-46b4-a157-72be62820b34@vsphere.local

/usr/lib/vmidentity/tools/scripts/lstool.py list –url http://localhost:7080/lookupservice/sdk –type VRUI

RESULT Service ID: h5-dr-5abc29cb-fc9a-46b4-a157-72be62820b34

The IP addresses should also match.

To remove a stale entry

/usr/lib/vmidentity/tools/scripts/lstool.py unregister –url http://localhost:7080/lookupservice/sdk –id h5-dr-5abc29cb-fc9a-46b4-a157-72be62820b34 –user ‘administrator@vsphere.local’ –password ‘VMware123!’ –no-check-cert

For all the other commands including the windows commands please checkout my original post

https://paulsbestscriptlets.com/2018/02/27/remove-stale-srm-entries-from-psc/

Please find commands for 7.0 below:

/usr/lib/vmware-lookupsvc/tools/lstool.py list –url http://localhost:7090/lookupservice/sdk  –type com.vmware.vcDr
/usr/lib/vmware-lookupsvc/tools/lstool.py list –url http://localhost:7090/lookupservice/sdk  –type VCDR
/usr/lib/vmware-lookupsvc/tools/lstool.py list –url http://localhost:7090/lookupservice/sdk  –type VrUi

/usr/lib/vmware-lookupsvc/tools/lstool.py unregister –url http://localhost:7090/lookupservice/sdk –id ‘Service_ID’ –user ‘administrator@vsphere.local’ –password ‘password’ –no-check-cert 

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s