Configure Teradata Fabric for a Teradata FICON Node | Teradata Fabric - Configuring Teradata Fabric for a Teradata FICON Node - 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
In some Teradata systems, fiber-channel connection (FICON) nodes are used as parsing engine-only (PE-only, as opposed to having AMP) nodes with no network connectivity. Although they do not have AMPs, FICON nodes still require access to a Teradata Fabric query or a query that references a view referencing a Teradata Fabric query. If the FICON nodes do not have network connectivity, they need to use the following features:
  • The Teradata Fabric Manager proxy feature to access Teradata Fabric Manager
  • The Teradata Fabric bridge feature to access remote systems
To run Teradata Fabric using this configuration, the following is recommended.
In this scenario, Hop 1 uses a BYNET network interface as the initiating and target network; Hop 2 uses the customer LAN network.
  1. From Edit System select the Enable Proxy connections to QGMs for nodes that do not have direct access checkbox.
  2. Select Connectivity through local nodes.
    Use the default port and network values.
  3. Add nodes in the following order:
    1. Add non-FICON nodes to the system, if not already added
    2. Add FICON nodes
  4. To route PE requests from the Teradata FICON node to a target system, do the following:
    1. Set up a Teradata Fabric link as a single bridge.
    2. Make sure the bridge includes all the TPA nodes that have connectivity to all target nodes.