Configuring or Testing Teradata ServiceConnect - Teradata Software for Azure

Teradata Vantage™ on Azure (DIY) Installation and Administration Guide
Product
Teradata Vantage on Azure
Release Number
5.01
Published
July 2018
Language
English (United States)
Last Update
2018-07-18
dita:mapPath
kmk1523992471627.ditamap
dita:ditavalPath
TeradataAzure_PubCloud_5.01_5.01.01.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud
To configure a portlet on a Viewpoint VM, you must know the admin password for the Viewpoint portal. Obtaining that password is part of configuring Teradata Viewpoint.

You must have a site ID to configure or test Teradata ServiceConnect.

[Enterprise, Advanced, Base tiers only] Teradata ServiceConnect allows Teradata Customer Support to connect to your site. Use the Server Management portlet in Teradata Viewpoint to configure ServiceConnect.
  1. Open a Teradata Customer Support incident with a synopsis of Validation Request for Teradata Server Management on Azure Teradata Configuration. Teradata Customer Support obtains permission to access your Azure configuration, confirms that connectivity is functioning, and closes the incident.
    This process can take up to five days.
  2. From the Azure portal, note the private IP address of the first CMIC.
  3. From your browser, display the Viewpoint portal logon screen. 
    http://public-DNS/c
    where: public-DNS is the DNS host name of the Viewpoint VM.
  4. Log in to the Viewpoint portal using administrative credentials.
  5. From the Teradata Viewpoint portal page, click in the top right corner of the page.
  6. In the Viewpoint Administration menu, select Server Management.
  7. In the SiteIDs header, click to add a site ID. The site ID is the one you specified when deploying the software or configuring the CMICs.
  8. In the Configure list, click General.
  9. In the Details pane, enter the site ID and the host ID. The host ID is the private IP address of the first CMIC (if multiple CMICs were deployed).
  10. In the Login pane, enter credentials as follows:
    • At Name, enter rest.
    • At Password, enter the Server Management REST password you specified when deploying the software or configuring the CMICs.
  11. Click Test. If the test is successful, appears. If one of the entries is incorrect, a detailed error message appears.
  12. Click Apply.
  13. From the Configure list, click ServiceConnect.
  14. Log in to Teradata ServiceConnect. The Teradata ServiceConnect details appear. If the system was previously set up with a site ID, the SiteID box is populated.
  15. Do one of the following:
    ServiceConnect Description
    If ServiceConnect has not been configured 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 is tested as part of the process so there is no need to click Test Connection afterwards.
    If ServiceConnect is configured Click Test Connection.

    An Asset Baseline and Alert Escalation Test is run.

    • 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.
  16. [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 ensure the connection is valid.

    3. In the Port box, type the port number for the HTTP proxy.
    4. If credential authentication is required, 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 ensure the connection is valid.

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