Deploying Teradata Server Management from a Solution Template - 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
You must be logged into the Azure portal with sufficient permissions in the Azure subscription and be assigned the Contributor role. See Azure Documentation Center. In addition, check if Azure service limits need to increase.
This deployment creates a new Azure resource group and connects the Server Management VMs to an existing subnet in the same VNet as the Teradata Database VM and all the software application VMs.

This template creates one NSG for Teradata Server Management during the deployment process. All ports to the NSG are opened automatically after completing this procedure.

To use public IP addresses, you must create them after the VMs are created, then adjust the NSG rules to accept connections using public IP addresses.

If the interface times out while performing the steps in this procedure, return to the previous blade and click OK to continue where you left off.

  1. Log in to the Azure Marketplace.
  2. Click located in the upper left and search the Marketplace for Teradata Server Management. A list of Teradata products appears under the Results pane.
  3. Select Teradata Server Management, and 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, an SSH public key is strongly recommended.
    SSH public key
    Copy and paste an Open SSH public key which can be generated with tools such as PuTTY or SecureCRT.
    Password
    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.
    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: 2.
    If you deploy one CMIC, you cannot add a second one later. You will have to remove the first one, then redeploy two.
    VM Size To change the size, do the following:
    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 Teradata Database 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 Teradata Database 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 Teradata Database 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 may 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. See https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-public-ip-address.
    2. Adjust the NSG rules to accept connections using public IP addresses to allow access. The solution template defines an NSG for each software product VM.
Complete the applicable procedures under Teradata Server Management Configuration.
Related information