Configure COP Entries | Teradata Vantage on AWS (DIY) - 2.2 - Configuring COP Entries - Teradata Vantage on AWS

Teradata Vantageā„¢ on AWS (DIY) Installation and Administration Guide

Product
Teradata Vantage on AWS
Release Number
2.2
Release Date
May 2021
Content Type
Administration
Configuration
Installation
Publication ID
B035-2800-041K
Language
English (United States)
If you enable Scale Out/In at the time of deployment, three extra IP addresses are provisioned and assigned on each node, and then redistributed during scaling out or scaling in. No new COP IP addresses are allocated for scaling out and no COP IP addresses are removed for scaling in. Client machines can use the same group of COP entries to connect to the scaled system. In other words, scaling out or scaling in is transparent on client machines that have correctly configured COP entries.
  1. If you did not enable Scale Out/In at the time of deployment, enter the following command to allocate enough COP entries to support the number of nodes on the system:
    # tdc-network-copentries --allocate nodecount
    where nodecount is the number of nodes on the system after scaling out.
    The hosts file on all the TPA nodes is updated.
  2. Type # tdc-network-copentries to display the COP entries in the correct order for the system, as shown in the following example:
    172.31.61.41   mysyscop1
    172.31.61.49   mysyscop2
    172.31.61.77   mysyscop3
    172.31.61.19   mysyscop4
    172.31.61.114  mysyscop5
    172.31.61.51   mysyscop6
    172.31.61.34   mysyscop7
    172.31.61.82   mysyscop8
  3. Assign the COP entries on your client machine.