vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Virtual servers can use a shared high-capacity SAN-based primary storage platform or high-performance local disk storage. Because each instance is part of the larger cloud environment, communication between all virtual servers is instantaneous.
* Why do I receive a capacity error when I provision a virtual server?

When you provision a virtual server, you might receive an insufficient capacity to complete the request error. When provisioning fails, all the virtual server instances within that particular request fail. A capacity error occurs when the data center or router has insufficient resources to fulfill the service request. Resource availability changes frequently, so you might wait and try again later. For more information about strategies to avoid this error, see [Resource considerations for virtual server instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-capacity-considerations).
* How do I log in to my server?

Log in to your console and go to your Devices menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-navigating-devices). In the Device List, select your instance. You can view and manage the device usernames and passwords to use to log in. For more information, see [Viewing and managing device usernames and passwords](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-view-update-user-name-password-for-device).
* How do I use VPN to access the IBM Cloud Private network?

You can log in to the VPN through [the web interface](https://www.softlayer.com/VPN-Access) or use a [stand-alone VPN client](https://cloud.ibm.com/docs/iaas-vpn?topic=iaas-vpn-standalone-vpn-clients) for Linux, macOS, or Windows.
[IBM Cloud® Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-started) Cloud Functions is a polyglot Functions-as-a-Service (FaaS) programming platform based on Apache OpenWhisk that you can use to write lightweight code called actions. [More info](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-logs) 
 [IBM Cloud® Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-getting-started) Code Engine is a fully managed, serverless platform that runs your containerized workloads, including web apps, micro-services, event-driven functions, or batch jobs [More info](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logs). 







 Container services 

The following table lists services that send logs to IBM Log Analysis:



Table 3. List of container services

 Service Description More info 

 [IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started) You can use IBM Cloud Container Registry to provide a multi-tenant private image registry that you can use to store and share your container images with users in your IBM Cloud account. [More info](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_logs) 
 [IBM Cloud® Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-getting-started) You can use the IBM Cloud Kubernetes Service service to deploy highly available apps in Docker containers that run in Kubernetes clusters. [More info](https://cloud.ibm.com/docs/containers?topic=containers-healthlogdna)
The client can also configure their compute VMs to uses these forwarders, if required.
* VMware Update Manager (VUM) provides updating of vSphere hosts and VM hardware and tools. VUM uses the Proxy to gain access to the internet repositories.



VMware Aria Operations collects data from objects in the environment. Each piece of data that is collected is called a metric observation or value. VMware Aria Operations uses the vCenter adapter to collect raw metrics from vCenter. In addition to the metrics it collects, VMware Aria Operations calculates capacity metrics, badge metrics, and metrics to monitor the health of your system. Alert definitions are a combination of symptoms and recommendations that identify problem areas and generate alerts on which you act for those areas.





 Monitored components 



 Monitoring of vCenter 

The monitoring of vCenter is accomplished with VMware Aria Operations and the VMware SDDC Health Management Pack. VMware Aria Operations for Logs collects the log data from vCenter and the Content Pack for vSphere adds specific understanding to the logs and in turn sends alerts to VMware Aria Operations.

The VMware SDDC Health Management Pack monitors the SDDC Management stack and provides badges for health and alerts related to configuration and compliance of SDDC product components that include vCenter.





 Monitoring of vSphere hosts 

Monitoring of the vSphere hosts is accomplished with VMware Aria Operations through vCenter and the collection of logs through VMware Aria Operations for Logs.





 Monitoring of vSAN 

To monitor vSAN, VMware Aria Operations, and VMware Aria Operations for Logs are used. In vCenter, you can use an extra set of vSAN Health Checks. Installation of the Management Pack for vSAN provides more dashboards to aid with the monitoring of vSAN.

VMware Aria Operations generates an alert if a problem occurs in the SDDC product components in the storage area network that the VMware vSAN adapter is monitoring. An alert that is related to configuration compliance and health is passed through VMware SDDC Health Solution management pack from VMware vSAN Management Pack.
VMware Aria Operations and the VMware Aria Operations Management Pack for VMware NSX provides visibility into the network topology. VMware Aria Operations for Logs collects the log data from the NSX components such as Controllers, ESG, and logical switches. VMware Aria Operations™ for Networks provides in-depth troubleshooting of network issues. 



In addition to monitoring, Operations Management on IBM Cloud, helps with configuration, compliance, and many of the proactive tasks detailed in this documentation.





 Related links 



* [About vSphere Monitoring and Performance](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.monitoring.doc/GUID-A8B06BE0-E5FC-435C-B12F-A31618B21E2C.html)
* [VMware security hardening guides](https://www.vmware.com/security/hardening-guides.html)
* [Operations management introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-opsmgmt-intro)
* [Considerations about changing vCenter Server artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impactvcenter_chg_impact)
Understanding connectivity options for the VPC environment 

The following table provides information on VPC network flows and connections for various scenarios you might encounter.



Table 1. Details about VPC network flows and connections

 Use Case                          From                                                                         To                                                                                                                                     Connection through      Connection method                    

 Local networks                    Virtual Server (VPC)<br><br>Location: VPC 1, Zone 1, Subnet 1                Virtual Server (VPC)<br><br>Location: VPC 1, Subnet 1, Zone 1                                                                          Private backbone        Automatic, through VPC routing table 
 Local networks                    Virtual Server (VPC)<br><br>Location: VPC 1, Zone 1, Subnet 1                Virtual Server (VPC)<br><br>Location: VPC 1, Subnet 2, Zone 2                                                                          Public internet         VPN gateway with VPN Connection      
 Multi-region networks             Virtual Server (VPC)<br><br>Location: Region A, VPC 1, Zone 1, Subnet 1      Virtual Server (VPC)<br><br>Locations: Region B, VPC 2, Subnet 1, Zone 3<br><br>Region C, VPC 3, Subnet 1, Zone 1                      Private backbone        Transit gateway                      
 Local networks                    Virtual Server (VPC)<br><br>Location: VPC 1, Zone 1, Subnet 1                Bare Metal<br><br>Location: Classic Infrastructure data center 1                                                                       Public internet         IPSec VPN                            
 Local networks                    Virtual Server (VPC)<br><br>Location: VPC 1, Zone 1, Subnet 1                Bare Metal<br><br>Location: Classic Infrastructure data center 1                                                                       Private backbone        VRF-enabled account                  
 Multi-region networks             Virtual Server (VPC)<br><br>Location: Region A, VPC 1, Zone 1, Subnet 1      Bare Metal<br><br>Locations: Region B, Classic Infrastructure data center 1<br><br>Region C, Classic Infrastructure data center 1      Private backbone        Transit gateway                      
 Cloud-to-intranet (Dev/Test)      Virtual Server (VPC)<br><br>Location: VPC 1, Zone 1, Subnet 1                On-Premise network                                                                                                                     Public internet         VPN gateway with VPN Connection      
 Cloud-to-intranet (Production)    Virtual Server (VPC)<br><br>Location: VPC 1, Zone 1, Subnet 1                On-Premise network                                                                                                                     Private backbone        Direct Link
That is, virtual machine (VM) workloads that are currently functioning continue to function without an outage if you complete the following procedure. Enterprises must engage their change management policies to enable a structured and communicated upgrade and plan for contingencies. However, during the upgrade process of certain management functions, such as vCenter Server and NSX Manager, temporary outages of management functions, configuration changes, powering off and on VMs, might be impacted.







 Before you begin 

The time to complete the upgrade is unknown. It is possible that it might take several maintenance windows to completely upgrade an environment. Running up-leveled and down-leveled versions of the SDDC software is supported by VMware during the upgrade process. However, some functions such as vMotion, maybe limited during this process.

Complete the following requirements before you begin the upgrade:



* Upgrade any extensions or snap-ins within the vCenter Server environment. Review the following documentation before you plan your upgrade:



* [VMware vSphere 7.0 release notes](https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html)
* [About VMware ESXi upgrade](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-65B5B313-3DBB-4490-82D2-A225446F4C99.html)



* Set up vSphere Update Manager (VUM) within your vCenter Server instance to download updates from VMware vSphere. For more information, see [VMware Update Manager introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-introvum-intro).
* Open a support ticket with the IBM Cloud for VMware Solutions team to notify them that an upgrade is being planned. The ticket remains open until the instance is registered at the upgraded level in the IBM Cloud for VMware Solutions console.
KMIP for VMware overview 

The Key Management Interoperability Protocol (KMIP™) for VMware® service provides a highly available service to manage encryption keys that are used by VMware in IBM Cloud®. This service offers runtime capability to allow customers to create, retrieve, activate, revoke, and destroy the encryption keys. It also provides management capability to maintain the associations between the client credentials and the encryption keys.

The KMIP for VMware service is available as a stand-alone service without being associated to a VMware instance. Each instance of the service can serve one or more VMware vCenter Server® instances or VMware vSphere® clusters.

The supported client applications are vCenter Server 6.7 and 7.0 and vSphere 6.7 and 7.0.



 Technical specifications for KMIP for VMware 

For more information about resource requirements and planning for KMIP for VMware, see [Planning for KMIP for VMware](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip-implementationkmip-implementation-planning).

The following specifications are included with the KMIP for VMware service:



* A VMware-compatible KMIP
* Two managed services - [Key Protect](https://cloud.ibm.com/catalog/services/key-protect) and [Hyper Protect Crypto Services](https://cloud.ibm.com/catalog/services/hyper-protect-crypto-services)
* Available in multiple geographic regions worldwide
* Highly available KMIP network service endpoints provided in each region







 Considerations when you install KMIP for VMware instances 

Review the following considerations before you install a KMIP for VMware instance:



* KMIP for VMware uses the IBM Key Protect service or the Hyper Protect Crypto Services (HPCS) service to create, encrypt, and decrypt encryption keys. Therefore, before you install KMIP for VMware, ensure that you review the following considerations.



* You ordered a usable Key Protect or HPCS service instance in the IBM Cloud region where your KMIP for VMware instance is to be hosted:
ibmcloud dl virtual-connection-create|vcc --type TYPE --network-id NETWORK_ID --name VIRTUAL_CONNECTION_NAME [--help|-h] [--output format]



 Command options 

--type TYPE
: Specify the type of virtual connection. Values are classic or vpc.

--network-id NETWORK_ID
: Specify the ID of the network. Not required when using classic type.

--name NAME
: Specify the name of the virtual connection.

--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.





 Examples 



* ibmcloud dl virtual-connection-create fb0df64a-ef8d-4b3c-b473-dc0230593529 --type vpc --network-id crn:v1:staging:public:is:us-south:a/28e4d90ac7504be694471ee66e70d0d5::vpc:r134-b8b62f60-f152-471f-971a-376da52721e0 --name newVC
* ibmcloud dl vcc fb0df64a-ef8d-4b3c-b473-dc0230593529 --type vpc --network-id crn:v1:staging:public:is:us-south:a/28e4d90ac7504be694471ee66e70d0d5::vpc:r134-b8b62f60-f152-471f-971a-376da52721e0 --name newVC --output json









 ibmcloud dl virtual-connection-delete 

Delete a virtual connection.

ibmcloud dl virtual-connection-delete|vcd GATEWAY_ID VIRTUAL_CONNECTION_ID [--help|-h] [--force|-f]
[IBM® Event Streams for IBM Cloud®](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-getting_started) event-streams [Location-based events](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-at_events) 







 Network services 

The following table lists network services that send auditing events:



Table 7. List of network services

 Service CRN service name Events 

 [IBM Cloud® Direct Link solution](https://cloud.ibm.com/docs/dl?topic=dl-get-started-with-ibm-cloud-dl) directlink.dedicated [Global events](https://cloud.ibm.com/docs/dl?topic=dl-at_events) 
 [IBM Cloud® Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started) transit [Global events](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-at_events) 
 [IBM Cloud® DNS Services](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-getting-started) dns-svcs [Global events](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-at_events) 
 [IBM Cloud® Internet Services (CIS)](https://cloud.ibm.com/docs/cis?topic=cis-getting-started) internet-svcs [Global events](https://cloud.ibm.com/docs/cis?topic=cis-at_events) 







 Observability services 

The following table lists observability services that send auditing events:



Table 8. List of observability services

 Service CRN service name Events
You can create and assign a floating IP to a virtual server instance to provide your service with outbound connectivity to a third-party vendor service or external service. One floating IP can be assigned to multiple virtual server instances and subnets.

The following diagram demonstrates the difference in applying external connectivity to a service through a public gateway and a floating IP address. In this scenario, three virtual server instances are connecting to services and customers through a public gateway and floating IP address.

External service 1 and External service 2 (logging) receive outbound traffic from Virtual server instance 1 and Virtual server instance 2 through a single Public gateway connection. Floating IP address 1, which is associated with this public gateway connection, allows the Virtual server instances to access External service 1 by IP address through a firewall. The External customer sends and receives traffic to and from Virtual server instance 3 through floating IP address 2:

Zoom

![Examples of external connectivity](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/public-gateway.svg)

Figure 1. Examples of external connectivity
technology and computing networking vpn and remote access 
 technology and computing networking 
 technology and computing operating systems linux 
 technology and computing operating systems mac os 
 technology and computing operating systems unix 
 technology and computing operating systems windows 
 technology and computing operating systems 
 technology and computing programming languages c and c++ 
 technology and computing programming languages java 
 technology and computing programming languages javascript 
 technology and computing programming languages visual basic 
 technology and computing programming languages 
 technology and computing software databases 
 technology and computing software desktop publishing 
 technology and computing software desktop video 
 technology and computing software graphics software animation 
 technology and computing software graphics software 
 technology and computing software net conferencing 
 technology and computing software shareware and freeware 
 technology and computing software 
 technology and computing tech news 
 technology and computing technical support 
 technology and computing technological innovation 
 technology and computing 
 travel budget travel 
 travel business travel 
 travel honeymoons and getaways 
 travel hotels 
 travel specialty travel adventure travel 
 travel specialty travel ecotourism 
 travel specialty travel sightseeing tours 
 travel specialty travel vineyards 
 travel tourist destinations africa 
 travel tourist destinations australia and new zealand 
 travel tourist destinations canada 
 travel tourist destinations caribbean 
 travel tourist destinations eastern europe 
 travel tourist destinations europe 
 travel tourist destinations france 
 travel tourist destinations greece 
 travel tourist destinations italy 
 travel tourist destinations japan 
 travel tourist destinations mexico and central america 
 travel tourist destinations national parks 
 travel tourist destinations seaside resort 
 travel tourist destinations ski resorts 
 travel tourist destinations south america 
 travel tourist destinations spas 
 travel tourist destinations theme parks 
 travel tourist destinations united kingdom 
 travel tourist destinations 
 travel tourist facilities bed and breakfast 
 travel tourist facilities camping 
 travel tourist facilities hotel 
 travel transports air travel air and space accident 
 travel transports air travel airfare 
 travel transports air travel airlines 
 travel transports air travel airplanes 
 travel transports air travel airports 
 travel transports air travel helicopters 
 travel transports air travel 
 travel transports public transport 
 travel transports road travel road accident 
 travel transports sea travel cruises 
 travel transports train travel 
 travel travel agencies 
 travel travel guides 
 travel traveling with kids 
 travel vacation rentals 
 travel
SC-2 - Application Partitioning 



  Control requirements 

SC-2 - 0
:   The information system separates user functionality (including user interface services) from information system management functionality.





  Implementation guidance 

See the resources that follow to learn more about how to implement this control.



*  [Creating and connecting the management and workload VPCs](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-create-vpcs)







  IBM Cloud for Financial Services profile 

The rules related to this control that follow are part of the IBM Cloud for Financial Services v1.2.0 profile in [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started).



*  Check whether at least # Virtual Private Cloud (VPC)s have been created
*  Check whether at least # instances of Transit Gateway have been created







  NIST supplemental guidance 

Information system management functionality includes, for example, functions necessary to administer databases, network components, workstations, or servers, and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical. Organizations implement separation of system management-related functionality from user functionality by using different computers, different central processing units, different instances of operating systems, different network addresses, virtualization techniques, or combinations of these or other methods, as appropriate. This type of separation includes, for example, web administrative interfaces that use separate authentication methods for users of any other information system resources. Separation of system and user functionality may include isolating administrative interfaces on different domains and with additional access controls.
* CLI
* API
* Terraform







 Using virtual private endpoints for VPC to privately connect to DNS Services 

IBM Cloud® Virtual Private Endpoints (VPE) for VPC enables you to connect to DNS Services from your VPC network by using the IP addresses of your choosing, allocated from a subnet within your VPC.

VPEs are virtual IP interfaces that are bound to an endpoint gateway created on a per service, or service instance, basis (depending on the service operation model). The endpoint gateway is a virtualized function that scales horizontally, is redundant and highly available, and spans all availability zones of your VPC. Endpoint gateways enable communications from virtual server instances within your VPC and IBM Cloud® service on the private backbone. VPE for VPC gives you the experience of controlling all the private addressing within your cloud. For more information, see [About virtual private endpoint gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpe).



 Before you begin 

Before you target a virtual private endpoint for DNS Services you must complete the following tasks.



* Ensure that a [Virtual Private Cloud is created](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-started).
* Make a plan for your [virtual private endpoints](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-considerations).
* Ensure that [correct access controls](https://cloud.ibm.com/docs/vpc?topic=vpc-vpe-configuring-acls) are set for your virtual private endpoint.
* Understand the [limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-limitations-vpe) of having a virtual private endpoint.
* Understand how to [view details](https://cloud.ibm.com/docs/vpc?topic=vpc-vpe-viewing-details-of-an-endpoint-gateway) about a virtual private endpoint.







 Setting up a VPE for DNS Services