Yugabyte network and connectivity requirements

Ensure that the requirements for Delphix Continuous Data Engine network connectivity are met before you proceed further. This page addresses YugabyteDB connector-specific network and connectivity requirements.

Ports for Yugabyte connectoryugabyte architecture

Yugabyte Inter-node connectivity requirements

The Yugabyte connector requires the following inter nodes within a YugabyteDB cluster to communicate with each other:

  • Communication to the Master yb-master service on TCP 7100

  • Communication to the Tablet yb-tserver services on TCP 9100

For more information, read the Yugabyte Network Requirements documentation.

SSH connectivity to staging/target host

  1. Staging and target environments are required to have sshd running and configured for Delphix Continuous Data Engine to connect over ssh.

  2. The Delphix Continuous Data Engine platform expects to maintain long-running, highly performant-SSH connections with the host environment.

Whitelisting inbound port for SSH connection to target host

Creating NFS mounts on the target host

The Delphix Continuous Data Engine shares its storage space with the target host using NFS mounts. 

Protocol

Port Number

Use

TCP

22

SSH connection to the target database environment.

TCP/UDP

111

Remote Procedure Call (RPC) port mapper used for NFSv3 mounts.

TCP

1110

Network Status Monitor (NSM) client from target hosts to the Delphix Continuous Data Engine.

TCP

2049

NFS client from target hosts to the Delphix Continuous Data Engine (NFSv3 and NFSv4).

TCP

54043

Client mount daemon (NFSv3 only).

TCP

54044

Lock state notification service (NFSv3 only).

TCP

54045

Network Lock Manager (NLM) client from target hosts to Delphix Continuous Data Engine (NFSv3 only).

UDP

33434 - 33464

Traceroute from the target database server to the Delphix Continuous Data Engine (optional).

Connecting to YugabyteDB instances (VDBs)

Outgoing (From) 

Incoming (To) 

Protocol 

Port List 

Use 

Tservers End-user hosts  

Target YugabyteDB instance 

TCP 

<PGSQL Proxy Bind Port for TServer>

5433 

Connecting to the created Postgres database instance on the target host. 

<CSQL Proxy Bind Port for TServer>

9042 

Connecting to the created CSQL database instance on the target host. 

<RPC Bind Port for TServer>

9100 

Internode (server-to-server or node-to-node) communication, including xCluster 

Masters End-user hosts 

Target YugabyteDB instance 

TCP 

<RPC Bind Port for Master>

7100 

Internode (server-to-server or node-to-node) communication, including xCluster