This topic outlines the network and connectivity requirements for the Delphix Engine and DB2 standby and target environments.
Port Allocations Specific to DB2
The Delphix Engine makes use of the following network ports for DB2 standby and target:
Inbound to the Delphix Engine Port Allocation
Protocol | Port Number | Use |
| TCP/UDP | 111 | Remote Procedure Call (RPC) port mapper used for NFS mounts Note: RPC calls in NFS are used to establish additional ports, in the high range 32768-65535, for supporting services. Some firewalls interpret RPC traffic and open these ports automatically. Some do not. |
| TCP | 1110 | NFS Server daemon status and NFS server daemon keep-alive (client info) |
| TCP/UDP | 2049 | NFS Server daemon from vFiles to the Delphix Engine |
| TCP | 4045 | NFS lock daemon/manager |
| UDP | 33434 - 33464 | Traceroute from standby and target hosts to the Delphix Engine (optional) |
| UDP/TCP | 32768 - 65535 | NFS mountd and status services, which run on a random high port. Necessary when a firewall does not dynamically open ports. |
Outbound from a Standby or Target Environment Port Allocation
Protocol | Port Numbers | Use |
TCP | 873 | Rsync connections used during V2P. |
| TCP | 8415 | DSP connections used for monitoring and script management. Typically DSP runs on port 8415. |
Inbound to a Standby or Target Environment Port Allocation
Protocol | Port Numbers | Use |
TCP | 22 | SSH connections to the target environment |
HADR Service Ports
The HADR ports set for HADR_LOCAL_SVC and HADR_REMOTE_SVC on the DB2 Master and Standby hosts. The specific ports used at the customers' discretion and need to be specified during the linking process. It is highly recommended that this ports also be defined in the /etc/services file to ensure that they are only used by DB2 for the specified databases.
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.
AppData Port Requirements
- The next release of the Delphix Engine will significantly augment the port/protocol utilization of AppData. The upcoming-only requirements have been marked with a *.
- AppData V2P uses RSYNC to export to the target. RSYNC between the target and Delphix Engine is not required for general virtualization usage. The V2P-only requirements have been marked with a ^.
From Source to Delphix Engine | From Delphix Engine to Source | From Target to Delphix Engine | From Delphix Engine to Target |
|---|---|---|---|
| RSYNC (TCP Port 873) | RSYNC (TCP Port 873) | DSP (Default TCP Port 8415) | DSP (Default TCP Port 8415) |
| DSP (Default TCP Port 8415) | SSH (TCP Port 22) | NFS | SSH (TCP Port 22) |
| *NFS | DSP (Default TCP Port 8415) | ^RSYNC (TCP Port 873) | ^RSYNC (TCP Port 873) |