My VCP 4.0 Certification

I have completed my VCP on NOV 2009 and from that moment I was following up with VMware education department for my certificate. Finally I received it yesterday. Thanks to VMware for it :)

Vmotion between esx3.5 and 4.0 host; Error VMotion is not license

I was testing if HA/DRS cluster can exist with ESX 4.0 and 3.5 . You can have full fledge DRS enabled cluster. But there is some bug.

I forgot to set vmotion enable on my vSwitch (normal manual mistake which people does ) and I was testing vmotion from 4.0 host to 3.5. It was giving me weird message

I called VMware license support guy and he/she (since they put me on mute) directly went to vSwitch and changed the setting. I am pretty sure they knew this error message in-hand. As you can have look at error and you can understand it is completely misguiding. This 3.5 host was part of VC2.5 HA/DRS cluster. Was wondering how come it will not be licensed?

Let’s see if VMware already had fix or accept it as bug.

VI3 hosts cannot be added if vCenter is licensed but License Server is not Configured

I had thought of playing with VC4.0 /ESX3.5/4.0 . I had VC4.0 and then from my VC2.5 I disconnect one ESX host and was trying to connect my VC4.0 . It was giving me error

I then checked license and found that it was added with IP address. I then added another VI3 license server using FQDN and then I was able to add ESX host into VC4.0

VMkernel capacity view released

Today I got an update

that Capacity View has been released. Capacity View is a free server and storage capacity management tool for VMware admins that helps you quickly identify and diagnose:

· Capacity related performance issues like:

o High VM I/O latency

o Under allocated memory, CPU and storage

· How many VM “slots” are available for new VMs

· VMs with over-provisioned memory, CPU and storage

Capacity View is a small, easy to use tool that provides VMware performance and capacity diagnostics. Download now and be up and running in 3 minutes

Working with Blade7:Integrating Onboard Administrator and Virtual Connect Manger with AD

1. Make sure  you define access level and create e AD security group accordingly.

2. Make sure you perform “Directory Settings” as shown below.

A. “ Directory Server Address:* : “ can be any Domain controller IP address.

B. “Directory Server SSL Port:*”  will be fixed 636

C. “Search Context 1: ”  will be in the format of  OU=Users,OU=ABCD,DC=abcd,DC=net

D. One thing to remember is that user from ABC OU can be only able to authenticate. So if you want to user from EFG to be authenticated then either you move the user to ABCD OU or create another “Search Context” with following  OU=Users,OU=EFG ,DC=ABCD,DC=net. The other way to find out field would be looking at user object properties.

3. We need to create directory group as shown below. Make sure you set the correct privilege level and check correct Device bay for access.

4.. Same setting has been done on VC Manager

and then