VMware Cloud Community
LucasAlbers
Expert
Expert
Jump to solution

installing dell openmanage 6.1 on esxi 4.0 (released.)

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

Reply
0 Kudos
67 Replies
Webio
Enthusiast
Enthusiast
Jump to solution

ok. I've rebooted ESXi server and query returns that I have Dell_OpenManage_ESXi installed and /usr/lib/ext/dell/dataeng status informs me that three OM processes are running (dsm_sa_datamgr32d, dsm_sa_eventmgr32d, dsm_sa_snmp32d). But when I'm trying to connect to my server using "Server Administrator" (runned on my desktop on port 1311) I'm still having error "Login failed....connection error". Can this be related to Windows 7 which I use as a desktop system? When DELL OM is enabled is there any additional TCP port opened? I can scan my server with nmap.

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

probably you are not using the correct server administrator to connect to openManage.

Go to support site( support.dell.com ) and search for 6.1.0, A00 – download Open Manage Server Administrator Managed Node. You can use this as server administrator.

Reply
0 Kudos
Webio
Enthusiast
Enthusiast
Jump to solution

OK. I'll try that. I presumed that Dell OpenManage Server Administrator Web Services located in Systems Management when I have selected ESXi will work.

EDIT: It works. Big thanks

Reply
0 Kudos
ToddStriegel
Contributor
Contributor
Jump to solution

I don't know how I missed that but I most certainly did. That worked perfectly. Thank you!

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

nice to hear that Smiley Happy

Reply
0 Kudos
LucasAlbers
Expert
Expert
Jump to solution

thanks for helping everyone on this question.

in summary.

you need to patch the host up from ga.

install it using vihostupdate or vma or esxupdate.

turn on cim using the uservars.

install the 6.1 patch

reboot

install the 6.1 managed node client on your windows box.

tada!

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

Exactly !!

Reply
0 Kudos
josephus
Contributor
Contributor
Jump to solution

Thanks for the infos so far, I still have a couple of questions regarding the upgrade from 3.5U4-DELL.

So I have a free ESXi 3.5U4 with Dell Openmanage 6.01. The system is on a USB key, I want to upgrade using the latest

"VMware ESXi 4.0 (upgrade ZIP)

Version 4.0.0 | 171294 - 06/22/09"

upgrade. What happens to my previous Openmanage install? (dell's oem.tgz)

Will ESXi4 remove it or do I have to uninstall it before applying the 6.1 openmanage?

Btw, what's the deal with the Dell ESXI4 iso? Why do people have to install 6.1 openmanage on it, I thought it's already included. The only diff in ESXi3.5 was that dell added their oem.tgz (openmanage 6.0x) and that's all. Does this installer image have something extra in it?

Reply
0 Kudos
JMBCalgary
Contributor
Contributor
Jump to solution

One more question on this, We are running Dell 2950's as our hosts, but I think the ESXi 4 we have is direct form the Vmware Download site and not from the Dell Support site, will this cause a problem with installing the Dell open manage software? Do I have to take and rebuild my ESXi host using the Dell ESXi4 installer?

Thanks.

Reply
0 Kudos
ToddStriegel
Contributor
Contributor
Jump to solution

That's exactly what I did. I grabbed the vSphere ISO from VMware, installed, patched to Patch 1, installed Dell OM and it worked properly.

Reply
0 Kudos
ToddStriegel
Contributor
Contributor
Jump to solution

"Btw,

what's the deal with the Dell ESXI4 iso? Why do people have to install

6.1 openmanage on it, I thought it's already included. The only diff in

ESXi3.5 was that dell added their oem.tgz (openmanage 6.0x) and that's

all. Does this installer image have something extra in it?"

I personally do not like to use an image someone has modified, unless I did the modification. I install the OS then install the management. In this case though, I could not get the management to talke to my OM Administrator. It ended up being I had to upgrade the admin, which I cannot do, so I installed on another system.

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

From ESXi 4.0 onwards Dell OpenManage will be bundled as a separate bulletin so that customers can download and install it on ESXi when ever required

in the case of ESXi 3.5 you were not having this freedom. if youy think you dont need it, you can remove Openmanage. same in the case of installation as well.

I believe the Dell customized images has just the support links and all in which you can see at the yellow screen Support information tab.

Reply
0 Kudos
JMBCalgary
Contributor
Contributor
Jump to solution

So I have tried to load the ESXi OpenMange using the Vmware VI Remote CLI and I keep getting errors.

This is the message I get on 4 ESXi hosts that I have tried, I have patched them all to 4.0.0, 175625

unpacking c:\tmp\oem-dell-openmanage-esxi_6.1-0000.zip ...

metadata.zip.sig does not exist

signature mismatch : metadata.zip

Unable to unpack update package.

Thanks,

Jesse

Reply
0 Kudos
LucasAlbers
Expert
Expert
Jump to solution

Read this whole post again, I encountered this issue previously.

I encountered this issue when attempting a free version of esxi with the client.

Use vima or run esxupdate from the host, read this discussion from the top to see resolution.

Reply
0 Kudos
JMBCalgary
Contributor
Contributor
Jump to solution

I have the VIMA appliance but I am unsure how to get the Dell update file onto the appliance to install the update. How do I use the ESXupdate tool from the host, do I need to enable SSH on the host to make this work, is this possible on ESXi.

We are not using the Free version.

Jesse

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

Hello,

here are the exact steps for installing dell openmanage on ESXi 4.0. This is provided in their support site.

1) Download the appropriate RCLI (Remote Command Line Interface) package from http://www.vmware.com/http://www.vmware.com/support/developer/vcli/ 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 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.

Reply
0 Kudos
JMBCalgary
Contributor
Contributor
Jump to solution

My problem is at step 3 of your guide:

At the command Prompt I enter:

C:\Program Files (x86)\VMware\VMware VI Remote CLI\bin>vihostupdate.pl --server

jmcges04.jayman.com -i -b c:\tmp\oem-dell-openmanage-esxi_6.1-0000.zip

Then I get back:

unpacking c:\tmp\oem-dell-openmanage-esxi_6.1-0000.zip ...

metadata.zip.sig does not exist

signature mismatch : metadata.zip

Unable to unpack update package.

C:\Program Files (x86)\VMware\VMware VI Remote CLI\bin>

So I cant get to a point where it even installs the Dell Package.

Thanks,

Jesse

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

i am not sure on this error. can you do the below methods to copy the zip file to ESXi directly and do install?

1) On an ESXI box, open /etc/inetd.conf file and search for ssh --> this line will be commented by default. uncomment the line and save the file

2) get the process ID of inetd service by doing ps | grep inted

3) kill -1 update

Reply
0 Kudos
ToddStriegel
Contributor
Contributor
Jump to solution

I got that the first time I downloaded it. I downloaded it through the Dell Download Manager and got this. I then changed to download it straight through Firefox and I was able to install it after that.

Reply
0 Kudos
krishnaprasad
Hot Shot
Hot Shot
Jump to solution

okay... probably the zip file is getting corrupted hence the signature missing error.

Reply
0 Kudos