Port requirements for Site Recovery Manager 5 and vCenter Server 5

6 August, 2012 How To, VMware 0

A few days ago Troy Hampel (@MrTroyH) asked me on Twitter if I had some troubleshooting blogs about resource mapping permission in Site Recovery Manager 5, unfortunately I didn’t, simply because I did not came across any issues with permissions when I was implementing my SRM 5 infrastructure 🙂 But this gave me an idea to summarize the ports used by the Site Recovery Manager 5 between the Protected Site and the Recovery Site but also the local site communication.

vCenter Server

  • 80 – HTTP
  • 443 – SSL interface
  • 902 – VMware management
  • 8096 – Tomcat web server

vSphere Client

  • 8095 – SRM client plugin to communicate with SRM server and vCenter Server (local site)
  • 9007 – SRM client plugin to communicate with vCenter server (local site)

Site Recovery Manager Server

  • 80 – SRM Server at Protected Site to vCenter Server at Recovery Site. SRM communication with local vCenter server and vSphere Client plug-in download
  • 443 – SRM communication with remote vCenter Server via HTTP over SSL tunnel
  • 902 – VMware management, needs to be open between SRM server and ESX(i) hosts
  • 1433 – SRM Connectivity to Microsoft SQL Server (local site)
  • 1521 – SRM Connectivity to Oracle (local site)
  • 1526 – SRM Connectivity to Oracle (local site)
  • 5000 – SRM Connectivity to IBM DB/2 (local site)
  • 8095 – SOAP interface between the vCenter Server proxy and SRM
  • 8123 – SOAP port between SRM and vSphere Replication Management server (local site)
  • 9085 – HTTP interface for downloading the UI plugin and icons (local site)
  • 9007 – SOAP interface for external API clients via WSDL
  • 9008 – SOAP interface for external API clients via HTTP

vSphere Replication  Management Server

  • 80 – All traffic to SRM servers goes through the vCenter proxy
  • 8043 – SOAP interface between the vCenter proxy and VRMS
  • 8080 – VAMI Web UI for the VRMS appliance

vSphere Replication Server (if used)

  • 902 – VMware management (specifically the NFC service), needs to be open between VR server and ESX(i) hosts on the same site
  • 8123 – SOAP interface used by VRMS to manage VR servers (local site)
  • 5480 – VAMI Web UI for the VR server (local site)
  • 31031 – Initial replication traffic
  • 44046 – Ongoing replication traffic

Storage Replication Adapters (if used)

  • See vendor documentation

All ports are TCP. No UDP ports are used by SRM 5.

Source:

Cheers!

– Marek.Z

Be the first to comment

Leave a reply...