Port Requirements | Teradata Fabric - Port Availability - Teradata Fabric

Teradata® Fabric - Installation and User Guide - 3.11
Product
Teradata Fabric
Release Number
3.11
Published
August 2026
ft:locale
en-US
ft:lastEdition
2026-08-15
dita:mapPath
svw1780362788070.ditamap
dita:ditavalPath
ezw1784752870623.ditaval
dita:id
lxg1591800469257

Make sure that network ports are open between the Teradata Fabric-attached systems (data sources) and Teradata Fabric Manager by running curl -k https://qgm_host:9444/api from the node to check connectivity to Teradata Fabric Manager. Systems include the Teradata nodes, Hadoop master node, all Hadoop data nodes, Oracle driver nodes, BigQuery driver nodes, Arrow Flight SQL nodes, and Generic JDBC driver nodes.

The following illustration and table describe the port numbers used between Teradata Fabric-attached systems and Teradata Fabric Manager in a fabric.



Port Description
22
  • One-way connection from the Teradata Fabric Manager to all Teradata Fabric-attached nodes; used if performing automatic installation of packages.
  • One-way connection from the Teradata Fabric Manager to another Teradata Fabric Manager; used during cluster creation when using the SSH method.
443
  • One-way connection to access Google BigQuery and Cloud Storage.
  • One-way connection to access the BigQuery API and OAuth API endpoints using a standard HTTPS connection.
1025/443 One-way connection from the target Teradata driver to the target Teradata system (JDBC connection).
1521 One-way connection from the target Oracle driver to the target Oracle system.
5000-5002 Two-way connections between all Teradata Fabric-attached nodes; other available ports can be used, but ports 5000-5002 are recommended. When upgrading, two ports per fabric are required.
5100 Two-way connections between Teradata Fabric connected nodes in a fabric when using Teradata Cloud.
8443 One-way connection from the target Hive driver to the Apache Knox Gateway if Apache Knox Gateway is enabled on Hadoop nodes.
9443
  • One-way HTTPS connection from Viewpoint or a browser to Teradata Fabric Manager.
  • One-way connection from Teradata Fabric Manager to another Teradata Fabric Manager; used during cluster creation when using the join token method.
9444 One-way HTTPS connection from Teradata Fabric-attached nodes to Teradata Fabric Manager.
9445 Two-way HTTPS connection between clustered Teradata Fabric Managers in a fabric.
10000 One-way connection between the target Hive driver to target Hiveserver2.
10016 One-way connection from the target Spark SQL driver to the target Spark Thrift Server.
* For the Generic JDBC and Arrow Flight SQL connectors, the port required depends on the data source. Refer to your data source user guide for port requirements.