Configuring ServiceConnect for Server Management

[Base, Advance, and Enterprise tier users only] Use the Server Management portlet in Teradata Viewpoint to configure ServiceConnect.
  1. From your browser, display the Viewpoint portal log on screen.
    http://public-DNS/c
    where: public-DNS is the DNS host name of the Viewpoint instance.
  2. Log on to the Viewpoint portal.
    The user name is admin and the password is the Viewpoint instance ID.
    You are now ready to configure ServiceConnect.
  3. From the Teradata Viewpoint portal page, click in the top right corner of the page.
  4. In the Viewpoint Administration menu, select Server Management.
  5. In the SiteIDs header, click to add a site ID.
  6. In the Configure list, click General.
  7. In the Details pane, enter the names of the Site ID and the Host ID.
    The site ID is the one you specified when configuring the CMIC instance. The host ID is the private IP address of the first CMIC instance (if multiple CMICs were deployed).
  8. In the Login pane, enter credentials as follows:
    • At Name, enter rest.
    • At Password, enter the Server Management REST password you specified when configuring the CMIC instance.
  9. Click Test.
    If the test is successful, appears. If one of the entries is incorrect, a detailed error message appears.
  10. Click Apply.
  11. From the Configure list, click ServiceConnect.
  12. 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.
  13. Do one of the following:
    ServiceConnect Description
    If ServiceConnect has not been 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 SiteIDs, 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
    1. 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.
  14. [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/*.pac file path.

    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.
  15. Click Apply.

results matching ""

    No results matching ""