Resolve BAR Setup Connection Warnings | Teradata Vantage on VMware - Resolving BAR Setup Connection Warnings - Teradata Vantage on VMware

Teradata Vantage™ on VMware Developer Tier Getting Started Guide
Product
Teradata Vantage on VMware
Release Number
Deployer 3.04
Published
October 2021
Language
English (United States)
Last Update
2021-10-29
dita:mapPath
wua1545241606155.ditamap
dita:ditavalPath
aby1526581614426.ditaval
dita:id
B035-5938
Product Category
Cloud
If you get a Connection to system unsuccessful warning message when adding a Vantage system in the BAR Setup portlet, the DSC vnode may not be able to resolve the Vantage 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, as in the following example:
      # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config
NETCONFIG_DNS_STATIC_SERVERS="153.64.251.200 153.65.8.10"
    2. Extract the DNS search domains, as in the following example:
      # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config
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, as in the following example:
      # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config
NETCONFIG_DNS_STATIC_SERVERS="153.64.251.200"

      Check 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, as in the following example:
      # grep "NETCONFIG_DNS_STATIC_SERVERS" /etc/sysconfig/network/config
NETCONFIG_DNS_STATIC_SERVERS="153.64.251.200 153.65.8.10"
    4. Extract the DNS search domains, as in the following example:
      # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config
NETCONFIG_DNS_STATIC_SEARCHLIST="labs.teradata.com"

      Check 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, as in the following example:
      # grep "NETCONFIG_DNS_STATIC_SEARCHLIST" /etc/sysconfig/network/config
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 SQL Engine COP entries.
  3. Extract the Vantage COP entries from the hosts file in 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'