According to the descriptor in the .vib file, LSI is just checking for versions "vmware-esx-storcli-1.12.00" and above for an update.
What you may do is to run:
esxcli software vib install -v /vmfs/volumes/backup/LSI/storcli/new/vmware-esx-storcli-1.12.13.vib --no-sig-check --dry-run
to see whether this will automatically remove the old vib. If it does run the command again without "--dry-run".
Otherwise you may consider to first remove the old vib and then install the new one.
André
It does not work either:
~ # esxcli software vib install -v /vmfs/volumes/backup/LSI/storcli/new/vmware-e
sx-storcli-1.12.13.vib
[DependencyError]
File path of '/opt/lsi/storcli/storcli' is claimed by multiple non-overlay VIBs: set(['LSI_bootbank_vmware-esx-storcli-1.09.13_1.09.13-01', 'LSI_bootbank_vmware-esx-storcli-1.12.13_1.12.13-01'])
File path of '/opt/lsi/storcli/libstorelib.so' is claimed by multiple non-overlay VIBs: set(['LSI_bootbank_vmware-esx-storcli-1.09.13_1.09.13-01', 'LSI_bootbank_vmware-esx-storcli-1.12.13_1.12.13-01'])
Please refer to the log file for more details.
~ #
There is no risk in adding RAM to ESX host but you have to power off all the VMs one by one before shutting down the server.
if you have HA created then you can simply move the VMs to other hosts during this maintenance
Sorry, I can't tell you for sure what LSI is doing here. However according to the readme in the package it might be required to uninstall the old package before you can install the new one.
from the "VMWARE_MN_Readme.txt":
1. The installed VIB Package can be list using command
"esxcli software vib list "
2. The VIB Package can be installed using the command
"esxcli software vib install -v=vmware-esx-storcli.vib"
3.The VIB Package can be removed using the command
"esxcli software vib remove -n=vmware-esx-storcli.vib"
André
if the ESX host is set to synch with NTP server then you can select the each and every VMs to synch the times with ESX hosts only.
there is no additional settings required to do in AD VMs to synch time with NTP.
When VMware Tools is installed within a virtual machine and the virtual machine is then migrated to an older ESXi host, the vSphere Web Client properly detects that the version of VMware Tools installed is equal to or greater than the version provided by the ESXi host on which the virtual machine is residing. However, the yellow banner is designed to match the exact VMware Tools version provided by the host against the virtual machine.
If the VMware Tools status is listed as Current, you can safely ignore this message
In the beginning, Hyper-V was an afterthought to most enterprise users, just another native Windows Server tool with little business value. Slowly but surely, the perception changed as the product continued to evolve. Some of the biggest improvements came in the launch of Windows Server 2012. Dubbed “3.0”, this version of Hyper-V introduced a number of exciting new features, including a few we’ve yet to really dig into, such as:
More VMs. The enhanced clustering capabilities in Hyper-V 3.0 highlight some of the strengths it draws from Windows Server 8. Thanks to the underlying OS, it can support as many as 63 nodes and up to 4,000 VMs (or 8000 depending on who you ask) on a single host, which is considerably more than what VMware handles.
Bigger VMs. The enterprise community couldn’t help but give consideration to the trending alternative when learning of the beefier support for workloads. Hyper-V 3.0 supports as much as 32 cores in virtual processing power and 512 GB of RAM, allowing for type of scalability high-volume businesses demand.
More virtual disk space. The VHDX feature is another scalability improvement made by Microsoft. VHDX trumps the original virtual hard disk (VHD) format by supporting 16TB in storage, while enabling virtual environments to enjoy better storage, performance, and data protection.
VM replication. Hyper-V Replica allows administrators to replicate the state of a live virtual machine from its primary location to a backup location of sorts. With no need for special storage or network hardware, this feature may come in handy for recovery efforts should disaster strike at the primary site.
VM grouping and isolation. Version 3.0 also includes support for affinity and non-affinity rules. Like the Distributed Resource Scheduler (DRS) rules in VMware, these options allow you to determine whether or not VMs with similar resource needs run on the same host.
To run ESXi 5.5 on the DL 380 G5 server you must enable the following options in the BIOS
ADVANCED OPTIONS
1) Vitrual isntall DISK (ACTIVE)
PROCESSOR OPTIONS
1) NO-EXECUTE MEMORY PROTECTION (ACTIVE)
2) INTEL (R) VITTUALIZATION TECHNOLOGY (ACTIVE)
GREETINGS. 
Hello,
Horizon Standard Suite comes in two forms, the bundle and the add-on. If you buy the bundle it includes vSphere desktop licenses and vCenter. The vSphere desktop license is limited in the number of powered on VMs you have, so if you buy a 60 seat license you can have 60 VMs powered on. If you buy the add-on, then you need to supply your own vSphere and vCenter licenses.
You should look and see which option will be more cost effective for your setup.
Horizon Suite (any version) is sold in groups of either 10 or 100 seats. If you go with the bundle version you'll need to buy 70 seats in order to be able to power on 61 VMs. If you go with the add-on version then you might be able to just buy 50 seats for the 41 concurrently connected users.
Hope that helps,
Ian
Sorry about the late reply, but I'm still happy to look at any nested virtualization issues involving VMware products.
Good response King!, that picture is acutally one of the best I've seen to help explain the differences between the disk metrics. Seeing as our OP is seeing GAVG of over 80ms I would say he needs to dig deeper into the SAN unless most of the time is coming from the KAVG.
Hi. Both the connecting WinXP VM and the non-connecting Win7 VM are configured as NAT. ipconfigs attached.
@varfuso - I am assuming the same thing, but unfortunately just saying that without performing any due diligence and providing more proof of effort won't fly from a support standpoint. There are other vm's in that same subnet on that same host, and all of them appear to be working fine right now. (the vm in question included) The problem as it was reported to me was that a particular vm loses the ability to ping another vm randomly for a couple minutes overnight on sporadic dates, which causes a soft reboot (that part by design). I don't know if this means the source vm is going offline, the destination vm is, or if there is an underlying issue on the subnet and this overnight issue on the other related subnet vm's is just going unreported.
My suspicions aside, I just want to be able to say that (among my other tests) I researched the vmware "xyz log" (if there is one I could use to investigate such an issue) and found nothing wrong with any of the infrastructure I support.
This was really crazy:
~ # esxcli software vib remove -n=vmware-esx-storcli.vib
[NoMatchError]
No VIB matching VIB search specification 'vmware-esx-storcli.vib'.
Please refer to the log file for more details.
Did not work, so let's see if the old storcli is still installed:
~ # esxcli software vib list | grep storcli
vmware-esx-storcli-1.09.13 1.09.13-01 LSI PartnerSupported 2014-07-25
it *IS* there! Let's try again, this time with version-number:
~ # esxcli software vib remove -n=vmware-esx-storcli-1.09.13.vib
[NoMatchError]
No VIB matching VIB search specification 'vmware-esx-storcli-1.09.13.vib'.
Please refer to the log file for more details.
Again no go??? Try without "vib":
~ # esxcli software vib remove -n=vmware-esx-storcli-1.09.13
Removal Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed:
VIBs Removed: LSI_bootbank_vmware-esx-storcli-1.09.13_1.09.13-01
VIBs Skipped:
Yuppie! The old removed, half work is done. Now the new one:
~ # esxcli software vib install -v /vmfs/volumes/backup/LSI/storcli/new/vmware-esx-storcli-1.12.13.vib
[InstallationError]
('LSI_bootbank_vmware-esx-storcli-1.12.13_1.12.13-01', 'Could not find a trusted signer.')
vibs = LSI_bootbank_vmware-esx-storcli-1.12.13_1.12.13-01
Please refer to the log file for more details.
Looks so that VMware forgot something again:
~ # esxcli software vib install -v /vmfs/volumes/backup/LSI/storcli/new/vmware-esx-storcli-1.12.13.vib --no-sig-check
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: LSI_bootbank_vmware-esx-storcli-1.12.13_1.12.13-01
VIBs Removed:
VIBs Skipped:
Seems to be done. Let's check version:
~ # /opt/lsi/storcli/storcli -v
StorCli SAS Customization Utility Ver 1.12.13 May 29, 2014
(c)Copyright 2014, LSI Corporation, All Rights Reserved.
Exit Code: 0x00
~ #
OK, FINALLY! So update did not work, I had to uninstall it, and install new...
You can check vmkernel.log to ensure you don`t have any issues
I don't see 5.5.2 in the list of SDKs that are available for download. How can I download 5.5.2?
Thanks,
-Darrell
As long as your disk/raid controller supports drives with 4KB sector-size you are OK on vSphere side. It should not be any problem for VMFS5 file-system because it uses block/sub-block size 1MB and ESXi will not be aware of RAID levels on the storage array. If you are presenting the LUNs from 4KB sector-size drives it should function normally.
Does the network adapter show up in the Windows 7 guest? What NIC type/model do you see in the Device Manager?
You may also want to check whether "Connect at Power on" (and/or "Connected" while powered on) is checked in the VM's settings.
André
Here is the list of other issues what i have faced during the VSAN deployment. It will be helpful to others.
http://www.unixarena.com/2014/06/vsan-deployment-issues-fixes.html