.TH "GCLOUD_COMPUTE_INTERCONNECTS_ATTACHMENTS_PARTNER_CREATE" 1



.SH "NAME"
.HP
gcloud compute interconnects attachments partner create \- create a Compute Engine partner interconnect attachment



.SH "SYNOPSIS"
.HP
\f5gcloud compute interconnects attachments partner create\fR \fINAME\fR \fB\-\-edge\-availability\-domain\fR=\fIAVAILABILITY_DOMAIN\fR \fB\-\-router\fR=\fIROUTER\fR [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-enable\-admin\fR] [\fB\-\-encryption\fR=\fIENCRYPTION\fR] [\fB\-\-ipsec\-internal\-addresses\fR=[\fIADDRESSES\fR]] [\fB\-\-mtu\fR=\fIMTU\fR] [\fB\-\-region\fR=\fIREGION\fR] [\fB\-\-stack\-type\fR=\fISTACK_TYPE\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fBgcloud compute interconnects attachments partner create\fR is used to create
partner interconnect attachments. A partner interconnect attachment binds the
underlying connectivity of a provider's Interconnect to a path into and out of
the customer's cloud network.



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fINAME\fR

Name of the interconnect attachment to create.


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-edge\-availability\-domain\fR=\fIAVAILABILITY_DOMAIN\fR

Desired edge availability domain for this attachment:
\f5availability\-domain\-1\fR, \f5availability\-domain\-2\fR, \f5any\fR.

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

\fIAVAILABILITY_DOMAIN\fR must be one of:

.RS 2m
.TP 2m
\fBany\fR
Any Availability Domain
.TP 2m
\fBavailability\-domain\-1\fR
Edge Availability Domain 1
.TP 2m
\fBavailability\-domain\-2\fR
Edge Availability Domain 2
.RE
.sp


.TP 2m
\fB\-\-router\fR=\fIROUTER\fR

Google Cloud Router to use for dynamic routing.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

Human\-readable plain\-text description of attachment.

.TP 2m
\fB\-\-enable\-admin\fR

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

.TP 2m
\fB\-\-encryption\fR=\fIENCRYPTION\fR

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

Possible values are:

\f5NONE\fR \- This is the default value, which means the interconnect attachment
carries unencrypted traffic. VMs can send traffic to or receive traffic from
such interconnect attachment.

\f5IPSEC\fR \- The interconnect attachment carries only traffic that is
encrypted by an IPsec device; for example, an HA VPN gateway or third\-party
IPsec VPN. VMs cannot directly send traffic to or receive traffic from such an
interconnect attachment. To use HA VPN over Cloud Interconnect, the interconnect
attachment must be created with this option.

\fIENCRYPTION\fR must be one of: \fBIPSEC\fR, \fBNONE\fR.

.TP 2m
\fB\-\-ipsec\-internal\-addresses\fR=[\fIADDRESSES\fR]

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

.TP 2m
\fB\-\-mtu\fR=\fIMTU\fR

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

.TP 2m
\fB\-\-region\fR=\fIREGION\fR

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

To avoid prompting when this flag is omitted, you can set the
\f5\fIcompute/region\fR\fR property:

.RS 2m
$ gcloud config set compute/region REGION
.RE

A list of regions can be fetched by running:

.RS 2m
$ gcloud compute regions list
.RE

To unset the property, run:

.RS 2m
$ gcloud config unset compute/region
.RE

Alternatively, the region can be stored in the environment variable
\f5\fICLOUDSDK_COMPUTE_REGION\fR\fR.

.TP 2m
\fB\-\-stack\-type\fR=\fISTACK_TYPE\fR

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

.RS 2m
.TP 2m
\fBIPV4_IPV6\fR
Both IPv4 and IPv6 protocols are enabled on this attachment.
.TP 2m
\fBIPV4_ONLY\fR
Only IPv4 protocol is enabled on this attachment.
.RE
.sp



.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha compute interconnects attachments partner create
.RE

.RS 2m
$ gcloud beta compute interconnects attachments partner create
.RE