Deploying Teradata Server Management from a Solution Template
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 again so you can continue where you left off.
For information on taking down an Azure VM, see Stop, Deallocate, or Delete a VM in Azure.
- Log in to Azure Marketplace portal using your user name and password.
- Click located in the upper left and search for Teradata.A list of Teradata products appears under the Results pane.
- Select Teradata Server Management.
- 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.Note: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.
- Click OK.
- Click the Server Management blade.
Parameter Name Action Site ID 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 system name prefix Enter a prefix for all Server Management VMs. Server Management admin password Enter the Server Management Administrative password, using 6 to 32 alphanumeric characters. Confirm admin password Enter the password again to confirm. Server Management REST password Enter the Server Management REST password, using 6 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. You must deploy a minimum of two CMICs for high availability. VM Size To change the size, do the following:
- Click to display a list of VM sizes for the storage type you want.
- Click to highlight the size you want.
- Click Select.
The storage size is per node. For more information, see Supporting Software Storage.
- Click OK.
- 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 for the public subnet. The template creates a new public subnet in the selected VNet using this CIDR address. For more information, see VNets.
Check to ensure the CIDR address you enter is not being used by existing subnets in the same VNet by going to the Azure portal.
- Click the Summary blade, review the summary, and click OK.
- To monitor the VM creation progress, do the following from the Azure portal.
- 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.
- From the left panel, click the Resource groups blade.
- Under the Name column, select a resource.
- Under Settings, click Deployments.
- 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.
- 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.
- Under Operation details, when the STATUS column displays OK, select the resource.The PROVISIONING STATE displays Succeeded.
- Click to see notifications to determine if the deployment has started.
- [Optional] To use public IP addresses, do the following after the VMs are created.
- Create the public IP addresses.For more information, see https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-public-ip-address.
- Adjust the NSG rules to accept connections using public IP addresses.The solution template defines an NSG for each software product VM.
- Create the public IP addresses.