Deploying Teradata Server Management from a Solution Template

You must be logged into the Azure portal using an account with a sufficient level of permissions in the Azure subscription and be assigned the Contributor role at the subscription level. See the Azure Documentation Center. Also check whether Azure service limits need to be increased. See Azure Service Limits.
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. For information on which ports are opened, see Network Security Groups and Ports.

If you want 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 Azure Marketplace portal using your user name and password.
  2. Click located in the upper left and search for Teradata.
    A list of Teradata products appears under the Results pane.
  3. Select Teradata Server Management.
  4. Click the Basics blade to configure the 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.
    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.
    Parameter Name Action
    Site ID [Enterprise, Advanced, and Base tiers only] Type the site ID to be used when connecting to the Teradata Database. If you do not have the site ID, you can continue without it, and add it later. See Site IDs.
    Server Management admin password Enter the Server Management Administrative password, using 12 to 32 alphanumeric characters.
    Confirm admin password Enter the password again to confirm.
    Server Management REST password Enter the Server Management REST password, using 12 to 32 alphanumeric characters.
    Confirm REST password Enter the password again to confirm.
    Server Management VM Count Enter the number of Server Management VMs (CMICs) you want 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. Click to highlight the size you want.
    3. Click Select.

    The storage size is per node. See Supporting Software VM Sizes.

  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 public 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 the Summary blade, review the summary, and click OK.
  10. Click the Buy blade, review the terms of use and privacy policy, and click Purchase.
    This process can take anywhere between 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.
  11. 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.
  12. [Optional] To use public IP addresses, do the following after the VMs are created.
    1. Create the public IP addresses.
    2. Adjust the NSG rules to accept connections using public IP addresses.
      The solution template defines an NSG for each software product VM.
Complete the applicable procedures under Teradata Server Management Configuration.

results matching ""

    No results matching ""