Quotas and Limits

The following sections describe quotas and limits for Cloud Interconnect. To change a quota, simply request additional quota using the Cloud Console. Limits cannot generally be increased unless specifically noted.

Quotas

This table highlights important quotas for each project. See the quotas page for other quotas.

Item Quota Notes
Interconnects Quota This is the number of interconnects per project. Interconnects are not associated with regions or VPC networks.
Interconnect bandwidth per project Calculated automatically This quota represents the total interconnect bandwidth for the project, calculated by adding up the bandwidths of each interconnect it contains.

The bandwidth of each interconnect is calculated by multiplying the capacities of its circuits (either 10 Gbps or 100Gbps) by the number of circuits in the interconnect. For example, an interconnect consisting of four 10 Gbps circuits has 40 Gbps of bandwidth. If you have two such interconnects in your project, this quota is automatically set to 80 Gbps.
Interconnect attachments Quota This quota represents the number of interconnect attachments (VLANs) that you can configure in each region for your project. Regardless of this quota, you are also limited to a total of 16 interconnect attachments per interconnect. If you require additional attachments per interconnect, refer to Maximum number of interconnect attachments (VLANs) that can be associated with a single interconnect in limits, below.
Interconnect attachments total Mbps Quota This quota represents the maximum bandwidth capacity of all interconnect attachments in a given region for a given project, irrespective of their relationship with interconnects. In addition to this quota, the limits described in the next table apply.
Cloud Routers Quotas This quota represents the number of Cloud Routers you can create within your project, in any network and region. Networks also have a limit on the number of Cloud Routers in any given region. See Cloud Router quotas and limits for more details.

Limits

The following limits apply to interconnects and interconnect attachments. Unless otherwise stated, these limits cannot be increased.

Item Limit Notes
Maximum number of physical circuits per interconnect 8 x 10 Gbps (80 Gbps) circuits or
2 x 100 Gbps (200 Gbps) circuits
An interconnect is a logical connection to Google, made up of one or more physical circuits. You can request one of the following circuit choices:
  • Up to 2 x 100 Gbps (200 Gbps) circuits.
  • 10 Gbps increments up to eight circuits (80 Gbps) to increase the maximum total bandwidth of all interconnect attachments that use the interconnect to 80 Gbps.
    To determine the bandwidth, multiply the number of physical circuits by the bandwidth per circuit (10 Gbps).
Maximum number of interconnect attachments (VLANs) that can be associated with a single interconnect 16 Each interconnect supports no more than 16 interconnect attachments (VLANs), even if you would otherwise have quota to create more interconnect attachments.
Maximum bandwidth per interconnect attachment Capacities from 50 Mbps to 50 Gbps The maximum possible bandwidth per interconnect attachment depends on the bandwidth capacity you order. See the Pricing page for capacities. For Partner Interconnect, not all partners offer all capacities.

The throughput of individual flows on an interconnect attachment is limited, as described below. To achieve maximum throughput, you must use multiple five-tuple flows (for example: 10+) with packet sizes within the MTU of the interconnect attachment.
Maximum total packet rate per interconnect attachment (VLAN) This rate varies according to the attachment's capacity:
  • The maximum rate for a 50 Gbps interconnect attachment (VLAN) is 6.25M packets per second (pps).
  • The maximum rate for a 10 Gbps interconnect attachment (VLAN) is 1.25M packets per second (pps)
This represents the maximum packet rate for the entire interconnect attachment (VLAN).
Maximum bandwidth per traffic flow on an interconnect attachment 3 Gbps. Even if you configure your attachment above 3 Gbps, your per-flow capacity is capped at 3 Gbps. A traffic flow is identified by either a five-tuple hash for non-fragmented packets or a three-tuple hash for fragmented packets.
  • A five tuple hash consists of a protocol, source IP address, source port, destination IP address, and destination port.
  • A three-tuple hash consists of a protocol, source IP address, and destination IP address.
The following cases describe where the maximum bandwidth is lower than 3 Gbps:
  • If the bandwidth capacity of your interconnect attachment itself is less than 3 Gbps, then the bandwidth per traffic flow is limited by the bandwidth of the interconnect attachment.
  • If you reach the maximum packet rate per traffic flow, described next.
Maximum packet rate per traffic flow on an interconnect attachment 250,000 packets per second This number represents the maximum rate of packets per traffic flow, as identified by a five-tuple hash for non-fragmented packets and by a three-tuple hash for fragmented packets, as described in the previous section.
Maximum Transmission Unit 1440 bytes The size of the largest IP packet that can be transmitted over an interconnect attachment.
Maximum lifetime of (Partner) interconnect attachment pairing key 28 days The maximum amount of time that can pass between generating a (partner) interconnect attachment pairing key and successful attachment provisioning by the partner. If a pairing key is no longer valid, you just delete and recreate a new pairing key for the partner interconnect provider to use.
Cloud Router limits Because Dedicated Interconnect and Partner Interconnect require Cloud Router, all of the Cloud Router quotas and limits apply. There are limits on the maximum number of learned custom dynamic routes and on the number of advertised routes. Carefully review the Cloud Router Quotas and limits page for more information.

概览

出于多种原因,Cloud Interconnect 会对资源用量实施配额限制。例如,配额可避免出现意料之外的用量突增,从而为 Google Cloud 用户社区提供保护。配额还可帮助正在通过免费层级探索 Google Cloud 的用户避免中断试用。

所有项目在开始时都具有相同的配额,您可以通过申请更多配额来更改配额。根据您使用产品的情况,一些配额可能会自动增加。

权限

要查看配额或申请增加配额,IAM 成员需要拥有以下某个角色。

任务 所需的角色
检查项目的配额 项目 Owner 或Editor Quota Viewer
修改配额,申请更多配额 项目 Owner 或 EditorQuota Admin 或具有 serviceusage.quotas.update 权限的自定义角色

检查配额

在 Cloud Console 中,转到配额页面。

使用 gcloud 命令行工具,运行以下命令来检查配额。请将 [PROJECT_ID] 替换为您自己的项目 ID。

    gcloud compute project-info describe --project [PROJECT_ID]

如需查看您在某一区域中已使用的配额,请运行以下命令:

    gcloud compute regions describe example-region

超出配额时引发的错误

如果在发出 gcloud 命令时超过了配额,gcloud 会显示一条 quota exceeded 错误消息,并返回退出代码 1

如果在发出 API 请求时超出了配额,Google Cloud 会返回以下 HTTP 状态代码:HTTP 413 Request Entity Too Large

申请更多配额

请从 Cloud Console 中的配额页面申请更多配额。配额申请需要 24 到 48 小时才能完成处理。

  1. 转到配额页面。

    转到“配额”页面

  2. 配额页面中,选择要更改的配额。
  3. 点击页面顶部的编辑配额按钮。
  4. 填写您的姓名、电子邮件和电话号码,然后点击下一步
  5. 填写您的配额申请,然后点击下一步
  6. 提交您的申请。

资源可用性

每个配额代表您可以创建的特定类型资源的数量上限,前提是该资源可用。必须要注意的是,配额无法保证资源可用性。即使您有可用配额,如果新资源不可用,您也无法创建新资源。例如,您在 us-central1 区域中拥有足够的配额来创建新的区域级外部 IP 地址,但如果该区域中没有可用的外部 IP 地址,则无法执行此操作。地区级资源可用性也会影响您能否创建新资源。

整个区域中的资源都不可用的情况很少见;但是,地区内的资源有时可能会耗尽,通常不会影响该资源类型的 SLA。如需了解详情,请查看资源的相关服务等级协议 (SLA)。