Here are documented network port numbers and protocols that must be open for Site Recovery Manager, vSphere Replication, and vCenter Server. Very nice and useful VMware KB article however during my last SRM implementation I have realized that some ports are not documented on KB article mentioned above.
We spent some time with customer's network admin to track what other ports are required so here they are. These other ports must be opened for full functionality of SRM + vSphere Replication.
If you use external MS-SQL database don't forget to allow network communication to database server. It is typically udp_1434 (MS-SQL Resolver) and tcp port of MS-SQL instance.
Credits: Network protocols and ports has been grabbed by customer's network admins (Ladislav Hajek and Ondrej Safranek) contributing with me on SRM project.
We spent some time with customer's network admin to track what other ports are required so here they are. These other ports must be opened for full functionality of SRM + vSphere Replication.
| Source | Target | Protocol_Port |
|---|---|---|
| SRM SERVER | VCENTER SERVER | http_80, https_443, tcp_80, tcp_8095 |
| SRM SERVER | ESX HOSTS | tcp/udp_902 |
| VCENTER SERVER | SRM SERVER | http_9085, https_9086, tcp_8095, tcp_9085 |
| REPLICATION APPLIANCE | VCENTER SERVER | tcp_80 |
| REPLICATION APPLIANCE | ESX HOSTS | http_80, tcp/udp_902 |
| ESX HOSTS | REPLICATION APPLIANCE | tcp_31031, tcp_44046 |
| VCENTER SERVER | VCENTER SERVER | http_80, tcp_10443, https_443 |
If you use external MS-SQL database don't forget to allow network communication to database server. It is typically udp_1434 (MS-SQL Resolver) and tcp port of MS-SQL instance.
Credits: Network protocols and ports has been grabbed by customer's network admins (Ladislav Hajek and Ondrej Safranek) contributing with me on SRM project.
1 comment:
A very useful post, thank you. The one time, TCP port 80 between two vCenter servers is particularly easy to miss!
Post a Comment