Public IP Addresses
- If you assign public IP addresses to all nodes in an MPP system, you can use the respective public IP address to connect to any node from an external location.
By default, you can use up to 20 static public IP addresses within a given region associated with a given subscription. If you plan to deploy a system comprising more than 20 nodes, you must first submit a request to increase your networking limits accordingly in order to assign static public IP addresses to all nodes. See Azure Service Limits
- If you assign a public IP address to only one (the first) node in an MPP system, you can use the respective public IP address to connect to the first node from an external location and use the private IPs on the VM subnet to connect with other nodes.
- If you do not assign a public IP address to any nodes in an MPP system, you can deploy a VM in the system's VNet, assign a public IP address to that VM, and then use that VM as a jump box to connect with system nodes from an external location. See SSH Tunneling.
If you want to use public IP addresses when deploying other Teradata software products (Data Mover, Data Stream Controller, Ecosystem Manager, Server Management, or Viewpoint) using a Teradata ecosystem, you must create the public IP addresses after the VM is created.
If you are deploying Teradata software products separately, you can either create a new public IP address or not assign any public IP address to the VM. Instead, you can access the VM using another jump box VM in the same VNet or through a VPN. If using a public IP address, review the NSG rules to lock down access to only known source IP ranges.
If your use case allows for fluctuating public IP addresses, you can use the portal or the PowerShell/CLI script to change the IP address Assignment setting to Dynamic after deployment. Before doing so, however, you must dissociate the public IP addresses from the network interface. If needed, you must also submit a request to increase your networking limits above the default value of 60 for dynamic public IP addresses within a given region associated with a given subscription. See Azure Service Limits.