Private IP Addresses - 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

Teradata deploys a default VNet with three subnets, but also provides the option to use an existing VNet in the same region.

If you choose to use your company’s own VNet, follow these guidelines:
  • Define three different subnets: one for Teradata and two for BYNET® 0 and 1.
  • Each subnet must have enough available IPs for each Teradata node. For example, an eight-node system requires eight IPs for subnet 1, eight IPs for subnet 2, and eight IPs for subnet 3.
  • Only subnet 1 must be able to talk to external Teradata or third-party components; subnet 2 and subnet 3 (BYNET subnets) are for local traffic only.
  • Use a unique address space for each subnet; do not overlap subnets.
  • Only TPA (database) nodes require one IP from each subnet. Other Teradata components, such as Viewpoint, require one IP per VM in subnet 1.