vania-janet/multiturn-rag-retrieval-data huggingface dataset:
SSH keys can either be of type RSA or Ed25519. Ed25519 can be used only if the operating system supports this key type. Ed25519 can't be used with Windows or VMware images.
* --dedicated-host: ID or name of the host destination where the instance is placed.
* --dedicated-host-group: ID or name of the host group destination where the instance is placed.
* --placement-group: ID or name of the placement group. The placement group restrictions for the virtual server instance.
* --user-data: data|@data-file. User data to transfer to the virtual server instance.
* --subnet: ID or name of the subnet.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --sgs: Comma-separated security group IDs or names for primary network interface.
* --allow-ip-spoofing: Disables the source and destination checks on this interface. If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --primary-network-interface: PRIMARY_NETWORK_INTERFACE_JSON|@PRIMARY_NETWORK_INTERFACE_JSON_FILE, primary network interface in JSON or JSON file. For the data schema, see the primary_network_interface property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --network-interface: NETWORK_INTERFACE_JSON|@NETWORK_INTERFACE_JSON_FILE, network interface attachment in JSON or JSON file.
Mount target name Specify a mount target name. The name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. You can later edit the name if you want. 
 Zone Zone is inherited from the file share (for example, Dallas 2). 
 VPC Select an available VPC. The list includes only those VPCs with a subnet in the selected zone. 
 Subnet Select a subnet from the list. 
 Reserved IP address Required for the mount target. The IP address cannot be changed afterward. However, you can delete the mount target and create another one with a different IP address. 
 Reserving method You can have the file service select an IP address for you. The reserved IP becomes visible after the mount target is created. Or, specify your own IP. 
 Auto-release Releases the IP address when you delete the mount target. Enabled by default. 
 Security groups The security group for the VPC is selected by default, or select from the list. 
 Encryption in transit Disabled by default, click the toggle to enable. For more information about this feature, see [Encryption in transit - Securing mount connections between file share and host](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit). 



* If you selected VPC as the access mode, provide a name for the mount target and select the VPC where the file share is to be used in.



5. Select the right profile for your workload. The profile that you select determines the input/output performance of a file share. The dp2 profile provides the most flexibility. For more information about file storage IOPS tier and Custom profiles, see [File storage profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profiles).
6. Specify the size for the file share. You can later [increase this size](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-expand-capacity).
The routing to internet uses these uplinks and public IP addresses to the uplinks are provisioned by the automation.
6. A single Tier-1 gateway is provisioned by the automation for the workloads. You can use this topology or customize it by provisioning new Tier-1 gateways.
7. You can expand the default topology by adding new segments to the existing Tier-1 Gateway (or to the new Tier-1 gateways provisioned by you). The route advertisements between T1 and T0 gateways are customizable by you fully and done by NSX-T. No routing protocol is required or used between T1 and T0 advertisements.



The following diagram shows an example of a customer deployment by using the standard topology. Consider that the segments are attached directly to the Tier-0 gateway. You can add more segments to the Tier-0 gateway or delete the Tier-1 gateway that is deployed by the automation, if needed.

Zoom

![Single-site – single tenant example topology](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/v2t-diagrams-1-zone-t0.svg)

Figure 2. Single-site – single tenant example topology



1. The vCenter Server automation deploys an example single-site topology, which follows the principles that are presented in this model. The deployment includes a single vCenter and three NSX-T Managers that are deployed on the cluster on the initial IBM Cloud data center location.
2. The vCenter Server automation deploys two edge cluster transport nodes and a single edge cluster for your Tier-0 and Tier-1 gateways.
3. The Tier-0 gateway provides north-south routing capabilities and access to IBM Cloud private network is provided though its uplinks.
4. Access to private network is provided though private uplinks, which are attached to a portable subnet on a private primary VLAN on the IBM Cloud private network. The routing to IBM Cloud services uses these uplinks.
6. Create a subnet_reserved_ip resource or use an existing subnet_reserved_ip by referring to the subnet_reserved_ip data source. For more information, see the Terraform documentation on [ibm_is_subnet_reserved_ip](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/is_subnet_reserved_ip)

resource "ibm_is_subnet_reserved_ip" "example_reserved_ip" {
subnet = ibm_is_subnet.example_subnet.id
name = "example-reserved-ip1"
address = "${replace(ibm_is_subnet.example_subnet.ipv4_cidr_block, "0/24", "13")}"
}







 Creating an instance by using Terraform 

Create the instance by using one of the following examples. For more information, see the Terraform documentation on [ibm_is_instance](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_instance).

Run one of the following Terraform commands based on the image that you plan to use.



* Create an instance by using a stock image or custom image from your account for your instance.

resource "ibm_is_instance" "example_instance" {
name = "example-instance-reserved-ip"
image = data.ibm_is_image.example_image.id
profile = data.ibm_is_instance_profile.example_profile.name

primary_network_interface {
name = "eth0"
subnet = ibm_is_subnet.example_subnet.id
primary_ip {
reserved_ip = ibm_is_subnet_reserved_ip.example_reserved_ip.reserved_ip
}
}
network_interfaces {
name = "eth1"
subnet = ibm_is_subnet.example_subnet.id
primary_ip {
name = "example-reserved-ip1"
auto_delete = true
This option is only required if you want to specify the unique resource by name inside this VPC.
* --name is the user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --auto-delete determines how the auto-delete feature is set. If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false (default: true).
* --target is the target of the reserved IP.
* --output specifies the output format; only JSON is supported.
* -q, --quiet suppresses verbose output.







 Updating a reserved IP from the CLI 

To update a reserved IP by using the CLI, run the following command:

ibmcloud is subnet-reserved-ip-update SUBNET RESERVED_IP [--vpc VPC] [--name NEW_NAME] [--auto-delete true | false] [--output JSON] [-q, --quiet]

Where:



* SUBNET is the ID of the subnet.
* RESERVED_IP is the ID of the reserved IP.
* --vpc is the ID or name of the VPC. It is only required if you want to specify the unique resource by name inside this VPC.
* --name is the new name of the reserved IP.
* --auto-delete determines how the auto-delete feature is set. If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false (default: true).
* --output specifies the output format; only JSON is supported.
* -q, --quiet suppresses verbose output.







 Deleting a reserved IP from the CLI 

To delete a reserved IP by using the CLI, the reserved IP must be unbound. After unbinding the reserved IP, run the following command to delete it:
ibm_is_subnet_reserved_ip](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_subnet_reserved_ip)<br> * [ibm_is_subnet_routing_table_attachment](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_subnet_routing_table_attachment)<br> * [ibm_is_virtual_endpoint_gateway](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_virtual_endpoint_gateway)<br> * [ibm_is_virtual_endpoint_gateway_ip](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_virtual_endpoint_gateway_ip)<br> * [ibm_is_volume](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_volume)<br> * [ibm_is_vpc](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpc)<br> * [ibm_
See [Migrating use of security group associations](https://cloud.ibm.com/docs/vpc?topic=vpc-2022-03-29-migrationmigrate-security-group-assoc) for guidance on how to migrate to use security group targets, which allow security groups to be associated with VPC resources beyond network interfaces, such as endpoint gateways and load balancers.





 For all version dates 

Reserved IP management. You can explicitly [Reserve an IP in a subnet](https://cloud.ibm.com/apidocs/vpccreate-subnet-reserved-ip) ahead of time, and [List all reserved IPs on a subnet](https://cloud.ibm.com/apidocs/vpclist-subnet-reserved-ips) to see all your VPC resources that are using IP addresses on that subnet, including load balancers and VPN gateways (with [limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-known-issuesip-known-issues)). For more information, see [Managing IP addresses](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-ip-addresses).

UDP support for network load balancers. When [creating a network load balancer](https://cloud.ibm.com/apidocs/vpccreate-load-balancer) (NLB), you can now set User Datagram Protocol (UDP) as the communications protocol for NLB listeners and pools by specifying udp for the protocol sub-property of the [listener](https://cloud.ibm.com/apidocs/vpccreate-load-balancer-listener-request) and [pool](https://cloud.ibm.com/apidocs/vpccreate-load-balancer-pool) properties respectively. (Health checks do not support UDP for monitoring the health of pool members.) For more information, see [Configuring UDP for network load balancers](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-udp&interface=api).
Getting started as a user in API Connect V10 Reserved 

See how easy it is to create, manage, secure, and share APIs.

API Connect V10 Reserved service is the cloud-based edition of IBM API Connect. The Reserved service offers a comparable set of features for managing the lifecycle of APIs, hosted in IBM Cloud. API Connect makes it easy to create, securely expose, manage, and monetize APIs so that you and your customers can power digital applications and spur innovation.

If you are an administrator, see [Getting started as an administrator](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-getting-started-admin) for instructions on configuring your new Reserved service instance and adding users.

In this tutorial, you verify your access to API Connect, then open the API Manager and create an API. Ready to get started?



 Step 1. Log in to API Connect with your provider organization 

To use the API Manager, you must be invited to a provider organization in API Connect. An administrator from your company creates the provider organization, defines access settings, and then adds users.

You can log into the API Connect with your provider organization by completing the following steps:



1. [Log in](https://cloud.ibm.com/login/) to IBM Cloud using your IBM ID.
2. On the IBM Cloud Dashboard, click ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/images/icon_cloud_menu.png) and select API Management.
3. In the navigation list, expand API Connect and click Services.
4. On the Services page, display the provider organizations for your company's API Connect Reserved service by expanding the row that displays the service name. Your administrator can tell you which provider organization you belong to.

Provider organizations belong to Reserved instances, so you need to expand your Reserved instance to see the list of associated provider organizations.
--------------------







 ibmcloud is subnet-reserved-ip-update 

Update a reserved IP.

ibmcloud is subnet-reserved-ip-update SUBNET RESERVED_IP [--vpc VPC] [--name NEW_NAME] [--auto-delete true | false] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is subnet-reserved-ip-update 2201-3f2e33d4-2140-44b4-843c-d73e03d585f1 2201-7fc11925-47ff-4080-a314-be64c662c302 --name my-reserved-ip2
* ibmcloud is subnet-reserved-ip-update my-subnet my-reserved-ip --name my-reserved-ip2
* ibmcloud is subnet-reserved-ip-update 2201-3f2e33d4-2140-44b4-843c-d73e03d585f1 2201-7fc11925-47ff-4080-a314-be64c662c302 --auto-delete false
* ibmcloud is subnet-reserved-ip-update 2201-3f2e33d4-2140-44b4-843c-d73e03d585f1 2201-7fc11925-47ff-4080-a314-be64c662c302 --name my-reserved-ip2 --output JSON







 Command options 



* SUBNET: ID or name of the subnet.
* RESERVED_IP: ID or name of the reserved IP.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --name: The new name of the reserved IP.
* --auto-delete: Indicates whether this reserved IP member automatically deletes when either target is deleted, or the reserved IP is unbound.
: The number of BFD packets not received by a neighbor that causes the originating interface to be declared down. Range [1 - 255]

--bgp-asn value
: Gateway BGP-ASN. Excluded ASNs: 0, 13884, 36351, 64512, 64513, 65100, 65201‍–‍65234, 65402‍–‍65433, 65500, and 4201065000‍–‍4201065999

--bgp-cer-cidr value
: BGP customer edge router CIDR

--bgp-ibm-cidr value
: BGP IBM CIDR

--billing VALUE
: Billing (metered | non-metered). Select metered to charge per GB and non-metered for a flat rate. Set for gateway-create requests to select the gateway's metered billing option.

-connection value
: Type of network connection that you want to bind to your direct link. One of: direct, transit.

--resource-group-id VALUE
: Resource group ID for this resource. Set for gateway-create requests to select the gateway's resource group.

--routing ROUTING
: Gateway routing (global | local). Select global to connect resources across regions. Set for gateway-create requests to select the gateway's routing option.

--speed-mbps SPEED_MBPS
: Speed of the gateway in Mbps.

--vlan value
: Gateway VLAN ID

--output value
: Specify whether you want the output displayed in JSON format. Currently, json is the only supported format. Optional.

--help|-h
: Get help on this command. Optional.
For more information on adding gateways to your Reserved instance, see [Adding remote gateways](https://cloud.ibm.com/docs/apiconnect?apiconnect-ri-reg-gwy). For information on managing user access to gateways, see [Managing gateways](https://cloud.ibm.com/docs/apiconnect?apiconnect-ri-mng-gwy).





 Using the toolkit 

The toolkit provides a CLI for working with assets such as APIs and developer portals. For information on downloading and setting up the toolkit, see [Setting up your toolkit](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.toolkit.doc/ri_toolkit.html) in the extended V10 Reserved documentation.
* --total-volume-bandwidth: The amount of bandwidth (in megabits per second) that is allocated exclusively to instance storage volumes. An increase in this value results in a corresponding decrease to total network bandwidth.
* --boot-volume: BOOT_VOLUME_JSON|@BOOT_VOLUME_JSON_FILE, boot volume attachment in JSON or JSON file. For the data schema, see the boot_volume_attachment property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --volume-attach: VOLUME_ATTACH_JSON|@VOLUME_ATTACH_JSON_FILE, volume attachment in JSON or JSON file, list of volumes. For the data schema, see the volume_attachments property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --keys: Comma-separated IDs or names of SSH keys. SSH keys can either be of type RSA or Ed25519. Ed25519 can be used only if the operating system supports this key type. Ed25519 can't be used with Windows or VMware images.
* --dedicated-host: ID or name of the host destination where the instance is placed.
* --dedicated-host-group: ID or name of the host group destination where the instance is placed.
* --placement-group: ID or name of the placement group. The placement group restrictions for the virtual server instance.
* --user-data: data|@data-file. User data to transfer to the virtual server instance.
* --sgs: Comma-separated security group IDs or names for primary network interface.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --dedicated-host: ID or name of the host destination where the instance is placed.
* --dedicated-host-group: ID or name of the host group destination where the instance is placed.
* --placement-group: ID or name of the placement group. The placement group restrictions for the virtual server instance.
* --user-data: data|@data-file. User data to transfer to the virtual server instance.
* --subnet: ID or name of the subnet.
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --sgs: Comma-separated security group IDs or names for primary network interface.
* --allow-ip-spoofing: Disables the source and destination checks on this interface. If false, source IP spoofing is not allowed on this interface. One of: false, true.
* --primary-network-interface: PRIMARY_NETWORK_INTERFACE_JSON|@PRIMARY_NETWORK_INTERFACE_JSON_FILE, primary network interface in JSON or JSON file. For the data schema, see the primary_network_interface property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* --network-interface: NETWORK_INTERFACE_JSON|@NETWORK_INTERFACE_JSON_FILE, network interface attachment in JSON or JSON file. For the data schema, see the network_interfaces property in the [API documentation](https://cloud.ibm.com/apidocs/vpccreate-instance).
* ibmcloud is bm-nicc cli-bm --subnet 2302-531ad9fc-c86a-4504-b5cf-a46981fddb5f --name cli-snic --address 10.240.128.51 --auto-delete true --ip-name cli-snicip Create bare metal NIC with new reserved IP.







 Command options 



* SERVER: ID or name of the server.
* --subnet: Subnet ID or name for the network interface.
* --name: Name of the network interface.
* --interface-type: Type of the network interface. One of: pci, vlan. (default: pci).
* --rip: ID or name of the existing reserved IP.
* --address: The IP address to reserve, which must not already be reserved on the subnet.
* --auto-delete: If set to true, this reserved IP automatically deletes when the target is deleted. One of: true, false. (default: true).
* --ip-name: The user-defined name for this reserved IP. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --security-groups: Comma-separated security group IDs or names for the network interface.
* --vpc: ID or name of the VPC. This is only required to specify the unique subnet and unique security-groups by name inside this VPC.
* --allowed-vlans: Comma-separated VLAN IDs. Indicates which VLAN IDs (for VLAN interfaces only) can use this PCI interface. It can be passed as separate values or as any range of numbers.
* --vlan: Indicates the 802.1Q VLAN ID tag that must be used for all traffic on this VLAN interface.
* --allow-interface-to-float: Indicates if the interface can float to any other server within the same resource_group.
: Gateway BGP-ASN. Excluded ASNs: 0, 13884, 36351, 64512, 64513, 65100, 65201‍–‍65234, 65402‍–‍65433, 65500, and 4201065000‍–‍4201065999

--bgp-cer-cidr value
: BGP customer edge router CIDR.

--bgp-ibm-cidr value
: BGP IBM CIDR.

--billing value
: Billing of resources (metered | non-metered). Select metered to charge per GB and non-metered for a flat rate.

--connection value
: Type of network connection that you want to bind to your direct link. One of: dedicated, connect.

--loa-reject-reason LOA_REJECT_REASON
: Specify the reason for the Letter of Authorization (LOA) rejection.

--name NAME
: Name of the gateway.

--operational-status OPERATIONAL_STATUS
: Specify the gateway's operational status. Values are loa_accepted or loa_rejected.

--routing VALUE
: Gateway routing of resources (global | local). Select global to connect resources across regions.

--speed-mbps SPEED_MBPS
: Specify the speed of the gateway in Mbps.

--help|-h
: Get help on this command. Optional.

--output value
: Specify whether you want the output displayed in JSON format. Currently, json is the only supported format. Optional.

To clear/update the [MD5 authentication for BGP peers](https://cloud.ibm.com/docs/dl?topic=dl-dl-md5), use the --file option to update the gateway as per the [template](https://cloud.ibm.com/apidocs/direct_linkupdate-gateway).





 Examples
0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024 lb-subnet

Public IPs
Reserved IPs ID Address Subnet
0767-16871e0f-c43a-4b6e-8491-a3e075362046 10.241.64.11 0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024
0767-a7db5d37-42cf-473e-ab27-07b679d64ceb 10.241.64.12 0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024

Provision status update_pending
Operating status online
Is public false
Listeners
Pools ID Name

Resource group ID Name
42c4f51adc3147b4b4049ad9826c30a1 Default

Created 2023-02-10T13:36:44-06:00
Instance Group Supported -
SourceIP Session Supported -
Security groups ID Name
r014-b739c959-fb3c-44cc-9ec5-41c45b4d637e astonish-backing-shadiness-frostlike-cosmos-hunk

UDP Supported false







 Working with DNS zones with the API 

You can bind and unbind DNS zones to a network load balancer during provisioning, or to an existing load balancer.



 Creating a load balancer bound to a private DNS zone with the API 

You will need the CRN of the private DNS that you want to bind to your load balancer. To find it, click Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > Resource List from the IBM Cloud console. Click the table row of the DNS whose CRN you want to find.