A. Mikkelsen VMware ESX scripts, commands, tools and other nice to know things that will make your virtualization days easier!!!!

Wednesday, September 29, 2010

Configure IBM Blades (running ESX) and Cisco switches for failover

Filed under: Performance,Troubleshooting,White Papers — Tags: , , , , , , , , , , — A. Mikkelsen @ 21:18 pm

Using IBM Blades and Cisco switches to run your ESX enviroment?

If yes, have you tested what happens if you unplug the network cables going into one switch?

If you like me have bundled 2 or more cables going from one switch, to one backbone switch and done the same for the other switch, then your VM’s using that switch will loose network connection (from outside the host).
This is not the way I wanted the setup to work.

After a bit of googling i found a blog from Scott Lowe (http://blog.scottlowe.org/2007/06/22/link-state-tracking-in-blade-deployments/) about the problem and also a solution.
The solution is called Link State Tracking. Many users have tried the solution and have got it to work, so I had to test it…..

I added the following lines to each of the Blade Switches (Port-Channel, group and interfaces may be different on your system).

----------UPLINK to CORE switch------------
interface Port-Channel1
link state group 1 upstream

----------LINK to Blade server------------
interface range GigabitEthernet0/1 - 14
link state group 1 downstream

----------Global command------------
link state track 1

conf t
interface Port-Channel1
link state group 1 upstream
interface range GigabitEthernet0/1 - 14
link state group 1 downstream
link state track 1

Remember to write the changes to memory using

wri

After this was done on both Blade switches, i just had to test it.
I started a ping to a VM that I knew was using Switch1 to communicate with external network traffic.
Then I unplugged the to 2 network cables going into Switch1 and waited to see if the ping command would loose the communication with the VM….
It didn’t loose connection. So the the VM must have switched to Switch2.

So configuring the Blade Switches for Link State Tracking is to proper way to configure the switches.
A big thanks goes to Scott Lowe for the blog on Link State Tracking.

Thursday, September 23, 2010

Guest warning after upgrade to vSphere 4.1

Filed under: Errors,Troubleshooting,vSphere (ESX),Workstation — Tags: , , , , , , , — A. Mikkelsen @ 19:04 pm

After we upgraded to vSphere 4.1, the SCSI adaptor of all our WINXP guests changed from LSI Logic Parallel  to BusLogic Parallel. This change should normally not create any warnings or problems it VMware Tools are up to date.

But after the upgrade all our WINXP guests got the following warning when powered on in the event log.

Message from esxhost01.labt.local: The guest operating system is Windows XP and you have one or more virtual SCSI devices installed in your virtual machine. Windows XP does not support the BusLogic SCSI adapter that VMware ESX currently uses for its virtual SCSI devices. Select OK to continue or Cancel to cancel. info 22-09-2010 15:55:25 VM name vpxuser
I then changed the SCSI adaptor back to LSI Logic Parallel and I now got almost the same warning.

Message from esxhost01.labt.local: The guest operating system is Windows XP and you have one or more virtual SCSI devices installed in your virtual machine. Windows XP does not support the LSI Logic SCSI adapter that VMware ESX currently uses for its virtual SCSI devices. Select OK to continue or Cancel to cancel. info 22-09-2010 15:55:25 VM name vpxuser

I contacted VMware support and they told me that it was a known “feature”/”bug” and send me the following link to suppress the waring in the Event log.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007122

There is two ways to suppress the warning.

Through vSphere Client

  • Using the vSpher Client logon to your vCenter server.
  • Poweroff the VM.
  • Edit the VM’s settings
  • Navigate to Options > Advanced > General
  • Click Configuration Parameters
  • Add the following rows, by using Add Row
    • If you have a BusLogic Parallel SCSI adaptor
      buslogic.noDriver = "FALSE"
    • If you have a LSI Logic Parallel SCSI adaptor
    • lsilogic.noDriver = "FALSE"
  • Click OK twice to close the dialogs and save the changes.
  • PowerOn the VM

Editing the VMX file

  • Open a SSH to the host ex. using Putty
  • Navigate to the VM’s files (relpace with your own path)
    cd /vmfs/volumes/lun01/winxp01/
  • Open the config file  in your favorit editor .
    vi winxp01.vmx
  • Add the following line to the file
    • If you have a BusLogic Parallel SCSI adaptor
    • buslogic.noDriver = "FALSE"
    • If you have a LSI Logic Parallel SCSI adaptor
    • lsilogic.noDriver = "FALSE"
  • Save and close the config file.
  • PowerOn the VM

I haven’t tested if it possible to add the lines to the global config file on each host (/etc/vmware/config) for all VM’s..

I will test this next week.

Wednesday, September 22, 2010

Problems with FullScreen in vSphere 4.1

Filed under: Errors,vSphere (ESX) — Tags: , , , , , — A. Mikkelsen @ 12:54 pm

After we upgraded to vSphere 4.1 we have been expirence problems with VM’s entering FullScreen mode.

The issue is that 9/10 times a VM enter FullScreen mode, you are not able to move the mouse to the bottom part of the screen and select a program or the Start option.

VMware is aware of the bug.
They say that it is resolved  in ESX 5 (next year)  – FullScreen mode should be completely redesigned.

Until then a patch is requested from PR, but no timeframe is released.
So if you have the same problem, please file a support request with VMware to speed up the process.

Tuesday, September 21, 2010

Copy & Paste option is disabled in vSphere Client 4.1 – default

Filed under: Security,Troubleshooting — Tags: , , , , , — A. Mikkelsen @ 14:23 pm

Yesterday we upgraded one of our vSphere Clusters to 4.1 – it went smoothly 🙂

But today the users reported that they weren’t able to use cut % paste between the guest and their computer using the vSphere Client (Console).

After a quick google we found that VMware has tightened the vSphere security by disabling this feature. See VMware KB 1026437.

If you need the cut & paste functionality you can enable it again on the guest or host level.

For a single VM:

  • Using the vSpher Client logon to your vCenter server.
  • Poweroff the VM.
  • Edit the VM’s settings
  • Navigate to Options > Advanced > General
  • Click Configuration Parameters
  • Add the following rows, by using Add Row
    isolation.tools.copy.disable –  false
    isolation.tools.paste.disable  – false
    
  • Click OK twice to close the dialogs and save the changes.
  • PowerOn the VM

For all VM’s on a host ESX/ESXi

Must be done on all hosts, so you don’t loose the functionality when the VM is migrated to another host.

  • Open a SSH to the host ex. using Putty
  • Open /etc/vmware/config in your favorit editor .
  • Add these lines to the file

    isolation.tools.copy.disable="FALSE"
    isolation.tools.paste.disable="FALSE"
    
  • Save and close the config file. Cut & Paste will work after a VM powerson, reboots or resume.

Powered by WordPress