SRM and VR Reconfiguration Fails with the Error: "Failed to Register H5 UI." After Changing vCenter from Standalone to Enhanced Linked Mode or from Enhanced Linked mode to Standalone

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

• The SRM and vSphere Replication (VR) reconfiguration fails with the error message: "Failed to register H5 UI."
• This issue arises after a vCenter is changed from Standalone mode to Enhanced Linked Mode or vice versa.

Cause

• Review of the /opt/vmware/support/logs/dr/drconfig.log reveals that the plugin registration process failed. The following error entries were found:

2025-03-05 17:48:46,160 [srm-reactive-thread-11] ERROR com.vmware.dr.client.shared.utils.ExtManagerHelper - Failed to mirror plugin registration to VC ExtensionManager.
2025-03-05 17:48:46,161 [srm-reactive-thread-11] WARN  com.vmware.srm.client.h5config.commands.impl.CreatePluginLsppRegCommand - Failed to create plugin lspp registration:
2025-03-05T17:48:46.515+08:00 error drconfig[01367] [SRM@6876 sub=ConfigOp opID=54f47748-84f7-435f-8acc-f6189b87c475-configure:7f3b] Operation failed
--> (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    reason = "Failed to register H5 UI."

• Further review of the /var/log/vmware/vpxd.log file indicates an issue with the plugin lookup service registration on the vCenter. The log contains the following error:.

2025-03-05T17:48:45.827+08:00 error vpxd[07277] [Originator@6876 sub=Req@internalvim25... opID=fixed-op-id-d5] Method vim.ExtensionManager.updateExtension threw undeclared fault of type vmodl.MethodFault

2025-03-05T17:48:45.827+08:00 error vpxd[07277] [Originator@6876 sub=Default opID=fixed-op-id-d5] [VpxLRO] -- ERROR lro-1024752 -- 5253a87a-f445-17d2-63ef-2355071d290d(52125204-09a7-eae1-e187-76171be97464) -- ExtensionManager -- vim.ExtensionManager.updateExtension: :lookup.fault.EntryNotFoundFault
--> Result:
--> (lookup.fault.EntryNotFoundFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    errorMessage = "Entry with name serviceId: b2eca325-54f8-45b1-8a4f-76c7c0fcbbbb_com.vmware.drui.plugin not found.",
-->    name = "serviceId: b2eca325-54f8-45b1-8a4f-76c7c0fcbbbb_com.vmware.drui.plugin"
-->    msg = "Received SOAP response fault from [<<cs p:0000557969b49710, TCP:localhost:1080>, /lookupservice/sdk>]: set

2025-03-05T17:48:46.319+08:00 warning vpxd[06335] [Originator@6876 sub=MoExtensionMgr opID=fixed-op-id-b3] Failed to update LS service registration; id: b2eca325-54f8-45b1-8a4f-76c7c0fcbbbb_com.vmware.drui.plugin, spec: (lookup.ServiceRegistration.SetSpec) {
-->    serviceVersion = "8.8.0",
-->    vendorNameResourceKey = <unset>,
-->    vendorNameDefault = <unset>,
-->    vendorProductInfoResourceKey = <unset>,
-->    vendorProductInfoDefault = <unset>,
-->    serviceEndpoints = <unset>,
-->    serviceAttributes = <unset>,
-->    serviceNameResourceKey = "com.vmware.drui.plugin.label",
-->    serviceNameDefault = <unset>,
-->    serviceDescriptionResourceKey = "com.vmware.drui.plugin.summary",
-->    serviceDescriptionDefault = <unset>
--> }, N6Lookup5Fault18EntryNotFoundFault9ExceptionE(Fault cause: lookup.fault.EntryNotFoundFault

This failure indicates that the vCenter failed to update the service registration with the ExtensionManager, causing the reconfiguration failure.

• When the vCenter is switched from Standalone to Enhanced Linked Mode, the plugin registration, which was previously local to the Standalone vCenter, is now expected to be shared across both sites. Since the plugin is not registered for sharing, the reconfiguration fails when attempting to update the registration.
  
  Similarly, when the vCenter server is switched from enhanced linked mode to standalone, the plugin registration which was shared previously across both the sites is no longer available. Due to this the reconfiguration task fails to update the registrations on the vCenter .

 

Resolution

To resolve this issue, follow these steps:

1. List all registered lookup services: Run the following command on the vCenter to list all the registered lookup services:
   /usr/lib/vmware-lookupsvc/tools/lstool.py list --url http://localhost:7090/lookupservice/sdk > /tmp/psc_services.txt --no-check-cert
   This will output the list of all registered lookup services to the file /tmp/psc_services.txt.

2. Identify the SRM and vSphere Replication service IDs: Search through the output file (/tmp/psc_services.txt) for the service entries related to SRM and vSphere Replication.

3. Unregister the lookup service registrations and extension: To unregister the lookup service registrations and the extension from the vCenter MOB, please reach out to Broadcom Support for assistance.
   
   
4. Reconfigure SRM and vSphere Replication appliances: Follow the configuration wizard for both SRM and vSphere Replication appliances. Ensure that the configuration completes without any errors.