Skip to content

Posts tagged ‘vCenter’

8
Jan

Where to find VMware version information

Here some links to find version information about VMware vSphere products

http://vsphere-land.com/vinfo/release-build-info

and about VMware Tools versions

http://packages.vmware.com/tools/versions

20
Dec

How long can an ESXi host run?

Before starting an upgrade at a customer site I was surprised how long an ESXi host can run. Here the proof.

 

9
Dec

Upgrade VMware vCenter Appliance 5.1 to 5.5

A lot of my customers are running the vCenter Appliance version 5.1. Now they start to ask to upgrade this appliance to the newest version.

Here I will show you step by step the upgrade process. This is based on the VMware KB article 2058441

 

Prerequisites

  • Verify the time set on the old (VMware vCenter 5.1) appliance and the new (VMware vCenter 5.5) appliances are in sync. Be aware that from version 5.5 the clock on the appliance is always set to the UTC time zone. In the older version you could select your own tome zone. (see VMware KB)
  • Be sure SSO (if installed on separate machine) is on the same version of the vCenter you want to upgrade to.
  • If the vCenter database is external, make backup on the Database server. For backing up the embedded database look at this KB
  • Create a snapshot of the OLD vCenter appliance before you start the upgrade procedure.

Upgrade Procedure

  • First step of the upgrade procedure is deploying a fresh VM of the latest vCenter Appliance.
  • Next is to configure the VM so that network connectivity is possible. The only thing that needs to be configured is IP address, subnet and gateway. The Original vCenter hostname and IP settings will be configured (copied) in the NEW vCenter Appliance based on the setting of the old vCenter.
  • Connect to the old and new vCenter appliance via a supported web browser. (personal experience is that IE works and Chrome not! For the upgrade process.
  • On the NEW vCenter, Accept the EULA

  • Next step in the upgrade process is to specify that you want to upgrade from a previous version

  • Still in the NEW appliance, copy the local appliance code to the clipboard

  • On the OLD vCenter appliance, go to the Upgrade tab and paste the clipboard content in the text box and press the import button.

     

     

  • If the import was successful you get a notice and then copy the upgrade key back to the clipboard

     

     

  • On the NEW server paste the upgrade key in the bottom text box and proceed by clicking the next button.

     

     

  • There is an option to replace the SSL certificates on the NEW with those ones from the OLD vCenter Appliance

     

     

  • Now the new SSO password must be entered for the SSO administrator account administrator@vsphere.local. (this was admin@system-domain in pre 5.5 versions)

     

     

  • Select now all the servers that need to check for compatibility with the new vCenter

     

     

  • After pressing next we see that we are ready to start the migration.

     

  • Pressing next will get following screen where you have to confirm that the upgrade process can proceed.

     

     

  • When you hit the start, the migration process start.

     

     

  • When you start the migration you will notice that the OLD vCenter server will be shut downed and the NEW vCenter server will have the IP configuration (hostname, IP settings) of the OLD ESX host.

    After a successful upgrade you can start upgrading the ESXi hosts to the latest ESXi version.

     

     

  • Can you login in the new vCenter Appliance via the Web Client and everything works fine you can remove the old vCenter Appliance from the inventory and from disk.
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

}

19
Dec

Remove leftovers of a vCenter plugin

During an upgrade at a customer site we removed a Dell Appliance that was connected to vCenter. We dit remove the aplliance just by powering it off and then remove it from the entry. Normally you should do an unregister from in the Dell Appliance.

Now we saw that there was a plugin that could not be loaded.

After some research on the internet I passed by on the website of William Lam (virtuallyGhetto).

He has written a nice article that describes step by step how to fix the problem we had. Look here.

 

Problem solved, thanks William for the good work.

10
Dec

Upgrade ESXi 5.0 to 5.1 via VMware Update Manager : incompatible

Today I am at customer site to upgrade en vSphere environment to the latest and greatest version of VMware vSphere 5.1.

We started the migration process by importing the VMware ESXi image we downloaded from the VMware download website.

In Update Manager we checked the server and saw that the server was not compliant with the new ESXi version so we could start the remediation.

After the remediation started we got the following message in Update Manager stating that the server was incompatible for this upgrade.

After some research on the internet I found following VMware KB 2034945 article.

As pointed out in this article the upgrade worked after a reboot of the ESX host.

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

27
Jun

VMware vCenter Error Call “PropertyCollector.RetrieveContents” for object “propertyCollector” on vCenter Server failed

A customer of mine called me with a weird problem with a Template which was converted back to a Virtual Machine. See here the problem which occurs when the customer wanted to edit the settings of this VM.

The cause of this problem is that an ISO was mounted from a datastore which does not exist anymore.

To solve this problem, just connect to the ESX host where the VM is registered on. Edit the setting here and put the CDROM on “Client Device”.

Then check on which datastore the VM is located. Then unregister and register the VM again in the ESX host. Now you are able again to edit jthe setting of this VM via vCenter

30
May

Unable to remove VMware ESXi host in VMware vCenter

During a migration process from ESX to ESXi at a customer site we had a problem removing a server from the vCenter inventory.

We checked the permissions on this server and we saw that the user who wanted to remove the server was admin on datacenter level. Here the screen we got.

Knowing there is a PowerCLI command to remove a ESXi host from the vCenter, we walked that way with success.

I used this
PowerCLI script to remove this server from the inventory after moving the
server out of the cluster to the datacenter level.


Connect-VIServer vCenterServer

Remove-VMHost “HostThatCannotBeRemovedViaGui” –confirm:$false

Disconnect-VIServer –confirm:$false