Configuring the CMICs in Batch Mode - Teradata Software for AWS

Teradata Vantage™ on AWS (DIY) Installation and Administration Guide
Product
Teradata Vantage on AWS
Release Number
5.08
Published
November 2018
Language
English (United States)
Last Update
2018-11-07
dita:mapPath
upc1519757374969.ditamap
dita:ditavalPath
TeradataAWS_PubCloud_5.08.ditaval
dita:id
B035-2800
lifecycle
previous
Product Category
Cloud
Depending on how you deployed your instances, use the following table to determine whether you need to complete this procedure.
Ecosystem AWS CloudFormation (without Ecosystem)
No Yes
Alternatively, you can configure the CMIC interactively.

You must have the Server Management administrative and Server Management REST passwords to complete this procedure in batch mode. If you do not have these passwords, configure the CMICs interactively.

When configuring CMIC in batch mode, you must provide information in JSON, which requires data to be entered in an exact format. If you experience problems, verify the format is correct.

  1. From the AWS Web Console, note IP information as follows:
    • For CMIC instances, the Public IP address of each
    • For MPP Teradata Database instances, the secondary Private IP address of each database node
    • For single-node Teradata Database instances, the primary Private IP address of each database node
    • For the Teradata Viewpoint instance and other managed instances such as Teradata Data Mover and Teradata Ecosystem Manager, the Private IP address of each instance
  2. From your SSH client console, log on to the first CMIC instance as cmic or ec2-user using the applicable AWS key pair. 
    # ssh -i  private-key-file.pem  cmic@public-IP
    or
    # ssh -i  private-key-file.pem  ec2user@public-IP
  3. Create a JSON config file based on the current CMIC configuration. 
    # sudo /opt/teradata/cmic/bin/cmic-cloud-config -d /tmp/cmic.cfg
  4. Using a text editor, make your changes to the config file, and save it. The cmic.cfg file is in the following format:
    {
  "cmic-metadata-version" : "2.0",
  "cmic-ip-list": "aa.aa.aa.aa bb.bb.bb.bb",
  "dbs-ip-list" : "[zzz.zz.zz.zzz zzz.zz.zz.yyy]",
  "managed-ip-list" : "xxx.xx.xx.yy yyy.yy.yy.yyy",
  "viewpoint-ip" : "xxx.xx.xx.xxx",
  "sm-admin-password" : "",
  "sm-rest-password" : "",
  "siteid" : "AMZTDBnnnnnnnnn"
}
    where:
    • sm-admin-password is the Server Management Administrative password.
    • sm-rest-password is the Server Management REST password.
    • viewpoint-ip is the private IP address of the Viewpoint instance.
    • siteid [Enterprise, Advanced, and Base tiers only] is the Teradata site ID to be used when connecting to Teradata for support.
    • managed-ip-list is the list of private IP addresses of all the managed instances, such as Teradata Data Mover and Teradata Ecosystem Manager, separated by a space.
    • dbs-ip-list is the space-separated list of IP address values as follows:
      • For MPP Teradata Database instances, the secondary private IP address of each database node, enclosed in brackets.
      • For single-node Teradata Database instances, the primary private IP address of the database node, without brackets.
  5. Update the CMIC configuration with the values in the file which completes the updates to the CMIC configuration. 
    # sudo /opt/teradata/cmic/bin/cmic-cloud-config -a /tmp/cfg.json
After completing this procedure, you can configure the Server Management portlet on the Viewpoint server.
Related information