Where to Put No Ingress in the Link Setup - Teradata Fabric

Teradata® Fabric - Installation and User Guide - 3.11

Product
Teradata Fabric
Release Number
3.11
Publication Date
August 2026
Content Type
Administration
Configuration
Installation
User Guide
Publication ID
B035-5991-086K
ft:locale
en-US
ft:lastEdition
2026-08-15
dita:mapPath
svw1780362788070.ditamap
dita:ditavalPath
ezw1784752870623.ditaval
ft:sourceId
dita
dita:id
lxg1591800469257

When adding a link, select No Ingress for the hop that moves in the direction towards the connection that cannot be made.

For example, a PrivateLink connection from an on-prem node to a cloud node: the link points from the on-prem node to the cloud node. In this scenario the Hop1 Initiating network option is set to No ingress since the cloud deployment cannot connect to the on-prem nodes. However, if the link points from the cloud node to the on-prem node, then the Hop1 Target network is set to No ingress.

The same logic applies to bridge scenarios. Whatever system is directly behind the load balancer is where the ingress network is applied.