This page was very concise and easy to follow:
Categories
Category: vSphere
Posts regarding the vSphere suite of products from VMware
Categories
vSphere 6.0 U1 | view topic
After upgrading our hosts to ESXi 6.0 U1, none of our Veeam jobs would run. After much searching, we found out that SSLv3 is disabled by default and is the reason the jobs weren’t completing. There are a couple of KBs describing the issue, but the quick and fast solution for us was to add the following at the end of each host’s /etc/vmware/config.
vmauthd.ssl.noSSLv3 = false
Source: After applying update 1 for vSphere 6.0, Job’s fail with NFC storage unavailable
Source: vSphere 6.0 U1 | view topic
Source: Enabling support for SSLv3 in ESXi (2121021)
Here is some great information about backing up and restoring ESXi host configurations. Great for taking backups before updating. The host profiles after restoring were all compliant too.
vicfg-cfgbackup.pl –server=ESXi_host_IP_address –username=root -s output_file_nameWhere
ESXi_host_IP_addressis the IP address of the ESXi host andoutput_file_nameis the name of the backup file you will create.
vicfg-cfgbackup.pl –server=ESXi_host_IP_address –username=root -l backup_file
WhereESXi_host_IP_addressis the IP address of the ESXi host andbackup_fileis the name of the backup file to use for the restore.
Don’t forget to configure the scratch partition!
At VMworld I was surprised at the number of questions I was asked related to booting ESXi off of USB/SD. Unfortunately, the vSphere docs largely assume you will use a local disk and don’t really cover USB/SD, as such it’s not always easy to find answers to common questions. Below are some answers to several of […]
While trying to update our ESXi 5.5 host to 6.0. the error “Cannot run upgrade script on host” occurred at ~93%. After some googling, we found the below website (it referenced ESXi 5.0 but it worked for the 5.5–>6.0 upgrade), whose second option resolved our issue.
The basic resolution steps were…
- disable HA for the cluster
- remove the ESXi host from the cluster
- connect via SSH to the ESXi host and run the following commands to uninstall the FDM agent:
cp /opt/vmware/uninstallers/VMware-fdm-uninstall.sh /tmp
chmod +x /tmp/VMware-fdm-uninstall.sh
/tmp/VMware-fdm-uninstall.sh
- reboot the host
- add the ESXi host back to the cluster
Thanks Keine!
While trying to create a host profile on one of our ESXi hosts, we came across this error:
Cannot configure or query coredump partition
These hosts are all booted using a USB key (to maximize available direct attached storage space) so perhaps this was why the coredump partition wasn’t configured.
Nonetheless, the only resolve was to SSH into the host (as root) and run the following commands:
esxcli system coredump partition get
This command gave “Not a known device: mpx.#######:##:##:##:#”
Run the following command to clear that error:
esxcli system coredump partition set -u
And the next command to instruct the system to find a suitable partition for the coredumps.
esxcli system coredump partition set -e true -s
Running the first command again will verify that the partition has been set.
esxcli system coredump partition get
Lo and behold, creating a new host profile is now successful!
Thanks to Varrow Blogs for the detailed steps.
Source: Varrow Blogs | Giving Back to the IT Community – The Technology Blogs of Varrow Engineers | Page 17
Trying to import the client’s workstations and servers into the current vsphere environment. After taking a system image within Windows, I mounted the USB device (with WindowsImageBackup directory in the disk’s root) and restored into the VM. Subsequent boot yielded BSOD. Stumbled upon this VMware KB article which solved the problem first shot.
- Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
- In the Registry Editor, select HKEY_LOCAL_MACHINE.
- Select File > Load Hive.
- Navigate to the drive on which Windows is installed (usually C:\).
- Open the file named SYSTEM located at Windows/system32/config.
- Name the file as P2V, when prompted.
- Navigate to HKEY_LOCAL_MACHINE\P2V\ControlSet001\services\LSI_SAS.
- Right-click the Start key and click Modify.
- Set the Value data to REG_DWORD 0.
- Close the Registry Editor.
- Restart the virtual machine.
After deploying a Proliant ML150 G6 with ESXi 5.5U2 to a remote office, the users were complaining of dismal performance. After investigating and reviewing various metrics of the machine, we noticed very high disk latencies (average of 20ms).
After doing some “Googleing”, it was decided to install the Battery-Backed-Write-Cache battery module (what a mouthful!). Yes, one would think that once you install and configure a RAID controller, that would be it, but not in this case.
Nonetheless, a battery was procured and plugged in. The BIOS upon boot immediately states to use the HP Array Configuration Utility to enable the read/write cache. One needs to install the HP utilities onto the ESXi box if it wasn’t built from the HP ESXi ISO. By logging into the console via SSH, first confirm the battery status and then enable the read/write cache ratio. In our instance we configured 50% read / 50% write. Refer to this post for the HP ACU commands.
Check out the performance gain / decreased latency:
Categories
HP Smart Array CLI commands on ESXi
Good resource when maintaing a battery for a P410 controller running ESXi5.5U2 on HP ML150G6.
via HP Smart Array CLI commands on ESXi | Kalle’s playground.
I was trying to figure out why nothing would happen after I tried to install the vSphere client on my Windows 8.1 workstation. Thanks to Brian’s quick tip, I was able to install it without a hitch:
Dism /online /enable-feature /featurename:NetFx3 /All /Source:F:\sources\sxs /LimitAccess
Thanks Brian!
via Installing vSphere client on Windows 8.1 | Brian Williams.