The Resolving Connection Warning | Teradata DSA | DSU - 17.00 - Resolving Connection Warning: Adding Source Teradata System - BAR - Data Stream Architecture - Data Stream Utility

Teradata® DSA - DSU Installation, Configuration, and Upgrade Guide

Product
BAR
Data Stream Architecture
Data Stream Utility
Release Number
17.00
Release Date
August 2020
Content Type
Configuration
Installation
Publication ID
B035-3153-129K
Language
English (United States)
When adding a source system in the BAR Setup portlet, you might receive this warning message when you click Apply in the System and Nodes page:

Warning message that appears when the DSU vNode is not able to resolve the SQL Engine / Teradata Database COP entries

This is caused by the DSU vNode not being able to resolve the SQL Engine / Teradata Database COP entries.

To resolve the connection warning, follow these steps to verify that the servers and domains configured in Viewpoint are also configured in the DSU vNode.

  1. SSH into Viewpoint and extract the DNS servers and search domains.
    1. Extract the DNS servers:
      # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config

      Sample output:

      NETCONFIG_DNS_STATIC_SERVERS="153.64.251.200 153.65.8.10"
    2. Extract the DNS search domains:
      # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config

      Sample output:

      NETCONFIG_DNS_STATIC_SEARCHLIST="td.teradata.com teradata.com"
  2. SSH into the DSU vNode, check the DNS servers and search domains in /etc/sysconfig/network/config, and if necessary, add those that are in Viewpoint.
    1. Extract the DNS servers:
      # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config

      Sample output:

      NETCONFIG_DNS_STATIC_SERVERS="153.64.251.200"

      Notice that 153.65.8.10 from Viewpoint is missing.

    2. If necessary, add any missing servers.
      # sed -i "s/^NETCONFIG_DNS_STATIC_SERVERS=.*$/NETCONFIG_DNS_STATIC_SERVERS=\"153.64.251.200 153.65.8.10\"/" /etc/sysconfig/network/config
    3. If you added a server, verify it is now there.
      # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config

      Sample output:

      NETCONFIG_DNS_STATIC_SERVERS="153.64.251.200 153.65.8.10"
    4. Extract the DNS search domains:
      # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config

      Sample output:

      NETCONFIG_DNS_STATIC_SEARCHLIST="labs.teradata.com

      Note that td.teradata.com and teradata.com from Viewpoint are missing.

    5. If necessary, add any missing search domains:
      # sed -i "s/^NETCONFIG_DNS_STATIC_SEARCHLIST=.*$/NETCONFIG_DNS_STATIC_SEARCHLIST=\"labs.teradata.com td.teradata.com teradata.com\"/" /etc/sysconfig/network/config
    6. If you added a search domain, verify it is now there.
      # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config

      Sample output:

      NETCONFIG_DNS_STATIC_SEARCHLIST="labs.teradata.com td.teradata.com teradata.com"
    7. Execute /sbin/netconfig update -f to apply the change at the end.
  3. If the warning message continues, it is because the DNS server doesn't contain any DNS record for the database COP entries. Extract the SQL Engine / Teradata Database COP entries from the hosts file in Viewpoint and append them to the hosts file in the DSU vNode.
    The basic syntax is as follows:

    # grep TeradataSystemNamecop* /etc/hosts | ssh root@DSU_public_ip 'cat >> /etc/hosts'

    For example, if the TeradataSystemName is system1 and the public IP for the DSU vNode is 10.25.23.170, use the following syntax:

    # grep system1cop* /etc/hosts | ssh root@10.25.23.170 'cat >> /etc/hosts'