Network Fabric for Systems| Teradata Data Mover - 17.11 - Network Fabric for Systems - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers

Product
Teradata Data Mover
Release Number
17.11
Release Date
October 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-4102-091K
Language
English (United States)

A network fabric defines the data path between one or more nodes in a Teradata system and DSA media servers using the most efficient interface when transferring data. In a Data Mover-DSA configuration, media servers are installed on the target system nodes.

Network fabrics are defined by using one of the following methods:
  • The dsa_configfabric script provided in the Data Mover installation package
    • You can also find the script under the /opt/teradata/datamover/support/dsa_configfabric directory.
  • The config_fabric command in the DSC command line
  • The DSA portlet

    The DSA portlet version must match the DSC version. See Teradata® Data Stream Utility Installation, Configuration, and Upgrade Guide, B035-3153 for more information.

For example, a configuration where the media server on SystemA is connected in the following way:
  • to System B using both a high-speed BYNET network (10.16.xx.xx) and a LAN network (10.25.xx.xx)
  • to System C using only a LAN network (10.25.xx.xx)
In this example, defining network fabrics for System B and System C makes sure that traffic from System B to System A uses the high-speed BYNET, while System C to System A uses the LAN network. The difference, when compared to a logical netmask configuration, is that while the netmask allows traffic from the media server to both System B and System C, it cannot limit the System B traffic to use only the high-speed BYNET.
Below is a sample fabric XML for System B, specifying the media server IP addresses to be used on System A. This is using a configuration where both system A and B are 2-node MPP systems. A similar fabric XML is needed to configure a fabric for System C. For more information, see Teradata® DSA User Guide, B035-3150.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<dscConfigFabrics xmlns="http://schemas.teradata.com/v2012/DSC">
   <fabric_name>systemBFabricConfig</fabric_name>
   <system_name>systemB</system_name>
   <is_enabled>true</is_enabled>
   <tpa_to_ms>
       <node_name>systemB-01</node_name>
       <ms_info>
           <media_server>systemAcop1_ms</media_server>
           <ip_address>10.16.108.150</ip_address>
       </ms_info>
   </tpa_to_ms>
   <tpa_to_ms>
       <node_name>systemB-01</node_name>
       <ms_info>
           <media_server>systemAcop2_ms</media_server>
           <ip_address>10.16.108.63</ip_address>
       </ms_info>
   </tpa_to_ms>
   <tpa_to_ms>
       <node_name>systemB-02</node_name>
       <ms_info>
           <media_server>systemAcop1_ms</media_server>
           <ip_address>10.16.108.150</ip_address>
       </ms_info>
   </tpa_to_ms>
   <tpa_to_ms>
       <node_name>systemB-02</node_name>
       <ms_info>
           <media_server>systemAcop2_ms</media_server>
           <ip_address>10.16.108.63</ip_address>
       </ms_info>
   </tpa_to_ms>
</dscConfigFabrics>