Configure Network Fabric | Teradata Data Mover - Configuring a Network Fabric - Teradata Data Mover

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

Teradata Data Mover
Release Number
November 30, 2021
English (United States)
Last Update
Product Category
Analytical Ecosystem
Data Mover provides the dsa_configfabric script as part of the installation package to make the fabric configuration process faster and easier. The script generates two XML files that contain the source and target system fabric definitions. The script performs the following tasks:
  • Identifies all the nodes and media servers defined on the source and target systems
  • Connects to each TPA node on the source or target system
  • Pings each media server from those nodes using different networking interfaces available on each media server. The script uses the following criteria when selecting an interface:
    • If bynet(s) respond, the script selects the bynet with the highest tailing number (for instance, if both bynet1 and bynet0 respond, bynet1 is selected).

      This is only true if the selected interface is not excluded from the media server definition within the DSC configuration.

    • If bynet(s) do not respond, a list of interface options are displayed. The interfaces that the script can connect to from the node are colored green, and the ones that did not respond are colored red.
    • The script automatically selects a network interface when one has been previously configured for another node in the same system.

      For example: Consider having two nodes on the same system, N1 and N2, that need to be configured with a media server on the target system (MS2). If you select network interface EthX on MS2 for connection to N1, then EthX will also be chosen for the N2 to MS2 connection. This is only true if N2 can communicate with that interface on MS2.

  1. Before running the configuration script, make sure that all interfaces that will be part of the fabric are available in the DSC media server configuration.
  2. [Optional] Use one of the following two methods if interfaces are missing from the DSC configuration:
    Method Description
    Manually export, add interfaces, and reconfigure each media server
    1. Export the media server configuration:

      dsc export_config -t MEDIA_SERVER -n media_server_name -f media_server_XML_config_filename

    2. Edit the media_server_XML_config_filename and add the missing interfaces.
    3. Save the changes:

      dsc config_media_servers -f media_server_XML_config_filename

    Reset all the media server settings registered with DSC Run the following command:

    dsc config_media_servers -f media_server_XML_config_filename

    Using the hardware upgrade script resets the settings for all the DSCs using that media server. Use with caution.
    The media server configuration should look similar to the example below after the hardware resets.
    Media Server Name   Port    Pool Shared Pipes   IP Address(es)   NetMask(s)     
    server1_ms         15401   100                 10.0.***.***  
    server2_ms         15401   100                 10.1.***.***  
  3. Run the script to generate the fabric for the source and target systems.
    Use the following help command output for the list of available script parameters:
    dsa_configfabric -s source_TPA -t target_TPA -b source_base_name -c target_base_name -p source_system_root_password -q target_system_root_password -r ping_timeoout
        -s: Is the hostname for one of the source TPA Nodes were we can connect to from DSC server
        -t: Is the hostname for one of the target TPA Nodes were we can connect to from DSC server
        -b: Is the base-name for the source system. This is the name defined before the cop entries (Example: If cop enteries are kiwicop1 and kiwicop2 then the base name is kiwi)
        -c: Is the base-name for the target system. This is the name defined before the cop entries (Example: If cop enteries are kiwicop1 and kiwicop2 then the base name is kiwi)
        -p: Is the password for -s option. (optional)
        -q: Is the password for -t option. (optional)
        -r: Is the number of seconds we are going to wait before timing out ping command. default is 1 (optional)
        This script must be executed from the DSC server. DSC should be running.
  4. Add the generated DSA fabric configuration files to the DSC configuration:
    dsc config_fabrics -f ./output/xml_generated_file_name.xml