"Incoming Storage Traffic" error occurs in the vSphere Replication Management UI.

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms 

• An "Incoming Storage Traffic" error occurs in the vSphere Replication Management UI.
  The Storage Traffic IP address ### must match one of the NIC IP addresses.

• The hbrsrv service was not running.
• Attempting to reconfigure the service failed. With error below
  

  In the /var/log/vmware/hbrsrv.log file, similar entries are seen:
  ####-##-##T06:39:40.150Z error hbrsrv[62257] [Originator@6876 sub=Main] HbrError stack:
  ####-##-##T06:39:40.150Z error hbrsrv[62257] [Originator@6876 sub=Main]    [0] Exception Vmacore::Exception: Cannot assign requested address
  ####-##-##T06:39:40.150Z error hbrsrv[62257] [Originator@6876 sub=Main]    [1] HbrSrv failed to bind (listen addr=##.#.##.###) (port=31031)
  ####-##-##T06:39:40.150Z error hbrsrv[62257] [Originator@6876 sub=Main]    [2] Failed to start LWD listener (ports: 31031).

• Additionally, log export was unsuccessful. 
    

Environment

vSphere Replication 9.0.1
vSphere Replication 9.0.2

Cause

The IP address specified for incoming storage traffic is not held by the vSphere Replication appliance.

Resolution

 

• Option 1: Reconfigure the vSphere Replication (VR) appliance using the correct IP address.

• Option 2: To segregate replication traffic, add a new NIC to the appliance, assign it a dedicated IP address, and configure it as the incoming storage traffic interface.
  
  

Create a VM Network Adapter to Use for Incoming Replication Traffic on the Combined vSphere Replication Appliance