Server with UUID not found
Article ID: 382712
Updated On:
Products
Issue/Introduction
SRM UI displays these errors.
Server with UUID 'ab28b535-####-####-####-############' not found.
ERRORServer for guid 'fb28b535-####-####-####-############' not found, but pair server(s) exist: [PairSetupImpl {_server = SrmServerImpl { _guid = 0202eca5-####-####-####-############ _url = https://prodsrm.broadcom.com:443/drserver/vcdr/vmomi/sdk }_pairServerGuid = fb28b535-####-####-####-############_pairLsppUrl = https://prodsrm.broadcom.com:443/lookupservice/sdk_pairLsppsThumbprint = A3:##:D9:##:E7:##:E4:##:9F:##:3B:##:C0:##:A0:##:F9:##:B5:##:2F:##:8A:##:3E:##:EC:##:2A:##:18:##}]Operation ID: cd676860-232a-4da1-9537-############11/14/24, 11:23:34 AM -0500
ERRORUnable to retrieve Site Recovery Manager summary data.Server with UUID 'fb28b535-####-####-####-############' not found.Operation ID: 2e1c671d-####-####-####-############
11/14/24, 11:23:34 AM -0500
Error: "Site pair context is not valid".
Environment
VMware Live Site Recovery
vSphere Replication
Cause
The paired appliance has been unregistered or redeployed before breaking the site pair.
drconfig.log:
Log messages showing SRM unregistered
2025-03-21T15:15:32.786Z info drconfig[01381] [SRM@6876 sub=DrConfigConfigurationManager opID=f500468f-03cb-4a87-8561-############-clear:8baa] ClearSrm: Starting clear configuration task
--> (drConfig.ConfigurationSpec) {
--> siteName = <unset>,
2025-03-21T15:15:48.861Z info drconfig[122709] [SRM@6876 sub=InfraNodeConfig opID=f500468f-03cb-4a87-8561-############-clear:8baa] Successfully removed service with service id '17a1d48d-85dc-44b7-bf84-############'
Log messages showing SRM registered
2025-03-21T15:38:53.594Z info drconfig[01003] [SRM@6876 sub=DrConfigConfigurationManager opID=24ff8879-8f6c-47ce-b69f-############-configure:d9d2] ConfigureSrm: Starting create configuration task
--> (drConfig.ConfigurationSpec) {
--> siteName = "",
--> hostName = "",
2025-03-21T15:38:53.595Z info drconfig[01037] [SRM@6876 sub=ConfigOp opID=24ff8879-8f6c-47ce-b69f-############-configure:d9d2] Created new uuid for srm: 'f5d5ce99-79b6-4295-b3ce-############'
Resolution
H5Logs/dr.topology.log:
_type = vcDr
_serviceDescriptionResourceKey =
_siteId = Production SRM
_id = 0202eca5-####-####-####-############
_nodeId = b6d89447-b38c-4b46-b9e9-############
_product = com.vmware.dr
The _id has now changed to:
_type = vcDr
_serviceDescriptionResourceKey =
_siteId = Production SRM
_id = 4c0ff160-####-####-####-############
_nodeId = 8a179682-91b5-11e8-847d-############
_product = com.vmware.dr
Check the _siteId & _id under the Neighbors section of the log. This information must be consistent in the logs. If it's not then it's a clear indication of the appliance being redeployed or unregistered from SRM/vSphere Replication VAMI.
Unregister the SRM from the peer site and reconfigure both SRM appliances. If available, use the SRM configuration export to import the data; otherwise, set up all mappings from the beginning.
NOTE: Please take screenshots wherever necessary from the working SRM UI before you begin to dismantle the setup.
Additional Information
This article applies to both SRM & vSphere Replication.
FAQ: Site Recovery Manager & vSphere Replication Redeployment Guidelines
Feedback
