VMware ESXi 4.1 and Dell OMSA 6.3

VMware ESXi 4.1 and Dell OMSA

Setting up Dell OpenManage Server Administrator is a very simple and straight forward endeavor.  This is probably why when the process recently failed I wandered off aimlessly in to the ether following post after post in a fruitless search for the answer I desperately needed.

Hopefully what follows will pull together a few different manuals, blogs and forum posts, along with a tidbit or two that I did not find while searching.

I will be talking specifically about ESXi 4.1, and Dell OpenManage 6.3 in this post.

Here is my process:

Download everything you will need:

  • VMware-vSphere-CLI-4.1.0-254719
  • OM-SrvAdmin-Dell-Web-6.3.0-2075.VIB-ESX41i_A00.8.zip
  • OM-SrvAdmin-Dell-Web-Win-6.3.0-2075_A00.20.exe

Put your host in to maintenance mode

Once you have everything downloaded I personally like to put the host I will be working with in to maintenance mode, I recommend rebooting, so you might as well get this out of the way up front.  While that process is happening:

Update VMware vSphere CLI using: VMware-vSphere-CLI-4.1.0-254719.

Install the VIB

With your host in maintenance mode open vSphere CLI and enter the following line, taking care to change the esxiservername, possibly the username and your password:

Reboot the host

Install Dell OpenManage Server Administrator Managed Node

To access OMSA on your host you will first need to install Dell OpenManage Server Administrator Managed Node using: OM-SrvAdmin-Dell-Web-Win-6.3.0-2075_A00.20.exe.

Finished!

or maybe not.

Can’t install the VIB?

Generally this means either update the CLI or verify you are using the correct version of the VIB, there are probably others but since I didn’t encounter the issue here is the limit of what I can offer.

If you cannot access the host I have seen many posts about it things to check:

  • Are you using an OMSA managed node and not directly trying to access the host?
  • Do you have a blank password for the management conosle on the ESXi host?
  • You can verify that the services are running: /usr/lib/ext/dell/srvadmin/bin/dataeng status
  • Is UserVars.CIMOEMProvidersEnabled set to 1?

Leave that setting as is, instead:

Go to vSphere, select the host, choose the configuration tab, go to the software window and click advanced settings.  From here find UserVars and then: UserVars.CIMoemProviderEnabled set that to 1 if it isn’t.  This is NOT UserVars.CIMOEMProvidersEnabled, there is a difference!

Once you have changed this or verified the setting is correct restart the host and you should now have no problem accessing Dell OMSA on ESXi from the Managed Node.

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

13 Responses to VMware ESXi 4.1 and Dell OMSA 6.3

  1. Tim Jones says:

    Thank you for the instructions. I appreciate you taking the time to post them. They were concise and very helpful.

    Have a Good Day!

  2. waqqas31 says:

    Sam,

    It’s also possible to install the OM Agents on white box (non-Dell) ESXi servers as well, as this is almost the only way to monitor PERC cards on an ESXi host. Details are here:

    http://waqqas31.wordpress.com/2010/11/15/install-dell-openmanage-server-administrator-agents-on-any-esxi-4-1-white-box-server-to-manage-perc-cards/

  3. Brian says:

    Just wanted to thank you on this one. After many Google searches and “internal error” on OM while trying to login, flipping the CIMoemProviderEnabled to 1 did the trick. Already had CIMoemProvidersEnabled set to 1. Not sure why Vmware has 2 properties with such close names. Might have something to do with vSphere 4 to 4.1 upgrade adding a new prop? Anyway, thanks. Hopefully this helps others as well

  4. Richard Karel says:

    I am struggling with the issue of trying to stop and restart the OMSA agent on ESXi. I believe that it should stop and start with the management agents. If one were to want to stop or start the agent only, what is the path and command?
    Thanks

    • samdecker says:

      Hello Richard,

      “/usr/lib/ext/dell/srvadmin/bin/dataeng” has several options. start, stop, restart, force-reload,status…etc. I’ve only used the status to verify everything is running. If you have a machine you don’t mind playing around with, that may be the command you’re looking for.

  5. Brian Farrugia says:

    Hi,
    thanks for the guide. I managed to install OMSA 6.4. The last part were you have to set to 1 the CIMoemProviderEnabled variable solved the “internal error” I had when I tried to log on to the ESXi server.
    I have used your guide together with posts from http://communities.vmware.com/thread/277354?start=0&tstart=0 in my personal documentation.
    thanks again
    Brian

  6. Prateek says:

    Thanks for posting. However i would like to kn ow is there any way i can also that incase of any harware error or so we can generate alerts ? Right now we have 4 free esxi servers and i once in a while just log into them using OMSA and see if there is any error.
    I dont have vcenter just free esxi
    Thank you again.

  7. Alex says:

    For ESXi 4.1 Update 1 Build 348481, installing OM-SrvAdmin-Dell-Web-6.3.0-2075.VIB-ESX41i_A00.8.zip sends an error
    No matching bulletin or VIB was found in the metadata.No bulletins for this plat
    form could be found. Nothing to do.
    Be careful when you go Update 1!!

  8. Alex says:

    About the harware error generate alerts, you can try to use the check_esxi_hardware.py. A phyton script that can give you a hardware status of your ESXi server: “OK” , “Warning” , “Critical” or “Unknown”
    From that, use your favorite monitor app and send alerts as you wish.
    Read more here
    http://www.claudiokuenzler.com/nagios-plugins/check_esxi_hardware.php

  9. thanks
    iincase any others are as stupid as me, – i have spent half a day trying to log on to the guest with administrator credentials
    make sure you log into the HOST (even though the desktop sortcut gives the guest) and make sure you use “root” as username – with the VSphere password which must be set

  10. Ariel Sandberg says:

    Thanks Dude!
    was getting “internal error” on the logins until I changed UserVars.CIMOEMProviderEnabled to 1.

    it is very clearly documented on the new omsa (6.5) documentation but I was following this link for 6.3 omsa documentation http://support.dell.com/support/edocs/software/smsom/6.3/en/omsa_ig/html/instesxi.htm

    It still references UserVars.CIMOEMProvidersEnabled (WITH AN “S”).

    Cheers,
    Ariel

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s