# Vertex AI Vector Search: subnet must belong to the VPC, watch CIDR conflicts (deployment_troubleshooting)

## TL;DR

[Vector Search load-testing framework troubleshooting]: 'Subnetwork X is not valid for Network Y' means the subnet isnt in the VPC you named, check VPC_NETWORK_NAME. 'Conflicting IP cidr range' means a duplicate MASTER_IPV4_CIDR_BLOCK, use a different one per deployment. 'Failed to create Vector Search index' means check the GCS bucket and path, confirm the Vertex AI API is enabled, and check permissions.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

PSC address errors about resource.network mean you should only specify subnetwork, not network.

Context: Vector Search load-testing framework troubleshooting: Subnetwork X is not valid for Network Y means the subnet specified does not belong to the VPC named in VPC_NETWORK_NAME. Conflicting IP cidr range means a duplicate MASTER_IPV4_CIDR_BLOCK in the same VPC, use a different block per deployment. Failed to create Vector Search index means check the Cloud Storage bucket and path, confirm the Vertex AI API is enabled, and check permissions. Invalid value for field resource.network on PSC addresses means only specify subnetwork, not network.