Ports Used by Unity - Teradata Unity

Teradata Unity Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Unity
Release Number
16.10
Published
January 2018
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
sgt1496162519660.ditamap
dita:ditavalPath
2523_ICUCustomer_unity_1610.ditaval.ditaval
dita:id
B035-2523
lifecycle
previous
Product Category
Analytical Ecosystem

Make sure the networking and firewall configurations allow communications between each specific server pair for the specified protocols and ports.

Protocol Port From To Description
ICMP N/A Unity Unity Used during setup only. Ping test between Unity-managed Server.
TCP 1026 Unity Ecosystem Manager Used to access the Unity repository.
Viewpoint
Ecosystem Manager
1025 Unity Teradata System Used to access the Teradata system.
Client Server Unity Used by client applications to connect to Unity as a Teradata system.
TCP 5344 Client Server Unity Used for running unityadmin on the client server.
Viewpoint Unity Used for Unity management connections, inter-process communication and to retrieve system state and information.
Unity
Ecosystem Manager
TCP 5345- 5348 (varies with number of Unity processes) Unity Unity Used for internal inter-process communication between the Unity-managed Servers. Depending on the number of processes, the range can be higher or lower than 5345 - 5348. The unity.properties file located at /etc/opt/teradata/config/unity.properties lists the ports used.
The ports are listed as interconnectPort. For example:
r1_dsp_sys1.backplane.interconnectPort=5345
r1_dsp_sys2.backplane.interconnectPort=5346
r1_wdg.backplane.interconnectPort=5347
r1_ept.backplane.interconnectPort=5348
TCP 22 Client Server Unity Used for remote management of the Unity-managed server. This is the ssh port.
Unity Unity Used for configuration and maintenance.
Viewpoint
TCP 6001 Client Server Unity [Deprecated] Used to support a sockclient connection that has been deprecated. A warning will prompt to use unityadmin.