fatih's Posts

Hi,   As Andre is also saying , check the ILO logs. I have had issues with thermal and cooling , the fans have not leveled up automatically and I also had these reboots. Nothing related to ESXi really. I increased the fan cooling setting in BIOS , before they just was sitting at 10% and the server rebooted from time to time. After I have changed to increased cooling the fans is running at 30%-50% constantly and no reboots anymore. The inlet temperature for me is around 22-23 celsius.   /Fatih

Just want to add my experience. Had the exact same issue after an VCSA 6.5 U1 upgrade to VCSA 6.7 ( not U1 ) and I had a colon in the root password As someone earlier suggested and tested the solution for me was also to first login through console , enable ssh , login through ssh , change root password to something simple , login to management , logout , change root password to something more complex ( might work with colon again..but I did not dare to use colon again.. )

Exactly , the same and repeating task is "Query" all the time. There is one Query task for one of the 31 ESX hosts all the time. It keeps querying every 1-15 seconds a new ESX hosts constantly without anyone selecting any ESX hosts or even beeing in the vShield Manager interface. My experience from earlier vShield Manager installations is also that it querys only when you select one ESX in the vShield Manager interface. But those installation vas pre 4.1 U2 ( 4.1 / 4.1 U1 ) , this is first I have done with 4.1 U2 but then again..it is vShield Manager which is querying so it should not be any difference if ESX is 4.1 U1 or U2 It is really annoying and fills up the task/event windows everywhere. One another thing I noticed now. I searched through the logs (vmkernel/vmkwarning/messages etc ) to see if I could see any evidence of the Query task and the only thing I think is related is /var/log/vmware/esxupdate.log which logs this every 15 min (since we installed vShield Manager ) [2012-01-02 12:36:14]   DEBUG:       lock: Lock file /var/run/esxupdate.pid created with PID 771 [2012-01-02 12:36:15]    INFO:        cos: vsish command /usr/sbin/vsish cannot be found [2012-01-02 12:36:15]    INFO:        cos: No hardware vendor/model information obtained [2012-01-02 12:36:15]    INFO: vmware.esx: BIOS reports Vendor , Model [2012-01-02 12:36:15]    INFO:  esxupdate: -- Command: query Args: ['query'] Options: {'nodeps': None, 'all': None, 'retry': 5, 'force': None, 'vibview': None, 'nocache': None, 'compliant': None, 'loglevel': 'DEBUG', 'cleancache': None, 'bundles': None, 'nosigcheck': None, 'bundlezips': None, 'olderversion': None, 'proxyurl': None, 'meta': None, 'timeout': 30.0, 'cachesize': None, 'HA': True, 'maintenancemode': None} [2012-01-02 12:36:15]   DEBUG: vmware.esx: VIBs loaded: database 881  metadata 0  pkgdb 0 [2012-01-02 12:36:15]   DEBUG: vmware.esx: Final VIB counts: metadata 0  pkgdb 0 [2012-01-02 12:36:15]    INFO:  esxupdate: All done! [2012-01-02 12:36:16]   DEBUG:       lock: Lock file /var/run/esxupdate.pid created with PID 782 [2012-01-02 12:36:16]    INFO:        cos: vsish command /usr/sbin/vsish cannot be found [2012-01-02 12:36:16]    INFO:        cos: No hardware vendor/model information obtained [2012-01-02 12:36:16]    INFO: vmware.esx: BIOS reports Vendor , Model [2012-01-02 12:36:16]    INFO:  esxupdate: -- Command: query Args: ['query'] Options: {'nodeps': None, 'all': None, 'retry': 5, 'force': None, 'vibview': None, 'nocache': None, 'compliant': None, 'loglevel': 'DEBUG', 'cleancache': None, 'bundles': None, 'nosigcheck': None, 'bundlezips': None, 'olderversion': None, 'proxyurl': None, 'meta': None, 'timeout': 30.0, 'cachesize': None, 'HA': True, 'maintenancemode': None} [2012-01-02 12:36:17]   DEBUG: vmware.esx: VIBs loaded: database 881  metadata 0  pkgdb 0 [2012-01-02 12:36:17]   DEBUG: vmware.esx: Final VIB counts: metadata 0  pkgdb 0 [2012-01-02 12:36:17]    INFO:  esxupdate: All done! /Fatih

I have done several upgrades from ESX 3.01 / 3.02 to 3.5 U1 and everytime almost every VM gets all the resource settings mixed up from Unreserved/Unlimited to some random number... I have even done this by reinstalling a completely new VC 2.5 instead of just upgrade but I get the same result , so I suppose there must be some VM settings on the ESX servers that VC 2.5 misunderstands.. And then I have just put them back to unlimited/unreserved one by one..

I don't know the exact way to do it with vcb commands but we do it with Vranger. We do a backup of the VM and select only the first disk which is a regular .vmdk file. The Vranger lets you deselect the drives you dont want to backup, for example the rdm volumes.

I have done similar things by "remove from inventory" on the vm itself by rightclicking on it in the VC client and then through the console move the files to the new place and then register the vm either from the console or just by browsing the datastore within the VC client and choose the .vmx file and then rightclick and "add to inventory" Worked for me. Regards

I'm sure you right. Haven't looked that up. But for me CPU downgrade has worked for me without any hassle on any of the 40+ vms I converted and I have done it on Windows 2000 SP3/4 and Windows 2003 without SP and also with SP1 and SP2.. Maybe it has to do something with the ESX version also, all these conversion and downgrades I have done in either 3.01 or 3.02. Regards

You're correct. You shall choose "Advanced Configuration and Power Interface PC". I have done this in many servers and its works perfect. The "Uni" is for Windows 2000. Regards

I have also upgraded and have done fresh installations with the same error but Vmotion seems to work perfect and even faster ! I was able to get an correct answer from servers not yet upgraded when I used vmkping from an upgraded server... Maybe the problem is only with the command utility "vmkping" itself ? Regards

Or if you are already in to HP products you could also use HP Rapid Deployment Pack with builtin scripted installation support for ESX server on any ESX supported Proliant server. Just PXE boot any server, drop your own modified esx scripted installation job on the PXE booted server and 15-30 minutes later you have it freshly installed and always identically installations between any servers. (could also inlude other packages for example HP PSP (configured) ) RDP is licensed per physical/virtual server so I highly recommend you use it for your physical servers and continue with VC for your virtual...