Deploy Server Management from a Template | Teradata Vantage on Azure (DIY) - Deploying Server Management from a Solution Template - Teradata Vantage on Azure

Teradata Vantageā„¢ on Azure (DIY) Installation and Administration Guide

Teradata Vantage on Azure
Release Number
March 2021
English (United States)
Last Update
Product Category
  • You must log into the Azure portal using an account with sufficient permissions in the Azure subscription and be assigned the Contributor role at the subscription level. See Azure Documentation Center.
  • You might need to increase Azure service limits. See Azure Service Limits.
Deploying Server Management from a solution template creates a new Azure resource group and connects the Server Management VMs to an existing subnet in the same VNet as the Vantage VM and the software application VMs.

During the deployment process, this template creates one NSG for Teradata Server Management. All ports to the NSG automatically open after completing this procedure.

  1. Log in to the Azure Marketplace and search for Teradata Server Management.
  2. Select Teradata Server Management, then click Get it now > Continue.
  3. In the listing, click Create.
  4. Click the Basics blade to configure basic settings.
    Parameter Name Action
    User name Enter the operating system admin name used to log in.
    Authentication type Select an authentication method.
    For security reasons, we recommend an SSH public key.
    Enter a password of at least 12 characters, using at least 1 lower case character, 1 upper case character, 1 number, and 1 special character. Enter the password again to confirm.
    SSH public key
    Copy and paste an Open SSH public key which can be generated with tools such as PuTTY or SecureCRT.
    Subscription Select an Azure subscription.
    Resource group Select one of the following:
    • Create new and enter a name for the resource group.
    • Use existing and select an empty existing resource group.
    Location Select a region where you want to deploy the solution and where all resources will be created.
  5. Click OK.
  6. Click the Server Management blade to configure the settings.
    Parameter Name Action
    Site ID[Enterprise, Advanced, Base tiers only] String that identifies this Teradata deployment for Teradata Customer Support (AZRTDB followed by up to 9 numbers). If you do not have the site ID, you can continue without it, and add it later.
    Server Management admin password Enter the Server Management Administrative password, using 12 to 15 characters starting with a letter. It can consist of only letters and numbers.
    Confirm admin password Enter the password again to confirm.
    Server Management REST password Enter the Server Management REST password, using 12 to 15 characters starting with a letter. It can consist of only letters and numbers.
    Confirm REST password Enter the password again to confirm.
    Server Management VM Count Number of Server Management VMs (CMICs) to deploy. Minimum for high availability: 3.
    If you deploy one CMIC, you cannot add additional CMIC VMs later. You will have to remove the first one, then redeploy a minimum of three.
    VM Size
    1. Click "" to display a list of VM sizes for the storage type you want.
    2. Highlight the size you want, then click Select.

    Storage size is per node.

  7. Click OK.
  8. Click the Network Settings blade to configure the virtual network.
    Parameter Name   Action
    Virtual network Existing virtual network Select the existing virtual network containing the Vantage VM.

    Although you are not prevented from creating a new VNet, the purpose of this procedure is to deploy the VMs on the same VNet as the Vantage VM and all software application VMs, such as Teradata Viewpoint, and so on.

    Subnets VM subnet name Select the existing VM subnet named vmsubnet.

    The Vantage and software application VMs will be attached to this private subnet.

    Allow remote SSH access from (CIDR block) Enter a CIDR block of IP addresses from which remote SSH connections will be accepted.
  9. Click OK.
  10. Click the Summary blade, review the summary, and click OK.
  11. Click the Buy blade, review the terms of use and privacy policy, and click Purchase.
    This process can take 5 to 15 minutes depending on your configuration and the availability of resources in your region.
    Trying to SSH into the VM might cause the creation of the VM to fail. Do not try to SSH into the VM until either you get confirmation the VM has been created or you receive a failure notification.
  12. To monitor the VM creation progress, do the following from the Azure portal.
    1. Click "" to see notifications to determine if the deployment has started.
      Notifications send alerts only if you have set them prior to starting the deployment.
    2. From the left panel, click the Resource groups blade.
    3. Under the Name column, select a resource.
    4. Under Settings, click Deployments.
    5. Select any of the resources and look at the pane to the right to see if they are being deployed.
      The deployment is not complete until all VMs in the cluster are provisioned and the automatic process of configuring the database has finished.
      Under Operation details, a blue status symbol appears in the first column next to each resource to indicate the deployment process is continuing.
    6. Click "" located at the top of the right pane to refresh the pane.
      Under Operation details, the blue status symbol changes to a green check mark in the first column next to each resource to indicate the deployment process has finished.
    7. Under Operation details, when the STATUS column displays OK, select the resource.
      The PROVISIONING STATE displays Succeeded.
  13. [Optional] To use public IP addresses, do the following after the VMs are created.
    1. Create the public IP addresses and assign these addresses to a VM.
    2. Adjust the NSG rules to accept connections using public IP addresses.
      The solution template defines an NSG for each software product VM.
PostrequisiteComplete the applicable procedures under Server Management Configuration.