This topic outlines the network and connectivity requirements for the Delphix Engine and Windows source and target environments.
Port Allocations Specific to Unstructured Files
The Delphix Engine makes use of the following network ports for unstructured files dSources and VDBs:
Outbound from the Delphix Engine
Protocol | Port Numbers | Use |
TCP | xxxx | Delphix Connector connections to source and target environments. Typically, the Delphix Connector runs on port 9100. |
Inbound to the Delphix Engine
Protocol | Port Number | Use |
TCP | 3260 | iSCSI target daemon for connections from iSCSI initiators on the target environments to the Delphix Engine |
Outbound from a Source, Staging, or Target Environment
Protocol | Port Numbers | Use |
TCP | 80 | The Delphix Connector registers environments over HTTP |
| TCP | xxxx | DSP connections used for monitoring and script management. Typically, DSP runs on port 8415. |
Inbound to a Source, Staging, or Target Environment
Protocol | Port Numbers | Use |
TCP | xxxx | Delphix Connector connections to source environments. Typically, the Delphix Connector runs on port 9100. |
| TCP | 445 | If a staging environment is used, the staging server must be able to access SMB (Windows File Sharing) files on the source server. |
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 via the Delphix command line interface (CLI). |
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. |
| TCP/UDP | 32768 - 65535 | Required for NFS mountd and status services from target environment only if the firewall between Delphix and the target environment does not dynamically open ports. Note: If no firewall exists between Delphix and the target environment, or the target environment dynamically opens ports, this port range is not explicitly required. |
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.