gcloud compute interconnects attachments partner create - create a Compute Engine partner interconnect attachment

gcloud compute interconnects attachments partner createNAME--edge-availability-domain=AVAILABILITY_DOMAIN--router=ROUTER[--candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS][--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS][--candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS][--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS][--description=DESCRIPTION][--enable-admin][--encryption=ENCRYPTION][--ipsec-internal-addresses=[ADDRESSES]][--mtu=MTU][--region=REGION][--resource-manager-tags=[KEY=VALUE,…]][--stack-type=STACK_TYPE][GCLOUD_WIDE_FLAG …]

NAME

Name of the interconnect attachment to create.

--edge-availability-domain=AVAILABILITY_DOMAIN

Desired edge availability domain for this attachment:availability-domain-1,availability-domain-2,any.

In each metro where the Partner can connect to Google, there are two sets ofredundant hardware. These sets are described as edge availability domain 1 and2. Within a metro, Google will only schedule maintenance in one availabilitydomain at a time. This guarantee does not apply to availability domains outsidethe metro; Google may perform maintenance in (say) New York availability domain1 at the same time as Chicago availability domain 1.

AVAILABILITY_DOMAIN must be one of:

any

Any Availability Domain

availability-domain-1

Edge Availability Domain 1

availability-domain-2

Edge Availability Domain 2

--router=ROUTER

Google Cloud Router to use for dynamic routing.

--candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS

Single IPv4 address + prefix length to be configured on the cloud routerinterface for this interconnect attachment. Example: 203.0.113.1/29

--candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS

Single IPv6 address + prefix length to be configured on the cloud routerinterface for this interconnect attachment. Example: 2001:db8::1/125

--candidate-customer-router-ip-address=CANDIDATE_CUSTOMER_ROUTER_IP_ADDRESS

Single IPv4 address + prefix length to be configured on the customer routerinterface for this interconnect attachment. Example: 203.0.113.2/29

--candidate-customer-router-ipv6-address=CANDIDATE_CUSTOMER_ROUTER_IPV6_ADDRESS

Single IPv6 address + prefix length to be configured on the customer routerinterface for this interconnect attachment. Example: 2001:db8::2/125

--description=DESCRIPTION

Human-readable plain-text description of attachment.

--enable-admin

Administrative status of the interconnect attachment. If not provided oncreation, defaults to disabled. When this is enabled, the attachment isoperational and will carry traffic. Use --no-enable-admin to disable it.

--encryption=ENCRYPTION

Indicates the user-supplied encryption option for this interconnect attachment(VLAN attachment).

Possible values are:

NONE - This is the default value, which means the interconnectattachment carries unencrypted traffic. VMs can send traffic to or receivetraffic from such interconnect attachment.

IPSEC - The interconnect attachment carries only traffic that isencrypted by an IPsec device; for example, an HA VPN gateway or third-partyIPsec VPN. VMs cannot directly send traffic to or receive traffic from such aninterconnect attachment. To use HA VPN over Cloud Interconnect, the interconnectattachment must be created with this option.

ENCRYPTION must be one of:IPSEC,NONE.

--ipsec-internal-addresses=[ADDRESSES]

List of IP address range names that have been reserved for the interconnectattachment (VLAN attachment). Use this option only for an interconnectattachment that has its encryption option set as IPSEC. Currently only oneinternal IP address range can be specified for each attachment. When creating anHA VPN gateway for the interconnect attachment, if the attachment is configuredto use a regional internal IP address, then the VPN gateway's IP address isallocated from the IP address range specified here. If this field is notspecified when creating the interconnect attachment, then when creating any HAVPN gateways for this interconnect attachment, the HA VPN gateway's IP addressis allocated from a regional external IP address pool.

--mtu=MTU

Maximum transmission unit (MTU) is the size of the largest IP packet passingthrough this interconnect attachment. Must be one of 1440, 1460, 1500, or 8896.If not specified, the value will default to 1440.

--region=REGION

Region of the interconnect attachment to create. If not specified, you might beprompted to select a region (interactive mode only).

To avoid prompting when this flag is omitted, you can set thecompute/region property:

gcloudconfigsetcompute/regionREGION

A list of regions can be fetched by running:

gcloudcomputeregionslist

To unset the property, run:

gcloudconfigunsetcompute/region

Alternatively, the region can be stored in the environment variableCLOUDSDK_COMPUTE_REGION.

--resource-manager-tags=[KEY=VALUE,…]

A comma-separated list of Resource Manager tags to apply to the interconnect.

--stack-type=STACK_TYPE

Stack type of the protocol(s) enabled on this interconnect attachment.STACK_TYPE must be one of:

IPV4_IPV6

Both IPv4 and IPv6 protocols are enabled on this attachment.

IPV4_ONLY

Only IPv4 protocol is enabled on this attachment.

Run$gcloud help for details.