Resolving BAR Setup Connection Warnings

Teradata Database on VMware Base, Advanced, Enterprise Tiers Getting Started Guide

brand
Cloud
prodname
Teradata Database on VMware
vrm_release
Deployer 3.01
category
Configuration
Installation
featnum
B035-5958-097K
If you get a Connection to system unsuccessful warning message when adding a Teradata Database system in the BAR Setup portlet, the DSC vNode may not be able to resolve the Teradata Database COP entries. To resolve this issue, you can verify the servers and domains configured in Teradata Viewpoint are also configured in the DSC vNode.
  1. SSH into Teradata 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 DSC vNode to check the DNS servers and search domains, and then add the servers and domains that are in Teradata 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 if 153.65.8.10 is missing from Teradata Viewpoint.

    2. 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

      Notice if td.teradata.com and teradata.com are missing from Teradata Viewpoint.

    5. 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. Apply the change. /sbin/netconfig update -f
    If the warning message continues, the DNS server may not contain any DNS record for the Teradata Database COP entries.
  3. Extract the Teradata Database COP entries from the hosts file in Teradata Viewpoint and append them to the hosts file in the DSC vNode using the following syntax: # grep TeradataSystemNamecop* /etc/hosts | ssh root@DSC_public_ip 'cat >> /etc/hosts'

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

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