.TH "GCLOUD_COMPUTE_INTERCONNECTS_GROUPS_CREATE\-MEMBERS" 1



.SH "NAME"
.HP
gcloud compute interconnects groups create\-members \- create new member interconnects in a Compute Engine interconnect group



.SH "SYNOPSIS"
.HP
\f5gcloud compute interconnects groups create\-members\fR \fINAME\fR \fB\-\-interconnect\fR=[\fIINTERCONNECT\fR,...] [\fB\-\-admin\-enabled\fR] [\fB\-\-customer\-name\fR=\fICUSTOMER_NAME\fR] [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-facility\fR=\fIFACILITY\fR] [\fB\-\-intent\-mismatch\-behavior\fR=\fIINTENT_MISMATCH_BEHAVIOR\fR] [\fB\-\-interconnect\-type\fR=\fIINTERCONNECT_TYPE\fR] [\fB\-\-link\-type\fR=\fILINK_TYPE\fR] [\fB\-\-noc\-contact\-email\fR=\fINOC_CONTACT_EMAIL\fR] [\fB\-\-remote\-location\fR=\fIREMOTE_LOCATION\fR] [\fB\-\-requested\-features\fR=[\fIFEATURES\fR,...]] [\fB\-\-requested\-link\-count\fR=\fIREQUESTED_LINK_COUNT\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fBgcloud compute interconnects groups create\-members\fR is used to create new
member interconnects in an interconnect group.

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



.SH "EXAMPLES"

To create interconnects interconnect1 and interconnect2 in interconnect group
example\-interconnect\-group, run:

.RS 2m
$ gcloud compute interconnects groups create\-members \e
    example\-interconnect\-group \-\-interconnect\-type=DEDICATED \e
    \-\-link\-type=LINK_TYPE_ETHERNET_10G_LR \-\-requested\-link\-count=1 \e
    \-\-facility=iad\-1 \-\-interconnect="name=interconnect1" \e
    \-\-interconnect="name=interconnect2"
.RE



.SH "POSITIONAL ARGUMENTS"

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

Name of the interconnect group to create members.


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-interconnect\fR=[\fIINTERCONNECT\fR,...]

New member interconnects to create in the interconnect group. To create multiple
interconnects, this flag should be specified multiple times.

Each interconnect takes in the same set of flags as the \f5gcloud compute
interconnects create\fR command, except instead of a location, a facility must
be specified. These flags are defined as a comma separated list of flag=value
pairs.

Example: \-\-interconnect name=interconnect1,facility=iad\-1,description="my
interconnect",link\-type=LINK_TYPE_ETHERNET_10G_LR,requested\-link\-count=1,
interconnect\-type=DEDICATED,admin\-enabled,
noc\-contact\-email=noc@google.com,customer\-name=customer\-name
requested\-features=MACSEC:CROSS_SITE_NETWORK

Note that for multiple requested\-features, use a colon (:) as the delimiter, as
the comma is used to separate the flags. Similarly, if you need to use a comma
in another flag value, you should set an alternative delimiter for the
\-\-interconnect flag. Run \f5gcloud topic escaping\fR for more information.


.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\-\-facility\fR=\fIFACILITY\fR

The facility (zone free location) to create the interconnect in.

.TP 2m
\fB\-\-intent\-mismatch\-behavior\fR=\fIINTENT_MISMATCH_BEHAVIOR\fR

The behavior when the intent of the interconnect group does not match the
topology capability of the member interconnects. \fIINTENT_MISMATCH_BEHAVIOR\fR
must be one of: \fBREJECT\fR, \fBCREATE\fR.

.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\-\-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 location of the interconnect for 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\-\-requested\-link\-count\fR=\fIREQUESTED_LINK_COUNT\fR

Target number of physical links in the link bundle.


.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 groups create\-members
.RE

.RS 2m
$ gcloud beta compute interconnects groups create\-members
.RE