vania-janet/multiturn-rag-retrieval-data huggingface dataset:
--------------------







 ibmcloud is subnet-reserved-ips 

List all reserved IPs in the subnet.

ibmcloud is subnet-reserved-ips SUBNET [--vpc VPC] [--output JSON] [-q, --quiet]



 Command options 



* SUBNET: ID or name of the subnet.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is subnet-reserved-ip 

View details of reserved IP.

ibmcloud is subnet-reserved-ip SUBNET RESERVED_IP [--vpc VPC] [--output JSON] [-q, --quiet]



 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.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is subnet-reserved-ip-create 

Reserve an IP in a subnet.

ibmcloud is subnet-reserved-ip-create SUBNET [--vpc VPC] [--name NAME] [--address ADDRESS] [--auto-delete true | false] [--target TARGET] [--output JSON] [-q, --quiet]



 Command examples
Each floating IP is a single /32 IP address, and you can order as many as you need within VPC [Quotas](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas).



Table 3. Public uplink HA VIP to be used for Public floating IPs

 Interface name Interface type VLAN ID Subnet Allow float Allow IP spoofing Enable infra NAT NSX-T interface Segment name 

 vlan-nic-t0-pub-uplink-vip vlan 700 vpc-t0-public-uplink-subnet true false false T0 Public Uplink VIP vpc-zone-t0-public-vlanid 



VLAN interfaces with Allow IP spoofing and Enable Infrastructure NAT set to false allow public floating IP address to traverse non-NATted to the public uplinks of the T0 logical router. For high availability with NSX-T T0 logical router, HA VIPs can be used. When you order floating IP address for public uplinks, always use the VIP VLAN interface instead of the uplinks that are reserved for the actual Edge Nodes.

You can currently use the public IPs, for example:



* To perform destination NAT done in either Tier-0 or Tier-1 Logical Routers for inbound public traffic to NSX-T overlay.
* To perform source NAT done in either Tier-0 or Tier-1 Logical Routers for outbound public traffic from NSX-T overlay.
* To establish VPNs in either Tier-0 or Tier-1.



For more information, see the [Network Services provided by Tier-0 and Tier-1 Logical Routers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-nsx-t-logical-routersvpc-ryo-nsx-t-logical-routers-edge-gateway).

For public IPs, you can currently use one or more /32 IP address, but you cannot have subnets, such as /29 or /26.
Each floating IP is a single /32IP address, and you can order as many as you need within [VPC Quotas](https://cloud.ibm.com/docs/vpc?topic=vpc-quotas).



Table 1. Public uplink HA VIP to be used for Public floating IPs

 Interface name Interface type VLAN ID Subnet Allow float Allow IP spoofing Enable Infra NAT NSX-T interface Segment name 

 vlan-nic-t0-pub-uplink-vip vlan 700 vpc-t0-public-uplink-subnet true false false T0 Public Uplink VIP vpc-zone-t0-public-vlanid 



VLAN interfaces with Allow IP spoofing and Enable Infrastructure NAT set to false allow public floating IP address to traverse non-NATted to the public uplinks of the T0 logical router. For high availability with NSX-T T0 logical router, HA VIPs can be used. When ordering floating IP address for public uplinks, always use the VIP VLAN interface instead of the uplinks that are reserved for the actual Edge Nodes.

You can currently use the public IPs, for example:



* To perform destination NAT done in either Tier-0 or Tier-1 Logical Routers for inbound public traffic to NSX-T overlay.
* To perform source NAT done in either Tier-0 or Tier-1 Logical Routers for outbound public traffic from NSX-T overlay.
* To establish VPNs in either Tier-0 or Tier-1.



For more information, see [Network Services provided by Tier-0 and Tier-1 Logical Routers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-nsx-t-vpc-routingvpc-ryo-nsx-t-vpc-routing-edge-services).

For public IPs, you can currently use one or more /32 IP address, but you cannot have subnets, such as /29 or /26.
--------------------







 ibmcloud is subnet-reserved-ip-create 

Reserve an IP in a subnet.

ibmcloud is subnet-reserved-ip-create SUBNET [--vpc VPC] [--name NAME] [--address ADDRESS] [--auto-delete true | false] [--target TARGET] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is subnet-reserved-ip-create 2201-3f2e33d4-2140-44b4-843c-d73e03d585f1 --name my-reserved-ip --address 10.240.64.10 --auto-delete true
* ibmcloud is subnet-reserved-ip-create my-subnet --name my-reserved-ip --address 10.240.64.10 --auto-delete true
* ibmcloud is subnet-reserved-ip-create 2201-3f2e33d4-2140-44b4-843c-d73e03d585f1 --name my-reserved-ip --address 10.240.64.10 --auto-delete true --target r134-5be98168-017a-459c-959f-7a6c1f7b813b
* ibmcloud is subnet-reserved-ip-create my-subnet --name my-reserved-ip --address 10.240.64.10 --auto-delete true --target my-vpe
* ibmcloud is subnet-reserved-ip-create 2201-3f2e33d4-2140-44b4-843c-d73e03d585f1 --name my-reserved-ip --address 10.240.64.10 --output JSON







 Command options 



* SUBNET: ID or name of the subnet.
* --vpc: ID or name of the VPC.
Logging for API Connect V10 Reserved 

IBM® API Connect for IBM Cloud® V10 Reserved exposes platform logs that you can monitor with the IBM Log Analysis service.

To monitor the logs for V10 Reserved, you must configure a logging instance in a region. For information, see [Configuring IBM Cloud platform logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_svc_logs).
You can also see the specifics of the reserved IP address that was used for the virtual network interface of the mount target in the primary_ip section. By default the virtual network interface is deleted along with the mount target when the mount target is deleted.

{
"access_control_mode": "security_group",
"created_at": "2023-05-30T01:59:46.000Z",
"href": "$vpc_api_endpoint/v1/shares/0995b8c6-c323-4e59-9ea9-fa14dd66bba8/mount_targets/9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"id": "9fdf4438-f5b4-4b6f-8bca-602494fd6c31",
"lifecycle_reasons": [],
"lifecycle_state": "deleting",
"mount_path": "domain.com:/vol_xyz_2891fd0a_63aa_4deb_9ed5_1159e37cb5aa",
"name": "target-name1",
"primary_ip": {
"address": "10.10.12.64",
"href": "$vpc_api_endpoint/v1/subnets/2302-ea5fe79f-52c3-4f05-86ae-9540a10489f5/reserved_ips/0716-6fd4925d-7774-4e87-829e-7e5765d454ad",
"id": "0716-6fd4925d-7774-4e87-829e-7e5765d454ad",
"name": "my-reserved-ip",
"resource_type": "subnet_reserved_ip"
},
The Reserved IPs tab is a list of all reserved IPs associated with the subnet. For more information about Reserved IPs, see [Managing IP addresses](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-ip-addresses&interface=ui).





 Creating subnets in VPC using the CLI 

To create a subnet by using the CLI, run the following command:

ibmcloud is subnet-create SUBNET_NAME VPC ((--zone ZONE_NAME --ipv4-address-count ADDR_COUNT) | --ipv4-cidr-block CIDR_BLOCK) [--acl ACL] [--pgw PGW] [--rt RT] [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--output JSON] [-q, --quiet]

Where:

SUBNET_NAME
: Name of the subnet.

VPC
: ID or name of the VPC.

--ipv4-cidr-block
: The IPv4 range of the subnet. This option is mutually exclusive with --ipv4-address-count.

--ipv4-address-count
: The total number of IPv4 addresses required, must be a power of 2 and minimum value is 8. This option is mutually exclusive with --ipv4-cidr-block.

--zone
: Name of the zone.

--acl
: The ID or name of the network ACL.

--pgw
: The ID or name of the public gateway.

--rt
: The ID or name of the routing table.

--resource-group-id
: The ID of the resource group. This ID is mutually exclusive with --resource-group-name.

--resource-group-name
: Name of the resource group. This name is mutually exclusive with --resource-group-id.

--output
: Specify output format, only JSON is supported. One of: JSON.
--bgp-cer-cidr BGP_CER_CIDR
: Specify the BGP customer edge router CIDR.

--bgp-ibm-cidr BGP_IBM_CIDR
: Specify the BGP IBM CIDR.

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

--carrier-name value
: Specify the gateway CARRIER NAME.

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

--ccr XCR
: Select the IBM cross-connect router for the Direct Link connection.

--customer-name value
: Specify the gateway CUSTOMER NAME.

--default-export-route-filter value
: Default export route filter. One of permit, deny.

--default-import-route-filter value
: Default import route filter. One of permit, deny.

--location-name LOCATION
: Specify the location name; for example, dal10.

--resource-group-id value
: Resource group ID for this resource. If unspecified, the account's default resource group is used.

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

--speed-mbps SPEED_MBPS
: Specify a value for the speed.

--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.
* ibmcloud is instance-network-interface-create my-vnic 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --address 10.2.3.4 --ip-name my-reserved-ip --auto-delete false
* ibmcloud is instance-network-interface-create my-vnic 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --address 10.2.3.4 --ip-name my-reserved-ip --auto-delete false --sg 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --sg 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8
* ibmcloud is instance-network-interface-create my-vnic my-instance my-subnet --sg my-sg-1 --sg my-sg-2 Create a network interface for a virtual server instance with security group by using resource name.







 Command options 



* NIC_NAME: Name of the network interface.
* INSTANCE: ID or name of the instance.
* SUBNET: ID or name of the subnet.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --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.
* --reserved-ip-id is the ID of the reserved IP address to be unbound.
* -f, --force forces the operation without confirmation.









 Binding and unbinding a reserved IP address with the API 

To bind or unbind a reserved IP address by using the API, perform the following prerequisites and procedures.



 Prerequisites 

The following prerequisites must be met before you can use the API to bind or unbind reserved IP addresses:



1. Set up your [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup).
2. Store the following values in variables to use in the API command:

export EndpointGatewayId=<endpoint_gateway_id>
export ReservedIPId=<reserved_ip_id>







 Binding a reserved IP to an endpoint gateway 

To bind an endpoint gateway for the specific VPC, see the following example:

curl -X PUT
-sH "Authorization:${iam_token}"
"$vpc_api_endpoint/v1/endpoint_gateways/$EndpointGatewayId/ips/$ReservedIPId?version=$api_version&generation=2"





 Unbinding a reserved IP to an endpoint gateway 

To unbind an endpoint gateway for the specific VPC, see the following example:

curl -X DELETE
-sH "Authorization:${iam_token}"
"$vpc_api_endpoint/v1/endpoint_gateways/$EndpointGatewayId/ips/$ReservedIPId?version=$api_version&generation=2"
* --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.
* --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).
* --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.
* --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).
A profile is a combination of vCPU and RAM that can be instantiated quickly to start a virtual server instance. In the IBM Cloud console, you can choose from popular profile configurations or select from a list of profiles that best fit your needs. For more information, see [Profiles](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profiles).







 October 2018 



 03 October 2018 

Provision virtual server by using 3rd-party images
: You can now provision a virtual server instance from an image that was created by a 3rd party vendor by using the IBM Cloud catalog Cloud Images link. To access the link, you must first have your catalog credentials set up with an upgraded account to order virtual servers. For more information, see [Third-party images](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-3rd-party).





 30 October 2018 

View suspended billing on your virtual server
: You can now view whether your virtual server instance supports billing. For more information, see [Viewing suspend billing](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-viewing-suspend-billing-feature).





 31 October 2018 

Placement groups available on virtual servers
: With placement groups, you can use public instances to build for high availability within a data center or provide and extra level of fault tolerance within a larger deployment. Each placement group can be assigned a maximum of 5 new virtual server instances. Each virtual server is provisioned on different physical hosts. For more information, see [Placement groups](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-placement-groups).







 September 2018 



 26 September 2018 

Reserved servers now available
: Reserved servers offer guaranteed resources for future deployments and with one or three year contract terms, offers you cost savings. You can reserve up to 20 virtual server instances of a specific size. Reserved capacity must be provisioned first before other virtual server instances.
Configurations of the two secondary interfaces are specified in JSON format. See help text for '--network-interfaces' option.







 Command options 



* --name: Name of the server.
* --zone: Name of the zone.
* --profile: Name of the bare metal server profile.
* --image: ID or name of the image.
* --keys: Comma-separated IDs or names of SSH keys.
* --user-data: data|@data-file. User data to transfer to the bare metal server.
* --pnic-name: Name of the primary network interface.
* --pnic-subnet: Subnet ID or name for the primary network interface.
* --vpc: ID or name of the VPC. This ID or name is only required to specify the unique subnet by name inside this VPC.
* --pnic-rip: ID or name of the existing reserved IP that is bound to the primary network interface.
* --pnic-rip-address: The IP address of the primary network interface to reserve, which must not already be reserved on the subnet.
* --pnic-rip-auto-delete: If set to true, this reserved IP of the primary network interface automatically deletes when the target is deleted. One of: true, false. (default: true).
* --pnic-rip-name: The user-defined name for this reserved IP of the primary network interface. Names must be unique within the subnet that the reserved IP resides in. Names beginning with ibm- are reserved for provider-owned resources.
* --pnic-sgs: Comma-separated security group IDs for primary network interface.
* --pnic-allowed-vlans: Comma-separated VLAN IDs. Indicates which VLAN IDs (for VLAN interfaces only) can use the primary network interface. It can be passed as separate values or as any range of numbers.
* --pnic-ein: Enable Infrastructure NAT (EIN). If true, the VPC infrastructure performs any needed NAT operations.
You can bind or unbind a reserved IP address by using the CLI.

Before you begin, make sure to [set up your CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).



 Binding a reserved IP to an endpoint gateway 

To bind a reserved IP to an endpoint gateway by using the CLI, run the following command:

ibmcloud is endpoint-gateway-reserved-ip-bind ENDPOINT_GATEWAY --reserved-ip-id RESERVED_IP_ID [--json]

Where:



* ENDPOINT_GATEWAY is the ID of the endpoint gateway.
* --reserved-ip-id is the reserved IP identity to be used as the primary IP for the network interface. If not specified, an available address on the subnet is selected and reserved automatically.
* --json forces the operation without confirmation.







 Unbinding a reserved IP to an endpoint gateway by using the CLI 

To unbind a reserved IP to an endpoint gateway by using the CLI, run the following command:

ibmcloud is endpoint-gateway-reserved-ip-unbind ENDPOINT_GATEWAY (--address ADDRESS | --reserved-ip-id RESERVED_IP_ID) [-f, --force]

Where:



* ENDPOINT_GATEWAY is the ID of the endpoint gateway.
* --address is the reserved IP address to be unbound.
* --reserved-ip-id is the ID of the reserved IP address to be unbound.
* -f, --force forces the operation without confirmation.









 Binding and unbinding a reserved IP address with the API 

To bind or unbind a reserved IP address by using the API, perform the following prerequisites and procedures.



 Prerequisites 

The following prerequisites must be met before you can use the API to bind or unbind reserved IP addresses:



1.
* --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).
* --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.
* --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.
For more information about creating a version for the catalog offering, see [Onboarding software to your account](https://cloud.ibm.com/docs/account?topic=account-create-private-catalog&interface=cli).
* --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.
* --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.
* --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).
* --metadata-service, --ms: Enable or disable the Instance Metadata Service. One of: true, false.
* --metadata-service-protocol, --msp: The communication protocol for the metadata service endpoint.