vSphere Replication Enhanced Mapping Test UI limit for ESXi host display
search cancel

vSphere Replication Enhanced Mapping Test UI limit for ESXi host display

book

Article ID: 438861

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

In large-scale VMware Cloud Foundation (VCF) or vSphere environments, the Enhanced Replication Mapping test details page intermittently or consistently fails to list specific ESXi hosts. While replication functionality remains operational, the UI does not render the full inventory, leading to concerns regarding host eligibility or connectivity.

Symptoms:

  • Specific ESXi hosts are missing from the "Test Details" list within the Enhanced Replication Mapping UI.

  • Users may be unable to verify health of specific hosts during replication mapping tests.

  • VR Client logs (typically found in SRM/VR client service logs) contain the following warning:

    WARN com.vmware.vr.client.replications.HealthMonitoringDetailsDataHandler - The requested hosts: 128 are less then the total number of hosts:

Environment

VMware Cloud Foundation (VCF) 

vSphere Replication 9.x

Cause

A hard-coded display limit exists within the HealthMonitoringDetailsDataHandler logic in the vSphere Replication/SRM Client service.

The UI is architecturally capped at retrieving and displaying a maximum of 128 host entities for the health monitoring details view.

Resolution

This is a known display limitation. Engineering has identified the hard-coded constraint and a fix is planned for a future release and backport.

There is no configuration change available in the current version to increase this UI display limit.

Workaround & Functional Validation: To validate the health of hosts not visible in the UI, you can manually inspect the HMS logs on the vSphere Replication Management Server (VRMS) appliance for test heartbeat signals (PING-GID).

  1. Trigger the Test: In the vSphere Client, initiate an Enhanced Replication Mapping test.

  2. Access the VRMS: Log in to the VRMS appliance via SSH as root.

  3. Filter Logs: Run the grep command to check heartbeat signals:

    grep "PING-GID" /opt/vmware/hms/hms.log

    The output will show the source and destination host names that successfully completed the health ping, showing a failReason if the test fails.

Additional Information

Note: This issue is a visual inventory display limitation and is distinct from the functional connection exhaustion issue (which causes hosts to disconnect from vCenter) documented in KB 404721

Powered by Wolken Software