Teradata Server Management Configuration
[Base, Advance, and Enterprise tier users only] To ensure Teradata processes are prepared for the Server Management connection after launching a Server Management instance, open a TaYS incident with a synopsis of Validation Request for Teradata Server Management on AWS Teradata Configuration. After Teradata Customer Support obtains permission to access your AWS configuration and confirms the connectivity is functioning, they will close the incident. This process may take up to five days to complete.
[All users] If you launched one or more instances of Server Management using CloudFormation, the CMICs are automatically configured to communicate with each other. However, the newly launched CMICs must be configured manually to manage the existing database and application nodes in the Teradata ecosystem. Configure CMICs, either interactively or in batch mode, using the configuration file.
When configuring the CMICs for Teradata Database nodes in an MPP instance, you must use the secondary private IP address of each database node. For a single-node system, use the primary private IP address.
The time zone for the Teradata Server Management instance is UTC and cannot be changed.
Using the Server Management portlet in Teradata Viewpoint, you must configure the CMICs for alerts, regardless of launch method. You can set alerts for node failures, issues with Teradata software, and many other alert types.
[Base, Advanced, or Enterprise tier users only] You must also configure the CMICs for ServiceConnect regardless of launch method.