vania-janet/multiturn-rag-retrieval-data huggingface dataset:
[DRS troubleshooting information](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-5E7F6DEC-02A2-4221-AABA-EDFB9AE9EC70.html) 
 Storage DRS is not supported on a host Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. [DRS troubleshooting information](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.resmgmt.doc/GUID-5E7F6DEC-02A2-4221-AABA-EDFB9AE9EC70.html) 
 Datastore cluster is out of space Configure to send email one time when critical when disk usage is over 85%. [Adding NFS storage to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingnfs) 
 Datastore is in multiple data centers Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. [Storage DRS cannot operate on a datastore](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.troubleshooting.doc/GUID-976F5B21-8C64-4C85-BE75-0D86655E32DD.html) 
 vSphere Distributed Switch VLAN trunked status Configure to send email one time when critical when not all the configured VLANs in the vSphere Distributed Switch were trunked by the physical switch. [Enabling vSphere Distributed Switch health check in the vSphere Web Client (2032878)](https://kb.vmware.com/s/article/2032878) 
 vSphere Distributed Switch MTU matched status Not considered essential for notification.
Important Change the NFS management datastore name back to the original name, management-share, and remount the NFS datastore as read-only on the ESXi server. 



The following table lists the operations that might be impacted if SSH or shell access is disabled for various resources.



Table 2. Operations that are impacted by SSH and shell access (local)

 Attempted change Impacted operations Severity Recovery method 

 Disable SSH or shell access for vCenter Server or PSC. Pairing a primary and secondary instance might fail. Important 



If you choose to disable SSH or shell access, re-enable it temporarily before you complete the indicated operations.





 Management subnets for vCenter Server instances 

The following information discusses the subnets that are ordered by VMware Solutions and it provides options for you to order extra subnets for your own use.

With each IBM Cloud bare metal server order, the following ranges of IP addresses are ordered by default:



* A primary public range of 32 IP addresses
* A primary private range of 64 IP addresses



In addition, the following management subnets are also reserved for IBM Cloud for VMware Solutions:



* Two portable private subnets of 64 IP addresses on the first VLAN - one for management and the other one for VTEPS
* Two portable private subnets of 64 IP addresses on the second VLAN - one for VMotion and one for vSAN
* A public portable subnet of 16 IP addresses on the public VLAN

Do not use these components for other purposes, do not change their names, and do not delete them, or the stability of your environment is severely compromised.



If you need more subnets to use, you can obtain IP addresses to use in one of the following ways.



* Option 1 (recommended) - Use VMware NSX® virtual network overlays. A sample VXLAN template is provided upon order. This VXLAN can be used as a starting point for building software-defined networking (SDN).
The change to the device queue length reduces the storage array queue for all VMs to an equal share. SIOC engages only if resources are constrained and the storage I/O latency is over a defined threshold.

In order for SIOC to determine when a storage device is congested or constrained, it requires a defined threshold. The congestion threshold latency is different for different storage types. The default selection is to 90% of peak throughput. The percentage of peak throughput value indicates the estimated latency threshold when the VMware® datastore is using that percentage of its estimated peak throughput.

Incorrectly configuring SIOC for a VMware® datastore or for a VMDK can significantly impact performance.



 Configuring Storage I/O Control for a VMware datastore 



1. Browse to the VMware® datastore in the vSphere Web Client navigator.
2. Click the Manage tab.
3. Click Settings and click General.
4. Click Edit for Datastore Capabilities.
5. Select the Enable Storage I/O Control checkbox.

Zoom

![NSF VMware® datastore.](https://cloud.ibm.com/docs-content/v1/content/04e9937a86546143babfc65ea21fdd4ea2d12d13/FileStorage//images/3_0.svg)

Select Enable Storage I/O Control.
6. Click OK.



This setting is specific to the VMware® datastore and not to the host.





 Configuring Storage I/O Control for Virtual Servers 

You can also limit individual virtual disks for individual VMs or grant them different shares with SIOC. By limiting the disks and granting different shares, you can match and align the environment to the workload with the acquired File Storage for Classic volume IOPS number. The limit is set by IOPS, and it's possible to set a different weight or "Shares."
The Client is responsible for restoration, timeliness, validity of backups, and alerting of failed backups via [IBM Cloud® Activity Tracker](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-activity-tracker.) More information can be found in the [Backup and Restore documentation](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-dashboard-backups). 
 Read-only replicas, Databases for PostgreSQL and Databases for EnterpriseDB ONLY Databases for PostgreSQL and Databases for EnterpriseDB are responsible for providing the capability of deploying read-only replicas across regions (except for replicating data into or outside of eu-de). The Client is responsible for provisioning, configuring, monitoring, and promoting read-only replicas.
ClientIPClass The classification of the visitor's IP address, possible values are: unknowncleanbadHostsearchEnginewhitelistgreylistmonitoringServicesecurityScannernoRecordscanbackupServicemobilePlatformtor string 
 ClientRefererHost The referer host string 
 ClientRefererPath The referer path requested by visitor string 
 ClientRefererQuery The referer query-string was requested by the visitor string 
 ClientRefererScheme The referer url scheme requested by the visitor string 
 ClientRequestHost The HTTP hostname requested by the visitor string 
 ClientRequestMethod The HTTP method used by the visitor string 
 ClientRequestPath The path requested by visitor string 
 ClientRequestProtocol The version of HTTP protocol requested by the visitor string 
 ClientRequestQuery The query-string was requested by the visitor string 
 ClientRequestScheme The url scheme requested by the visitor string 
 ClientRequestUserAgent Visitor's user-agent string string 
 Datetime The date and time the event occurred at the edge int or string 
 EdgeColoCode The airport code of the Cloudflare datacenter that served this request string 
 EdgeResponseStatus HTTP response status code returned to browser int 
 Kind The kind of event, currently the only possible value is firewall string 
 MatchIndex Rules match index in the chain int 
 Metadata Additional product-specific information. Metadata is organized in key:value pairs. Key and Value formats can vary by Cloudflare security product and can change over time object 
 OriginResponseStatus HTTP origin response status code returned to browser int 
 OriginatorRayID The RayID of the request that issued the challenge/jschallenge string 
 RayID The RayID of the request string 
 RuleID The Cloudflare security product-specific RuleID triggered by this request string 
 Source The Cloudflare security product triggered by this request string
Set the MTU value to 9000.





 Results 



Table 1. Results

 Network Name MTU 

 External 1500 
 Management 9000 
 vMotion 9000 









 Creating on-premises Service Mesh compute profiles 



1. Log in to the vSphere Web Client.
2. From the Home menu, select the HCX option.
3. Under Infrastructure, click InterConnect.
4. Under Multi-Site Service Mesh, click Compute Profiles.
5. From Create Compute Profile:



1. Provide Compute Profile Name.
2. Select All Services to be enabled, click Continue.
3. Select the Cluster, click Continue.
4. Select the Datastore, click Continue.
5. Select Network Profile for Management, click Continue.
6. Select Network Profile for External/Uplink, click Continue.
7. Select Network Profile for vMotion, click Continue.
8. Select Network Profile for vSphere Replication (Management), click Continue.
9. Select Distribute Switch for extension, for example, Private-Switch, click Finish.







 Results 

A compute profile for the cluster and storage combination is created and is available with the Service Mesh creation.









 HCX on-premises Service Mesh 





 Creating on-premises Service Mesh 



1. Log in to the vSphere Web Client.
2. From the Home menu, select the HCX option.
3. Under Infrastructure, click InterConnect.
4. Under Multi-Site Service Mesh, click Service Mesh.
5. From Create Service Mesh:



1. Select sites: on-premises and vCloud Organization, click Continue.
2. Select Source Compute Profile.
3. Select Remote Compute Profile. For example, CloudCompute.
4. Select All Services, click Continue.
5. Click Continue, on page Advanced Configuration - Override Uplink Network profiles (Optional)
6. Click Continue.
7.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4

 buildctl --version
buildctl github.com/moby/buildkit v0.10.6 0c9b5aeb269c740650786ba77d882b0259415ec7

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.10.2", GitCommit:"50f003e5ee8704ec937a756c646870227d7c8b58", GitTreeState:"clean", GoVersion:"go1.18.8"}

 ibmcloud -version
ibmcloud version 2.12.1+b8488a1-2022-10-31T15:08:10+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.61 false
cloud-internet-services[cis] 1.14.9 true
code-engine[ce] 1.40.1 true
container-registry 1.0.2 true
SSL connectivity 

The Db2 on Cloud database uses a certificate for SSL connections that is issued by a third-party digital certificate authority (CA).

The CA certificate is part of the Db2 driver package. If your application connects with a driver from the Db2 driver package, you do not need to download the certificate separately. You can download the Db2 driver package from the web console.

However, if your application has its own driver, you might need to download the certificate separately. You can download the certificate from the web console.

Secure Sockets Layer (SSL) is a security protocol that provides communication privacy. SSL enables client and server applications to communicate in a way that is designed to prevent eavesdropping, tampering, and message forgery. SSL-enabled client applications use standard encryption techniques to help ensure secure communication.



 Configuring your Db2 client 

The IBM [Global Security Kit (GSkit) ships with Db2 release 9.5 and later](https://www.ibm.com/support/pages/gskit-versions-shipped-db2). However, if the GSKit needs to be downloaded and configured, see [Configuring GSKit](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-ssl_supportssl_cfg_gskit).



1. Download the SSL certificate from the web console into a new directory:

db2inst1@macing1:/home/db2inst1> mkdir SSL
db2inst1@macing1:/home/db2inst1> cd SSL
db2inst1@macing1:/home/db2inst1/SSL>
2. Create keystore in the SSL directory. The following example command pertains to Linux:

gsk8capicmd_64 -keydb -create -db "mykeystore.kdb" -pw "passw0rd" -stash

You must have the ability to write to the directory or you will get an error.
3. Add SSL certificate to the keystore.
Citrix Netscaler VPX terminology 

The Citrix Netscaler VPX platform uses both product-specific terminology and basic load balancer terminology and concepts, many of which are defined here.



  NetScaler IP (NSIP) 

The IP of the load balancer designated for management purposes.





  SubNet IP (SNIP) 

A SNIP is the source IP address of a packet used by the NetScaler every time it wants to communicate with a server (or object). Servers also use the SubNet IP to respond to the NetScaler.





  Virtual IP (VIP) 

A VIP is an IP address to which a client sends requests. The NetScaler terminates the client connection at the VIP and then initiates a connection with a server configured in the load balancing service. This can be either a public IP address for public (internet) traffic, or a private IP address for private (intranet) traffic.





  Virtual server 

A virtual server, in load balancing terms, refers to the combination of the IP address, port, and protocol to which an IP client connects and where traffic requests are sent for a particular application that is being load-balanced by the NetScaler.





  Service 

The combination of IP address, port, and protocol used to route requests to a specific server. A service, once configured, must later be associated to a virtual server.





  Server object 

A virtual entity that enables you to assign a significant name to a physical server, rather than using its regular IP address.





  Monitor 

An element that allows you to track a service, assuring that it is operating correctly. The monitor uses probes and heartbeat signals to keep track of the service status.
Click Manage physical adapters to migrate the physical adapters and VMkernel adapters, vmnic0 and vmk0 to the vDS.
6. Select an appropriate uplink on the vDS for physical adapter vmnic0. For this example, use Uplink1. The physical adapter is selected and an uplink is chosen.
7. Select to migrate the management network on vmk0 from the standard vSwitch to the distributed vSwitch as follows. Select these steps on host VMWARE_BMS002 / esx-002 and VMWARE_BMS003 / esx-003.
8. Select vmk0, and click Assign port group dpg-vmk.
9. Finish the configuration.
10. Review the changes to ensure that you are adding two hosts, two uplinks (vmnic0 from each host), and two VMkernel adapters (vmk0 from each host).
11. Click Finish.
12. Check connectivity to the host, and clear alarms if needed.







 Migrate the vCenter to VMWARE_BMS002 

Next, you need to migrate the vCenter:



1. Log into the vCenter Server using vSphere Client via Web Browser on the Jump machine.
2. Click to select the vCenter Virtual Machine.
3. Right Click, and select Migrate.
4. Click Change both compute resource and storage, click Next.
5. Select VMWARE_BMS002 / esx-002, click Next
6. Select DataStore1, click Next.
7. Change Port group to be dpg-management.
8. Click Next, then click Finish.



After the vCenter migration, you may execute the following IBM Cloud CLO command to validate that the vCenter's VLAN NIC has been moved to VMWARE_BMS002 / esx-002.

ibmcloud is bm-nics $VMWARE_BMS002
Datastore capability alarm Not configured in vCenter Server instances as they do not support VASA storage. No additional information 
 VASA provider disconnected Not configured in vCenter Server instances as they do not support VASA storage. No additional information 
 VASA Provider certificate expiration alarm Not configured in vCenter Server instances as they do not support VASA storage. No additional information 
 VM storage compliance alarm Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [VM storage compliance alarm (2061940)](https://kb.vmware.com/s/article/2061940) 
 Datastore compliance alarm Not considered essential for notification. Alarm reviewed as part of proactive daily checks. [Working with datastores](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.storage.doc/GUID-3CC7078E-9C30-402C-B2E1-2542BEE67E8F.html) 
 Refreshing CA certificates and CRLs for a VASA provider failed Not configured in vCenter Server instances as they do not support VASA storage. No additional information 
 Insufficient vSphere HA failover resources Configure to send email one time when critical. [Knowledge - KB0012739 v0.01](https://watson.service-now.com/nav_to.do?uri=kb_knowledge.do?sys_id=fe1f0beedb8db300d5a971198c96191a) 
 vSphere HA failover in progress Not considered essential for notification. Alarm reviewed as part of proactive daily checks. No additional information 
 Cannot find vSphere HA primary agent Configure to send email one time when unable to find or communicate with HA primary agent.
Go to the cluster, select Related Objects, VMs, and in the table enable the columns for VM Tools running and VM Tools version. Review the list and install VM Tools if needed. 
 VMs with snapshots For more information about best practices when you work with snapshots, see [Best practices for using snapshots in the vSphere environment (1025279)](https://kb.vmware.com/s/article/1025279). It is important to identify the existence of VMs with snapshots as using a single snapshot for more than 72 hours creates a snapshot file that continues to grow in size and can cause the snapshot storage location to run out of space and impact the system performance. To review VMs with snapshots, connect to vCenter by using the Web Client, select the vCenter Server and go to Related Objects tab. Right-click on the column titles and go to Show/Hide Columns list. From the list of columns chose Needs Consolidation option. This column shows a summary of all the VMs that are currently running. 
 AD/DNS OS patching The Microsoft® Active Directory™ (AD) / Domain Name Server (DNS) is automatically set up to download the updates only. For more information, see [More limitations and considerations](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_limitationstrbl_limitations) for further updating advice. 
 Check storage latency Check storage latency to understand any changes for the vSphere ESXi hosts to access the datastores. Too high a latency causes applications that are hosted in the VMs to slow down. In vCenter, go to the Performance tab. On each of the datastores, review the average write latency per VM. 
 Review VMs with virtual devices Virtual devices such as CD or diskette drives create an overhead, therefore, remove any devices that are not needed for a VM. 
 vSAN capacity advice When any capacity device in your cluster reaches 80% full, vSAN automatically rebalances the cluster until the space available on all capacity devices is lower than the threshold.
* Remote Collectors installed on separate VMs.
* Index Data Nodes deployed on separate VMs.
* Small-to-medium deployments – up to 500 assets with 30 days of indexing.



* Fully Distributed - Add more base VMs and scale-out VMs according to the number of assets and data retention requirements:



* Application components distributed onto separate VMs to facilitate scaling.
* Required deployment pattern as number of assets increases in the range 500 - 100000.
* Remote Collectors installed on separate VMs.
* UI on multiple VMs.
* App and Plugins on multiple VMs.
* Central Collector configured in a Cluster.
* Relational datastore that is deployed in a primary or secondary model.
* Messaging Datastore deployed in a cluster.
* Index datastore that is deployed with primary data nodes.
* More data nodes that are used for scaling out as number of assets increases.





All components must have an FQDN and registered in DNS before any VM deployment. This step is completed by the IBM Cloud® for VMware Solutions automation for the initial all-in-one deployment, but is your responsibility when you scale the deployment.
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.11", GitCommit:"38d3c1f3d5306401bcf39a71bad3b5a5106033d7", GitTreeState:"clean", BuildDate:"2022-03-16T14:08:11Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

 buildctl --version
buildctl github.com/moby/buildkit v0.10.3 c8d25d9a103b70dc300a4fd55e7e576472284e31

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.9.0", GitCommit:"7ceeda6c585217a19a1131663d8cd1f7d641b2a7", GitTreeState:"clean", GoVersion:"go1.17.5"}

 ibmcloud -version
ibmcloud version 2.7.0+04dfeac-2022-04-28T17:14:20+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.59 false
cloud-internet-services[cis] 1.14.4 true
code-engine[ce] 1.35.0 true
container-registry 0.1.571 true
container-service[kubernetes-service/ks] 1.0.420 false
cra 0.1.20 false
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.3", GitCommit:"aef86a93758dc3cb2c658dd9657ab4ad4afc21cb", GitTreeState:"clean", BuildDate:"2022-07-13T14:30:46Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4

 buildctl --version
buildctl github.com/moby/buildkit v0.10.4 a2ba6869363812a210fcc3ded6926757ab780b5f

 helm version --client
Client: &version.Version{SemVer:"v2.17.0", GitCommit:"a690bad98af45b015bd3da1a41f6218b1a451dbe", GitTreeState:"clean"}

 helm3 version --client
version.BuildInfo{Version:"v3.10.0", GitCommit:"ce66412a723e4d89555dc67217607c6579ffcb21", GitTreeState:"clean", GoVersion:"go1.18.6"}

 ibmcloud -version
ibmcloud version 2.11.1+c18277d-2022-09-23T21:49:24+00:00

 ibmcloud plugin list
Listing installed plug-ins...

Plugin Name Version Status Private endpoints supported
cloud-functions[wsk/functions/fn] 1.0.61 false
cloud-internet-services[cis] 1.14.8 true
code-engine[ce] 1.39.3 true
container-registry 1.0.1 true
container-service[kubernetes-service/ks] 1.0.454 false
Adding NFS storage to vCenter Server instances 

You can expand the capacity of your VMware vCenter Server® instance according to your business needs by adding Network File System (NFS) storage.



 Before you add NFS storage to vCenter Server instances 



* Adding NFS storage to vCenter Server instances with VMware vSphere® 6.5 is not supported.
* Do not add NFS storage from the VMware vSphere Web Client. The changes that you make on the vSphere Web Client are not synchronized with the IBM Cloud® for VMware Solutions console.
* IBM does not manage NFS file shares that you add manually to an instance.
* You can add or remove NFS storage shares to or from an existing NFS or vSAN cluster.
* If you mount IBM Cloud Endurance NFS storage to your cluster, consider the following steps:



* Ping the NFS server for the storage and note the subnet for the server IP address.
* Review the VMKernel adapters for the hosts that will use the storage and make note of the subnet for vmk3. Use the [file storage list](https://cloud.ibm.com/cloud-storage/file) to authorize the vmk3 subnet to access the NFS datastore.
* Review the static routes defined on the hosts with the esxcli network ip route ipv4 list command. A static route must be displayed for the NFS server IP subnet to the gateway for the vmk3 subnet listed in the previous step.









 Procedure to add NFS storage to vCenter Server instances 



1. From the VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, click the instance for which you want to expand capacity.
3. Click the Infrastructure tab.
4. In the Clusters table, click the cluster to which you want to add NFS storage.
5. In the Storage section, click Add.
6. In the Add NFS storage side panel, complete the storage configuration.