Connection Considerations

If you are using VMs in Azure, configure these VMs to reside in the same VNet. When configuring the software, use private IP addresses to connect to these VMs.

If you are using VMs to connect from the Azure public cloud to an on-premises Teradata system, use public IP addresses to connect to the on-premises Teradata system when configuring the software.

You need to use public IP addresses only if you deploy a VM using a public Azure virtual network. If you deploy a VM using a private Azure virtual network, the VMs have private IPs and a VNet connection is required for SSH access.

When deploying a VM, make a note of the IP and DNS addresses of the Teradata Database VM and the IP and DNS addresses of the additional software. Use this information when configuring the additional software VMs. The VM location determines whether to use internal or external addresses when configuring the following software:
  • Teradata Data Mover
  • Teradata Ecosystem Manager
  • Teradata REST Services
  • Teradata Viewpoint

For example, use Teradata Database private IP addresses in Data Mover job XML and Data Mover portlets if all VMs reside in the same VNet. In Data Mover portlets, use the private IP address of the Data Mover VM to connect to a Teradata Database system. If source and target systems reside outside Azure, such as an on-premises system, use the public IP addresses instead.

Note
Only the software listed above can connect to an on-premises system if you have opened the appropriate inbound ports in the corporate firewall on those premises.

results matching ""

    No results matching ""