The following is a list of all the components and their versions as per VMware Validated Design 4.2.
During the process of deploying an OVF (Log Insight in this example) using the vSphere Web Client running on a local windows vCenter instance, I encountered the following error:
‘A connection error occurred. Verify that your computer can connect to vCenter Server.’ Continue reading
This post was a result of requiring access to the VCSA BASH Shell console in order to perform such functions as certificate-manager (/usr/lib/vmware-vmca/bin/certificate-manager).
The default Shell access when you initially login to the VCSA via SSH is the basic Appliance Shell:
The following steps detail how to suppress the vCenter cluster warning:
The number of heartbeat datastores for host is 1, which is less than required: 2
You may encounter this situation in a lab scenario where you do not have greater than 1 shared datastore per cluster. Continue reading
The following table represents the recommended VMware vSphere ESXi host settings to be applied when an ESXi host(s) is connected to a single array and also details multi-array settings when at least one of the arrays is XtremIO.
The following information is referenced from EMC KB303782:
Recommended settings for VNX, VMAX, VPLEX, and XtremIO Colocation within VMware vSphere
- Unless otherwise noted, the term VMAX refers to VMAX, VMAX3, and VMAX All Flash arrays
- The setting for FC Adapter policy IO Throttle Count can be set to the value specific to the individual storage array type if connections are segregated. If the storage arrays are connected using the same vHBA s, use the multi-array setting in the table.
- The value for Disk.SchedNumReqOutstanding can be set on individual LUNs and therefore the value used should be specific to the underlying individual storage array type.
Experiencing issues connecting to an ESXi host from vCenter Server?
A good place to start your troubleshooting is by restarting the ESXi management agents.
The following method uses the CLI option SSH/Local console to restart an ESXi host management agents:
The following script allows the user to Enable/Disable SSH at a per vSphere cluster level. You may download the ‘SSH.ps1‘ script here: SSH.ps1 (Remove the .doc extension).
The script will begin by prompting you to enter the vCenter Host IP Address, username and password. A list of all the available clusters residing in vCenter will be returned, followed by a prompt to enter the cluster name you wish to Enable/Disable SSH for: