Skip to content

Posts from the ‘Infrastructure’ Category

5
Sep

VMware Support Assistant browser incompatibility

VMware Support Assistant is a must have FREE tool for your VMware vSphere installation.

Look at the VMware Site for more info on the VMware Support Assistant appliance.

The installation procedure can be found here or on YouTube.

During the installation at a customer site I found out that configuring the applicanse not always works as it should be. During the installation wizard where we make a connection to the SSO server I got following error:

Something failed. Try again.

A general error occured while attempting to acquire token from SSO service; will wrap and re-throw the exception. Re-trying the request might solve the problem; check the error details for more info A general error occured while attempting to acquire token from SSO service; will wrap and re-throw the exception. Re-trying the request might solve the problem; check the error details for more info Error communicating to the remote server https://MyServer:7444/sts/STSService/vsphere.local

Error communicating to the remote server https://MyServer:7444/sts/STSService/vsphere.local

com.ctc.wstx.exc.WstxIOException: Invalid null character in text to output Invalid null character in text to output Invalid null character in text to output

 

 

After some research I found out that it was a browser issue.

It does NOT work in the newest Chrome (version 37) on MAC and NOT on Internet Explorer on Windows 7.

It works on Internet Explorer 10 on a Windows 2008 R2 server.

After the configuration it is working perfectly now.

 

 

 

 

 

14
Aug

Convert RDM to VMDK

In preparation for a SRM project we had to check and migrate all RDM files to VMDK.

Check which VM has RDM using PowerCLI

Get-VM | Get-HardDisk -DiskType “RawPhysical”,”RawVirtual” | Select Parent,Name,DiskType,ScsiCanonicalName,DeviceName

 

Verify how RDM is connected

Edit the settings of the virtual machine in the VMware web client (while the machine is running) to verify if the RDM is connected physical or virtual.

The field compatibility tells how the RDM is connected, Physical or Virtual

 

  1. Convert Physical RDM to VMDK

    A physical connected RDM cannot be converted online to a VMDK. Before that we need to convert the Physical RDM to a Virtual RDM. (VMware KB)

  • Write down the drive letter of the disk in the guest OS
  • Stop the Virtual Machine by doing a shutdown of the guest OS
  • Note-down the LUN ID of the RDM by going into the multipath settings of the RMD connected to the VM

  • Remove the RDM, and check “Delete fr

  • Re-Add the RDM but change the compatibility mode to Virtual. Be sure the RDMs are connected to a separate SCSI-Controller (VM-PARAVIRTUAL). Select the same LUN ID as the LUN disconnected.

  • Power on the virtual machine
  • Go into storage management and check if the disk is online. Default it will be offline, bring it back online and connect it to the correct drive letter.

  • No your server is up and running with a Virtual RDM wich can be migrated online to a VMDK (see Convert Virtual RDM to VMDK)
  1. Convert Virtual RDM to VMDK

    A Virtual connected RDM can be migrated to a VMDK while the machine is running. (VMware KB)

  • Check if the RDM is connected virtual. Edit the VM settings and check compatibility mode of the disk

  • Start the Storage migration of the virtual machine

  • Be sure you change the disk mode to Thin or Thick provisioned.

  • If you select “Same format as source” then the RMD link file will be moved and NO migration to VMDK will happen.
  • If needed you can select this setting for each disk (and VMX config file) if you go into the advanced

  • Change the setting for each individual disk and start the migration

  • After the migration check the disk to see it is a VMDK and not a RDM.
29
Oct

vSphere 5.5 Quick stats not up to date

After doing a upgrade from mixed VMware vSphere environment to a clean 5.5 environment we noticed the warning “Quick Stats on HOSTNAME is not up to date” on each ESX hosts summary page.

Below you can see the screens with the warning.

Webclient

vSphere Client

 

After some googling I found this VMware KB: KB 2061008

In this KB the ask you to add some extra advanced settings in the vCenter. Below the setps to add these settings.

 

After this change is done, the vCenter service needs to be restarted.

According to the KB this should be enough but my experience is that the VPXA agent needs to be restarted on all ESX hosts in the vCenter. This can be done manually or via PowerCLI.

Manually

  1. Go to the configuration tab of an ESX host and select the Security Profile
  2. Select properties
  3. Select the VPXA agent
  4. Select options
  5. Restart the service.

NOTE: you will get some error popups because the vCenter looses the connection for a second with the ESXi host.

PowerCLI

$VMhosts Get-Datacenter “Your DataCenter” | Get-VMHost

foreach ($VMhost in $VMhosts)

{

    Get-VMHostService -VMHost $VMhost |

    where {$_.Key -eq “vpxa”} |

    Restart-VMHostService -Confirm:$false -ErrorAction SilentlyContinue

}

21
May

Unable to expand VMFS partition

Today I was asked to expand a local datastore of a ESXi 4.1. Expanding a disk is normally no problem when you are able to increate the size of the disk. After increasing the disk size you should be able to increate the partition size.

The ESXi was managed by a vCenter 5.0.  On the storage adapter I did a RESCAN data stores after the disk size was increased.  Then I went into the DATASTORE properties and I saw following

 

 

 

 

 

 

 

 

 

 

 

 

This above view was via a vCenter connection.  Then I found following VMware KB which told me to make a direct connection to the ESXi host.  After going to into the datastore properties I found out that I could increase.

 

 

 

 

 

 

 

 

 

 

When I selected this local datastore and finished the expansion I saw following result in the vSphere Client direct to the ESXi and via vCenter.

 

 

 

 

 

 

 

 

 

 

Lucky for the customer this expansion went OK.

Hopefully if you have this problem this KB article fixes also your problem.

Success

 

Gert Van Gorp

31
Oct

Resizing a system or data disk in a virtual machine

I get a lot of questions of students and customers about resizing a virtual disk. This is the reason for this blog.

The following procedure will guide you step by step through the process of resizing (increasing) a disk of a virtual machine.

Before you make virtual hardware changes be sure you have taken a full backup of the virtual machine.

 

NOTE: If you do not want any troubles only increase the disk size. Decreasing can cause loss of data.

 

Flow

 

Increase Disk using diskpart

Step 1: Edit the virtual machine settings and increase the size of the disk (VMDK).

Step 2: Open the console of this virtual machine and start a command prompt.

Step 3: Start diskpart and execute following steps.

list volume
à this gives you a list of the available partitions

select volume x
à select the partition number you want to increase

extend
à this will add the empty disk space into the partition.

Now the partition has increased in size.

NOTE: On Windows 2008 this can be done via the Device Manager / Storage, but I have seen some weird things like showing incorrect partition sizes.

 

Increase Disk using Third Party tool

Since I have some great experiences with the Acronis Disk Director tool I will explain the steps to increase a disk using this tool. Another tool that can be used is e.g. GParted.

Step 1: Be sure you have a boot image (ISO) of the Acronis Disk Director Tool that supports your guest OS.

Step 2: Boot your virtual machine using the boot image ISO. Use the ESC button during booting your virtual machine to activate the “one time boo menu”

Step 3: Select the partition you want to increase and right mouse click on it. Then select “Resize Volume”

Step 4: Increase the disk space of the selected partitions by decreasing the unallocated space to 0

Step 5: After increasing the partition you have to commit the changes.

Step 6: Now you need to reboot your virtual machine after disconnecting the boot image.

12
Jul

VMware Cloud Infrastructure & Management

Today 12th of July VMware announced a new suite of products. Look here for news release.

I the near future I will blog about this new release in a sort of “How to” format to introduce the new feature.

 

The suite consists out of following products.

VMware vSphere 5.0

VMware vCenter Site Recovery Manager 5.0

VMware vSphere Storage Appliance 1.0

vShield App 5.0 with Data Security

VMware vCloud Director 1.5

A new product most of the time means, a new set of licenses. VMware moved from 6 different licenses to 5, they removed the Advanced license. Lucky for the owners of this license (with a active subscription, they will be migrated to Enterprise. Look here for the license paper

 

Here a list of vSphere 5 introduction links

VMware Cloud Infrastructure: http://www.vmware.com/cloud-infrastructure/

The Console Blog: VMware Unveils vSphere 5 and the Cloud Infrastructure Suite

NTPRO: http://www.ntpro.nl/blog/

Kendrickcolemand: vCenter 5 – To Appliance or Not?, Using VMware AutoDeploy for ESXi

YellowBricks.com Live BLogging, vSphere 5.0 Clustering technical deepdive

UP2V: http://up2v.nl/

VmwareTips: VMware 2011 Mega Launch

Virtual Geek: Raising the Bar V = vSphere 5!

CRN VMware Adds Virtual Machine-Based Licensing In vSphere 5

vTexan: really cool things in vSphere5