Return
-
Title
Default ports used by vRanger -
Description
This article provides a complete listing of network ports required by vRanger to facilitate communication of the various application processes including different repository types, physical server protection and VA. -
Resolution
By default, vRanger configured to use the following ports for the processes outlined:
Minimum port 0 - maximum port 655535:
Port Protocol Function 22 TCP - vRanger to VMware® ESXi™ Host
- vRanger to VA
- VA to VA
53 TCP - vRanger/VA/ESXi Host to DNS Server
137 TCP - vRanger/VA/ESXi Host to CIFS Repository
137 UDP - vRanger/VA/ESXi Host to CIFS Repository
138 UDP - vRanger/VA/ESXi Host to CIFS Repository
139 TCP - vRanger/VA/ESXi Host to CIFS Repository
443 TCP - vRanger and VA to ESXi hosts
- vRanger and VA to VMware® vCenter™
445 TCP - vRanger/VA/ESXi Host to CIFS Repository
- vRanger to VA
902 TCP - VA to Hosts
- vRanger to Hosts
2049 TCP - vRanger/VA/ESXi Host to NFS Repository
2049 UDP - vRanger/VA/ESXi Host to NFS Repository
37453 TCP - vRanger/VA/ESXi Host to NetVault SmartDisk Repository
10011 TCP - RDA Control Channel
11000 TCP - RDA Data Channel
51000 TCP - Physical Backup: vRanger to physical server
Please note:
- For the VA designated for Linux® FLR, the firewall must be configured to allow ICMP (ping) packets.
- For physical backups to function correctly, the firewall must be configured to allow WMI connections.
- When backing up physical servers, the vRanger client reads the data directly from the disk and sends data from the source server to the repository. Depending on the repository type, the firewall must be configured to allow connection between the physical server and the repository (CIFS/NFS/SmartDisk/RDA)
Other ports are used by other services independently. For example, if a system uses port 135 for any reason, this is outside of product specification.