Thursday, March 25, 2010

Using Array Configuration Utility (ACU) on ESX host to extend VMFS volume

We had a situation where we had local VMFS volume and it needed to be expanded. Condition was without rebooting it. Searched through VMTM forum and could not found the way to expand VMFS volume with additional drives.  We have to reboot  no matter what so ever we do . This blog will explain about using ACU (Array Configuration Utility )

1. To start with we need to put HD into empty slot in ESX host.

2. We need to install HP Insight Manager and then ACU utility for Linux.

3. To install HP Insight Manager on 3.5 please follow this link.

4. For installing ACU on ESX host please download it from this link

While installing ACU I had issue with rpm . I had installed hpsmh-3.0.0-68 and my hprsm-8.1.1-29 was failing during the install

[root@xxx]# ./installvm811.sh --install
HP Insight Manager Agent 8.1.1-13 Installer for VMware ESX Server
Target System is VMware ESX Server 3.5.0 build-176894
This script will now attempt to install the HP Insight Manager Agents.
Do you wish to continue (y/n) y
Verifying VMware ESX Server version                                      [ OK ]
Verifying RPM packages:
        Verifying hp-OpenIPMI-8.1.1-26.vmware30.i386.rpm                 [ OK ]
        Verifying hpasm-8.1.1-29.vmware30.i386.rpm                       [ OK ]
        Verifying hprsm-8.1.1-29.vmware30.i386.rpm                       [ OK ]
        Verifying hpsmh-2.1.15-210.vmware30.i386.rpm                     [ OK ]
Checking for previously installed agents                                 [FAILED]
Some agents have already been installed. Please remove the previous installation.
Check hpmgmtlog for additional information

I then checked the log and found this
The following packages have already been installed on your system:
hpsmh-3.0.0-68
Please remove the previous installation
Exit 1

So I had to remove this RPM . For that we need to find the RPM name.

[root@xxxx 811]# rpm -qa | grep -i hp
VMware-esx-drivers-scsi-hpsa-350.2.4.66.95vmw-153875
hpsmh-3.0.0-68
Now since we found the rpm we can uninstall it
[root@xxxx 811]# rpm -e hpsmh-3.0.0-68
error: Failed dependencies:
   hpsmh is needed by (installed) cpqacuxe-8.25-5
Now we have to uninstall cpqacuxe-8.25-5
So here is the way
[root@zxxx  811]# rpm -e cpqacuxe-8.25-5
cpqacuxe still running! Stop it first.
Stop it first
[root@zxxx 811]# cpqacuxe -stop
[root@xxxx 811]# rpm -e cpqacuxe-8.25-5
[root@xxx 811]# rpm -e hpsmh-3.0.0-68
Stopping hpsmhd: [  OK  ]

5. Once you have installed HP Insight Manager agent on ESX host then you should install ACU

[root@xxx  hp_install]# rpm -ivh cpqacuxe-8.25-5.noarch.rpmcpqacuxe-8.25-5.noarch.rpm
[root@xxx  hp_install]# rpm -ivh cpqacuxe-8.25-5.noarch.rpm
Preparing...                ########################################### [100%]
   1:cpqacuxe               ########################################### [100%]

6. We have to enable the remote once it is installed.

[root@xxx  hp_install]# cpqacuxe --enable-remote
Array Configuration Utility version 8.25.5.0
Make sure that you have gone through the following checklist:
   1. Change the administrator password to something other than the default.
   2. Only run ACU on servers that are on a local intranet or a secure network.
   3. Secure the management port (port 2301 or 2381)on your network.
Remote connection enabled!

7. Now you should be able to access this using  url  https://<ILO IP>:2381. Use root and password for root . Once you logged in you will see something as squared below

clip_image002

8. Open it and that will bring the screen for ACU . You can see the unassigned drives. We will be using those drives and creating another array . Click on array and it will list all the option.

clip_image004

9. Select all the drives which you want to part of the array

clip_image006

10. Once you create array it will appear below the same controller .it will appear as unused space. We need to create logical partition

clip_image008

11. Create logical partition has to be saved or else it will not be visible. If you missed anything you can delete or discard.

clip_image010

12. It will popup following message. Choose OK

clip_image012

13. Once it is done it will appear under ESX host like this after host is rebooted. I was not able to get it without rebooting ESX host.

clip_image014

14. Now we need to extend the existing VMFS volume and select properties . Add the above capacity as extent.

clip_image016

I will be writing another one where I will be doing it from BIOS since reboot is required.

Friday, March 19, 2010

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 :)

Wednesday, March 17, 2010

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

Tuesday, March 9, 2010

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

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