Configuring or Testing ServiceConnect - Teradata Software for AWS

Teradata Vantageā„¢ on AWS (DIY) Quick Deployment Guide

Product
Teradata Vantage on AWS
Release Number
5.08
Published
November 2018
Language
English (United States)
Last Update
2018-11-07
dita:mapPath
uxv1521735824743.ditamap
dita:ditavalPath
TeradataAWS_PubCloud_5.08.ditaval
dita:id
B035-2801
Product Category
Cloud
You must already have the site ID for your AWS deployment to configure or test Teradata ServiceConnect.
[Base, Advanced, and Enterprise tiers only] Use the Server Management portlet in Teradata Viewpoint to configure ServiceConnect, which allows remote connectivity by Teradata Customer Support.
  1. Open a Teradata Customer Support incident with a synopsis of Validation Request for Teradata Server Management on AWS Teradata Configuration. Teradata Customer Support obtains permission to access your AWS configuration, confirms that connectivity is functioning, and closes the incident.
    This process may take up to five days.
  2. From the AWS Web Console, note the private IP address of the first CMIC instance (if multiple CMICs were deployed).
  3. From your browser, display the Viewpoint portal logon screen. http://viewpoint-public-DNS/c
  4. Log on to the Viewpoint portal. The user name is admin and the password is the Viewpoint instance ID.
  5. From the Teradata Viewpoint portal page, click .
  6. In the Viewpoint Administration menu, select Server Management.
  7. In the SiteIDs header, click to add a site ID.
  8. In the Configure list, click General.
  9. In the Details pane, enter the site ID and host ID. The host ID is the private IP address of the first CMIC instance (if multiple CMICs were deployed).
  10. In the Login pane, enter the credentials.
    • At Name, enter rest.
    • At Password, enter the Server Management REST password.
  11. Click Test and Apply.
  12. From the Configure list, click ServiceConnect.
  13. Log in to Teradata ServiceConnect. If the system was previously set up with a site ID, the SiteID box populates.
  14. Do one of the following:
    ServiceConnect Action
    If ServiceConnect is not configured
    1. Click Create Connection.

      A connection is created, devices are configured, and an alert is generated. If no SM_LOG alert action set is defined, one is created for all times (Core, Evening, Weekend) and includes the log action in the Alert Viewer portlet. If no ALL alert is defined for Server Management, one is created and enabled for all Site IDs, and will send a notification when updates occur.

      After you create a connection, the connection automatically tests as part of the process, so there is no need to click Test Connection.

    If ServiceConnect is configured
    1. Click Test Connection.

      An Asset Baseline and Alert Escalation Test runs.

      • If the connection is successful, verify an email was received.
      • If the Asset Baseline fails, contact Teradata Customer Support.
      • If the Alert Escalation Test fails, ensure all nodes are in an operational state and test the connection again. If it fails a second time, contact Teradata Customer Support.
  15. [Optional] If you require outgoing connections to go through a proxy server, click Advanced options and do the following: If you enable Proxy Auto-Configuration, you cannot enable the HTTP Proxy or SOCKS Proxy. However, you can complete the authentication fields for either if the .pac file points to a proxy server that requires this information. If you have a *.pac file at a known URL, you can configure it, along with any authentication for the HTTP and SOCKS servers, if required.
    Proxy Options Description
    Auto-Configuration
    1. Under Proxy Auto-Configuration, select Enable if you have an automatic proxy configuration script.
    2. In the URL box, type the IP address of your proxy server.

      The format is http://proxy_server_IP_Address/path_to_file.pac.

    HTTP
    1. Under HTTP Proxy, select Enable.
    2. In the Host IP Address box, type the IP address of the HTTP proxy host.

      The IP address must be a valid IPv4 or IPv6 address. If it is IPv4, it is pinged to validate the connection.

    3. In the Port box, type the port number for the HTTP proxy.
    4. If the credentials require authentication, click Authenticate using the following information and type the login credentials.
    SOCKS
    1. Under SOCKS Proxy, select Enable.
    2. In the Host IP Address box, type the name or address of the SOCKS proxy host.

      The IP address must be a valid IPv4 or IPv6 address. If it is IPv4, it is pinged to validate the connection.

    3. In the Port box, type the port number for the SOCKS proxy.
    4. If the credentials require authentication, click Authenticate using the following information and type the login credentials.
  16. Click Apply.