Thursday, January 20, 2011

LUN not visible/VMKPing not working but ping works just fine on ESX 4.x

Scenario : The server and the storage are in 2 different locations. The service console is in a different network and the vmkernel is in a different network for SCSI drives.
Setup: HP Blades, iSCSI, EVA, Virtual Connect, ESX 4.1, vCenter 4.1, Left Hand Networks [LHN].
Issue: Customer has created a new lun and presented it to the host.
host is not seeing the lun under storage or storage adapters.
Customer is able to ping the lun but unable to vmkping the lun.
Resolution: The customer was using virtual connect and it was configured to interact with only LAN A and the host was in LAN B. Customer changed the setting in virtual connect to allow LAN B too and it got resolved.

Monday, January 10, 2011

Windows 7 EagleMode and Windows Vista EagleMode

Windows 7 BioMode and Windows Vista BioMode

Windows 7 PowerMode and Windows Vista PowerMode

Windows 7 TrayMode and Windows Vista TrayMode

Windows 7 VaultMode and Windows Vista VaultMode

Windows 7 ProgramMode and Windows Vista ProgramMode

Windows 7 ResourceMode and Windows Vista ResourceMode

Windows 7 WirelessMode and Windows Vista WirelessMode

Windows 7 WorkgroupMode and Windows Vista WorkgroupMode

Windows 7 MyCompMode and Windows Vista MyCompMode

Windows 7 PrintMode and Windows Vista PrintMode

Windows 7 HomeOfficeMode and Windows Vista HomeOfficeMode

Windows 7 SecureMode and Windows Vista SecureMode

Windows 7 UndefinedMode/windows explorer and Windows Vista UndefinedMode

Windows 7 PerformanceMode and Windows Vista PerformanceMode

Windows 7 GodMode and Windows Vista GodMode

Checking consistency of VMware snapshot chain

Scenario/Issue: Customer has many may snapshots on a virtual machine or your are getting errors related to snapshots. Snapshot manager GUI [graphical user interface] may show/report no snapshots but the command line shows that it has snapshots
Determine if the virtual machine has snapshots:
# [KB Article: 1006847]
vmware-cmd /vmfs/volumes/volume-UUID-or-name/vm1/vm1.vmx hassnapshot
The output will look like one of the following:
hassnapshot() =
hassnapshot() = 1
If the result is not equal to one (1), there are no snapshots for the virtual machine and there is no reason to proceed further.
Sometimes the CLI may also tell you that it has no snapshots but the folder containing the VM files has many delta files and you want to be sure that you do not miss out on any data.
The regular boring and usual way is to take the highest number of snapshot and run the command
cat -delta.vmdk and check the PID and CID and check the chain
or use the following
Please try this command to test the entire snapshot chain .. This will display any errors related to snapshot ..
Vmkfstools –t0 –v10 lastsnapshot-00000n.vmdk - This command has to be issued for each hdd of the virtual machine when you have more than one hdd per VM.

vmkfstools -q -v10 "your_disk.vmdk"
Try this command to display the CID , PID & parent file names for all the snapshots of a VM..
Change directory to the VM, then issue this command .
Find . –name \*.vmdk –size -10k | xargs egrep - i “CID|PID” | sort - n
------------------i claim no copyright on any of the content here. sharing is caring.

Saturday, January 8, 2011

ESXi 4.1 or 4.x not detecting HP NC522SFP PCIe NIC

Issue: You have installed or trying to install the esxi 4.x but it is not detecting the add on pcie hp nc522sfp nic card.
NC522SFP=QLogic QLE3142.
go to
which will take you to
if you are trying to install esx/esxi 4.x or already installed it.
and download the driver software according to the version of esx/esxi that you are installing.
You can use the tools provided by QLogic to update the firmware of the card but the recommended way is to follow the vmware way that is KB Article: 1019101
which is to copy the downloaded .zip file to the host using the winscp or any other such tool and then run the following command inside the directory where you copied or moved the file.
esxupdate --bundle= update

ESXi 4.1 or 4.x not detecting HP NC365T PCIe NIC

Issue: Installed the ESXi 4.1 and while installing it on DL 380 G7 and you did not get any prompt to install the custom drivers.
The onboard Nics are detected and working properly.
In the bios the PCIe are enabled.
Hardware: DL 380 G7 and HP NC365T PCIe NIC
Resolution: Checked the
and found that the NIC is actually a Intel 82580 MAC.
Download the following driver from vmware
Copy or move the package/bundle from the downloaded content to the host in question.
using the cd command go to the directory where you have copied the *.zip bundle.
Put the host in maintenance mode.
Run the command
esxupdate --bundle update
It will ask you to reboot, so reboot the host with the vSphere client or through command line.
Exit maintenance mode.
Now you should be able to see the Nic in question.

Tuesday, January 4, 2011

Unable to add VMXNET 3 with solaris 10 update 5.x on ESX 4.0

After adding the VMXNET 3 and installing the driver and rebooting the VM customer is unable to connect to the network and ifconfig –a will not show the VMXNET 3 interface. Customer has the latest VMware tools installed.
VMware OS: ESX 4.0 Update 1
VM OS: Solaris 10 (Update 5)
Take a snapshot before trying any of the steps below as a precaution.
*Install the e1000 ethernet interface on the Solaris VM.
*Install the latest VMware tools on the VM.
*Power off the VM.
*Install the second NIC onto a solaris VM using the VMXNET 3 driver.
*ifconfig VMXNET3s0 plumb
*ifconfig e1000g0 unplumb
*mv /etc/hostname.e1000g0 /etc/hostname.VMXNET3s0
*reboot the VM
This particular issue was an ongoing issue with the ESX 3.5. The /etc/hostname.xxxx file tells the solaris which network interface has to be used and even though the VMXNET 3 drivers are installed properly the /etc/hostname.xxxx has to be changed or edited to inform the solaris which network interface has to be used and in this scenario we have to changed it to /etc/hostname.VMXNET3s0 so that the solaris will try to use the VMXNET 3 network interface.
1] Do not remove the e1000 interface from the VMware VM configuration.
2] If the VM is using the DHCP then do the following as well
mv /etc/dhcp.e1000g1 /etc/dhcp.VMXNET3s0

Sunday, January 2, 2011

Ubuntu 10.10 not detecting sata drives

Issue start date: june 2009 to till now
Issue: Unable to install ubuntu
hardware profile
Asus p5nd motherboard
nvidia chipset
sata emulation set to sata not raid.
seagate 2*250gb drives
earlier these drives were in raid but in the beginning from feb 2009 i disabled raid and using the 2nd 250gb as a back up for the first primary drive.
asus driver cd has the linux drivers but it is not seeng the drives when booted from linux

1.Tried booting form the ubuntu 10.10 but checks out the requirements section fie stating that it has the required 2.disk space but in the next section it won't detect the both of my 250 GB seagate sata disks.
3.The seatools which is a windows based diagnostic tool for their product is also not detecting its own harddisks.
4.tried changing the sata emulation to every possible option like sata, raid and other such settings in the bios but no go.
5.tried the wubi installer from the disc inside windows but no go.
6.tried debian again today but it is unable to see the existing partitions in the disk.
7.tried suse linux and it says that the parted is unable to modify the disk where i want to dual boot but it does detect the drives.
8.tried booting from norton ghost and it just shows error for the disk that i want to dual boot.
9.tried every dos disk tools from hiren's boot cd 13 but no go.
10.trying with Redhat enterprise linux 5.3 and but no go.
11.Try sudo apt-get remove dmraid but no go,
12.Reinstalled my windows 7 (the c drive was 132 gb filled with my favourite customized applications and windows and games but i gave all that up for nothing) ultimate and installed win 7 ultimate x64 N edition but no go.
13.<1> I tried to boot from ubuntu again by restoring by BIOS to the defaults but no go
14.I tried change sata DMA settings and ide prefetch mode settings (every combination with raid enabled and disabled) but no go.