gcloud beta compute interconnects groups create-members - create new member interconnects in a Compute Engine interconnect group

gcloud beta compute interconnects groups create-membersNAME--interconnect=[INTERCONNECT,…][--admin-enabled][--customer-name=CUSTOMER_NAME][--description=DESCRIPTION][--facility=FACILITY][--intent-mismatch-behavior=INTENT_MISMATCH_BEHAVIOR][--interconnect-type=INTERCONNECT_TYPE][--link-type=LINK_TYPE][--noc-contact-email=NOC_CONTACT_EMAIL][--remote-location=REMOTE_LOCATION][--requested-features=[FEATURES,…]][--requested-link-count=REQUESTED_LINK_COUNT][GCLOUD_WIDE_FLAG …]

For an example, refer to theEXAMPLES section below.

NAME

Name of the interconnect group to create members.

--interconnect=[INTERCONNECT,…]

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

Each interconnect takes in the same set of flags as thegcloud computeinterconnects create command, except instead of a location, a facilitymust be specified. These flags are defined as a comma separated list offlag=value pairs.

Example: --interconnect name=interconnect1,facility=iad-1,description="myinterconnect",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-namerequested-features=MACSEC:CROSS_SITE_NETWORK

Note that for multiple requested-features, use a colon (:) as the delimiter, asthe comma is used to separate the flags. Similarly, if you need to use a commain another flag value, you should set an alternative delimiter for the--interconnect flag. Rungcloud topic escaping formore information.

--admin-enabled

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

--customer-name=CUSTOMER_NAME

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

--description=DESCRIPTION

An optional, textual description for the interconnect.

--facility=FACILITY

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

--intent-mismatch-behavior=INTENT_MISMATCH_BEHAVIOR

The behavior when the intent of the interconnect group does not match thetopology capability of the member interconnects.INTENT_MISMATCH_BEHAVIOR must be one of:REJECT,CREATE.

--interconnect-type=INTERCONNECT_TYPE

Type of the interconnect.INTERCONNECT_TYPE must be oneof:

DEDICATED

Dedicated private interconnect.

PARTNER

Partner interconnect. Only available to approved partners.

--link-type=LINK_TYPE

Type of the link for the interconnect.LINK_TYPE must beone of:

LINK_TYPE_ETHERNET_100G_LR

100Gbps Ethernet, LR Optics.

LINK_TYPE_ETHERNET_10G_LR

10Gbps Ethernet, LR Optics.

LINK_TYPE_ETHERNET_400G_LR4

400Gbps Ethernet, LR4 Optics.

--noc-contact-email=NOC_CONTACT_EMAIL

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

--remote-location=REMOTE_LOCATION

The location of the interconnect for Cross-Cloud Interconnect.

--requested-features=[FEATURES,…]

List of features requested for this interconnect.FEATURES must be one of:

CROSS_SITE_NETWORK

If specified then the interconnect is created on Cross-Site Network capablehardware ports. This parameter can only be provided during interconnect INSERTand cannot be changed using interconnect PATCH.

L2_FORWARDING

If specified then the interconnect is created on L2 forwarding capable hardwareports. This parameter can only be provided during interconnect INSERT and cannotbe changed using interconnect PATCH.

MACSEC

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 andcannot be changed using interconnect PATCH.

--requested-link-count=REQUESTED_LINK_COUNT

Target number of physical links in the link bundle.

Run$gcloud help for details.