Network and connectivity requirements for Unix environments
Port allocations specific to unstructured files
The Delphix Engine makes use of the following network ports for unstructured files dSources and vFiles:
Inbound to the Delphix Engine port allocation
Protocol | Port Number | Use |
|---|---|---|
TCP | 873 | Rsync connections used for communication to rsyncd during SnapSync |
TCP/UDP | 111 | Remote Procedure Call (RPC) port mapper used for NFSv3 mounts Note: RPC calls in NFSv3 use additional fixed ports for supporting services (lockd, mountd and statd) seen below. |
TCP | 1110 | NFS Server daemon status and NFS server daemon keep-alive (client info) |
TCP | 2049 | NFS Server daemon from vFiles to the Delphix Engine |
TCP | 54043 | NFSv3 mount daemon |
TCP | 54044 | NFSv3 stat daemon (lock state notification service) |
TCP | 54045 | NFSv3 lock daemon/manager |
TCP | 54046 | Connections from Source and Target Environments to the Engine When NFS Encryption is enabled |
UDP | 33434 - 33464 | Traceroute from source and target database servers to the Delphix Engine (optional) |
Outbound from a source environment port allocation
Protocol | Port Numbers | Use |
|---|---|---|
TCP | 873 | Rsync connections to rsyncd used during SnapSync |
TCP | xxxx | DSP connections used for monitoring and script management during SnapSync. Typically DSP runs on port 8415. |
Inbound to a source environment port allocation
Protocol | Port Numbers | Use |
|---|---|---|
TCP | 22 | SSH connections to the source environment |
Outbound from a target environment port allocation
Protocol | Port Numbers | Use |
|---|---|---|
TCP | 873 | Rsync connections to rsyncd used during V2P |
TCP | xxxx | DSP connections used for monitoring and script management. Typically DSP runs on port 8415. |
Inbound to a target environment port allocation
Protocol | Port Numbers | Use |
|---|---|---|
TCP | 22 | SSH connections to the target environment |
General outbound from the Delphix Engine port allocation
Protocol | Port Numbers | Use |
|---|---|---|
TCP | 25 | Connection to a local SMTP server for sending email |
TCP/UDP | 53 | Connections to local DNS servers |
UDP | 123 | Connection to an NTP server |
UDP | 162 | Sending SNMP TRAP messages to an SNMP Manager |
TCP | 443 | HTTPS connections from the Delphix Engine to the Delphix Support upload server |
TCP/UDP | 636 | Secure connections to an LDAP server |
TCP | 8415 | Connections to a Delphix replication target. See Configuring Replication. |
TCP | 50001 | Connections to source and target environments for network performance tests. |
General inbound to the Delphix Engine port allocation
Protocol | Port Number | Use |
|---|---|---|
TCP | 22 | SSH connections to the Delphix Engine |
TCP | 80 | HTTP connections to the Delphix GUI |
UDP | 161 | Messages from an SNMP Manager to the Delphix Engine |
TCP | 443 | HTTPS connections to the Delphix Management Application |
TCP | 8415 | Delphix Session Protocol connections from all DSP-based network services including Replication, SnapSync for Oracle, V2P, and the Delphix Connector. |
TCP | 50001 | Connections from source and target environments for network performance tests via the Delphix CLI. |
Firewalls and Intrusion Detection Systems (IDS)
Production databases on source environments (for dSources) are often separated from the non-production environment by firewalls. Firewalls can add milliseconds to the latency between servers. Accordingly, for best performance, there should be no firewalls between the Delphix Engine and the virtual database (VDB) target environments. If the Delphix Engine is separated from a source environment by a firewall, the firewall must be configured to permit network connections between the Delphix Engine and the source environments for the application protocols (ports) listed above.
Intrusion detection systems (IDSs) should also be made permissive to the Delphix Engine deployment. IDSs should be made aware of the anticipated high volumes of data transfer between dSources and the Delphix Engine.