In a migration project to VMware vSphere 5.5 I bumped into duplicate MAC address issue (I found out after some investigation).
Some info on the setup.
There are ESXi hosts that we are migrating from 5.0 to 5.5. Some VM’s where 2 VM’s (VM1 and VM2) share the same MAC address (production and test machine).
On ESXi 5.0 these 2 VM’s can run together on the same ESXi host.
I want to move the VM’s to an already upgraded ESXi 5.5 host, the first VM (VM1 moves without any problems. ) For the second VM (VM2) I get following error during vMotion. Same error happens when I cold migrate the VM2 to the same host (ESXi 5.5) as VM1 and try to power VM2 on.
After some Google research I came across following blog
And adding the advanced setting to VM2 fixed the problem.
Before starting an upgrade at a customer site I was surprised how long an ESXi host can run. Here the proof.
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.
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.
Gert Van Gorp
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.
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
VmwareTips: VMware 2011 Mega Launch
Virtual Geek: Raising the Bar V = vSphere 5!
vTexan: really cool things in vSphere5
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
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.
Remove-VMHost “HostThatCannotBeRemovedViaGui” –confirm:$false
Since VMworld San Francisco 2010 we are waiting for this nice app for the Ipad. VMware today released this app via the iTunes store for FREE (Direct Link), just as the VMware View Client for IPAD (Direct Link).
What are the features available in this app?
- Search for vSphere hosts and virtual machines in your vSphere environment
- Monitor the performance of vSphere hosts and virtual machines
- Manage virtual machines with the ability to start, stop and suspend
- View and restore your virtual machines’ snapshots
- Reboot vSphere hosts or put them into maintenance mode
- Diagnose vSphere hosts and virtual machines using built-in ping and traceroute tools
What is required for this app to be able to manage your vCenter?
vCenter Mobile Access (vCMA) virtual appliance available from the VMware Labs: http://labs.vmware.com/flings/vcma (Now supports SSL)
NOTE: This app is available as is, with community support.
- Network connection to the vCMA virtual appliance; can use built-in VPN client
VMware vSphere and VMware vCenter Server
Look at my blog entry to see how to setup the vCMA : limited-vsphere-management-using-a-mobile-device
An overview of the architecture
Some interesting links
On the VMware Labs website you can find a free appliance that can give you limited access to the management tools available in vSphere vCenter. The appliance is called vCMA or vCenter Mobile Access.
How to install?
- Go to the vmware.com/labs website and download vCMA as a OVF. Jump to site
- Extract the zip file that contains the OVF.
- In vCenter, go File – Deploy from OVF and point to the extracted OVF file.
- Once deployed, you can start the VM.
After the VM is started, there are 3 options to change settings
Using the menus on the console (to set network, timezone, login in to the command console)
Using the web interface https://vcma-host-or-ip:5480
Or using the command console. (use login in first screen)
- By default the root account has as password vmware (remember the console is by default in qwerty)
Special configuration settings to thing about!
- Set the IP to a fixed address
- Enter the DNS servers
- Change the default hostname and domainname. (http://communities.vmware.com/message/1335001)
- Change the root default password using the passwd, in the command console
How to use?
- It is very easy to start using this app.
- Open a browser (on you PC or mobile device)
- Point to http:// vcma-host-or-ip/vim (the folder /vim is needed and I hope VMware will change this in a next release)
- Enter the vCenter server name and the userID and password you normally use in the vcenter.
Now you can do some functions like
- Edit settings of a VM
- Change Powerstates of a VM
- Etc, install and discover.
Alternative apps you need to buy!
iDatacenter http://nym.se/idatacenter/ (iPAD)
iVMControl : http://itunes.apple.com/us/app/ivmcontrol-control-vmware/id404263941?mt=8 (iPAD, iPhone)