Configure ClientHandler Logical Netmask | Teradata Data Mover - Configuring the Logical Netmask for ClientHandler - Teradata Data Mover

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

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
jvt1700556161677.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
pqq1467243714524
Product Category
Analytical Ecosystem
BAR NC supports the configuration of multiple networks and logical netmasks. The following is an example of a BAR NC configuration with multiple network interfaces:
<dscConfigMediaServers xmlns="http://schemas.teradata.com/v2012/DSC">
  <media_server_name>sdt05126_ms</media_server_name>
  <port>15401</port>
  <ip_info>
     <ip_address>39.64.8.1</ip_address>
     <netmask>255.255.255.0</netmask>
  </ip_info>
  <ip_info>
    <ip_address>10.25.188.87</ip_address>
    <netmask>255.255.0.0</netmask>
  </ip_info>
</dscConfigMediaServers>
You can use the DSA portlet to configure netmasks instead of the DSC command line and XML files, if one is available in your environment. The DSA portlet version must match the DSC version.

The steps here are an example of a BAR NC configuration with single network interfaces.

  1. List the media server:
    # dsc list_components -t MEDIA_SERVER
    Data Stream Controller Command Line 16.20.00.00
    Command parameters:
    -type : MEDIA_SERVER
    Connected to DSC version 16.20.00.00
    Listing Components...
    Media Server Name Port Pool Shared Pipes IP Address(es) NetMask(s)
    -------------------------------------------------------------------------------
    sdt05126_ms 15401 100 10.25.188.87 255.255.254.0 
    -------------------------------------------------------------------------------
  2. For each media server export the configuration to an XML file:
    # dsc export_config -t MEDIA_SERVER -n sdt05126_ms -f sdt05126_ms.xml
    Data Stream Controller Command Line 16.20.00.00
    Command parameters:
    -type : MEDIA_SERVER
    -name : sdt05126_ms
    -file : sdt05126_ms.xml
    Connected to DSC version 16.20.00.00
    Exporting Configurations...
    Export config successful!
  3. Edit the exported XML file and set the netmask to the desired value:
    # cat sdt05126_ms.xml
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <dscConfigMediaServers xmlns="http://schemas.teradata.com/v2012/DSC">
        <media_server_name>sdt05126_ms</media_server_name>
        <port>15401</port>
        <pool_shared_pipes>100</pool_shared_pipes>
        <ip_info>
           <ip_address>10.25.188.87</ip_address>
           <netmask>255.255.254.0</netmask>
        </ip_info>
    </dscConfigMediaServers>
    • The example shows the values before editing the netmask to another value.
    • Leave only the IP addresses intended for data transfer in the exported XML file. Remove all other IP addresses, including their surrounding <ip_info> </ip_info> xml tags.
  4. Update the configuration with the new values with dsc config_media_servers:
    # dsc config_media_servers -f sdt05126_ms.xml
    Data Stream Controller Command Line 16.20.00.00
    Command parameters:
    -file : sdt05126_ms.xml
    Connected to DSC version 16.20.00.00
    Saving Media Server...
    Media Server config succeeded for "sdt05126_ms"
  5. List the media servers again to confirm that the netmask value has been changed:
    # dsc list_components -t MEDIA_SERVER
    Data Stream Controller Command Line 16.20.00.00
    Command parameters:
    -type : MEDIA_SERVER
    Connected to DSC version 16.20.00.00
    Media Server Name Port Pool Shared Pipes IP Address(es) NetMask(s)
    Listing Components...
    -------------------------------------------------------------------------------
    sdt05126_ms 15401 100 10.25.188.87 255.255.0.0 
    -------------------------------------------------------------------------------