vSphere Replication continues connecting to an ESXi host after 'com.vmware.vr.disallowedHost' tag applied.
search cancel

vSphere Replication continues connecting to an ESXi host after 'com.vmware.vr.disallowedHost' tag applied.

book

Article ID: 402534

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Multiple ESXi hosts were disallowed for replication. However VR still trying to connect to them.

hms.log

2025-06-25 10:13:34.972 INFO
onHandler )
[task=HTID-########-####-####-####--############] | Connecting to server
2025-06-25 10: 13:34.972
com. vmware.jvs1.sessions.net. impl.AbstractConnectionHandler [hms-main-thread-26425) (..net, imphbrsrv/13.Connecti
' ###.###.###.###:443' using
WARN
com.vnware.jvsl.util.RequestContextProviderImpl[hms-main-thread-26425] (Jvs.util.RequestContextProviderImpl)
[task=HTID-########-####-####-####--############ | Generating operation id for request (MoRef:
*MoRef: type = HbrSess ionManager, value = HbrS
ess ionManager, serverGuid

Environment

vSphere Replication 9.0.2.x

Cause

VR did not register com.vmware.vr.disallowedHost tag.

Resolution

1. Restart HMS service on the VR VAMI (https://VR_IP:5480). 

2. Remove replication tag from the ESXi

3. Add disallow replication tag to ESXi.

4. Again restart HMS service on the VR VAMI (https://VR_IP:5480) Check if connection stopped.