File: //snap/google-cloud-cli/394/help/man/man1/gcloud_compute_interconnects_wire-groups_create.1
.TH "GCLOUD_COMPUTE_INTERCONNECTS_WIRE\-GROUPS_CREATE" 1
.SH "NAME"
.HP
gcloud compute interconnects wire\-groups create \- create a Compute Engine wire group
.SH "SYNOPSIS"
.HP
\f5gcloud compute interconnects wire\-groups create\fR \fINAME\fR \fB\-\-bandwidth\-allocation\fR=\fIBANDWIDTH_ALLOCATION\fR \fB\-\-bandwidth\-unmetered\fR=\fIBANDWIDTH_UNMETERED\fR \fB\-\-cross\-site\-network\fR=\fICROSS_SITE_NETWORK\fR [\fB\-\-admin\-enabled\fR] [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-fault\-response\fR=\fIFAULT_RESPONSE\fR] [\fB\-\-validate\-only\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]
.SH "DESCRIPTION"
\fBgcloud compute interconnects wire\-groups create\fR is used to create wire
groups. A wire group represents a group of redundant wires between interconnects
in two different metros. Each WireGroup belongs to a CrossSiteNetwork.
For an example, refer to the \fBEXAMPLES\fR section below.
.SH "EXAMPLES"
To create a wire group, run:
.RS 2m
$ gcloud compute interconnects wire\-groups create example\-wg \e
\-\-cross\-site\-network=example\-csn \-\-bandwidth\-unmetered=1
.RE
.SH "POSITIONAL ARGUMENTS"
.RS 2m
.TP 2m
\fINAME\fR
Name of the wire group to create.
.RE
.sp
.SH "REQUIRED FLAGS"
.RS 2m
.TP 2m
\fB\-\-bandwidth\-allocation\fR=\fIBANDWIDTH_ALLOCATION\fR
The bandwidth allocation for the wire group. \fIBANDWIDTH_ALLOCATION\fR must be
one of:
.RS 2m
.TP 2m
\fBALLOCATE_PER_WIRE\fR
Configures a separate unmetered bandwidth allocation (and associated charges)
for each wire in the group.
.TP 2m
\fBSHARED_WITH_WIRE_GROUP\fR
Configures one unmetered bandwidth allocation for the wire group. The unmetered
bandwidth is divided equally across each wire in the group, but dynamic
throttling reallocates unused unmetered bandwidth from unused or underused wires
to other wires in the group.
.RE
.sp
.TP 2m
\fB\-\-bandwidth\-unmetered\fR=\fIBANDWIDTH_UNMETERED\fR
The amount of unmetered bandwidth to assign to the wire group.
.TP 2m
\fB\-\-cross\-site\-network\fR=\fICROSS_SITE_NETWORK\fR
Name of the crossSiteNetwork to operate on.
.RE
.sp
.SH "OPTIONAL FLAGS"
.RS 2m
.TP 2m
\fB\-\-admin\-enabled\fR
Administrative status of the wire group. If not provided on creation, defaults
to enabled. When this is enabled, the wire group is operational and will carry
traffic. Use \-\-no\-admin\-enabled to disable it.
.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR
An optional, textual description for the wire group.
.TP 2m
\fB\-\-fault\-response\fR=\fIFAULT_RESPONSE\fR
The fault response for the wire group. \fIFAULT_RESPONSE\fR must be one of:
.RS 2m
.TP 2m
\fBDISABLE_PORT\fR
Disable port
.TP 2m
\fBNONE\fR
None
.RE
.sp
.TP 2m
\fB\-\-validate\-only\fR
Validate the new configuration, but don't update it.
.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 wire\-groups create
.RE
.RS 2m
$ gcloud beta compute interconnects wire\-groups create
.RE