이 페이지에서는 IP 주소 사용률에 대한 네트워크 분석기 통계에 대해 설명합니다. 모든 통계 유형에 대한 자세한 내용은 통계 그룹 및 유형을 참조하세요.
IP 주소 사용률 통계에는 VM 및 부하 분산기와 같이 IP 주소를 사용하는 구성을 기반으로 계산되는 서브넷 범위의 IP 주소 할당 비율이 표시됩니다. 공유 VPC의 경우 네트워크 분석기는 호스트 프로젝트의 IP 주소 사용률 통계를 제공하며, 서비스 프로젝트의 정보가 통계 정보 파생을 위해 자동으로 집계됩니다.
Recommender API에서 통계 보기
gcloud CLI 또는 Recommender API에서 이러한 통계를 보려면 다음 통계 유형을 사용하세요.
이 통계는 분석된 프로젝트에서 비공개 서비스 액세스에 사용된 IP 주소 범위의 사용률 요약을 제공합니다. 비공개 서비스 액세스 IP 주소 범위는 Cloud SQL과 같은 Google Cloud관리형 서비스에서 사용됩니다.
비공개 서비스 액세스를 사용하는 경우 서비스에 대한 비공개 연결을 만들 때 사용되는 할당된 범위를 만듭니다. 네트워크 분석기에서는 할당된 IP 주소 범위를 PSA 범위라고 합니다.
관리형 서비스 프로듀서는 VPC 네트워크에 피어링된 서비스 관리형 가상 프라이빗 클라우드 (VPC)에 서브넷을 만듭니다.
서비스 프로듀서는 할당된 IP 주소 범위 내에 있는 서브넷에 사용 가능한 IP 주소 범위를 선택합니다. 네트워크 분석기에서는 서비스 프로듀서 서브넷을 PSA 서브넷이라고 합니다.
이 통계에는 다음 정보가 포함됩니다.
PSA 범위 프리픽스: 관리형 서비스에 대해 VPC 네트워크에서 예약된 할당된 IP 주소 범위(PSA 범위)의 프리픽스입니다.
PSA 서브넷 프리픽스: PSA 범위에서 생성된 서브넷의 프리픽스입니다.
PSA 서브넷 리전: 이 서브넷의 관리형 서비스에 사용되는 리전입니다.
PSA 서브넷 서비스: 이 서브넷을 사용하는 관리형 서비스의 이름입니다. 이 필드를 지원하는 서비스에 대한 자세한 내용은 이름 필드를 지원하는 관리형 서비스를 참조하세요.
할당 비율:
PSA 범위의 할당 비율은 관리형 서비스에 할당된 범위의 크기에 해당합니다. 사용하는 각 관리형 서비스는 서비스에 따라 다양한 크기의 범위 1개 또는 여러 개를 예약합니다.
PSA 서브넷의 할당 비율은 해당 범위의 총 IP 주소 수 대비 서비스 관리형 VPC 네트워크의 PSA 서브넷 범위에서 할당된 IP 주소 수에 해당합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# IP address utilization insights\n\nThis page describes the Network Analyzer insights for IP address\nutilization. For information about all the insight types, see\n[Insight groups and types](/network-intelligence-center/docs/network-analyzer/insight-groups-types).\n\nIP address utilization insights show the IP address allocation percentage of\nsubnet ranges, which are calculated based on configurations that use IP\naddresses, such as VMs and load balancers. In the case of Shared VPC,\nNetwork Analyzer provides the IP address utilization insights of the host\nproject, and the information from service projects is automatically aggregated\nto derive the insight information.\n\nView insights in the Recommender API\n------------------------------------\n\nTo view these insights in the gcloud CLI or the Recommender API, use\nthe following insight type:\n\n- `google.networkanalyzer.vpcnetwork.ipAddressInsight`\n\nYou need the following permissions:\n\n- `recommender.networkAnalyzerIpAddressInsights.list`\n- `recommender.networkAnalyzerIpAddressInsights.get`\n\nFor more information about using the Recommender API for\nNetwork Analyzer insights, see\n[Use the Recommender CLI and API](/network-intelligence-center/docs/network-analyzer/use-cli-recommender-api).\n\nHigh IP address utilization of a subnet\n---------------------------------------\n\nThis insight indicates that the IP address utilization of a subnet is too high\n(the allocation ratio is higher than 75 percent). Such an issue can prevent\nautomation from creating new VMs or upgrading a GKE cluster. This\ninsight includes the following information:\n\n- **Subnetwork:** The name of the subnetwork.\n- **Secondary range name:** If the insight shows the primary range of the subnet, this field is not displayed.\n- **IP address range:** The IP address range of the subnetwork range.\n- **Allocation ratio:** The percentage of IP addresses from the range of the subnet that are allocated.\n- **Resources using this range:** The count of the number of resources of this type that have allocated IP addresses within the IP address range of the subnet. This attribute gives a summary of the number of IP addresses used by resources such as VMs and load balancers.\n\nThe allocation ratio of the primary range includes the\n[four unusable IP addresses](/vpc/docs/subnets#unusable-ip-addresses-in-every-subnet).\n\n### Recommendations\n\nYou have two options:\n\n- [Expand the subnet primary ranges](/vpc/docs/create-modify-vpc-networks#expand-subnet).\n- [Add more secondary ranges](/vpc/docs/create-modify-vpc-networks#edit-secondary).\n\nIP address utilization summary\n------------------------------\n\nThis insight gives a summary of the IP address utilization of subnet ranges in the\nanalyzed project. In the case of Shared VPC, Network Analyzer gives a\nsummary of the IP address utilization of all relevant subnet ranges of the host\nproject, and also provides the insights of the service projects. It includes the\nfollowing information:\n\n- All subnet ranges that have an allocation ratio more than zero.\n- **Secondary range name:** The secondary range name of a subnet. This field is not displayed for the primary range of a subnet.\n- **Subnet range prefix:** The IP address range of the subnetwork range in CIDR format.\n- **Allocation ratio:** The ratio (between 0 and 1, 1 being 100%) of IP addresses allocated from the range of the subnet compared to the total number of IP addresses in the subnet.\n\nThe allocation ratio of the primary range includes the\n[four unusable IP addresses](/vpc/docs/subnets#unusable-ip-addresses-in-every-subnet).\n\n### Related topics\n\nFor more information, see\n[High IP address utilization insight](/network-intelligence-center/docs/network-analyzer/insights/vpc-network/ip-utilization#ip-allocation-ratio-high).\n\nPrivate services access IP address utilization summary\n------------------------------------------------------\n\nThis insight gives a summary of the utilization of IP address ranges used for\n[private services access](/vpc/docs/private-services-access) in the analyzed\nprojects. Private services access IP address ranges are used by Google Cloud\nmanaged services such as Cloud SQL.\n\nWhen you use private services access, you create an [allocated\nrange](/vpc/docs/configure-private-services-access#allocating-range) that is\nused when you create a [private\nconnection](/vpc/docs/configure-private-services-access#creating-connection) to\nthe service. In Network Analyzer, allocated IP address ranges are referred\nto as *PSA ranges*.\n\nThe managed service producer creates a subnet in a service-managed\nVirtual Private Cloud (VPC) that is peered to your VPC network.\nThe service producer chooses an available IP address range for the subnet that\nfalls within the allocated IP address range. In Network Analyzer, the\nservice producer subnets are referred to as *PSA subnets*.\n\nThis insight includes the following information:\n\n- **PSA range prefix**: The prefix of the allocated IP address range (PSA range) reserved in your VPC network for managed services.\n- **PSA subnet prefix**: The prefix of the subnet that was created from the PSA range.\n- **PSA subnet region**: The region used by the managed service for this subnet.\n- **PSA subnet service** : The name of the managed service that uses this subnet. For more information about the services that support this field, see [Managed services supporting the name\n field](#managed-services-supporting-the-name-field).\n- **Allocation ratio** :\n - The allocation ratio of the PSA range corresponds to how much of the range is allocated to managed services. Each managed service you use reserves one or multiple ranges of varying size, depending on the service.\n - The allocation ratio of the PSA subnet corresponds to the number of IP addresses that are allocated from the range of the PSA subnet in the service-managed VPC network compared to the total number of IP addresses in the range.\n\nIn the case of Shared VPC, Network Analyzer provides this insight\nin the host project.\n\n### Managed services supporting the name field\n\nThe name field is populated for the following services:\n\n- AlloyDB for PostgreSQL\n- Apigee\n- Cloud Build\n- Cloud SQL\n- Memorystore for Memcached\n- Memorystore for Redis\n- Vertex AI managed notebooks\n\n### Recommendations\n\nReview the allocation ratio for your PSA ranges and consider [adding new\nallocated IP address\nranges](/vpc/docs/configure-private-services-access#modifying-connection) as\nsoon as the allocation ratio is greater than 50%."]]
