Quotas and Limits

The following sections describe quotas and limits for Cloud Interconnect. To change a quota, simply request additional quota using the GCP 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 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 during the Cloud Interconnect 100G Beta period.
  • 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 Up to 10 Gbps For Dedicated Interconnect, the bandwidth per interconnect attachment is 10 Gbps. For Partner Interconnect, the maximum possible bandwidth per interconnect attachment is 10 Gbps, but might be lower, depending on the bandwidth capacity you ordered.
Maximum bandwidth capacity per traffic flow on an interconnect attachment Up to 3 Gbps The bandwidth per traffic flow, as identified by a five-tuple hash consisting of the protocol, source IP address, source port, destination IP address, and destination port, can be up to 3 Gbps. The following cases describe where it is lower:
  • If the bandwidth capacity of your interconnect attachment itself is less than 3 Gbps, possible with Partner Interconnect, 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 represents the maximum rate of packets per traffic flow, as identified by a five-tuple hash consisting of the protocol, source IP address, source port, destination IP address, and destination port.
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.

Overview

Cloud Interconnect enforces quotas on resource usage for a variety of reasons. For example, quotas protect the community of Google Cloud Platform users by preventing unforeseen spikes in usage. Quotas also help users who are exploring GCP 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 may increase automatically, based on your use of a product.

Permissions

To view quotas or request quota increases, IAM members need one of the following roles.

Task Required Role
Check quotas for a project Project owner or editor or Quota Viewer
Modify quotas, request additional quota Project owner or editor, Quota Admin, or custom role with the serviceusage.quotas.update permission

Checking your quota

In the GCP Console, go to the Quotas page.

Using the gcloud command-line tool, 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:

    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, GCP returns the following HTTP status code: HTTP 413 Request Entity Too Large.

Requesting additional quota

Request additional quota from the Quotas page in the GCP Console. Quota requests take 24 to 48 hours to process.

  1. Go to the Quotas page.

    Go to the Quotas page

  2. In the Quotas page, select the quotas you want to change.
  3. Click the Edit Quotas button at the top of the page.
  4. Fill out your name, email, and phone number and click Next.
  5. Fill in your quota request and click Next.
  6. Submit your request.

Resource availability

Each quota represents a maximum number for a particular type of resource that you can create, provided that resource is available. It's important to note that quotas do not guarantee resource availability. Even if you have available quota, you won't be able to create a new resource if it is not available. For example, you might have sufficient quota to create new regional, external IP address in the us-central1 region, but that would not be possible if there were 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 SLA for the type of resource. For more information, review the relevant Service Level Agreement (SLA) for the resource.

هل كانت هذه الصفحة مفيدة؟ يرجى تقييم أدائنا:

إرسال تعليقات حول...