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

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

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
pgy1512683352051.ditamap
dita:ditavalPath
DM_16_20_08_ICUCust_AsterIncluded.ditaval
dita:id
B035-4102
lifecycle
previous
Product Category
Analytical Ecosystem

If you use your media server for multiple Teradata systems, configuring a network fabric using the DSA config_fabrics command to segregate traffic can be more effective than using BAR NC logical netmask. By configuring a network fabric for a system, the traffic from each node is configured to use the best interface for the data transfer when multiple interfaces are available.

A network fabric defines the data path between each node and the media server in a Teradata system using the most efficient interface when transferring data. In a Data Mover-DSA configuration, media servers are installed on target system nodes. 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® Data Stream Architecture 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>
If available in your environment, you can use the DSA portlet to configure network fabrics instead of using the DSC command line and XML files. The DSA portlet version must match the DSC version. For more information, see the Teradata® Data Stream Utility Installation, Configuration, and Upgrade Guide, B035-3153.