Search the VMware Knowledge Base (KB)
View by Article ID

Network ports for Site Recovery Manager 6.0 (2103394)

  • 4 Ratings

Details

Site Recovery Manager  can experience problems if the required network ports are not open.
  • Site Recovery Manager fails to establish site pairing due to connection termination over port 9086.
  • Site Recovery Manager connection to remote site breaks frequently. 
In a Site Recovery Manager deployment, both the protected site and the recovery site must be able to resolve the vCenter Server instance by name. The correct ports must be open on both sites for uninterrupted communication.
 

Solution

The components that make up a Site Recovery Manager deployment, like vCenter Server, vSphere Web Client, Site Recovery Manager Server, the vSphere Replication appliance, and vSphere Replication servers, require different ports to be open. You must ensure that all the required network ports are open for Site Recovery Manager to function correctly.
 
General networking guidelines:
  • When troubleshooting Site Recovery Manager pairing and testing issues, eliminate firewalls and security applications as a possible cause of the problem by temporarily disabling or removing the software or item in question.
  • If you are using a VPN adapter such as SonicWALL or Juniper, ensure that the timeout setting is set to the maximum for any tunnel that is open on the required ports.

vCenter Server and ESXi Server network port requirements for Site Recovery Manager 6.0

Site Recovery Manager requires certain ports to be open on vCenter Server and on ESXi Server:
                                     
Default Port Protocol or Description Source Target Description
443 HTTPS Site Recovery Manager vCenter Server Default SSL Web port
443 HTTPS Site Recovery Manager Platform Services Controller
Traffic from Site Recovery Manager Server to local and remote Platform Services Controller.
10443 TCP Site Recovery Manager Local Inventory Service Server Used by Site Recovery Manager to publish data to the local Inventory Service.
902 TCP Site Recovery Manager Server on the recovery site Remote ESXi host Traffic from the Site Recovery Manager Server on the recovery site to ESX hosts when recovering or testing virtual machines with IP customization, with configured callout commands on recovered virtual machines, or that use raw disk mapping (RDM). All NFC traffic for updating or patching the VMX files of virtual machines that are replicated using vSphere Replication use this port.

Site Recovery Manager Server 6.0 network ports

The Site Recovery Manager Server instances on the protected and recovery sites require certain ports to be open.

Note: Site Recovery Manager Server at the recovery site must have NFC traffic access to the target ESXi servers.
                           
Default Port Protocol or Description Source Target Endpoints or Consumers
443 TCP Site Recovery Manager vCenter Server Default SSL Web Port for incoming TCP traffic
443 TCP Site Recovery Manager Platform Services Controller
Traffic from Site Recovery Manager Server to local and remote Platform Services Controller.
10443 TCP vSphere Web Client Local and remote Inventory Service Servers Used by Site Recovery Manager client plug-in to query the data in Inventory Service.
902 TCP and UDP Site Recovery Manager Server on the recovery site Remote ESXi host Traffic from the Site Recovery Manager Server on the recovery site to ESXi hosts when recovering or testing virtual machines with IP customization, with configured callout commands on recovered virtual machines, or that use raw disk mapping (RDM). All NFC traffic for updating or patching the VMX files of virtual machines that are replicated using vSphere Replication use this port.
1433 TCP Site Recovery Manager Microsoft SQL Server Site Recovery Manager connectivity to Microsoft SQL Server (for Site Recovery Manager database)
1521 TCP Site Recovery Manager Oracle Database Server Site Recovery Manager database connectivity to Oracle
1526 TCP Site Recovery Manager Oracle Database Server Site Recovery Manager database connectivity to Oracle
9086 HTTPS vSphere Web Client Site Recovery Manager All management traffic to Site Recovery Manager Server goes to this port. This includes traffic by external API clients for task automation and HTTPS interface for downloading the UI plug-in and icons. This port must be accessible from the vCenter Server proxy system. Used by vSphere Web Client to download the Site Recovery Manager client plug-in.

Site pairing port requirements

Port

Source

Target

Description

9086

vCenter Server

SRM server target site

vCenter and target SRM communication

9086

SRM server

SRM server on target site

SRM to SRM communication

443

SRM

PSC and vCenter

SRM to vCenter communication – local and remote

Network ports that must be open between the Site Recovery Manager and vSphere Replication Protected and Recovery sites

Site Recovery Manager and vSphere Replication require that the protected and recovery sites can communicate.

Port Protocol or Description Source Target Endpoints or Consumers
80 SOAP Site Recovery Manager and vSphere Replication appliance Remote vCenter Server Management traffic between Site Recovery Manager Server instances and vSphere Replication appliances. Traffic passes through the vCenter Server reverse proxy.
31031 Initial replication traffic ESXi host vSphere Replication appliance on the recovery site From the ESXi host at the protected site to the vSphere Replication appliance at the recovery site.
44046 Ongoing replication traffic ESXi host vSphere Replication appliance on the recovery site From the ESXi host at the protected site to the vSphere Replication appliance at the recovery site.

Additional Information

For translated versions of this article, see:

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 4 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 4 Ratings
Actions
KB: