Reference documentation and code samples for the Compute V1 Client class WireGroupEndpointInterconnect.
The redundant Interconnect connections for this endpoint.
Generated from protobuf message google.cloud.compute.v1.WireGroupEndpointInterconnect
Namespace
Google \ Cloud \ Compute \ V1Methods
__construct
Constructor.
data
array
Optional. Data for populating the Message object.
↳ interconnect
string
Required. An Interconnect connection. You can specify the connection as a partial or full URL. If the connection is in a different project from the cross-site network, use a format that specifies the project. See the following examples of partial and full URLs: global/interconnects/NAME projects/PROJECT_ID/global/interconnects/NAME - https://compute.googleapis.com/compute/projects/PROJECT_ID/global/interconnects/NAME
↳ vlan_tags
array
Required. To configure the wire group for VLAN mode, enter a VLAN tag, which is a number from 2
to 4093
. You can autoallocate a tag by entering 0
. To configure the wire group for port mode, enter -1
. Review the following guidelines: - A VLAN tag must be unique for an Interconnect connection across all attachments and wire groups. - Both endpoints of a wire must use the same VLAN tag value. - Single wire and redundant type wire groups must have only one VLAN tag. - Port mode pseudowires must have a single VLAN tag with a value of -1
for both endpoints. - Box and cross type wire groups must have two VLAN tags. The first is for the same-zone pseudowire, and the second is for the cross-zone pseudowire.
getInterconnect
Required. An Interconnect connection. You can specify the connection as a partial or full URL. If the connection is in a different project from the cross-site network, use a format that specifies the project. See the following examples of partial and full URLs: global/interconnects/NAME projects/PROJECT_ID/global/interconnects/NAME - https://compute.googleapis.com/compute/projects/PROJECT_ID/global/interconnects/NAME
string
hasInterconnect
clearInterconnect
setInterconnect
Required. An Interconnect connection. You can specify the connection as a partial or full URL. If the connection is in a different project from the cross-site network, use a format that specifies the project. See the following examples of partial and full URLs: global/interconnects/NAME projects/PROJECT_ID/global/interconnects/NAME - https://compute.googleapis.com/compute/projects/PROJECT_ID/global/interconnects/NAME
var
string
$this
getVlanTags
Required. To configure the wire group for VLAN mode, enter a VLAN tag,
which is a number from 2
to 4093
. You can autoallocate a tag by
entering 0
. To configure the wire group for port mode, enter -1
.
Review the following guidelines:
- A VLAN tag must be unique for an Interconnect connection across all attachments and wire groups.
- Both endpoints of a wire must use the same VLAN tag value.
- Single wire and redundant type wire groups must have only one VLAN tag.
- Port mode pseudowires must have a single VLAN tag with a value of
-1for both endpoints. - Box and cross type wire groups must have two VLAN tags. The first is for the same-zone pseudowire, and the second is for the cross-zone pseudowire.
setVlanTags
Required. To configure the wire group for VLAN mode, enter a VLAN tag,
which is a number from 2
to 4093
. You can autoallocate a tag by
entering 0
. To configure the wire group for port mode, enter -1
.
Review the following guidelines:
- A VLAN tag must be unique for an Interconnect connection across all attachments and wire groups.
- Both endpoints of a wire must use the same VLAN tag value.
- Single wire and redundant type wire groups must have only one VLAN tag.
- Port mode pseudowires must have a single VLAN tag with a value of
-1for both endpoints. - Box and cross type wire groups must have two VLAN tags. The first is for the same-zone pseudowire, and the second is for the cross-zone pseudowire.
var
int[]
$this
