Enabling Elasticity, Storage Expansion, and Node Failure Recovery

Enabling Elasticity, Storage Expansion, and Node Failure Recovery - Teradata Vantage for Azure

Teradata Vantage™ on Azure (DIY) Installation and Administration Guide

Product

Teradata Vantage on Azure

Release Number

7.5

Published

July 2019

Language

English (United States)

Last Update

2019-07-15

dita:mapPath

gjt1546881969307.ditamap

dita:ditavalPath

osc1546883696317.ditaval

dita:id

B035-2810

lifecycle

Product Category

Cloud

Enabling node failure recovery might result in losing diagnostic information while a failed node is stopped.

Create a service principal.
From the Azure portal, note the private IP and either the public IP or private DNS of the Vantage VM.
Log on to the VM using the authentication type you chose when deploying the VM.
Switch to the root user environment.
```
# sudo su -
```
Run the following command without arguments.
```
# tdc-feature-init
```
Enter the following information at the prompts:
- client ID (application ID)
- secret key (authentication key)
- tenant ID (Active Directory ID)
- subscription ID
If successful, the output displays Credentials validation succeeded.
Service principal details are written to /etc/opt/teradata/tdconfig/service_principal_config.json.
[Optional] Check the following directories:
- /var/log/boot.log (information)
- /var/log/messages (messages)
- /var/log/NFR/tdc-nodestart.log (node failure errors)