I noticed that dell open manage was available for download:
Dell OpenManage VIB for ESXi 4.0
On the installation directions it lists:
Custom Instructions for oem-dell-openmanage-esxi_6.1-0000.zip:
##################
1) Download the appropriate RCLI (Remote Command Line Interface) package from http://www.vmware.com/download/ depending on whether your system is running on Microsoft Windows or Linux.
2) Copy the Dell OpenManage bundle to a directory on your system.
3) Use the vihostupdate command. If you are using Microsoft Windows, navigate to the folder where you have installed the RCLI utilities to use this command. If you are using Linux, this command is installed when you install the RCLI RPM .
4) Execute the command Vihostupdate -- server -i -b .
5) The command output displays a successful or a failed update.
You must enable CIM OEM providers on the VMware ESXi 4 system after installing the Dell OpenManage bundle to manage a system with Dell OpenManage Server Administrator.
Using vSphere Client to Enable CIM OEM Providers:
To enable CIM OEM providers using VMware vSphere Client, you need to have the vSphere Client tool installed. You can download and install the tool from http://where is the IP address of the VMware ESXi 4 system.
To enable CIM OEM providers on the VMware ESXi 4 system using vSphere Client:
1) Log on to the VMware ESXi 4 system in which vSphere Client is installed.
2) Click the Configuration tab.
3) Under the Software section on the left side, click Advanced Settings.
4) In the Advanced Settings dialog box, click "UserVars" on the left pane.
5) Change the value of the "CIMOEMProvidersEnabled" field to 1.
6) Click OK.
7) Restart your system for the change to take effect. Use the Summary tab in vSphere Client to restart the system.
##################
So I downloaded the zip.
Put the system in maintenance.
Attempt to update via vihostupdate.pl, which gives the error:
unpacking e:\oem-dell-openmanage-esxi_6.1-0000.zip ...
metadata.zip.sig does not exist
signature mismatch : metadata.zip
Unable to unpack update package.
I verified the zip files are valid.
I am patching from a windows 2003 system. I am running esxi build 175625.
Ideas?
It appears the hp cim patch has the same issue:
http://communities.vmware.com/message/1307359#1307359
nice to hear that
Hello,
have you tried using vMA 4.0 (http://www.vmware.com/support/developer/vima/) ? I installed DELL OM 6.1 using this appliance without problems.
I have installed VMA version4 and downloaded oem-dell-openmanage-esxi_6.1-0000.zip
as im new to esxi can someone give me instructions/help on how to install oem-dell-openmanage-esxi_6.1-0000.zip on esxi4 using vma V4
This is how I updated my ESXi using vMA 4:
vihostupdate --server ESXI_IP --username root --password MY_PASSWORD -i -b oem-dell-openmanage-esxi_6.1-0000.zip
caveat, teh free version needs to be patched using vmwa appliance or via ssh access on the system like such:
/vmfs/volumes/4a528247-36d54338-78b9-00221927561b # esxupdate --loglevel=DEBUG --bundle oem-dell-openmanage-esxi
_6.1-0000.zip update
oem-dell-openmanage-esxi_6.1-0000.zip ############################################################
Unpacking cross_oem-dell-openmanage-esxi_.. ############################################################
Installing packages :cross_oem-dell-openm.. ############################################################
ok.
ok.
Hello LucasAlbers,
The RCLI utility can be downloaded from http://www.vmware.com/support/developer/vcli/ instead of www.vmware.com/download
also the exact command is Vihostupdate -- server
Thanks,
krishnaprasad
I have question related to this topic. How do you connect to Dell OM on ESXi 4? I've tried using OpenManager Server Administrator Web Services 6.0.3 which can be found in dell support site next after OpenManage VIB for ESXi 4.0 but it always says that "Login failed....connection error". I have completly new installation of ESXi 4 downloaded from Dell support website, CIMOEMProvidersEnables is set to 1 and ESXi is patched to 175625.
Can you login to tech support mode ( ESXi shell ) and see the status of OpenManage service?
/usr/lib/ext/dell/dataeng status
Interresting. I dont have dell directory in /usr/lib/ext. Any idea why? I've installed ESXi from VMware-VMvisor-Installer-4.0.0-164009-Dell-Customized-Ext.iso
have you rebooted the system after applying OpenManage zip file on your system? you will have to reboot to get it installed properly.
Yes. Few times.
Interesting !!!! can you execute the command esxupdate query
this should give us more details whether OpenManage is really installed or not.
After writing my previous post I've used esxupdate command and I've installed openmanage extensions from update package so it is now listed in query list. Do I need to have ESXi server patched with latest patches to install openmanage extension? I'm askign because I was trying to install it on my second ESXi server (164009) and I was getting error message after installation (second screenshot). When I try to run esxupdate query command on this server I'm only getting "Bulletin ID Installed Summary" line.
As per Dell support site you are supposed to install ESXi 4.0 Patch 1 before installing OpenManage.
Thats why I had mentioned error during update on second ESXi server but I still don't know why there was no Dell OM on first ESXi if it was installed from iso downloaded from dell site. I've reboot my ESXi at night and check if Dell directory will appear in ext folder
so does that mean you are able to see /usr/lib/ext/dell now?
Nope. Not yet I hope. I will restart ESXi server at night (now it is 4PM) and will let you know tomorrow.
EDIT: should I see it before restarting ESXi too?
Ran the esxupdate from ssh, rebooted esxi, worked a treat for me
thanks to you all for your help
Run esxupdate query commnad only after reboot.
Actually I'm having the same issues. I can run a "vihostupdate query" and see the Bulletin, I can run "/usr/lib/ext/dell/dataeng status" and see three running processes, I just cannot connect to Open Manage. Yes I have rebooted, several times. I even rebuilt the server, applied patch1 then OpenManage 6.1 and still no go. Any ideas?