If using virtual IP addresses to communicate between data sources due to Network Address Translation (NAT), AWS private links, port forwarding, and so on, QueryGrid must know these virtual IPs exist so they can be used to establish connectivity. To create this communication, each node that has a virtual IP address must have a text file containing the value of that virtual IP.
You can use virtual IP addresses on data source nodes, bridge nodes, or both. However, to reduce the number of virtual IP addresses that need to be configured, Teradata recommends using virtual IP addresses only on bridge nodes.
Using a Teradata-to-Hadoop QueryGrid link configured with NAT as an example, perform the following steps to configure the Virtual IP:
- On each node with a virtual IP, log on and go to the following directory:/etc/opt/teradata/tdqg/node
- In the directory, create a text file called virtual_ips.
- Using one virtual IP address per line, populate the text file with the virtual IP addresses for that node.The virtual IP addresses must be a valid IPV4 or IPV6 address. Each virtual IP entry is associated with a separate interface name which is reported to the QueryGrid Manager and are represented as vip followed by a number. These generated interface names are based on the order of the addresses listed in the file. In the following example, the IP address interface names are reported as vip0 and vip1:
fe80::250:56ff:fea5:67d9 10.20.255.100For the target system to successfully communicate with this virtual IP configured system, create a new network configuration with the virtual IP interface name and use this network configuration in the link configuration. If both the source and target systems are configured with NAT, the target system nodes also require similar configuration.
- Save the file.
- Restart the node:service tdqg-node restart
During QueryGrid operations, the IP address in each line of the file are read, validated, and used as virtual IP addresses. If the file does not exist in the /etc/opt/teradata/tdqg/node directory, a file not present message is logged in /var/opt/teradata/tdqg/node/version/logs/ tdqg-node.log.
- After restart, verify in Viewpoint that all nodes in the system show a status of ONLINE.
- Select View Node Details on each node to verify the correct vip interface names are listed in the Network Interfaces section.
For examples on configuring virtual IP addresses, log on to https://support.teradata.com and search for KB0013958.