IP Customization package deployment fails in Site Recovery Manager with VMware Tools 10.1.x or higher

Products

• VMware Live Recovery

Issue/Introduction

• IP Customization fails during a Test Recovery or Planned Migration in Site Recovery Manager (SRM).
• The task times out after a long period.
• In vmware-dr.log, you see errors similar to:
  • Received SOAP response fault from [host]: fileManagement An error occurred while communicating with the remote host.
  • N7Vmacore15SystemExceptionE Connection timed out (110)
  • Failed to upload file to VM by using uploadUrl: 'https://[FQDN]:443/guestFile?...'

Environment

VMware Site Recovery 9.0.x

Cause

Starting with VMware Tools 10.1.x, Site Recovery Manager transfers IP customization scripts directly to the ESXi hosts rather than through the vCenter Server. This requires direct connectivity from the SRM appliance to the recovery site hosts. If port 443 is blocked by a firewall, network hardening policy, or NSX rule, the script transfer will fail.

Resolution

1. Verify Connectivity: Run a connectivity test from the SRM appliance command line to the ESXi host at the recovery site:

curl -v telnet://<ESXi_Host_IP>:443
# OR
openssl s_client -connect <ESXi_Host_IP>:443

 

2.  Open Required Ports: Ensure the following ports are open bidirectional between the Site Recovery Manager appliance and the ESXi hosts:

443 (HTTPS): Required for script transfer and guest operations.
902 (TCP/UDP): Required for NFC traffic and RDM management.

3. Check Hardening Policies: Verify that the SRM appliance and ESXi host IPs are added to any "Hardening Exclusion Lists" or allowed through Intrusion Prevention Systems (IPS) that may be dropping traffic between management components.

Additional Information

Refer VMware Live Site Recovery Network ports document.