During the deployment process, this template creates one NSG for Teradata Server Management. All ports to the NSG automatically open after completing this procedure.
- Log in to the Azure Marketplace and search for Teradata Server Management.
- Select Teradata Server Management, then click .
- In the listing, click Create.
- 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.
- Click OK.
- 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. VM Size
- Click to display a list of VM sizes for the storage type you want.
- Highlight the size you want, then click Select.
Storage size is per node.
- 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 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.
- Click OK.
- 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 and assign these addresses to a VM.
- Adjust the NSG rules to accept connections using public IP addresses.The solution template defines an NSG for each software product VM.