Equinix v0.18.0 published on Monday, Sep 23, 2024 by Equinix
equinix.metal.getVirtualCircuit
Explore with Pulumi AI
Use this data source to retrieve a virtual circuit resource from Equinix Fabric - software-defined interconnections
See the Virtual Routing and Forwarding documentation for product details and API reference material.
Using getVirtualCircuit
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getVirtualCircuit(args: GetVirtualCircuitArgs, opts?: InvokeOptions): Promise<GetVirtualCircuitResult>
function getVirtualCircuitOutput(args: GetVirtualCircuitOutputArgs, opts?: InvokeOptions): Output<GetVirtualCircuitResult>
def get_virtual_circuit(customer_ipv6: Optional[str] = None,
metal_ipv6: Optional[str] = None,
subnet_ipv6: Optional[str] = None,
virtual_circuit_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetVirtualCircuitResult
def get_virtual_circuit_output(customer_ipv6: Optional[pulumi.Input[str]] = None,
metal_ipv6: Optional[pulumi.Input[str]] = None,
subnet_ipv6: Optional[pulumi.Input[str]] = None,
virtual_circuit_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetVirtualCircuitResult]
func LookupVirtualCircuit(ctx *Context, args *LookupVirtualCircuitArgs, opts ...InvokeOption) (*LookupVirtualCircuitResult, error)
func LookupVirtualCircuitOutput(ctx *Context, args *LookupVirtualCircuitOutputArgs, opts ...InvokeOption) LookupVirtualCircuitResultOutput
> Note: This function is named LookupVirtualCircuit
in the Go SDK.
public static class GetVirtualCircuit
{
public static Task<GetVirtualCircuitResult> InvokeAsync(GetVirtualCircuitArgs args, InvokeOptions? opts = null)
public static Output<GetVirtualCircuitResult> Invoke(GetVirtualCircuitInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetVirtualCircuitResult> getVirtualCircuit(GetVirtualCircuitArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: equinix:metal/getVirtualCircuit:getVirtualCircuit
arguments:
# arguments dictionary
The following arguments are supported:
- Virtual
Circuit stringId - ID of the virtual circuit to lookup
- Customer
Ipv6 string - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- Metal
Ipv6 string - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- Subnet
Ipv6 string - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- Virtual
Circuit stringId - ID of the virtual circuit to lookup
- Customer
Ipv6 string - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- Metal
Ipv6 string - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- Subnet
Ipv6 string - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- virtual
Circuit StringId - ID of the virtual circuit to lookup
- customer
Ipv6 String - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal
Ipv6 String - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet
Ipv6 String - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- virtual
Circuit stringId - ID of the virtual circuit to lookup
- customer
Ipv6 string - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal
Ipv6 string - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet
Ipv6 string - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- virtual_
circuit_ strid - ID of the virtual circuit to lookup
- customer_
ipv6 str - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal_
ipv6 str - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet_
ipv6 str - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- virtual
Circuit StringId - ID of the virtual circuit to lookup
- customer
Ipv6 String - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal
Ipv6 String - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet
Ipv6 String - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
getVirtualCircuit Result
The following output properties are available:
- Connection
Id string - UUID of Connection where the VC is scoped to
- Customer
Ip string - The Customer IP address which the CSR switch will peer with. Will default to the other usable IP in the subnet.
- Description string
- Description of the virtual circuit
- Id string
- The provider-assigned unique ID for this managed resource.
- Md5 string
- The password that can be set for the VRF BGP peer
- Metal
Ip string - The Metal IP address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the subnet.
- Name string
- Name of the virtual circuit
- Nni
Vlan int - Nni VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- Nni
Vnid int - Nni VLAN ID parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- Peer
Asn int - The BGP ASN of the peer. The same ASN may be the used across several VCs, but it cannot be the same as the local_asn of the VRF.
- Port
Id string - UUID of the Connection Port where the VC is scoped to
- Project
Id string - ID of the projct to which the virtual circuit belongs
- Speed string
- Description of the Virtual Circuit speed. This is for information purposes and is computed when the connection type is shared.
- Status string
- Status of the virtual circuit
- Subnet string
- A subnet from one of the IP blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /30 or /31. * For a /31 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /30 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- List<string>
- Tags attached to the virtual circuit
- Virtual
Circuit stringId - ID of the virtual circuit to lookup
- Vlan
Id string - UUID of the associated VLAN
- Vnid int
- VNID VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- Vrf
Id string - UUID of the associated VRF
- Customer
Ipv6 string - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- Metal
Ipv6 string - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- Subnet
Ipv6 string - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- Connection
Id string - UUID of Connection where the VC is scoped to
- Customer
Ip string - The Customer IP address which the CSR switch will peer with. Will default to the other usable IP in the subnet.
- Description string
- Description of the virtual circuit
- Id string
- The provider-assigned unique ID for this managed resource.
- Md5 string
- The password that can be set for the VRF BGP peer
- Metal
Ip string - The Metal IP address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the subnet.
- Name string
- Name of the virtual circuit
- Nni
Vlan int - Nni VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- Nni
Vnid int - Nni VLAN ID parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- Peer
Asn int - The BGP ASN of the peer. The same ASN may be the used across several VCs, but it cannot be the same as the local_asn of the VRF.
- Port
Id string - UUID of the Connection Port where the VC is scoped to
- Project
Id string - ID of the projct to which the virtual circuit belongs
- Speed string
- Description of the Virtual Circuit speed. This is for information purposes and is computed when the connection type is shared.
- Status string
- Status of the virtual circuit
- Subnet string
- A subnet from one of the IP blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /30 or /31. * For a /31 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /30 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- []string
- Tags attached to the virtual circuit
- Virtual
Circuit stringId - ID of the virtual circuit to lookup
- Vlan
Id string - UUID of the associated VLAN
- Vnid int
- VNID VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- Vrf
Id string - UUID of the associated VRF
- Customer
Ipv6 string - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- Metal
Ipv6 string - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- Subnet
Ipv6 string - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- connection
Id String - UUID of Connection where the VC is scoped to
- customer
Ip String - The Customer IP address which the CSR switch will peer with. Will default to the other usable IP in the subnet.
- description String
- Description of the virtual circuit
- id String
- The provider-assigned unique ID for this managed resource.
- md5 String
- The password that can be set for the VRF BGP peer
- metal
Ip String - The Metal IP address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the subnet.
- name String
- Name of the virtual circuit
- nni
Vlan Integer - Nni VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- nni
Vnid Integer - Nni VLAN ID parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- peer
Asn Integer - The BGP ASN of the peer. The same ASN may be the used across several VCs, but it cannot be the same as the local_asn of the VRF.
- port
Id String - UUID of the Connection Port where the VC is scoped to
- project
Id String - ID of the projct to which the virtual circuit belongs
- speed String
- Description of the Virtual Circuit speed. This is for information purposes and is computed when the connection type is shared.
- status String
- Status of the virtual circuit
- subnet String
- A subnet from one of the IP blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /30 or /31. * For a /31 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /30 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- List<String>
- Tags attached to the virtual circuit
- virtual
Circuit StringId - ID of the virtual circuit to lookup
- vlan
Id String - UUID of the associated VLAN
- vnid Integer
- VNID VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- vrf
Id String - UUID of the associated VRF
- customer
Ipv6 String - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal
Ipv6 String - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet
Ipv6 String - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- connection
Id string - UUID of Connection where the VC is scoped to
- customer
Ip string - The Customer IP address which the CSR switch will peer with. Will default to the other usable IP in the subnet.
- description string
- Description of the virtual circuit
- id string
- The provider-assigned unique ID for this managed resource.
- md5 string
- The password that can be set for the VRF BGP peer
- metal
Ip string - The Metal IP address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the subnet.
- name string
- Name of the virtual circuit
- nni
Vlan number - Nni VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- nni
Vnid number - Nni VLAN ID parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- peer
Asn number - The BGP ASN of the peer. The same ASN may be the used across several VCs, but it cannot be the same as the local_asn of the VRF.
- port
Id string - UUID of the Connection Port where the VC is scoped to
- project
Id string - ID of the projct to which the virtual circuit belongs
- speed string
- Description of the Virtual Circuit speed. This is for information purposes and is computed when the connection type is shared.
- status string
- Status of the virtual circuit
- subnet string
- A subnet from one of the IP blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /30 or /31. * For a /31 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /30 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- string[]
- Tags attached to the virtual circuit
- virtual
Circuit stringId - ID of the virtual circuit to lookup
- vlan
Id string - UUID of the associated VLAN
- vnid number
- VNID VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- vrf
Id string - UUID of the associated VRF
- customer
Ipv6 string - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal
Ipv6 string - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet
Ipv6 string - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- connection_
id str - UUID of Connection where the VC is scoped to
- customer_
ip str - The Customer IP address which the CSR switch will peer with. Will default to the other usable IP in the subnet.
- description str
- Description of the virtual circuit
- id str
- The provider-assigned unique ID for this managed resource.
- md5 str
- The password that can be set for the VRF BGP peer
- metal_
ip str - The Metal IP address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the subnet.
- name str
- Name of the virtual circuit
- nni_
vlan int - Nni VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- nni_
vnid int - Nni VLAN ID parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- peer_
asn int - The BGP ASN of the peer. The same ASN may be the used across several VCs, but it cannot be the same as the local_asn of the VRF.
- port_
id str - UUID of the Connection Port where the VC is scoped to
- project_
id str - ID of the projct to which the virtual circuit belongs
- speed str
- Description of the Virtual Circuit speed. This is for information purposes and is computed when the connection type is shared.
- status str
- Status of the virtual circuit
- subnet str
- A subnet from one of the IP blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /30 or /31. * For a /31 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /30 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- Sequence[str]
- Tags attached to the virtual circuit
- virtual_
circuit_ strid - ID of the virtual circuit to lookup
- vlan_
id str - UUID of the associated VLAN
- vnid int
- VNID VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- vrf_
id str - UUID of the associated VRF
- customer_
ipv6 str - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal_
ipv6 str - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet_
ipv6 str - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- connection
Id String - UUID of Connection where the VC is scoped to
- customer
Ip String - The Customer IP address which the CSR switch will peer with. Will default to the other usable IP in the subnet.
- description String
- Description of the virtual circuit
- id String
- The provider-assigned unique ID for this managed resource.
- md5 String
- The password that can be set for the VRF BGP peer
- metal
Ip String - The Metal IP address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the subnet.
- name String
- Name of the virtual circuit
- nni
Vlan Number - Nni VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- nni
Vnid Number - Nni VLAN ID parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- peer
Asn Number - The BGP ASN of the peer. The same ASN may be the used across several VCs, but it cannot be the same as the local_asn of the VRF.
- port
Id String - UUID of the Connection Port where the VC is scoped to
- project
Id String - ID of the projct to which the virtual circuit belongs
- speed String
- Description of the Virtual Circuit speed. This is for information purposes and is computed when the connection type is shared.
- status String
- Status of the virtual circuit
- subnet String
- A subnet from one of the IP blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /30 or /31. * For a /31 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /30 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
- List<String>
- Tags attached to the virtual circuit
- virtual
Circuit StringId - ID of the virtual circuit to lookup
- vlan
Id String - UUID of the associated VLAN
- vnid Number
- VNID VLAN parameter, see https://deploy.equinix.com/developers/docs/metal/interconnections/introduction/
- vrf
Id String - UUID of the associated VRF
- customer
Ipv6 String - The Customer IPv6 address which the CSR switch will peer with. Will default to the other usable IP in the IPv6 subnet.
- metal
Ipv6 String - The Metal IPv6 address for the SVI (Switch Virtual Interface) of the VirtualCircuit. Will default to the first usable IP in the IPv6 subnet.
- subnet
Ipv6 String - A subnet from one of the IPv6 blocks associated with the VRF that we will help create an IP reservation for. Can only be either a /126 or /127. * For a /127 block, it will only have two IP addresses, which will be used for the metalip and customerip. * For a /126 block, it will have four IP addresses, but the first and last IP addresses are not usable. We will default to the first usable IP address for the metal_ip.
Package Details
- Repository
- equinix equinix/pulumi-equinix
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
equinix
Terraform Provider.