配額與限制

這份文件列出 Cloud VPN 的配額和系統限制。

  • 「配額」有預設值，但通常可以申請調整。
  • 「系統限制」是固定值，無法變更。

如要變更配額，請參閱「申請更多配額」一節。

Google Cloud 使用配額來確保公平性，並減少資源使用量和可用性出現劇烈波動的情況。配額會限制 Google Cloud 專案可使用的Google Cloud 資源數量，且適用多種資源類型，包括軟硬體和網路元件。舉例來說，配額可能會限制能向特定服務發出的 API 呼叫次數、專案可同時使用的負載平衡器數量，或是可建立的專案數量。配額機制可防止服務過載，保障Google Cloud 使用者社群的權益，同時也有助於您管理自己的 Google Cloud 資源。

Cloud Quotas 系統具備以下功能：

如果嘗試使用的資源量超過配額限制，系統通常會阻擋該資源的存取活動，您所執行的工作就會失敗。

配額的計算通常是以 Google Cloud 專案為基準。在某個專案中使用資源，不會影響另一個專案的可用配額。在同一個 Google Cloud 專案內，所有應用程式和 IP 位址會共用配額。

詳情請參閱「Cloud Quotas 總覽」。

Cloud VPN 資源也有「系統限制」， 而且無法變更。

配額

下表列出每個專案的重要配額。如需其他配額資訊，請前往Google Cloud 控制台的「配額」頁面。

項目 配額 附註
VPN 閘道 配額 僅限高可用性 VPN
外部 VPN 閘道 配額 僅限高可用性 VPN
VPN 通道 配額 這個配額代表傳統 VPN 通道數量和 HA VPN 通道數量的總數。
路由器 配額

這項配額代表您可以在專案中建立的 Cloud Router 路由器數量，適用於所有網路和區域。另外，各個網路對任一區域中的 Cloud Router 路由器數量同樣設有限制。詳情請參閱 Cloud Router 的配額與限制。

基於 Cloud Router 的配額與限制，與通道相連的 Cloud VPN 閘道類型 (傳統版 VPN 或高可用性 VPN) 也完全不會影響 Cloud Router 路由器的數量，即便配額同樣套用至任一閘道類型也一樣。
目標 VPN 閘道 配額 僅限傳統 VPN
轉送規則 配額 僅限傳統 VPN

限制

下列限制適用於 Cloud VPN。在這個表格中，「VPN 通道」代表傳統版 VPN 通道或高可用性 VPN 通道。除非另有說明，否則這些上限均不得提高。

項目 限制 附註
各個 VPN 通道的頻寬 輸入和輸出總和上限為每秒 25 萬個封包

每秒 25 萬個封包大約相當於 1 Gbps 至 3 Gbps，視通道內的平均封包大小而定。

Cloud VPN 只能調節輸出的 IPsec 流量， 無法調節輸入的流量。

詳情請參閱「網路頻寬」。

已知問題

請注意下列問題：

Manage quotas

Cloud VPN 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.

後續步驟