Configuring Teradata QueryGrid Manager

  1. From the AWS Web Console, note the Private IP address of the QueryGrid Manager instance.
  2. From your SSH client console, log on to the QueryGrid Manager instance as ec2-user using the applicable AWS key pair.
    # ssh -i private-key-file ec2-user@private-IP 
    where:
    • The private-key-file is the private key file (.pem) of the AWS key pair specified when launching the instance.
    • The private-IP is the private IP address of the QueryGrid Manager instance.
  3. Switch to the root user environment.
    # sudo su -
  4. Add the user to the QueryGrid Manager user group to prevent permissions errors.
    # sudo usermod -A tdqgm ec2-user
  5. Reset the default viewpoint and support passwords:
    # /opt/teradata/tdqgm/bin/reset-password.sh
  6. [Optional] Change the private IP address to public IP address.
    By default, a QueryGrid Manager instance uses a private IP address, used by QueryGrid-attached nodes and other QueryGrid Manager instances to access it. To use the public IP and DNS instead:
    1. Open the properties file:
      /etc/opt/teradata/tdqgm/tdqgm.properties
    2. Update the following property value to true:
      qgm.cloud.aws.enable.public.address=true
    3. Restart the QueryGrid Manager instance.
  7. If you launched multiple instances of QueryGrid Manager for high availability, you must provide the SSH key for authentication when clustering them.
    Follow the instructions in Teradata QueryGrid Installation and User Guide, using the following option with the join-cluster.sh command:
    -k,--ssh-key-file filename

results matching ""

    No results matching ""