配额和限制

本文档列出了适用于 Network Connectivity Center 和路由器设备的配额和限制。

如需更改配额，请参阅申请额外的配额。

Google Cloud 使用配额来帮助确保公平性并减少资源使用和可用性的激增。配额用于限制您的 Google Cloud 项目可使用的Google Cloud 资源的数量。配额适用于一系列资源类型，包括硬件、软件和网络组件。例如，配额可以限制对某项服务的 API 调用次数、您的项目并发使用的负载均衡器数量或者您可以创建的项目数量。配额可以防止服务过载，从而保护Google Cloud 用户社区。配额还可以帮助您管理自己的 Google Cloud 资源。

Cloud 配额系统执行以下操作：

在大多数情况下，当您尝试消耗的资源超出其配额允许的范围时，系统会阻止对资源的访问，并且您尝试执行的任务会失败。

配额通常在 Google Cloud 项目级层应用。您在一个项目中使用资源不会影响您在另一个项目中的可用配额。在 Google Cloud 项目中，配额在所有应用和 IP 地址间共享。

如需了解详情，请参阅 Cloud 配额概览。

Network Connectivity Center 资源也有系统限制。系统限制不能更改。

配额

本部分列出了适用于 Network Connectivity Center 和路由器设备的配额。

Network Connectivity Center 配额

适用于 Cloud Router 的网络路由的配额也适用于 Network Connectivity Center 的中心辐射式结构。如需了解详情，请参阅 Cloud Router 配额和限制。

项 Quota 备注
每个项目的 Hub 数 Quota 每个项目（全球）
每个项目在每个区域的 Cloud VPN 隧道 Spoke 数量 Quota 每个区域中每个项目：仅支持高可用性 VPN 隧道
每个区域中每个项目的 Cloud Interconnect VLAN 连接 Spoke 数量 Quota 每个区域中每个项目的情况
每个区域中每个项目的路由器设备 spoke 数量 Quota 每个区域中每个项目的情况
每个项目的 VPC spoke 数量 Quota 包括 VPC spoke（边缘和中心 spoke 的组合），即使它们未连接到任何 hub。

每个 Hub 的活跃 VPC Spoke 数量

 Quota

仅适用于已接受 Hub 的 VPC Spoke；不适用于待处理或已被拒绝的 VPC spoke。

每个 hub 路由表的子网路由数

 Quota 仅适用于具有 VPC spoke 的 Hub

每个 hub 的动态路由数

 Quota 适用于所有 VPC spoke

每个 hub 的路由 VPC 网络数量

 Quota

每个 hub 以内部应用负载均衡器 IP 地址作为下一个跃点的静态路由的数量

 Quota 每个项目（全球）

路由器设备配额

适用于 Cloud Router 网络路由的配额也适用于连接到 Network Connectivity Center Hub 的路由器设备路由。

如需了解详情，请参阅 Cloud Router 配额。

限制

本部分列出了适用于 Network Connectivity Center 和路由器设备的限制。

Network Connectivity Center 限制

Network Connectivity Center 实施以下用量限额。

项 值
可链接到某个 Spoke 的 VPN 隧道数 8
可链接到某个 Spoke 的 VLAN 连接数 6
可关联到某个 Spoke 的路由器设备实例数 8
每个 hub 的活跃 VPC spoke 数量 250
每个 hub 的 VPC spoke（活跃和非活跃）数量上限 1000
每个 spoke 的包含或排除导出 CIDR 范围数量 16

路由器设备限制

Cloud Router 路由器的以下限制也适用于路由器设备：

  • 每个 VPC 网络和区域组合的 Cloud Router 路由器数上限
  • 给定 VPC 网络和区域内每个 Cloud Router 路由器的 BGP 对等体数量上限

如需了解详情，请参阅 Cloud Router 路由器限制。

Manage quotas

Network Connectivity Center enforces quotas on resource usage for various reasons. For example, quotas protect the community of Google Cloud users by preventing unforeseen spikes in usage. Quotas also help users who are exploring Google Cloud with the free tier to stay within their trial.

All projects start with the same quotas, which you can change by requesting additional quota. Some quotas might increase automatically based on your use of a product.

Permissions

To view quotas or request quota increases, Identity and Access Management (IAM) principals need one of the following roles.

Task Required role
Check quotas for a project One of the following:
Modify quotas, request additional quota One of the following:
  • Project Owner (roles/owner)
  • Project Editor (roles/editor)
  • Quota Administrator (roles/servicemanagement.quotaAdmin)
  • A custom role with the serviceusage.quotas.update permission

Check your quota

Console

  1. In the Google Cloud console, go to the Quotas page.

    Go to Quotas

  2. To search for the quota that you want to update, use the Filter table. If you don't know the name of the quota, use the links on this page instead.

gcloud

Using the Google Cloud CLI, run the following command to check your quotas. Replace PROJECT_ID with your own project ID.

    gcloud compute project-info describe --project PROJECT_ID

To check your used quota in a region, run the following command:

    gcloud compute regions describe example-region

Errors when exceeding your quota

If you exceed a quota with a gcloud command, gcloud outputs a quota exceeded error message and returns with the exit code 1.

If you exceed a quota with an API request, Google Cloud returns the following HTTP status code: 413 Request Entity Too Large.

Request additional quota

To adjust most quotas, use the Google Cloud console. For more information, see Request a quota adjustment.

Resource availability

Each quota represents a maximum number for a particular type of resource that you can create, if that resource is available. It's important to note that quotas don't guarantee resource availability. Even if you have available quota, you can't create a new resource if it is not available.

For example, you might have sufficient quota to create a new regional, external IP address in a given region. However, that is not possible if there are no available external IP addresses in that region. Zonal resource availability can also affect your ability to create a new resource.

Situations where resources are unavailable in an entire region are rare. However, resources within a zone can be depleted from time to time, typically without impact to the service level agreement (SLA) for the type of resource. For more information, review the relevant SLA for the resource.

后续步骤