@Generated(value="OracleSDKGenerator", comments="API Version: 20160918") public interface VirtualNetworkAsync extends AutoCloseable
close
void setEndpoint(String endpoint)
Sets the endpoint to call (ex, https://www.example.com).
endpoint
- The endpoint of the serice.void setRegion(Region region)
Sets the region to call (ex, Region.US_PHOENIX_1).
Note, this will call setEndpoint
after resolving the endpoint. If the service is not available in this region, however, an IllegalArgumentException will be raised.
region
- The region of the service.void setRegion(String regionId)
Sets the region to call (ex, ‘us-phoenix-1’).
Note, this will first try to map the region ID to a known Region and call setRegion
.
If no known Region could be determined, it will create an endpoint based on the default endpoint format (Region.formatDefaultRegionEndpoint(Service, String)
and then call setEndpoint
.
regionId
- The public region ID.Future<AttachServiceIdResponse> attachServiceId(AttachServiceIdRequest request, AsyncHandler<AttachServiceIdRequest,AttachServiceIdResponse> handler)
Adds the specified Service
to the list of enabled Service
objects for the specified gateway. You must also set up a route rule with the cidrBlock
of the Service
as the rule’s destination and the service gateway as the rule’s target. See RouteTable
.
Note:** The AttachServiceId
operation is an easy way to add an individual Service
to the service gateway. Compare it with updateServiceGateway
, which replaces the entire existing list of enabled Service
objects with the list that you provide in the Update
call.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<BulkAddVirtualCircuitPublicPrefixesResponse> bulkAddVirtualCircuitPublicPrefixes(BulkAddVirtualCircuitPublicPrefixesRequest request, AsyncHandler<BulkAddVirtualCircuitPublicPrefixesRequest,BulkAddVirtualCircuitPublicPrefixesResponse> handler)
Adds one or more customer public IP prefixes to the specified public virtual circuit. Use this operation (and not updateVirtualCircuit
) to add prefixes to the virtual circuit. Oracle must verify the customer’s ownership of each prefix before traffic for that prefix will flow across the virtual circuit.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<BulkDeleteVirtualCircuitPublicPrefixesResponse> bulkDeleteVirtualCircuitPublicPrefixes(BulkDeleteVirtualCircuitPublicPrefixesRequest request, AsyncHandler<BulkDeleteVirtualCircuitPublicPrefixesRequest,BulkDeleteVirtualCircuitPublicPrefixesResponse> handler)
Removes one or more customer public IP prefixes from the specified public virtual circuit. Use this operation (and not updateVirtualCircuit
) to remove prefixes from the virtual circuit. When the virtual circuit’s state switches back to PROVISIONED, Oracle stops advertising the specified prefixes across the connection.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ConnectLocalPeeringGatewaysResponse> connectLocalPeeringGateways(ConnectLocalPeeringGatewaysRequest request, AsyncHandler<ConnectLocalPeeringGatewaysRequest,ConnectLocalPeeringGatewaysResponse> handler)
Connects this local peering gateway (LPG) to another one in the same region.
This operation must be called by the VCN administrator who is designated as the requestor in the peering relationship. The acceptor must implement an Identity and Access Management (IAM) policy that gives the requestor permission to connect to LPGs in the acceptor’s compartment. Without that permission, this operation will fail. For more information, see VCN Peering.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ConnectRemotePeeringConnectionsResponse> connectRemotePeeringConnections(ConnectRemotePeeringConnectionsRequest request, AsyncHandler<ConnectRemotePeeringConnectionsRequest,ConnectRemotePeeringConnectionsResponse> handler)
Connects this RPC to another one in a different region.
This operation must be called by the VCN administrator who is designated as the requestor in the peering relationship. The acceptor must implement an Identity and Access Management (IAM) policy that gives the requestor permission to connect to RPCs in the acceptor’s compartment. Without that permission, this operation will fail. For more information, see VCN Peering.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateCpeResponse> createCpe(CreateCpeRequest request, AsyncHandler<CreateCpeRequest,CreateCpeResponse> handler)
Creates a new virtual customer-premises equipment (CPE) object in the specified compartment. For more information, see IPSec VPNs.
For the purposes of access control, you must provide the OCID of the compartment where you want the CPE to reside. Notice that the CPE doesn’t have to be in the same compartment as the IPSec connection or other Networking Service components. If you’re not sure which compartment to use, put the CPE in the same compartment as the DRG. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You must provide the public IP address of your on-premises router. See Configuring Your On-Premises Router for an IPSec VPN.
You may optionally specify a display name for the CPE, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateCrossConnectResponse> createCrossConnect(CreateCrossConnectRequest request, AsyncHandler<CreateCrossConnectRequest,CreateCrossConnectResponse> handler)
Creates a new cross-connect. Oracle recommends you create each cross-connect in a CrossConnectGroup
so you can use link aggregation with the connection.
After creating the CrossConnect
object, you need to go the FastConnect location and request to have the physical cable installed. For more information, see FastConnect Overview.
For the purposes of access control, you must provide the OCID of the compartment where you want the cross-connect to reside. If you’re not sure which compartment to use, put the cross-connect in the same compartment with your VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the cross-connect. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateCrossConnectGroupResponse> createCrossConnectGroup(CreateCrossConnectGroupRequest request, AsyncHandler<CreateCrossConnectGroupRequest,CreateCrossConnectGroupResponse> handler)
Creates a new cross-connect group to use with Oracle Cloud Infrastructure FastConnect. For more information, see FastConnect Overview.
For the purposes of access control, you must provide the OCID of the compartment where you want the cross-connect group to reside. If you’re not sure which compartment to use, put the cross-connect group in the same compartment with your VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the cross-connect group. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateDhcpOptionsResponse> createDhcpOptions(CreateDhcpOptionsRequest request, AsyncHandler<CreateDhcpOptionsRequest,CreateDhcpOptionsResponse> handler)
Creates a new set of DHCP options for the specified VCN. For more information, see DhcpOptions
.
For the purposes of access control, you must provide the OCID of the compartment where you want the set of DHCP options to reside. Notice that the set of options doesn’t have to be in the same compartment as the VCN, subnets, or other Networking Service components. If you’re not sure which compartment to use, put the set of DHCP options in the same compartment as the VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the set of DHCP options, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateDrgResponse> createDrg(CreateDrgRequest request, AsyncHandler<CreateDrgRequest,CreateDrgResponse> handler)
Creates a new dynamic routing gateway (DRG) in the specified compartment. For more information, see Dynamic Routing Gateways (DRGs).
For the purposes of access control, you must provide the OCID of the compartment where you want the DRG to reside. Notice that the DRG doesn’t have to be in the same compartment as the VCN, the DRG attachment, or other Networking Service components. If you’re not sure which compartment to use, put the DRG in the same compartment as the VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the DRG, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateDrgAttachmentResponse> createDrgAttachment(CreateDrgAttachmentRequest request, AsyncHandler<CreateDrgAttachmentRequest,CreateDrgAttachmentResponse> handler)
Attaches the specified DRG to the specified VCN. A VCN can be attached to only one DRG at a time, and vice versa. The response includes a DrgAttachment
object with its own OCID. For more information about DRGs, see Dynamic Routing Gateways (DRGs).
You may optionally specify a display name for the attachment, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
For the purposes of access control, the DRG attachment is automatically placed into the same compartment as the VCN. For more information about compartments and access control, see Overview of the IAM Service.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateIPSecConnectionResponse> createIPSecConnection(CreateIPSecConnectionRequest request, AsyncHandler<CreateIPSecConnectionRequest,CreateIPSecConnectionResponse> handler)
Creates a new IPSec connection between the specified DRG and CPE. For more information, see IPSec VPNs.
If you configure at least one tunnel to use static routing, then in the request you must provide at least one valid static route (you’re allowed a maximum of 10). For example: 10.0.0.0/16. If you configure both tunnels to use BGP dynamic routing, you can provide an empty list for the static routes. For more information, see the important note in IPSecConnection
.
For the purposes of access control, you must provide the OCID of the compartment where you want the IPSec connection to reside. Notice that the IPSec connection doesn’t have to be in the same compartment as the DRG, CPE, or other Networking Service components. If you’re not sure which compartment to use, put the IPSec connection in the same compartment as the DRG. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the IPSec connection, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
After creating the IPSec connection, you need to configure your on-premises router with tunnel-specific information. For tunnel status and the required configuration information, see:
IPSecConnectionTunnel
* IPSecConnectionTunnelSharedSecret
For each tunnel, you need the IP address of Oracle’s VPN headend and the shared secret (that is, the pre-shared key). For more information, see Configuring Your On-Premises Router for an IPSec VPN.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateInternetGatewayResponse> createInternetGateway(CreateInternetGatewayRequest request, AsyncHandler<CreateInternetGatewayRequest,CreateInternetGatewayResponse> handler)
Creates a new internet gateway for the specified VCN. For more information, see Access to the Internet.
For the purposes of access control, you must provide the OCID of the compartment where you want the Internet Gateway to reside. Notice that the internet gateway doesn’t have to be in the same compartment as the VCN or other Networking Service components. If you’re not sure which compartment to use, put the Internet Gateway in the same compartment with the VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the internet gateway, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
For traffic to flow between a subnet and an internet gateway, you must create a route rule accordingly in the subnet’s route table (for example, 0.0.0.0/0 > internet gateway). See updateRouteTable
.
You must specify whether the internet gateway is enabled when you create it. If it’s disabled, that means no traffic will flow to/from the internet even if there’s a route rule that enables that traffic. You can later use updateInternetGateway
to easily disable/enable the gateway without changing the route rule.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateLocalPeeringGatewayResponse> createLocalPeeringGateway(CreateLocalPeeringGatewayRequest request, AsyncHandler<CreateLocalPeeringGatewayRequest,CreateLocalPeeringGatewayResponse> handler)
Creates a new local peering gateway (LPG) for the specified VCN.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateNatGatewayResponse> createNatGateway(CreateNatGatewayRequest request, AsyncHandler<CreateNatGatewayRequest,CreateNatGatewayResponse> handler)
Creates a new NAT gateway for the specified VCN. You must also set up a route rule with the NAT gateway as the rule’s target. See RouteTable
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreatePrivateIpResponse> createPrivateIp(CreatePrivateIpRequest request, AsyncHandler<CreatePrivateIpRequest,CreatePrivateIpResponse> handler)
Creates a secondary private IP for the specified VNIC. For more information about secondary private IPs, see IP Addresses.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreatePublicIpResponse> createPublicIp(CreatePublicIpRequest request, AsyncHandler<CreatePublicIpRequest,CreatePublicIpResponse> handler)
Creates a public IP. Use the lifetime
property to specify whether it’s an ephemeral or reserved public IP. For information about limits on how many you can create, see Public IP Addresses.
For an ephemeral public IP assigned to a private IP: You must also specify a privateIpId
with the OCID of the primary private IP you want to assign the public IP to. The public IP is created in the same availability domain as the private IP. An ephemeral public IP must always be assigned to a private IP, and only to the primary private IP on a VNIC, not a secondary private IP. Exception: If you create a NatGateway
, Oracle automatically assigns the NAT gateway a regional ephemeral public IP that you cannot remove.
For a reserved public IP: You may also optionally assign the public IP to a private IP by specifying privateIpId
. Or you can later assign the public IP with updatePublicIp
.
Note:** When assigning a public IP to a private IP, the private IP must not already have a public IP with lifecycleState
= ASSIGNING or ASSIGNED. If it does, an error is returned.
Also, for reserved public IPs, the optional assignment part of this operation is asynchronous. Poll the public IP’s lifecycleState
to determine if the assignment succeeded.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateRemotePeeringConnectionResponse> createRemotePeeringConnection(CreateRemotePeeringConnectionRequest request, AsyncHandler<CreateRemotePeeringConnectionRequest,CreateRemotePeeringConnectionResponse> handler)
Creates a new remote peering connection (RPC) for the specified DRG.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateRouteTableResponse> createRouteTable(CreateRouteTableRequest request, AsyncHandler<CreateRouteTableRequest,CreateRouteTableResponse> handler)
Creates a new route table for the specified VCN. In the request you must also include at least one route rule for the new route table. For information on the number of rules you can have in a route table, see Service Limits. For general information about route tables in your VCN and the types of targets you can use in route rules, see Route Tables.
For the purposes of access control, you must provide the OCID of the compartment where you want the route table to reside. Notice that the route table doesn’t have to be in the same compartment as the VCN, subnets, or other Networking Service components. If you’re not sure which compartment to use, put the route table in the same compartment as the VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the route table, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateSecurityListResponse> createSecurityList(CreateSecurityListRequest request, AsyncHandler<CreateSecurityListRequest,CreateSecurityListResponse> handler)
Creates a new security list for the specified VCN. For more information about security lists, see Security Lists. For information on the number of rules you can have in a security list, see Service Limits.
For the purposes of access control, you must provide the OCID of the compartment where you want the security list to reside. Notice that the security list doesn’t have to be in the same compartment as the VCN, subnets, or other Networking Service components. If you’re not sure which compartment to use, put the security list in the same compartment as the VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the security list, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateServiceGatewayResponse> createServiceGateway(CreateServiceGatewayRequest request, AsyncHandler<CreateServiceGatewayRequest,CreateServiceGatewayResponse> handler)
Creates a new service gateway in the specified compartment.
For the purposes of access control, you must provide the OCID of the compartment where you want the service gateway to reside. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the service gateway, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateSubnetResponse> createSubnet(CreateSubnetRequest request, AsyncHandler<CreateSubnetRequest,CreateSubnetResponse> handler)
Creates a new subnet in the specified VCN. You can’t change the size of the subnet after creation, so it’s important to think about the size of subnets you need before creating them. For more information, see VCNs and Subnets. For information on the number of subnets you can have in a VCN, see Service Limits.
For the purposes of access control, you must provide the OCID of the compartment where you want the subnet to reside. Notice that the subnet doesn’t have to be in the same compartment as the VCN, route tables, or other Networking Service components. If you’re not sure which compartment to use, put the subnet in the same compartment as the VCN. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally associate a route table with the subnet. If you don’t, the subnet will use the VCN’s default route table. For more information about route tables, see Route Tables.
You may optionally associate a security list with the subnet. If you don’t, the subnet will use the VCN’s default security list. For more information about security lists, see Security Lists.
You may optionally associate a set of DHCP options with the subnet. If you don’t, the subnet will use the VCN’s default set. For more information about DHCP options, see DHCP Options.
You may optionally specify a display name for the subnet, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
You can also add a DNS label for the subnet, which is required if you want the Internet and VCN Resolver to resolve hostnames for instances in the subnet. For more information, see DNS in Your Virtual Cloud Network.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateVcnResponse> createVcn(CreateVcnRequest request, AsyncHandler<CreateVcnRequest,CreateVcnResponse> handler)
Creates a new virtual cloud network (VCN). For more information, see VCNs and Subnets.
For the VCN you must specify a single, contiguous IPv4 CIDR block. Oracle recommends using one of the private IP address ranges specified in RFC 1918 (10.0.0.0/8, 172.16/12, and 192.168/16). Example: 172.16.0.0/16. The CIDR block can range from /16 to /30, and it must not overlap with your on-premises network. You can’t change the size of the VCN after creation.
For the purposes of access control, you must provide the OCID of the compartment where you want the VCN to reside. Consult an Oracle Cloud Infrastructure administrator in your organization if you’re not sure which compartment to use. Notice that the VCN doesn’t have to be in the same compartment as the subnets or other Networking Service components. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the VCN, otherwise a default is provided. It does not have to be unique, and you can change it. Avoid entering confidential information.
You can also add a DNS label for the VCN, which is required if you want the instances to use the Interent and VCN Resolver option for DNS in the VCN. For more information, see DNS in Your Virtual Cloud Network.
The VCN automatically comes with a default route table, default security list, and default set of DHCP options. The OCID for each is returned in the response. You can’t delete these default objects, but you can change their contents (that is, change the route rules, security list rules, and so on).
The VCN and subnets you create are not accessible until you attach an internet gateway or set up an IPSec VPN or FastConnect. For more information, see Overview of the Networking Service.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<CreateVirtualCircuitResponse> createVirtualCircuit(CreateVirtualCircuitRequest request, AsyncHandler<CreateVirtualCircuitRequest,CreateVirtualCircuitResponse> handler)
Creates a new virtual circuit to use with Oracle Cloud Infrastructure FastConnect. For more information, see FastConnect Overview.
For the purposes of access control, you must provide the OCID of the compartment where you want the virtual circuit to reside. If you’re not sure which compartment to use, put the virtual circuit in the same compartment with the DRG it’s using. For more information about compartments and access control, see Overview of the IAM Service. For information about OCIDs, see Resource Identifiers.
You may optionally specify a display name for the virtual circuit. It does not have to be unique, and you can change it. Avoid entering confidential information.
Important:** When creating a virtual circuit, you specify a DRG for the traffic to flow through. Make sure you attach the DRG to your VCN and confirm the VCN’s routing sends traffic to the DRG. Otherwise traffic will not flow. For more information, see Route Tables.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteCpeResponse> deleteCpe(DeleteCpeRequest request, AsyncHandler<DeleteCpeRequest,DeleteCpeResponse> handler)
Deletes the specified CPE object. The CPE must not be connected to a DRG. This is an asynchronous operation. The CPE’s lifecycleState
will change to TERMINATING temporarily until the CPE is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteCrossConnectResponse> deleteCrossConnect(DeleteCrossConnectRequest request, AsyncHandler<DeleteCrossConnectRequest,DeleteCrossConnectResponse> handler)
Deletes the specified cross-connect. It must not be mapped to a VirtualCircuit
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteCrossConnectGroupResponse> deleteCrossConnectGroup(DeleteCrossConnectGroupRequest request, AsyncHandler<DeleteCrossConnectGroupRequest,DeleteCrossConnectGroupResponse> handler)
Deletes the specified cross-connect group. It must not contain any cross-connects, and it cannot be mapped to a VirtualCircuit
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteDhcpOptionsResponse> deleteDhcpOptions(DeleteDhcpOptionsRequest request, AsyncHandler<DeleteDhcpOptionsRequest,DeleteDhcpOptionsResponse> handler)
Deletes the specified set of DHCP options, but only if it’s not associated with a subnet. You can’t delete a VCN’s default set of DHCP options.
This is an asynchronous operation. The state of the set of options will switch to TERMINATING temporarily until the set is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteDrgResponse> deleteDrg(DeleteDrgRequest request, AsyncHandler<DeleteDrgRequest,DeleteDrgResponse> handler)
Deletes the specified DRG. The DRG must not be attached to a VCN or be connected to your on-premise network. Also, there must not be a route table that lists the DRG as a target. This is an asynchronous operation. The DRG’s lifecycleState
will change to TERMINATING temporarily until the DRG is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteDrgAttachmentResponse> deleteDrgAttachment(DeleteDrgAttachmentRequest request, AsyncHandler<DeleteDrgAttachmentRequest,DeleteDrgAttachmentResponse> handler)
Detaches a DRG from a VCN by deleting the corresponding DrgAttachment
. This is an asynchronous operation. The attachment’s lifecycleState
will change to DETACHING temporarily until the attachment is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteIPSecConnectionResponse> deleteIPSecConnection(DeleteIPSecConnectionRequest request, AsyncHandler<DeleteIPSecConnectionRequest,DeleteIPSecConnectionResponse> handler)
Deletes the specified IPSec connection. If your goal is to disable the IPSec VPN between your VCN and on-premises network, it’s easiest to simply detach the DRG but keep all the IPSec VPN components intact. If you were to delete all the components and then later need to create an IPSec VPN again, you would need to configure your on-premises router again with the new information returned from createIPSecConnection
.
This is an asynchronous operation. The connection’s lifecycleState
will change to TERMINATING temporarily until the connection is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteInternetGatewayResponse> deleteInternetGateway(DeleteInternetGatewayRequest request, AsyncHandler<DeleteInternetGatewayRequest,DeleteInternetGatewayResponse> handler)
Deletes the specified internet gateway. The internet gateway does not have to be disabled, but there must not be a route table that lists it as a target.
This is an asynchronous operation. The gateway’s lifecycleState
will change to TERMINATING temporarily until the gateway is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteLocalPeeringGatewayResponse> deleteLocalPeeringGateway(DeleteLocalPeeringGatewayRequest request, AsyncHandler<DeleteLocalPeeringGatewayRequest,DeleteLocalPeeringGatewayResponse> handler)
Deletes the specified local peering gateway (LPG).
This is an asynchronous operation; the local peering gateway’s lifecycleState
changes to TERMINATING temporarily until the local peering gateway is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteNatGatewayResponse> deleteNatGateway(DeleteNatGatewayRequest request, AsyncHandler<DeleteNatGatewayRequest,DeleteNatGatewayResponse> handler)
Deletes the specified NAT gateway. The NAT gateway does not have to be disabled, but there must not be a route rule that lists the NAT gateway as a target.
This is an asynchronous operation. The NAT gateway’s lifecycleState
will change to TERMINATING temporarily until the NAT gateway is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeletePrivateIpResponse> deletePrivateIp(DeletePrivateIpRequest request, AsyncHandler<DeletePrivateIpRequest,DeletePrivateIpResponse> handler)
Unassigns and deletes the specified private IP. You must specify the object’s OCID. The private IP address is returned to the subnet’s pool of available addresses.
This operation cannot be used with primary private IPs, which are automatically unassigned and deleted when the VNIC is terminated.
Important:** If a secondary private IP is the target of a route rule, unassigning it from the VNIC causes that route rule to blackhole and the traffic will be dropped.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeletePublicIpResponse> deletePublicIp(DeletePublicIpRequest request, AsyncHandler<DeletePublicIpRequest,DeletePublicIpResponse> handler)
Unassigns and deletes the specified public IP (either ephemeral or reserved). You must specify the object’s OCID. The public IP address is returned to the Oracle Cloud Infrastructure public IP pool.
Note:** You cannot update, unassign, or delete the public IP that Oracle automatically assigned to an entity for you (such as a load balancer or NAT gateway). The public IP is automatically deleted if the assigned entity is terminated.
For an assigned reserved public IP, the initial unassignment portion of this operation is asynchronous. Poll the public IP’s lifecycleState
to determine if the operation succeeded.
If you want to simply unassign a reserved public IP and return it to your pool of reserved public IPs, instead use updatePublicIp
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteRemotePeeringConnectionResponse> deleteRemotePeeringConnection(DeleteRemotePeeringConnectionRequest request, AsyncHandler<DeleteRemotePeeringConnectionRequest,DeleteRemotePeeringConnectionResponse> handler)
Deletes the remote peering connection (RPC).
This is an asynchronous operation; the RPC’s lifecycleState
changes to TERMINATING temporarily until the RPC is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteRouteTableResponse> deleteRouteTable(DeleteRouteTableRequest request, AsyncHandler<DeleteRouteTableRequest,DeleteRouteTableResponse> handler)
Deletes the specified route table, but only if it’s not associated with a subnet. You can’t delete a VCN’s default route table.
This is an asynchronous operation. The route table’s lifecycleState
will change to TERMINATING temporarily until the route table is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteSecurityListResponse> deleteSecurityList(DeleteSecurityListRequest request, AsyncHandler<DeleteSecurityListRequest,DeleteSecurityListResponse> handler)
Deletes the specified security list, but only if it’s not associated with a subnet. You can’t delete a VCN’s default security list.
This is an asynchronous operation. The security list’s lifecycleState
will change to TERMINATING temporarily until the security list is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteServiceGatewayResponse> deleteServiceGateway(DeleteServiceGatewayRequest request, AsyncHandler<DeleteServiceGatewayRequest,DeleteServiceGatewayResponse> handler)
Deletes the specified service gateway. There must not be a route table that lists the service gateway as a target.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteSubnetResponse> deleteSubnet(DeleteSubnetRequest request, AsyncHandler<DeleteSubnetRequest,DeleteSubnetResponse> handler)
Deletes the specified subnet, but only if there are no instances in the subnet. This is an asynchronous operation. The subnet’s lifecycleState
will change to TERMINATING temporarily. If there are any instances in the subnet, the state will instead change back to AVAILABLE.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteVcnResponse> deleteVcn(DeleteVcnRequest request, AsyncHandler<DeleteVcnRequest,DeleteVcnResponse> handler)
Deletes the specified VCN. The VCN must be empty and have no attached gateways. This is an asynchronous operation. The VCN’s lifecycleState
will change to TERMINATING temporarily until the VCN is completely removed.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DeleteVirtualCircuitResponse> deleteVirtualCircuit(DeleteVirtualCircuitRequest request, AsyncHandler<DeleteVirtualCircuitRequest,DeleteVirtualCircuitResponse> handler)
Deletes the specified virtual circuit.
Important:** If you’re using FastConnect via a provider, make sure to also terminate the connection with the provider, or else the provider may continue to bill you.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<DetachServiceIdResponse> detachServiceId(DetachServiceIdRequest request, AsyncHandler<DetachServiceIdRequest,DetachServiceIdResponse> handler)
Removes the specified Service
from the list of enabled Service
objects for the specified gateway. You do not need to remove any route rules that specify this Service
object’s cidrBlock
as the destination CIDR. However, consider removing the rules if your intent is to permanently disable use of the Service
through this service gateway.
Note:** The DetachServiceId
operation is an easy way to remove an individual Service
from the service gateway. Compare it with updateServiceGateway
, which replaces the entire existing list of enabled Service
objects with the list that you provide in the Update
call. UpdateServiceGateway
also lets you block all traffic through the service gateway without having to remove each of the individual Service
objects.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetCpeResponse> getCpe(GetCpeRequest request, AsyncHandler<GetCpeRequest,GetCpeResponse> handler)
Gets the specified CPE’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetCrossConnectResponse> getCrossConnect(GetCrossConnectRequest request, AsyncHandler<GetCrossConnectRequest,GetCrossConnectResponse> handler)
Gets the specified cross-connect’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetCrossConnectGroupResponse> getCrossConnectGroup(GetCrossConnectGroupRequest request, AsyncHandler<GetCrossConnectGroupRequest,GetCrossConnectGroupResponse> handler)
Gets the specified cross-connect group’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetCrossConnectLetterOfAuthorityResponse> getCrossConnectLetterOfAuthority(GetCrossConnectLetterOfAuthorityRequest request, AsyncHandler<GetCrossConnectLetterOfAuthorityRequest,GetCrossConnectLetterOfAuthorityResponse> handler)
Gets the Letter of Authority for the specified cross-connect.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetCrossConnectStatusResponse> getCrossConnectStatus(GetCrossConnectStatusRequest request, AsyncHandler<GetCrossConnectStatusRequest,GetCrossConnectStatusResponse> handler)
Gets the status of the specified cross-connect.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetDhcpOptionsResponse> getDhcpOptions(GetDhcpOptionsRequest request, AsyncHandler<GetDhcpOptionsRequest,GetDhcpOptionsResponse> handler)
Gets the specified set of DHCP options.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetDrgResponse> getDrg(GetDrgRequest request, AsyncHandler<GetDrgRequest,GetDrgResponse> handler)
Gets the specified DRG’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetDrgAttachmentResponse> getDrgAttachment(GetDrgAttachmentRequest request, AsyncHandler<GetDrgAttachmentRequest,GetDrgAttachmentResponse> handler)
Gets the information for the specified DrgAttachment
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetFastConnectProviderServiceResponse> getFastConnectProviderService(GetFastConnectProviderServiceRequest request, AsyncHandler<GetFastConnectProviderServiceRequest,GetFastConnectProviderServiceResponse> handler)
Gets the specified provider service. For more information, see FastConnect Overview.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetFastConnectProviderServiceKeyResponse> getFastConnectProviderServiceKey(GetFastConnectProviderServiceKeyRequest request, AsyncHandler<GetFastConnectProviderServiceKeyRequest,GetFastConnectProviderServiceKeyResponse> handler)
Gets the specified provider service key’s information. Use this operation to validate a provider service key. An invalid key returns a 404 error.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetIPSecConnectionResponse> getIPSecConnection(GetIPSecConnectionRequest request, AsyncHandler<GetIPSecConnectionRequest,GetIPSecConnectionResponse> handler)
Gets the specified IPSec connection’s basic information, including the static routes for the on-premises router. If you want the status of the connection (whether it’s up or down), use getIPSecConnectionTunnel
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetIPSecConnectionDeviceConfigResponse> getIPSecConnectionDeviceConfig(GetIPSecConnectionDeviceConfigRequest request, AsyncHandler<GetIPSecConnectionDeviceConfigRequest,GetIPSecConnectionDeviceConfigResponse> handler)
Deprecated. To get tunnel information, instead use:
getIPSecConnectionTunnel
* getIPSecConnectionTunnelSharedSecret
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetIPSecConnectionDeviceStatusResponse> getIPSecConnectionDeviceStatus(GetIPSecConnectionDeviceStatusRequest request, AsyncHandler<GetIPSecConnectionDeviceStatusRequest,GetIPSecConnectionDeviceStatusResponse> handler)
Deprecated. To get the tunnel status, instead use getIPSecConnectionTunnel
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetIPSecConnectionTunnelResponse> getIPSecConnectionTunnel(GetIPSecConnectionTunnelRequest request, AsyncHandler<GetIPSecConnectionTunnelRequest,GetIPSecConnectionTunnelResponse> handler)
Gets the specified tunnel’s information. The resulting object does not include the tunnel’s shared secret (pre-shared key). To retrieve that, use getIPSecConnectionTunnelSharedSecret
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetIPSecConnectionTunnelSharedSecretResponse> getIPSecConnectionTunnelSharedSecret(GetIPSecConnectionTunnelSharedSecretRequest request, AsyncHandler<GetIPSecConnectionTunnelSharedSecretRequest,GetIPSecConnectionTunnelSharedSecretResponse> handler)
Gets the specified tunnel’s shared secret (pre-shared key). To get other information about the tunnel, use getIPSecConnectionTunnel
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetInternetGatewayResponse> getInternetGateway(GetInternetGatewayRequest request, AsyncHandler<GetInternetGatewayRequest,GetInternetGatewayResponse> handler)
Gets the specified internet gateway’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetLocalPeeringGatewayResponse> getLocalPeeringGateway(GetLocalPeeringGatewayRequest request, AsyncHandler<GetLocalPeeringGatewayRequest,GetLocalPeeringGatewayResponse> handler)
Gets the specified local peering gateway’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetNatGatewayResponse> getNatGateway(GetNatGatewayRequest request, AsyncHandler<GetNatGatewayRequest,GetNatGatewayResponse> handler)
Gets the specified NAT gateway’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetPrivateIpResponse> getPrivateIp(GetPrivateIpRequest request, AsyncHandler<GetPrivateIpRequest,GetPrivateIpResponse> handler)
Gets the specified private IP. You must specify the object’s OCID. Alternatively, you can get the object by using listPrivateIps
with the private IP address (for example, 10.0.3.3) and subnet OCID.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetPublicIpResponse> getPublicIp(GetPublicIpRequest request, AsyncHandler<GetPublicIpRequest,GetPublicIpResponse> handler)
Gets the specified public IP. You must specify the object’s OCID.
Alternatively, you can get the object by using getPublicIpByIpAddress
with the public IP address (for example, 129.146.2.1).
Or you can use getPublicIpByPrivateIpId
with the OCID of the private IP that the public IP is assigned to.
Note:** If you’re fetching a reserved public IP that is in the process of being moved to a different private IP, the service returns the public IP object with lifecycleState
= ASSIGNING and assignedEntityId
= OCID of the target private IP.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetPublicIpByIpAddressResponse> getPublicIpByIpAddress(GetPublicIpByIpAddressRequest request, AsyncHandler<GetPublicIpByIpAddressRequest,GetPublicIpByIpAddressResponse> handler)
Gets the public IP based on the public IP address (for example, 129.146.2.1).
Note:** If you’re fetching a reserved public IP that is in the process of being moved to a different private IP, the service returns the public IP object with lifecycleState
= ASSIGNING and assignedEntityId
= OCID of the target private IP.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetPublicIpByPrivateIpIdResponse> getPublicIpByPrivateIpId(GetPublicIpByPrivateIpIdRequest request, AsyncHandler<GetPublicIpByPrivateIpIdRequest,GetPublicIpByPrivateIpIdResponse> handler)
Gets the public IP assigned to the specified private IP. You must specify the OCID of the private IP. If no public IP is assigned, a 404 is returned.
Note:** If you’re fetching a reserved public IP that is in the process of being moved to a different private IP, and you provide the OCID of the original private IP, this operation returns a 404. If you instead provide the OCID of the target private IP, or if you instead call getPublicIp
or getPublicIpByIpAddress
, the service returns the public IP object with lifecycleState
= ASSIGNING and assignedEntityId
= OCID of the target private IP.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetRemotePeeringConnectionResponse> getRemotePeeringConnection(GetRemotePeeringConnectionRequest request, AsyncHandler<GetRemotePeeringConnectionRequest,GetRemotePeeringConnectionResponse> handler)
Get the specified remote peering connection’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetRouteTableResponse> getRouteTable(GetRouteTableRequest request, AsyncHandler<GetRouteTableRequest,GetRouteTableResponse> handler)
Gets the specified route table’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetSecurityListResponse> getSecurityList(GetSecurityListRequest request, AsyncHandler<GetSecurityListRequest,GetSecurityListResponse> handler)
Gets the specified security list’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetServiceResponse> getService(GetServiceRequest request, AsyncHandler<GetServiceRequest,GetServiceResponse> handler)
Gets the specified Service
object.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetServiceGatewayResponse> getServiceGateway(GetServiceGatewayRequest request, AsyncHandler<GetServiceGatewayRequest,GetServiceGatewayResponse> handler)
Gets the specified service gateway’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetSubnetResponse> getSubnet(GetSubnetRequest request, AsyncHandler<GetSubnetRequest,GetSubnetResponse> handler)
Gets the specified subnet’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetVcnResponse> getVcn(GetVcnRequest request, AsyncHandler<GetVcnRequest,GetVcnResponse> handler)
Gets the specified VCN’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetVirtualCircuitResponse> getVirtualCircuit(GetVirtualCircuitRequest request, AsyncHandler<GetVirtualCircuitRequest,GetVirtualCircuitResponse> handler)
Gets the specified virtual circuit’s information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<GetVnicResponse> getVnic(GetVnicRequest request, AsyncHandler<GetVnicRequest,GetVnicResponse> handler)
Gets the information for the specified virtual network interface card (VNIC). You can get the VNIC OCID from the listVnicAttachments
operation.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListAllowedPeerRegionsForRemotePeeringResponse> listAllowedPeerRegionsForRemotePeering(ListAllowedPeerRegionsForRemotePeeringRequest request, AsyncHandler<ListAllowedPeerRegionsForRemotePeeringRequest,ListAllowedPeerRegionsForRemotePeeringResponse> handler)
Lists the regions that support remote VCN peering (which is peering across regions). For more information, see VCN Peering.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListCpesResponse> listCpes(ListCpesRequest request, AsyncHandler<ListCpesRequest,ListCpesResponse> handler)
Lists the customer-premises equipment objects (CPEs) in the specified compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListCrossConnectGroupsResponse> listCrossConnectGroups(ListCrossConnectGroupsRequest request, AsyncHandler<ListCrossConnectGroupsRequest,ListCrossConnectGroupsResponse> handler)
Lists the cross-connect groups in the specified compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListCrossConnectLocationsResponse> listCrossConnectLocations(ListCrossConnectLocationsRequest request, AsyncHandler<ListCrossConnectLocationsRequest,ListCrossConnectLocationsResponse> handler)
Lists the available FastConnect locations for cross-connect installation. You need this information so you can specify your desired location when you create a cross-connect.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListCrossConnectsResponse> listCrossConnects(ListCrossConnectsRequest request, AsyncHandler<ListCrossConnectsRequest,ListCrossConnectsResponse> handler)
Lists the cross-connects in the specified compartment. You can filter the list by specifying the OCID of a cross-connect group.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListCrossconnectPortSpeedShapesResponse> listCrossconnectPortSpeedShapes(ListCrossconnectPortSpeedShapesRequest request, AsyncHandler<ListCrossconnectPortSpeedShapesRequest,ListCrossconnectPortSpeedShapesResponse> handler)
Lists the available port speeds for cross-connects. You need this information so you can specify your desired port speed (that is, shape) when you create a cross-connect.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListDhcpOptionsResponse> listDhcpOptions(ListDhcpOptionsRequest request, AsyncHandler<ListDhcpOptionsRequest,ListDhcpOptionsResponse> handler)
Lists the sets of DHCP options in the specified VCN and specified compartment. The response includes the default set of options that automatically comes with each VCN, plus any other sets you’ve created.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListDrgAttachmentsResponse> listDrgAttachments(ListDrgAttachmentsRequest request, AsyncHandler<ListDrgAttachmentsRequest,ListDrgAttachmentsResponse> handler)
Lists the DrgAttachment
objects for the specified compartment. You can filter the results by VCN or DRG.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListDrgsResponse> listDrgs(ListDrgsRequest request, AsyncHandler<ListDrgsRequest,ListDrgsResponse> handler)
Lists the DRGs in the specified compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListFastConnectProviderServicesResponse> listFastConnectProviderServices(ListFastConnectProviderServicesRequest request, AsyncHandler<ListFastConnectProviderServicesRequest,ListFastConnectProviderServicesResponse> handler)
Lists the service offerings from supported providers. You need this information so you can specify your desired provider and service offering when you create a virtual circuit.
For the compartment ID, provide the OCID of your tenancy (the root compartment).
For more information, see FastConnect Overview.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListFastConnectProviderVirtualCircuitBandwidthShapesResponse> listFastConnectProviderVirtualCircuitBandwidthShapes(ListFastConnectProviderVirtualCircuitBandwidthShapesRequest request, AsyncHandler<ListFastConnectProviderVirtualCircuitBandwidthShapesRequest,ListFastConnectProviderVirtualCircuitBandwidthShapesResponse> handler)
Gets the list of available virtual circuit bandwidth levels for a provider. You need this information so you can specify your desired bandwidth level (shape) when you create a virtual circuit.
For more information about virtual circuits, see FastConnect Overview.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListIPSecConnectionTunnelsResponse> listIPSecConnectionTunnels(ListIPSecConnectionTunnelsRequest request, AsyncHandler<ListIPSecConnectionTunnelsRequest,ListIPSecConnectionTunnelsResponse> handler)
Lists the tunnel information for the specified IPSec connection.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListIPSecConnectionsResponse> listIPSecConnections(ListIPSecConnectionsRequest request, AsyncHandler<ListIPSecConnectionsRequest,ListIPSecConnectionsResponse> handler)
Lists the IPSec connections for the specified compartment. You can filter the results by DRG or CPE.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListInternetGatewaysResponse> listInternetGateways(ListInternetGatewaysRequest request, AsyncHandler<ListInternetGatewaysRequest,ListInternetGatewaysResponse> handler)
Lists the internet gateways in the specified VCN and the specified compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListLocalPeeringGatewaysResponse> listLocalPeeringGateways(ListLocalPeeringGatewaysRequest request, AsyncHandler<ListLocalPeeringGatewaysRequest,ListLocalPeeringGatewaysResponse> handler)
Lists the local peering gateways (LPGs) for the specified VCN and compartment (the LPG’s compartment).
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListNatGatewaysResponse> listNatGateways(ListNatGatewaysRequest request, AsyncHandler<ListNatGatewaysRequest,ListNatGatewaysResponse> handler)
Lists the NAT gateways in the specified compartment. You may optionally specify a VCN OCID to filter the results by VCN.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListPrivateIpsResponse> listPrivateIps(ListPrivateIpsRequest request, AsyncHandler<ListPrivateIpsRequest,ListPrivateIpsResponse> handler)
Lists the PrivateIp
objects based on one of these filters:
- Subnet OCID. - VNIC OCID. - Both private IP address and subnet OCID: This lets you get a privateIP
object based on its private IP address (for example, 10.0.3.3) and not its OCID. For comparison, getPrivateIp
requires the OCID.
If you’re listing all the private IPs associated with a given subnet or VNIC, the response includes both primary and secondary private IPs.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListPublicIpsResponse> listPublicIps(ListPublicIpsRequest request, AsyncHandler<ListPublicIpsRequest,ListPublicIpsResponse> handler)
Lists the PublicIp
objects in the specified compartment. You can filter the list by using query parameters.
To list your reserved public IPs: * Set scope
= REGION
(required) * Leave the availabilityDomain
parameter empty * Set lifetime
= RESERVED
To list the ephemeral public IPs assigned to a regional entity such as a NAT gateway: * Set scope
= REGION
(required) * Leave the availabilityDomain
parameter empty * Set lifetime
= EPHEMERAL
To list the ephemeral public IPs assigned to private IPs: * Set scope
= AVAILABILITY_DOMAIN
(required) * Set the availabilityDomain
parameter to the desired availability domain (required) * Set lifetime
= EPHEMERAL
Note:** An ephemeral public IP assigned to a private IP is always in the same availability domain and compartment as the private IP.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListRemotePeeringConnectionsResponse> listRemotePeeringConnections(ListRemotePeeringConnectionsRequest request, AsyncHandler<ListRemotePeeringConnectionsRequest,ListRemotePeeringConnectionsResponse> handler)
Lists the remote peering connections (RPCs) for the specified DRG and compartment (the RPC’s compartment).
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListRouteTablesResponse> listRouteTables(ListRouteTablesRequest request, AsyncHandler<ListRouteTablesRequest,ListRouteTablesResponse> handler)
Lists the route tables in the specified VCN and specified compartment. The response includes the default route table that automatically comes with each VCN, plus any route tables you’ve created.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListSecurityListsResponse> listSecurityLists(ListSecurityListsRequest request, AsyncHandler<ListSecurityListsRequest,ListSecurityListsResponse> handler)
Lists the security lists in the specified VCN and compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListServiceGatewaysResponse> listServiceGateways(ListServiceGatewaysRequest request, AsyncHandler<ListServiceGatewaysRequest,ListServiceGatewaysResponse> handler)
Lists the service gateways in the specified compartment. You may optionally specify a VCN OCID to filter the results by VCN.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListServicesResponse> listServices(ListServicesRequest request, AsyncHandler<ListServicesRequest,ListServicesResponse> handler)
Lists the available Service
objects that you can enable for a service gateway in this region.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListSubnetsResponse> listSubnets(ListSubnetsRequest request, AsyncHandler<ListSubnetsRequest,ListSubnetsResponse> handler)
Lists the subnets in the specified VCN and the specified compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListVcnsResponse> listVcns(ListVcnsRequest request, AsyncHandler<ListVcnsRequest,ListVcnsResponse> handler)
Lists the virtual cloud networks (VCNs) in the specified compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListVirtualCircuitBandwidthShapesResponse> listVirtualCircuitBandwidthShapes(ListVirtualCircuitBandwidthShapesRequest request, AsyncHandler<ListVirtualCircuitBandwidthShapesRequest,ListVirtualCircuitBandwidthShapesResponse> handler)
The deprecated operation lists available bandwidth levels for virtual circuits. For the compartment ID, provide the OCID of your tenancy (the root compartment).
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListVirtualCircuitPublicPrefixesResponse> listVirtualCircuitPublicPrefixes(ListVirtualCircuitPublicPrefixesRequest request, AsyncHandler<ListVirtualCircuitPublicPrefixesRequest,ListVirtualCircuitPublicPrefixesResponse> handler)
Lists the public IP prefixes and their details for the specified public virtual circuit.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<ListVirtualCircuitsResponse> listVirtualCircuits(ListVirtualCircuitsRequest request, AsyncHandler<ListVirtualCircuitsRequest,ListVirtualCircuitsResponse> handler)
Lists the virtual circuits in the specified compartment.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateCpeResponse> updateCpe(UpdateCpeRequest request, AsyncHandler<UpdateCpeRequest,UpdateCpeResponse> handler)
Updates the specified CPE’s display name or tags. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateCrossConnectResponse> updateCrossConnect(UpdateCrossConnectRequest request, AsyncHandler<UpdateCrossConnectRequest,UpdateCrossConnectResponse> handler)
Updates the specified cross-connect.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateCrossConnectGroupResponse> updateCrossConnectGroup(UpdateCrossConnectGroupRequest request, AsyncHandler<UpdateCrossConnectGroupRequest,UpdateCrossConnectGroupResponse> handler)
Updates the specified cross-connect group’s display name. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateDhcpOptionsResponse> updateDhcpOptions(UpdateDhcpOptionsRequest request, AsyncHandler<UpdateDhcpOptionsRequest,UpdateDhcpOptionsResponse> handler)
Updates the specified set of DHCP options. You can update the display name or the options themselves. Avoid entering confidential information.
Note that the options
object you provide replaces the entire existing set of options.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateDrgResponse> updateDrg(UpdateDrgRequest request, AsyncHandler<UpdateDrgRequest,UpdateDrgResponse> handler)
Updates the specified DRG’s display name or tags. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateDrgAttachmentResponse> updateDrgAttachment(UpdateDrgAttachmentRequest request, AsyncHandler<UpdateDrgAttachmentRequest,UpdateDrgAttachmentResponse> handler)
Updates the display name for the specified DrgAttachment
. Avoid entering confidential information.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateIPSecConnectionResponse> updateIPSecConnection(UpdateIPSecConnectionRequest request, AsyncHandler<UpdateIPSecConnectionRequest,UpdateIPSecConnectionResponse> handler)
Updates the specified IPSec connection.
To update an individual IPSec tunnel’s attributes, use updateIPSecConnectionTunnel
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateIPSecConnectionTunnelResponse> updateIPSecConnectionTunnel(UpdateIPSecConnectionTunnelRequest request, AsyncHandler<UpdateIPSecConnectionTunnelRequest,UpdateIPSecConnectionTunnelResponse> handler)
Updates the specified tunnel. This operation lets you change tunnel attributes such as the routing type (BGP dynamic routing or static routing). Here are some important notes:
If you change the tunnel’s routing type or BGP session configuration, the tunnel will go down while it’s reprovisioned.
If you want to switch the tunnel’s routing
from STATIC
to BGP
, make sure the tunnel’s BGP session configuration attributes have been set (bgpSessionInfo
).
If you want to switch the tunnel’s routing
from BGP
to STATIC
, make sure the IPSecConnection
already has at least one valid CIDR static route.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateIPSecConnectionTunnelSharedSecretResponse> updateIPSecConnectionTunnelSharedSecret(UpdateIPSecConnectionTunnelSharedSecretRequest request, AsyncHandler<UpdateIPSecConnectionTunnelSharedSecretRequest,UpdateIPSecConnectionTunnelSharedSecretResponse> handler)
Updates the shared secret (pre-shared key) for the specified tunnel.
Important:** If you change the shared secret, the tunnel will go down while it’s reprovisioned.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateInternetGatewayResponse> updateInternetGateway(UpdateInternetGatewayRequest request, AsyncHandler<UpdateInternetGatewayRequest,UpdateInternetGatewayResponse> handler)
Updates the specified internet gateway. You can disable/enable it, or change its display name or tags. Avoid entering confidential information.
If the gateway is disabled, that means no traffic will flow to/from the internet even if there’s a route rule that enables that traffic.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateLocalPeeringGatewayResponse> updateLocalPeeringGateway(UpdateLocalPeeringGatewayRequest request, AsyncHandler<UpdateLocalPeeringGatewayRequest,UpdateLocalPeeringGatewayResponse> handler)
Updates the specified local peering gateway (LPG).
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateNatGatewayResponse> updateNatGateway(UpdateNatGatewayRequest request, AsyncHandler<UpdateNatGatewayRequest,UpdateNatGatewayResponse> handler)
Updates the specified NAT gateway.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdatePrivateIpResponse> updatePrivateIp(UpdatePrivateIpRequest request, AsyncHandler<UpdatePrivateIpRequest,UpdatePrivateIpResponse> handler)
Updates the specified private IP. You must specify the object’s OCID. Use this operation if you want to:
- Move a secondary private IP to a different VNIC in the same subnet. - Change the display name for a secondary private IP. - Change the hostname for a secondary private IP.
This operation cannot be used with primary private IPs. To update the hostname for the primary IP on a VNIC, use updateVnic
.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdatePublicIpResponse> updatePublicIp(UpdatePublicIpRequest request, AsyncHandler<UpdatePublicIpRequest,UpdatePublicIpResponse> handler)
Updates the specified public IP. You must specify the object’s OCID. Use this operation if you want to:
Assign a reserved public IP in your pool to a private IP. * Move a reserved public IP to a different private IP. * Unassign a reserved public IP from a private IP (which returns it to your pool of reserved public IPs). * Change the display name or tags for a public IP.
Assigning, moving, and unassigning a reserved public IP are asynchronous operations. Poll the public IP’s lifecycleState
to determine if the operation succeeded.
Note:** When moving a reserved public IP, the target private IP must not already have a public IP with lifecycleState
= ASSIGNING or ASSIGNED. If it does, an error is returned. Also, the initial unassignment from the original private IP always succeeds, but the assignment to the target private IP is asynchronous and could fail silently (for example, if the target private IP is deleted or has a different public IP assigned to it in the interim). If that occurs, the public IP remains unassigned and its lifecycleState
switches to AVAILABLE (it is not reassigned to its original private IP). You must poll the public IP’s lifecycleState
to determine if the move succeeded.
Regarding ephemeral public IPs:
If you want to assign an ephemeral public IP to a primary private IP, use createPublicIp
. * You can’t move an ephemeral public IP to a different private IP. * If you want to unassign an ephemeral public IP from its private IP, use deletePublicIp
, which unassigns and deletes the ephemeral public IP.
Note:** If a public IP is assigned to a secondary private IP (see PrivateIp
), and you move that secondary private IP to another VNIC, the public IP moves with it.
Note:** There’s a limit to the number of PublicIp
a VNIC or instance can have. If you try to move a reserved public IP to a VNIC or instance that has already reached its public IP limit, an error is returned. For information about the public IP limits, see Public IP Addresses.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateRemotePeeringConnectionResponse> updateRemotePeeringConnection(UpdateRemotePeeringConnectionRequest request, AsyncHandler<UpdateRemotePeeringConnectionRequest,UpdateRemotePeeringConnectionResponse> handler)
Updates the specified remote peering connection (RPC).
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateRouteTableResponse> updateRouteTable(UpdateRouteTableRequest request, AsyncHandler<UpdateRouteTableRequest,UpdateRouteTableResponse> handler)
Updates the specified route table’s display name or route rules. Avoid entering confidential information.
Note that the routeRules
object you provide replaces the entire existing set of rules.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateSecurityListResponse> updateSecurityList(UpdateSecurityListRequest request, AsyncHandler<UpdateSecurityListRequest,UpdateSecurityListResponse> handler)
Updates the specified security list’s display name or rules. Avoid entering confidential information.
Note that the egressSecurityRules
or ingressSecurityRules
objects you provide replace the entire existing objects.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateServiceGatewayResponse> updateServiceGateway(UpdateServiceGatewayRequest request, AsyncHandler<UpdateServiceGatewayRequest,UpdateServiceGatewayResponse> handler)
Updates the specified service gateway. The information you provide overwrites the existing attributes of the gateway.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateSubnetResponse> updateSubnet(UpdateSubnetRequest request, AsyncHandler<UpdateSubnetRequest,UpdateSubnetResponse> handler)
Updates the specified subnet.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateVcnResponse> updateVcn(UpdateVcnRequest request, AsyncHandler<UpdateVcnRequest,UpdateVcnResponse> handler)
Updates the specified VCN.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateVirtualCircuitResponse> updateVirtualCircuit(UpdateVirtualCircuitRequest request, AsyncHandler<UpdateVirtualCircuitRequest,UpdateVirtualCircuitResponse> handler)
Updates the specified virtual circuit. This can be called by either the customer who owns the virtual circuit, or the provider (when provisioning or de-provisioning the virtual circuit from their end). The documentation for updateVirtualCircuitDetails
indicates who can update each property of the virtual circuit.
Important:** If the virtual circuit is working and in the PROVISIONED state, updating any of the network-related properties (such as the DRG being used, the BGP ASN, and so on) will cause the virtual circuit’s state to switch to PROVISIONING and the related BGP session to go down. After Oracle re-provisions the virtual circuit, its state will return to PROVISIONED. Make sure you confirm that the associated BGP session is back up. For more information about the various states and how to test connectivity, see FastConnect Overview.
To change the list of public IP prefixes for a public virtual circuit, use bulkAddVirtualCircuitPublicPrefixes
and bulkDeleteVirtualCircuitPublicPrefixes
. Updating the list of prefixes does NOT cause the BGP session to go down. However, Oracle must verify the customer’s ownership of each added prefix before traffic for that prefix will flow across the virtual circuit.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Future<UpdateVnicResponse> updateVnic(UpdateVnicRequest request, AsyncHandler<UpdateVnicRequest,UpdateVnicResponse> handler)
Updates the specified VNIC.
request
- The request object containing the details to sendhandler
- The request handler to invoke upon completion, may be null.Copyright © 2016–2019. All rights reserved.