Make sure that you review thesupported and unsupported featuresin
VPC networks with the RDMA network profile. If you attempt to
configure unsupported features, Google Cloud returns an error.
Create a network with the RDMA network profile
To create a VPC network with the RDMA network profile, do the
following.
Console
In the Google Cloud console, go to theVPC networkspage.
In theMaximum transmission unit (MTU)field, select8896.
SelectConfigure network profileand do the following:
In theZonefield, select the zone of the network profile that
you want to use.
The VPC network that you create is constrained to
this zone, which means that you can only create resources in the
network in this zone.
Select the RDMA network profile for the zone that you selected
previously, such aseurope-west1-b-vpc-roce.
To view the set of supported features for the network profile that
you selected, clickPreview network profile features.
In theNew subnetsection, specify the following configuration
parameters for a subnet:
In theNamefield, enter a name for the subnet.
In theRegionfield, select the region in which to create the
subnet. This region must correspond to the zone of the network
profile that you configured. For example, if you configured the
network profile foreurope-west1-b, then you must create the subnet
ineurope-west1.
If you select a range that is not an RFC 1918 address, confirm that
the range doesn't conflict with an existing configuration. For more
information, seeIPv4 subnet
ranges.
ClickDone.
To add more subnets, clickAdd subnetand repeat the previous steps.
You can alsoadd more subnetsto the network after you
have created the network.
NETWORK_PROFILE: the zone-specific name of the
network profile, such aseurope-west1-b-vpc-roce
The RDMA network profile isn't available in all zones. To view the
zone-specific instances of the network profile that are available,
follow the instructions tolist network profiles.
NETWORK: the name of the VPC network
that contains the new subnet
PRIMARY_RANGE: the primary IPv4 range for the new
subnet, in CIDR notation. For more information, seeIPv4 subnet ranges.
REGION: the Google Cloud region in which the
new subnet is created. This must correspond to the zone of the network
profile that you configured. For example, if you configured the
network profile in theeurope-west1-bzone by using the network
profile namedeurope-west1-b-vpc-roce, then you must create the
subnet in theeurope-west1region.
API
To create the network, make aPOSTrequest to thenetworks.insertmethodand specify thenetworkProfileproperty.
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/global/networks
{
"autoCreateSubnetworks": false,
"name": "NETWORK",
"networkProfile": "NETWORK_PROFILE"
}
Replace the following:
PROJECT_ID: the ID of the project where the
VPC network is created
NETWORK: a name for the VPC network
NETWORK_PROFILE: the zone-specific name of the
network profile, such aseurope-west1-b-vpc-roce
The RDMA network profile isn't available in all zones. To view the
zone-specific instances of the network profile that are available,
follow the instructions tolist network profiles.
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/subnetworks
{
"ipCidrRange": "IP_RANGE",
"network": "NETWORK_URL",
"name": "SUBNET"
}
Replace the following:
PROJECT_ID: the ID of the project that contains the
VPC network to modify
REGION: the name of the Google Cloud region where
the subnet is added. This region must correspond to the zone of the network
profile that you configured. For example, if you configured the
network profile in theeurope-west1-bzone by using the network
profile namedeurope-west1-b-vpc-roce, then you must create the
subnet in theeurope-west1region.
IP_RANGE: the primary IPv4 address range for the subnet.
For more information, seeIPv4 subnet ranges.
NETWORK_URL: the URL of the VPC network
where you're adding the subnet
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Create a VPC network for RDMA NICs\n==================================\n\nThis page describes how to create a VPC network with the\nRDMA network profile provided by Google Cloud.\n\nYou only need to configure a network profile if you want to run workloads\nthat require `MRDMA` NICs as described in [RDMA network profile overview](/vpc/docs/rdma-network-profiles).\nOtherwise, [create a regular VPC network](/vpc/docs/create-modify-vpc-networks)\nwithout a network profile.\n\nBefore you begin\n----------------\n\nMake sure that you review the\n[supported and unsupported features](/vpc/docs/rdma-network-profiles#supported-features) in\nVPC networks with the RDMA network profile. If you attempt to\nconfigure unsupported features, Google Cloud returns an error.\n\nCreate a network with the RDMA network profile\n----------------------------------------------\n\nTo create a VPC network with the RDMA network profile, do the\nfollowing. \n\n### Console\n\n1. In the Google Cloud console, go to the **VPC networks** page.\n\n\n [Go to VPC networks](https://console.cloud.google.com/networking/networks/list)\n\n \u003cbr /\u003e\n\n2. Click **Create VPC network**.\n\n3. In the **Name** field, enter a name for the network.\n\n4. In the **Maximum transmission unit (MTU)** field, select `8896`.\n\n5. Select **Configure network profile** and do the following:\n\n 1. In the **Zone** field, select the zone of the network profile that you want to use. The VPC network that you create is constrained to this zone, which means that you can only create resources in the network in this zone.\n 2. Select the RDMA network profile for the zone that you selected previously, such as `europe-west1-b-vpc-roce`.\n 3. To view the set of supported features for the network profile that you selected, click **Preview network profile features**.\n6. In the **New subnet** section, specify the following configuration\n parameters for a subnet:\n\n 1. In the **Name** field, enter a name for the subnet.\n 2. In the **Region** field, select the region in which to create the subnet. This region must correspond to the zone of the network profile that you configured. For example, if you configured the network profile for `europe-west1-b`, then you must create the subnet in `europe-west1`.\n 3. Enter an **IPv4 range** . This range is the [primary IPv4\n range](/vpc/docs/vpc#vpc_networks_and_subnets) for the subnet.\n\n If you select a range that is not an RFC 1918 address, confirm that\n the range doesn't conflict with an existing configuration. For more\n information, see [IPv4 subnet\n ranges](/vpc/docs/subnets#ipv4-ranges).\n 4. Click **Done**.\n\n7. To add more subnets, click **Add subnet** and repeat the previous steps.\n You can also [add more subnets](/vpc/docs/create-modify-vpc-networks#add-subnets) to the network after you\n have created the network.\n\n8. Click **Create**.\n\n### gcloud\n\n1. To create the network, use the [`gcloud compute networks create` command](/sdk/gcloud/reference/compute/networks/create)\n and specify the `--network-profile` flag.\n\n ```\n gcloud compute networks create NETWORK \\\n --subnet-mode=custom \\\n --network-profile=NETWORK_PROFILE\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eNETWORK\u003c/var\u003e: a name for the VPC network\n - \u003cvar translate=\"no\"\u003eNETWORK_PROFILE\u003c/var\u003e: the zone-specific name of the\n network profile, such as `europe-west1-b-vpc-roce`\n\n The RDMA network profile isn't available in all zones. To view the\n zone-specific instances of the network profile that are available,\n follow the instructions to\n [list network profiles](/vpc/docs/view-network-profiles#list_network_profiles).\n2. To add subnets, use the [`gcloud compute networks subnets create` command](/sdk/gcloud/reference/compute/networks/subnets/create).\n\n ```\n gcloud compute networks subnets create SUBNET \\\n --network=NETWORK \\\n --range=PRIMARY_RANGE \\\n --region=REGION\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eSUBNET\u003c/var\u003e: a name for the new subnet\n - \u003cvar translate=\"no\"\u003eNETWORK\u003c/var\u003e: the name of the VPC network that contains the new subnet\n - \u003cvar translate=\"no\"\u003ePRIMARY_RANGE\u003c/var\u003e: the primary IPv4 range for the new subnet, in CIDR notation. For more information, see [IPv4 subnet ranges](/vpc/docs/subnets#ipv4-ranges).\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the Google Cloud region in which the new subnet is created. This must correspond to the zone of the network profile that you configured. For example, if you configured the network profile in the `europe-west1-b` zone by using the network profile named `europe-west1-b-vpc-roce`, then you must create the subnet in the `europe-west1` region.\n\n### API\n\n1. To create the network, make a `POST` request to the\n [`networks.insert` method](/compute/docs/reference/rest/v1/networks/insert)\n and specify the `networkProfile` property.\n\n ```\n POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/global/networks\n {\n \"autoCreateSubnetworks\": false,\n \"name\": \"NETWORK\",\n \"networkProfile\": \"NETWORK_PROFILE\"\n }\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project where the VPC network is created\n - \u003cvar translate=\"no\"\u003eNETWORK\u003c/var\u003e: a name for the VPC network\n - \u003cvar translate=\"no\"\u003eNETWORK_PROFILE\u003c/var\u003e: the zone-specific name of the\n network profile, such as `europe-west1-b-vpc-roce`\n\n The RDMA network profile isn't available in all zones. To view the\n zone-specific instances of the network profile that are available,\n follow the instructions to\n [list network profiles](/vpc/docs/view-network-profiles#list_network_profiles).\n2. To add subnets, make a `POST` request to the\n [`subnetworks.insert` method](/compute/docs/reference/rest/v1/subnetworks/insert).\n\n ```\n POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/subnetworks\n {\n \"ipCidrRange\": \"IP_RANGE\",\n \"network\": \"NETWORK_URL\",\n \"name\": \"SUBNET\"\n }\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the project that contains the VPC network to modify\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the name of the Google Cloud region where the subnet is added. This region must correspond to the zone of the network profile that you configured. For example, if you configured the network profile in the `europe-west1-b` zone by using the network profile named `europe-west1-b-vpc-roce`, then you must create the subnet in the `europe-west1` region.\n - \u003cvar translate=\"no\"\u003eIP_RANGE\u003c/var\u003e: the primary IPv4 address range for the subnet. For more information, see [IPv4 subnet ranges](/vpc/docs/subnets#ipv4-ranges).\n - \u003cvar translate=\"no\"\u003eNETWORK_URL\u003c/var\u003e: the URL of the VPC network where you're adding the subnet\n - \u003cvar translate=\"no\"\u003eSUBNET\u003c/var\u003e: a name for the subnet\n\nWhat's next\n-----------\n\n- [Create VMs in your network](/ai-hypercomputer/docs/create/create-vm)\n- [Get an overview of network profiles](/vpc/docs/network-profiles)\n- [Learn about the RDMA network profile](/vpc/docs/rdma-network-profiles)"]]