Overview

This document provides information on the TCP ports used by services in Tibero.

• How to open ports according to database configuration
• How to open ports based on ProSync configuration
• Determining source and destination IPs when communicating between different IP ranges
• Opening ports according to firewall devices and software firewalls (reference for cases using two types of firewalls)

Method

Default Ports

• This document uses the default port information below.
• If ports are changed in your work environment, apply the changes by referring to the following information.

IP Ranges

• Explains how to set source and destination IPs when servers communicate across different IP ranges.

Same Range

• Within the same range, servers can communicate via L2 broadcast.

• Generally, no separate port opening is required for communication within the same range.
  However, if using software firewalls such as iptables, firewalld, or server security settings, necessary ports must be opened.

1. Same Range Communication (10.10.10.x)

• Connect from source 10.10.10.51 (eth0) to destination 10.10.10.52 (eth0).

• 10.10.10.51 (eth0) → 10.10.10.52 (eth0)

• The source IP seen at the destination is 10.10.10.51.

• Within the same range, connection is made directly via subnetting without passing through a Gateway.

2. Different Range Communication (10.10.10.x → 192.168.100.x)

• Connect from source 10.10.10.51 (eth0) to destination 192.168.100.52 (eth1).

• 10.10.10.51 (eth0) → 192.168.100.51 (eth1) → 192.168.100.52 (eth1)

• The source IP seen at the destination is 192.168.100.51.

• Within the same range, connection is made directly via subnetting without passing through a Gateway.

3. Same Range Communication (192.168.100.x)

• Connect from source 192.168.100.51 (eth1) to destination 192.168.100.52 (eth1).

• 192.168.100.51 (eth1) → 192.168.100.52 (eth1)

• The source IP seen at the destination is 192.168.100.51.

• Within the same range, connection is made directly via subnetting without passing through a Gateway.

4. Different Range Communication (192.168.100.x → 10.10.10.x)

• Connect from source 192.168.100.51 (eth1) to destination 10.10.10.52 (eth0).

• 192.168.100.51 (eth1) → 10.10.10.51 (eth0) → 10.10.10.52 (eth0)

• The source IP seen at the destination is 10.10.10.51.

• Within the same range, connection is made directly via subnetting without passing through a Gateway.

Different Range

• When servers perform L3 routing communication, communication between different ranges occurs.

• If there is a firewall device between servers of different ranges, port opening is required.

• Also, when using firewall devices or software firewalls, necessary ports must be opened respectively.

1. 10.10.10.x → 20.20.20.x

• Connect from source 10.10.10.51 (eth0) to destination 20.20.20.52 (eth0).

• 10.10.10.51 (eth0) → 10.10.10.1 (GW) → L3 Switch (routing) → 20.20.20.1 (GW) → 20.20.20.52 (eth0)

• The source IP seen at the destination is 10.10.10.51.

• If the L3 Switch does not have routing tables and physical network lines for different ranges, connection is not possible.

2. 192.168.100.x → 20.20.20.x

• Connect from source 192.168.100.51 (eth1) to destination 20.20.20.52 (eth0).

• 192.168.100.51 (eth1) → 10.10.10.51 (eth0) → 10.10.10.51 (GW) → L3 Switch (routing) → 20.20.20.1 (GW) → 20.20.20.52 (eth0)

• The source IP seen at the destination is 10.10.10.51.

• If the L3 Switch does not have routing tables and physical network lines for different ranges, connection is not possible.

Tibero SINGLE

• In a SINGLE environment, only ports used between the server and client need to be applied.

Diagram

Port Open

Tibero SINGLE + HA Solution

• If integrating HA Solution with SINGLE configuration, since Tibero does not use its own synchronization ports, open ports similarly to the SINGLE environment.

Diagram

Port Open

Tibero TSC (Primary-Target)

• In TSC environments, data synchronization occurs between Primary and Target nodes, so if synchronization ports are not opened, TSC synchronization may fail.

Diagram

Port Open

Tibero TSC (Primary-Target-Observer)

• In TSC environments, data synchronization occurs between Primary and Target nodes, so if synchronization ports are not opened, TSC synchronization may fail.
• Additionally, since Fail-Over is performed using the Observer, the Observer's monitoring port must also be opened.

Diagram

Port Open

Tibero TAC (2node)

• In TAC environments, nodes share real-time Block (cache) block information and check cluster status between nodes, so port opening between both nodes is required.

Diagram

Port Open

ProSync

• ProSync classifies nodes as Source and Target.
• Data extraction and data application can both be performed on the Source node.
• Alternatively, data extraction and data application can be separated between Source and Target nodes.
• However, if extraction and application are both done on the Source, DML statements used for data application are sent to the Target node, increasing network usage compared to when data application is performed on the Target node.
• To improve data application speed, it is recommended to configure data application on the Target node.

Source All for SINGLE

• The Source node performs both data extraction and data application.
• Data application is applied to the Target node's LISTNER_PORT.

Diagram

Port Open

Source All for TAC

• In TAC environments, there are two Source nodes, and data extraction is performed on each node.
• If data extraction and application are both performed on the Source, only connection to the Target node's LISTENER_PORT is required.

Diagram

Port Open

Source Extract, Target Apply for SINGLE

• When configuring data extraction on the Source node and data application on the Target node, ProSync processes must be running on each node.

Diagram

Port Open

Source Extract, Target Apply for TAC

• In TAC environments, when data extraction is performed on Source nodes and data application on Target nodes, port opening between Source and Target nodes is required.

Diagram

Port Open