Internal IP address ranges for TPU Nodes

Important: You can use this document with either the TPU VM or the TPU Node architecture. The two VM architectures are described in System Architecture.

TPU VM architecture

When you use TPU VMs, you SSH directly into the TPU VM.

TPU Node architecture

TPU Nodes run on a peer VPC network that Google manages. When you create a TPU Node, the system automatically creates a peer connection to a VPC network from your project. The peer connection provides access to the TPU Node from your instances, GKE clusters, and other Cloud Platform services that run on the same VPC network.

When you are writing applications to automatically create and manage TPU Nodes, you can reserve allocated IP address ranges to automatically identify open IP address ranges on your VPC network and reserve them to be used for your TPU Nodes.

Note: Cloud TPU VPC Service Controls can provide additional security for your Cloud TPU resources. To learn more about VPC Service Controls, see the VPC Service Controls overview. To learn about the limitations in using Cloud TPU with VPC Service Controls, see the supported products and limitations.

Automatic IP address configuration

When you create a TPU VM or TPU Node using the Google Cloud Platform (GCP) Google Cloud CLI, or the Google Cloud console, you do not need to specify an internal IP address or address range since the IP network address is automatically configured.

Note: Internal TPU IP addresses are only accessible by principals that have access to your project.

Manual IP address configuration

Note: You can only specify an internal IP address range for a TPU Node, not for a TPU VM.

You can also manually specify an internal IP address range for your TPU Node. You can use any valid address in your user-specified network or VPC internal network as long as it does not conflict with other addresses already used on that network.

Manually configured IP address ranges for TPU Nodes must meet the following requirements:

• The IP address range must be from within the internal IP address ranges:

   10.0.0.0        -   10.255.255.255  (10/8 prefix)
   172.16.0.0      -   172.31.255.255  (172.16/12 prefix)
   192.168.0.0     -   192.168.255.255 (192.168/16 prefix)

• Your range must be one of the following formats:

  W.X.Y.Z/N
  W.X.Y.Z

  where:

  • W,X,Y,Z are integers in the range 0-255 with no leading zeros.
  • /N is an optional address range size. If you do not specify a range size Cloud TPU selects the correct range size for your TPU type.

• Your range must have enough addresses to accommodate the size of your TPU type. If you omit the range size, Cloud TPU selects the correct range size for your TPU type. If you must specify a range size, select a range size that provides enough addresses for 1/4th the number of TPU cores in your node with at least 8 addresses at a minimum. For example, if you select a v3-512 TPU type with 512 cores, your range must have a size of /25 to provide 128 addresses for the TPU peer network. For both v3-8 and v3-32 TPU types, you must specify the minimum range size of /29 to provide at least 8 addresses.

• If you must select an address range, select one that does not conflict with another network resource on the network that you are using. For example, if you deploy your Cloud TPU on the "default" network that is created on standard Compute Engine projects, then this network will already have a subnetwork for us-central1 using the 10.128.0.0/20 range and you cannot place any of your subnetworks inside this range. This is true for all other regions.