vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[IA-2 - Identification and Authentication (organizational Users)](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2ia-2)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2control-requirements)
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2implementation-guidance)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2scc-fs-cloud-profile)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2nist-supplemental-guidance)



[IA-2 (1) - Network Access to Privileged Accounts](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2.1ia-2.1)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2.1control-requirements)
* [Implementation guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2.1implementation-guidance)
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2.1scc-fs-cloud-profile)
* Always On Failover Cluster Instances - SQL Server Always On Failover Cluster Instances (FCIs) use Windows Server Failover Clustering (WSFC) to provide high availability at the server instance level. An FCI is a single instance of SQL Server, deployed across WSFC nodes. FCIs require shared storage that all WSFC nodes can access. This guide does not discuss Always On Failover Cluster Instances.







 About Microsoft storage spaces 

The Microsoft SQL on VPC deployment patterns leverage Microsoft Storage Spaces. Storage Spaces is a technology in Windows Server that is conceptually similar to RAID, and is implemented in the operating system. Storage spaces can be used to group data volumes together into a storage pool and then the capacity from the pool is then used to create Storage spaces (virtual disks). A storage space appears to the Windows operating system as a regular drive from which you can create formatted volumes.

To create a storage space, a storage pool is first created. A storage pool is a collection of data volumes and enables storage aggregation and elastic capacity expansion. Then, a virtual disk is created where a resiliency type is assigned:



* Simple - Stripes data across data volumes to maximize disk capacity and increases throughput. Requires at least one data volume.
* Mirror - Stores two or three copies of the data across the set of data volumes to increases reliability, but reduces capacity. Requires at least two data volumes to protect from single disk failure and at least five data volumes to protect from two simultaneous disk failures.
* Parity - Stripes data and parity information across data volumes to increases reliability through journaling, but reduces capacity. Requires at least three physical disks to protect from single disk failure.



From a virtual disk, you can create one or more volumes, where you can configure the size, drive letter or folder, file system (NTFS file system or Resilient File System (ReFS), allocation unit size, and optionally a volume label.

For more information, see [Storage Spaces](https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/overview).





 About MS SQL Server 2019 editions 

A summary of SQL Server editions are as follows:
Which operating systems are supported in Parallels Server 4 Bare Metal? 

See the following table to see what operating systems are supported in Parallels Server 4 Bare Metal.



Table 1. Parallels Server 4 supported operating systems

 Operating system                                    Virtual machine  Virtuozzo container 

 Windows 7 (x32, x64)                                √                x                   
 Windows Server 2008 R2 (x32, x64)                   √                x                   
 Windows Server 2003 R2 (x32, x64)                   √                x                   
 Windows Vista with Service Pack 1 and 2 (x32, x64)  √                x                   
 Windows XP with Service Pack 2 and 3 (x32, x64)     √                x                   
 Windows 2000 with Service Pack 4 (x32, x64)         √                x                   
 Red Hat Enterprise Linux 5.3 (x32, x64)             √                √                   
 Red Hat Enterprise Linux 4.7 (x32, x64)             √                √                   
 CentOS 5.3 (x32, x64)                               √                √                   
 CentOS 4.7 (x32, x64)                               √                √                   
 Fedora 11 (x32, x64)                                √                √                   
 Fedora 10 (x32, x64)                                √                √                   
 SUSE Linux Enterprise Server 10 (x32, x64)          √                √                   
 Debian GNU/Linux 5.0 (x32, x64)                     √                √                   
 Debian GNU/Linux 4.0 (x32, x64)                     √                √                   
 Ubuntu Linux 9.04 (x32, x64)                        √                √                   
 Ubuntu Linux 8.10 (x32, x64)                        √                √                   
 FreeBSD 7 (x32, x64)                                √                x                   
 FreeBSD 6 (x32, x64)                                √                x                   



Virtuozzo Containers aren't licensed or supported with Parallels Server 4 Bare Metal by IBM Cloud®.

As of 04/05/2019, [Parallels Server 4 Bare Metal readme file](https://download.parallels.com/doc/psbm/en/Readme.pdf){ :external}
Ordering, viewing, and deleting services for Security and Compliance Readiness Bundle instances 

New deployments of Security and Compliance Readiness Bundle instances are no longer supported. You can still add or delete clusters, add or delete VMware ESXi™ servers or NFS storage, and add or remove services for existing instances. You can also view and delete your Security and Compliance Readiness Bundle instances.

You can order services for your Security and Compliance Readiness Bundle instances, such as a security and compliance solution. When you no longer need these services, you can delete them from your instances.



 Available services for Security and Compliance Readiness Bundle instances 

The following services are available for Security and Compliance Readiness Bundle instances:



* [Veeam Backup and Replication](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeamvm_overview)
* [Juniper vSRX](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-juniper-overview)
* [VMware HCX](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_considerations)
* [Red Hat OpenShift for VMware](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-ocp_overview)







 Procedures to order, view, or delete services for Security and Compliance Readiness Bundle instances 

The procedures to order, view, and delete services for Security and Compliance Readiness Bundle instances are similar to the procedures for VMware vCenter Server® instances. For more information, see the following topics:



* [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices)
* [Viewing services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_viewingservices)
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --metadata-service true Create instance template with metadata service enabled or disabled
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --metadata-service true --metadata-service-protocol http --metadata-service-response-hop-limit 60 Create instance template with metadata service configuration
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --host-failure-policy restart Create instance template with availability policy on host failure
Zone [List all regions](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referenceregions) <br>List all zones in a region](/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-referencezones) 







 Creating a bare metal server 

After you have all the information ready, you can use the CLI to create a bare metal server.

For example, you can create a bare metal server with the following configuration:



* For x86 architecture:



* ESXi image ID: "r134-31c8ca90-2623-48d7-8cf7-737be6fc4c3e"
* SSH Key ID: "a6b1a881-2ce8-41a3-80fc-36316a73f803"
* Name of the bare metal server: "my-bare-metal-server"
* A primary network interface with the following configurations:



* VLAN with the ID of "4" to attach to the server
* Name: "my-primary-network-interface"
* Subnet ID: "7ec86020-1c6e-4889-b3f0-a15f2e50f87e"



* A secondary VLAN interface with ID "4". This VLAN interface is floatable.
* Profile name: "bx2d-metal-192x768"
* Zone: "us-south-1"
In this file, add the configuration to create resource instances by using the HashiCorp Configuration Language. For more information about using this configuration language, see the [Terraform documentation](https://www.terraform.io/docs/language/index.html).

The following example creates a Continuous Delivery service instance by using the ibm_resource_instance resource, where name is a unique, descriptive name that identifies the resource instance.

data "ibm_resource_group" "group" {
name = "default"
}

resource "ibm_resource_instance" "cd_service_instance" {
name = "my CD service instance"
service = "continuous-delivery"
plan = "lite"
location = "us-south"
resource_group_id = data.ibm_resource_group.group.id
}

For more information about ibm_resource_instance, see the argument reference details in the [Terraform Registry Documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/resource_instance).

To provision your service instance to use customer-managed encryption, add and populate the parameters attribute with your key management service instance ID and root key ID.

parameters = {
kms_instance = <kms_instance_id>
kms_key = <kms_key>
}
3. Initialize the Terraform CLI.

terraform init
4. Create a Terraform execution plan. This plan summarizes all of the actions that must be run to create a Continuous Delivery service instance.

terraform plan
5. Apply the Terraform execution plan. Terraform takes all of the required actions to create the Continuous Delivery service instance.

terraform apply
To view the list of available instance profiles by using the CLI, run the following command:

ibmcloud is instance-profiles





 Viewing instance profiles with the API 

To view the list of available instance profiles by using the API, you can call the [List all instance profiles API](https://cloud.ibm.com/apidocs/vpclist-instance-profiles).

The following request example lists the available instance profiles. When you call the API, replace the API endpoint and IAM token with the values from your enterprise. For more information about the $vpc_api_endpoint and $iam_token variables, see the Authentication and Endpoint URLs sections in [Virtual Private Cloud API Introduction](https://cloud.ibm.com/apidocs/vpcabout-vpc-api).

curl -X GET "$vpc_api_endpoint/v1/instance/profiles?version=2021-02-23&generation=2" -H "Authorization: $iam_token"







 Block storage volume notes for profiles 

When you create secondary data volumes, you select a volume profile that best meets your requirements. Volume profiles are available as three predefined [IOPS tiers](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) or as a [custom IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilescustom). These volume profiles relate to virtual server instance profiles:



* A [3 IOPS general-purpose tier profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) provides IOPS/GB performance suitable for a virtual server instance Balanced profile.
* A [5-IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profilestiers) profile provides IOPS/GB performance suitable for a virtual server instance Compute profile.
If you want to disable Intel® Hyper-Threading, see [Disabling Intel Hyper-Threading Technology](https://cloud.ibm.com/docs/vpc?topic=vpc-disabling-hyper-threading).





 Next steps 

After you choose a profile, it's time to create an instance.



* [Creating an instance by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=uicreating-virtual-servers-ui)
* [Creating an instance by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=clicreating-virtual-servers-cli)
* [Creating an instance by using the API](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-rest-apisselect-profile-and-image)
* [Creating an instance by using Terraform](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=terraformcreate-instance-terraform)
* [Managing GPUs](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-gpus)
ibmcloud pi instance-update INSTANCE_ID [--memory AMOUNT] [--name NEW_NAME] [--pin-policy POLICY] [--processors NUMBER] [--processor-type TYPE] [--profile-id SAP_PROFILE_ID] [--storage-pool-affinity=True|False] [--json]



* INSTANCE_ID: The unique identifier or name of the instance.



Options



* --memory: New amount of memory for the server instance.
* --name: New name of the server instance.
* --pin-policy: New pin policy for the server instance ("none", "soft", "hard").
* --processors: New number of processors for the server instance.
* --processor-type: New processor type for the server instance.
* --profile-id: SAP profile ID.
* --storage-pool-affinity: Indicates if all volumes attached to the server must reside in the same storage pool. If set to false then volumes from any storage type and pool can be attached to the PVM instance; This impacts PVM instance snapshot, capture, and clone. For capture and clone only data volumes that are of the same storage type and in the same storage pool of the PVM instance's boot volume can be included. For snapshot all data volumes to be included in the snapshot must reside in the same storage type and pool. Once set to false, cannot be set back to true unless all volumes attached reside in the same storage type and pool.
* --json: Format output in JSON.



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







 ibmcloud pi instances 



 List all server instances 

ibmcloud pi instances [--long] [--json]

Options



* --json: Format output in JSON.
* --long: Retrieve all instance details.



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







 ibmcloud pi instance-operation 



 Perform an operation on an IBMi server instance
* NIC: ID or name of the network interface.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-network-interface-create 

Create a network interface for a virtual server instance.

ibmcloud is instance-network-interface-create NIC_NAME INSTANCE SUBNET [--vpc VPC] [--rip RIP | (--address ADDRESS --auto-delete true | false --ip-name IP_NAME)] [(--sg SG1 --sg SG2 ...)] [--allow-ip-spoofing false | true] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is instance-network-interface-create my-vnic 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3
* ibmcloud is instance-network-interface-create my-vnic 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 --rip 0711-5c7f016e-5bd2-42e3-8dff-81519e4e2469
* 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
Or you can reproduce the fingerprint of a public SSH key by entering a command similar to the following one:

ssh-keygen -E sha256 -lf id_rsa.pub



* Parameter -E specifies the hash algorithm that is used to produce the fingerprint.
* Parameter -lf specifies the file (name and location, if necessary) of the public SSH key half, which you want to check.







 Retrieving information from the CLI 

To list all of your Hyper Protect Virtual Servers service instances in your resource list from the CLI, enter the following command:

ibmcloud hpvs instances

The output displays a list of details for each instance. If you have no instances, a no instance found message is displayed.

To display details about a server instance, you need the cloud resource name (CRN) for the server instance. To get the CRN, run ibmcloud hpvs service instances. Then, run the following command:

ibmcloud hpvs instance CRN [--output json]

Where:

CRN
: Is the server's cloud resource name (CRN).

--output
: Displays results as JSON. The only valid value is json.

You can find example output [here](https://cloud.ibm.com/docs/hpvs-cli-plugindetails_list).
ibmcloud is instance-network-interfaces INSTANCE [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-profile 

View details of a virtual server instance profile.

ibmcloud is instance-profile PROFILE_NAME [--output JSON] [-q, --quiet]



 Command options 



* PROFILE_NAME: Name of the profile.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-profiles 

List all virtual server instance profiles in the region.

ibmcloud is instance-profiles [--output JSON] [-q, --quiet]



 Command options 



* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-reboot 

Restart the operating system of an instance.

ibmcloud is instance-reboot INSTANCE [--no-wait] [-f, --force] [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --no-wait: Execute the action immediately and drop all queued actions.
* --force, -f: Force the operation without confirmation.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.
* [ICM (Internet Communication Manager)](https://help.sap.com/saphelp_snc700_ehp01/helpdata/en/f9/e2350eca7f4a109eb0a7bc63135e27/frameset.htm) Service - Application server component that receives and dispatches Web requests (HTTP(S), SMTP, …). ICM evaluates the URL and forwards requests to AS ABAP or AS Java.
* IGS (Internet Graphic Server)



2. The ABAP Central Services Instances (ASCS) – This instance contains the message server, the enqueue server, and a separate start. The ASCS instance cannot process any dialog requests. It is used to manage locks, exchange messages, and balance workload in the SAP system. The ASCS instance includes:



* [Message Server](https://help.sap.com/saphelp_snc700_ehp01/helpdata/en/f9/e2350eca7f4a109eb0a7bc63135e27/frameset.htm) - The SAP message server runs as a separate process, mostly on the same host as the central instance. If an SCS instance (SAP Central Services) or ASCS instance (ABAP SCS) is configured in the system, the message server is part of this instance.
* [Stand-alone Enqueue Server](https://help.sap.com/saphelp_snc700_ehp01/helpdata/en/f9/e2350eca7f4a109eb0a7bc63135e27/frameset.htm) - Part of the central instance (ABAP or Java) that manages the SAP locks. In combination with the enqueue replication server, this single point-of-failure can be made into a high availability solution.
* ABAP Central services instance (ASCS instance) - Contains the ABAP message server and the stand-alone Enqueue Server
* The enqueue replication server instance is only mandatory in a high-availability system.





Optionally, you can install the ASCS instance with an integrated:
* OS: WIndows 2019
* NIC Qty: 1
* Data Volumes: None







 Connect to the server 

After the virtual server has been deployed you need to connect a Floating IP address to it so that you can access the server remotely, refer to [Adding a floating IP address](https://cloud.ibm.com/docs/vpc?topic=vpc-using-instance-vnicsadding-floating-ip).

Refer to [Connecting to Windows instances](https://cloud.ibm.com/docs/vpc?topic=vpc-vsi_is_connecting_windows) to access the Windows Administrator's password, however, in short the following commands are used from your laptop, where the instances command returns the <INSTANCE_ID> of the virtual server:

ibmcloud is instances
ibmcloud is instance-initialization-values <INSTANCE_ID> --private-key @/.ssh/id_rsa





 Download required files 

In this deployment pattern we are using the following products which should be downloaded to the bastion host:



* MS SQL Server Developer Edition which can be downloaded from [SQL Server products & resources](https://www.microsoft.com/en-gb/evalcenter/evaluate-sql-server-2019?filetype=EXE).
* SQL Server Management Studio (SSMS) which can be downloaded from [Download SQL Server Management Studio (SSMS)](https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15).
* Diskspd is a storage subsystem testing tool and can be downloaded from [DISKSPD 2.0.21a](https://github.com/Microsoft/diskspd/releases).
* PowerShell can interact with SQL Server instances, however, requires a module to be installed. If this module must be installed on the non-Internet connected SQL sever then download this module. Refer to [SqlServer](https://docs.microsoft.com/en-us/powershell/module/sqlserver/?view=sqlserver-ps) for more details.
"instance": {
"crn": "crn:v1:bluemix:public:dns-svcs:global:a/be636a7a6e4d4b6296bedf669ce8f757:c7295f57-4d25-4832-9d7e-a032de0c278c::"
},
"zone": {
"id": "0671b738-57f0-468e-8086-10bc480ac00e"
}
}
}

Sample output:

{
"id": "r014-e68a40fb-2b94-4a92-b8bd-dc9bb92c3ef3",
"name": "pdns-nlb-update-example",
"href": "https://us-east.iaas.cloud.ibm.com/v1/load_balancers/r014-e68a40fb-2b94-4a92-b8bd-dc9bb92c3ef3",
"crn": "crn:v1:bluemix:public:is:us-east:a/be636a7a6e4d4b6296bedf669ce8f757::load-balancer:r014-e68a40fb-2b94-4a92-b8bd-dc9bb92c3ef3",
"is_public": false,
"created_at": "2023-02-10T19:36:44Z",
"hostname": "e68a40fb-us-east.example.com",
"listeners": [],
"operating_status": "online",
"pools": [],
"private_ips": [
{
"address": "10.241.64.11",