.TH "GCLOUD_COMPUTE_INTERCONNECTS_CREATE" 1



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



.SH "SYNOPSIS"
.HP
\f5gcloud compute interconnects create\fR \fINAME\fR \fB\-\-interconnect\-type\fR=\fIINTERCONNECT_TYPE\fR \fB\-\-link\-type\fR=\fILINK_TYPE\fR \fB\-\-location\fR=\fILOCATION\fR \fB\-\-requested\-link\-count\fR=\fIREQUESTED_LINK_COUNT\fR [\fB\-\-admin\-enabled\fR] [\fB\-\-customer\-name\fR=\fICUSTOMER_NAME\fR] [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-noc\-contact\-email\fR=\fINOC_CONTACT_EMAIL\fR] [\fB\-\-remote\-location\fR=\fIREMOTE_LOCATION\fR] [\fB\-\-requested\-features\fR=[\fIFEATURES\fR,...]] [\fB\-\-subzone\fR=\fISUBZONE\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fBgcloud compute interconnects create\fR is used to create interconnects. An
interconnect represents a single specific connection between Google and the
customer.

For an example, refer to the \fBEXAMPLES\fR section below.



.SH "EXAMPLES"

To create an interconnect of type DEDICATED, run:

.RS 2m
$ gcloud compute interconnects create example\-interconnect \e
    \-\-customer\-name="Example Customer Name" \e
    \-\-interconnect\-type=DEDICATED \e
    \-\-link\-type=LINK_TYPE_ETHERNET_10G_LR \e
    \-\-location=example\-zone1\-1 \-\-requested\-link\-count=1 \e
    \-\-noc\-contact\-email=noc@example.com \e
    \-\-description="Example interconnect"
.RE

To create a Cross\-Cloud Interconnect, run:

.RS 2m
$ gcloud compute interconnects create example\-cc\-interconnect \e
    \-\-interconnect\-type=DEDICATED \e
    \-\-link\-type=LINK_TYPE_ETHERNET_10G_LR \e
    \-\-location=example\-zone1\-1 \-\-requested\-link\-count=1 \e
    \-\-remote\-location=example\-remote\-location \e
    \-\-noc\-contact\-email=noc@example.com \e
    \-\-description="Example Cross\-Cloud Interconnect"
.RE



.SH "POSITIONAL ARGUMENTS"

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

Name of the interconnect to create.


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-interconnect\-type\fR=\fIINTERCONNECT_TYPE\fR

Type of the interconnect. \fIINTERCONNECT_TYPE\fR must be one of:

.RS 2m
.TP 2m
\fBDEDICATED\fR
Dedicated private interconnect.
.TP 2m
\fBPARTNER\fR
Partner interconnect. Only available to approved partners.
.RE
.sp


.TP 2m
\fB\-\-link\-type\fR=\fILINK_TYPE\fR

Type of the link for the interconnect. \fILINK_TYPE\fR must be one of:

.RS 2m
.TP 2m
\fBLINK_TYPE_ETHERNET_100G_LR\fR
100Gbps Ethernet, LR Optics.
.TP 2m
\fBLINK_TYPE_ETHERNET_10G_LR\fR
10Gbps Ethernet, LR Optics.
.TP 2m
\fBLINK_TYPE_ETHERNET_400G_LR4\fR
400Gbps Ethernet, LR4 Optics.
.RE
.sp


.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

The location for the interconnect. The locations can be listed by using the
\f5gcloud compute interconnects locations list\fR command to find the
appropriate location to use when creating an interconnect.

.TP 2m
\fB\-\-requested\-link\-count\fR=\fIREQUESTED_LINK_COUNT\fR

Target number of physical links in the link bundle.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-admin\-enabled\fR

Administrative status of the interconnect. If not provided on creation, defaults
to enabled. When this is enabled, the interconnect is operational and will carry
traffic across any functioning linked interconnect attachments. Use
\-\-no\-admin\-enabled to disable it.

.TP 2m
\fB\-\-customer\-name\fR=\fICUSTOMER_NAME\fR

Customer name to put in the Letter of Authorization as the party authorized to
request an interconnect. This field is required for most interconnects, however
it is prohibited when creating a Cross\-Cloud Interconnect.

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

An optional, textual description for the interconnect.

.TP 2m
\fB\-\-noc\-contact\-email\fR=\fINOC_CONTACT_EMAIL\fR

Email address to contact the customer NOC for operations and maintenance
notifications regarding this interconnect.

.TP 2m
\fB\-\-remote\-location\fR=\fIREMOTE_LOCATION\fR

The remote location for a Cross\-Cloud Interconnect. The remote locations can be
listed by using the \f5gcloud compute interconnects remote\-locations list\fR
command to find the appropriate remote location to use when creating a
Cross\-Cloud Interconnect.

.TP 2m
\fB\-\-requested\-features\fR=[\fIFEATURES\fR,...]

List of features requested for this interconnect. \fIFEATURES\fR must be one of:

.RS 2m
.TP 2m
\fBCROSS_SITE_NETWORK\fR
If specified then the interconnect is created on Cross\-Site Network capable
hardware ports. This parameter can only be provided during interconnect INSERT
and cannot be changed using interconnect PATCH.
.TP 2m
\fBL2_FORWARDING\fR
If specified then the interconnect is created on L2 forwarding capable hardware
ports. This parameter can only be provided during interconnect INSERT and cannot
be changed using interconnect PATCH.
.TP 2m
\fBMACSEC\fR
If specified then the interconnect is created on MACsec capable hardware ports.
If not specified, the interconnect is created on non\-MACsec capable ports
first, if available. This parameter can only be provided during interconnect
INSERT and cannot be changed using interconnect PATCH.
.RE
.sp


.TP 2m
\fB\-\-subzone\fR=\fISUBZONE\fR

Subzone in the LOCATION specified by the \-\-location flag. \fISUBZONE\fR must
be one of:

.RS 2m
.TP 2m
\fBa\fR
Subzone a.
.TP 2m
\fBb\fR
Subzone b.
.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 create
.RE

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