DenshiKenshi
Contributor
Contributor

Dell OMSA 6.5 VIB Installation on ESXi 5?

Hi all:

Not sure why I'm banging my head on the wall for what should be a simple installation procedure.

I have a Dell PowerEdge R610 server with a fresh install of ESXi 5 Enterprise Plus (Build 469512--neither of the two available patches have been installed because we don't use vShield or iSCSI in this environment). I'm attempting to install the Dell OpenManage Server Assistant VIB so that I can monitor/manage the PERC controller without having to use the BIOS menus.

I read this Dell blog entry...

http://en.community.dell.com/techcenter/b/techcenter/archive/2011/08/26/dell-openmanage-server-assis...

...which instructed to download this file (my MD5 checksum is 0a485f2bc754a9aeb99e6caa26ae5863)...

http://en.community.dell.com/dell-groups/dtcmedia/m/mediagallery/19928975/download.aspx

...and follow these instructions for installation...

http://media.community.dell.com/en/dtc/attach/omsa6.5%20for%20esxi5_kb.pdf

Specifically, here are the exact steps from that doc:

1. Copy the Dell_OpenManage_ESXi_OM650-offline_bundle-467660.zip
file to the /var/log/vmware folder on the ESXi5.0 server.

2. Shut down all guest operating systems on the ESXi host and run the ESXi
host in maintenance mode.

3. If you are using Windows, navigate to the directory in which you have
installed the vSphere CLI utilities to run the command mentioned
in step 4.
If you are using vSphere CLI on Linux, you can run the command in step 4
from any directory.

4. Run the following command:
esxcli --server <IP Address of ESXi 5.0 host>
software vib install -d /var/log/vmware/<Dell
OpenManage file>

5. Type the root user name and password of the ESXi host when prompted.
The command output displays a successful update.

6. Restart the ESXi host system.

Unfortunately, here's what I get from step #4:

C:\Program Files\VMware\VMware vSphere CLI>esxcli --server 10.5.115.62 software
vib install -d /var/log/vmware/Dell_OpenManage_ESXi_OM650-offline_bundle-467660.
zip
Enter username: root
Enter password:
[InstallationError]
Error in copying from /bootbank/ata-pata.v01 to /altbootbank/ata-pata.v01: [Err
no 2] No such file or directory: '/altbootbank/ata-pata.v01'
       vibs = set(['VMware_bootbank_net-ixgbe_2.0.84.8.2-10vmw.500.0.0.469512',
'VMware_bootbank_ehci-ehci-hcd_1.0-3vmw.500.0.0.469512', 'VMware_bootbank_ata-pa
ta-atiixp_0.4.6-3vmw.500.0.0.469512', 'VMware_bootbank_scsi-megaraid2_2.00.4-9vm
w.500.0.0.469512', 'VMware_bootbank_uhci-usb-uhci_1.0-3vmw.500.0.0.469512', 'VMw
are_bootbank_net-r8168_8.013.00-3vmw.500.0.0.469512', 'VMware_bootbank_ohci-usb-
ohci_1.0-3vmw.500.0.0.469512', 'VMware_bootbank_scsi-qla4xxx_5.01.03.2-3vmw.500.
0.0.469512', 'VMware_bootbank_ata-pata-sil680_0.4.8-3vmw.500.0.0.469512', 'VMwar
e_bootbank_scsi-megaraid-sas_4.32-1vmw.500.0.0.469512', 'VMware_bootbank_scsi-ai
c79xx_3.1-5vmw.500.0.0.469512', 'VMware_bootbank_net-bnx2_2.0.15g.v50.11-5vmw.50
0.0.0.469512', 'VMware_bootbank_ata-pata-serverworks_0.4.3-3vmw.500.0.0.469512',
'VMware_bootbank_sata-sata-promise_2.12-3vmw.500.0.0.469512', 'VMware_bootbank_
scsi-fnic_1.5.0.3-1vmw.500.0.0.469512', 'VMware_bootbank_ata-pata-pdc2027x_1.0-3
vmw.500.0.0.469512', 'VMware_bootbank_scsi-hpsa_5.0.0-17vmw.500.0.0.469512', 'VM
ware_bootbank_scsi-bnx2i_1.9.1d.v50.1-3vmw.500.0.0.469512', 'VMware_bootbank_net
-igb_2.1.11.1-3vmw.500.0.0.469512', 'VMware_bootbank_net-e1000e_1.1.2-3vmw.500.0
.0.469512', 'VMware_bootbank_net-forcedeth_0.61-2vmw.500.0.0.469512', 'VMware_bo
otbank_sata-ata-piix_2.12-4vmw.500.0.0.469512', 'VMware_bootbank_scsi-qla2xxx_90
1.k1.1-14vmw.500.0.0.469512', 'VMware_bootbank_scsi-adp94xx_1.0.8.12-6vmw.500.0.
0.469512', 'VMware_bootbank_net-sky2_1.20-2vmw.500.0.0.469512', 'Dell_bootbank_O
penManage_6.5-0000', 'VMware_bootbank_esx-tboot_5.0.0-0.0.469512', 'VMware_bootb
ank_ipmi-ipmi-msghandler_39.1-4vmw.500.0.0.469512', 'VMware_bootbank_net-be2net_
4.0.88.0-1vmw.500.0.0.469512', 'VMware_bootbank_esx-base_5.0.0-0.0.469512', 'VMw
are_bootbank_ipmi-ipmi-si-drv_39.1-4vmw.500.0.0.469512', 'VMware_bootbank_net-nx
-nic_4.0.557-3vmw.500.0.0.469512', 'VMware_bootbank_sata-ahci_3.0-6vmw.500.0.0.4
69512', 'VMware_bootbank_scsi-ips_7.12.05-4vmw.500.0.0.469512', 'VMware_bootbank
_ata-pata-cmd64x_0.2.5-3vmw.500.0.0.469512', 'VMware_bootbank_scsi-mpt2sas_06.00
.00.00-5vmw.500.0.0.469512', 'VMware_bootbank_sata-sata-sil_2.3-3vmw.500.0.0.469
512', 'VMware_bootbank_sata-sata-svw_2.3-3vmw.500.0.0.469512', 'VMware_bootbank_
ata-pata-via_0.3.3-2vmw.500.0.0.469512', 'VMware_bootbank_scsi-lpfc820_8.2.2.1-1
8vmw.500.0.0.469512', 'VMware_bootbank_scsi-mptspi_4.23.01.00-5vmw.500.0.0.46951
2', 'VMware_bootbank_misc-cnic-register_1.1-1vmw.500.0.0.469512', 'VMware_bootba
nk_net-s2io_2.1.4.13427-3vmw.500.0.0.469512', 'VMware_bootbank_net-e1000_8.0.3.1
-2vmw.500.0.0.469512', 'VMware_bootbank_block-cciss_3.6.14-10vmw.500.0.0.469512'
, 'VMware_bootbank_net-enic_1.4.2.15a-1vmw.500.0.0.469512', 'VMware_bootbank_ata
-pata-amd_0.3.10-3vmw.500.0.0.469512', 'VMware_bootbank_ata-pata-hpt3x2n_0.3.4-3
vmw.500.0.0.469512', 'VMware_bootbank_sata-sata-nv_3.5-3vmw.500.0.0.469512', 'VM
ware_bootbank_misc-drivers_5.0.0-0.0.469512', 'VMware_bootbank_net-cnic_1.10.2j.
v50.7-2vmw.500.0.0.469512', 'VMware_bootbank_scsi-mptsas_4.23.01.00-5vmw.500.0.0
.469512', 'VMware_bootbank_scsi-aacraid_1.1.5.1-9vmw.500.0.0.469512', 'VMware_bo
otbank_ima-qla4xxx_2.01.07-1vmw.500.0.0.469512', 'VMware_bootbank_ipmi-ipmi-devi
ntf_39.1-4vmw.500.0.0.469512', 'VMware_bootbank_net-tg3_3.110h.v50.4-4vmw.500.0.
0.469512', 'VMware_bootbank_net-bnx2x_1.61.15.v50.1-1vmw.500.0.0.469512', 'VMwar
e_bootbank_net-r8169_6.011.00-2vmw.500.0.0.469512', 'VMware_bootbank_scsi-megara
id-mbox_2.20.5.1-6vmw.500.0.0.469512'])
Please refer to the log file for more details.

C:\Program Files\VMware\VMware vSphere CLI>

From what I can gather, it appears to choke when trying to back up the installed firmware to the altbootbank prior to performing the upgrade. This has happened on two different boxes at this point (the first was a Precision 490 workstation).

The only thing that comes to mind is that I'm using 2gb USB flash drives as the boot device. Should this make a difference and cause the VIB install to fail?

I guess a secondary question would be, does anyone know of a VIB injection method similar to the below which has been confirmed to work for ESXi 5 ISOs, so that I don't have to bother with a separate installation at all?

http://en.community.dell.com/techcenter/virtualization/w/wiki/customize-your-esxi-installer-with-inj...

Thanks in advance for any ideas on either.

0 Kudos
26 Replies
rajvm256
Enthusiast
Enthusiast

Can you check your esxupdate logs that should be there in /var/log/vmware (guess ..) to see if it is a space problem .. also please check how much space you have ..why not keep the patch bundle in a VMFS volume which has space ..

Thanks | http://virtualvm.info/
0 Kudos
AndreTheGiant
Immortal
Immortal

I've tried with VUM without issue.

See: http://vinfrastructure.it/en/2011/09/installing-dell-omsa-on-esxi-5/

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
DenshiKenshi
Contributor
Contributor

@Raj - I'm installing from /var/log/vmware because the instructions from Dell explicitly state to use that location.

Space doesn't appear to be an issue since the USB drive is 2gb instead of the required 1gb. Furthermore, the VIB is less than 5mb:

/var/log/vmware # ls -l Dell_OpenManage_ESXi_OM650-offline_bundle-467660.zip
-rw-r--r--    1 root     root            4913570 Nov 23 14:40 Dell_OpenManage_ESXi_OM650-offline_bundle-467660.zip

To be 100% sure, though, I copied the VIB to a datastore (local 1TB disk) and tried installing from there, but got the same result.

0 Kudos
DenshiKenshi
Contributor
Contributor

@Andre - Thanks, I've come across your blog post on the matter before. Unfortunately, I don't have a VUM setup and therefore have to rely upon the more manual methods.

It appears that PowerCLI will allow the VIB to be integrated into a standard ESXi 5 ISO, so I'll try playing with that and see how it goes.

0 Kudos
jonpartridge
Contributor
Contributor

I have the exact same issue on Dell R710s.  Originally I tried installing the VIB via CLI.  "esxcli software vib list" in fact lists "OpenManage  6.5-0000", however, I still cannot access OMSA on the host via the Dell vCenter Plugin.  UserVars.CIMvmw_OpenManageProviderEnabled is set to "1" and reboots have been performed.  It's a head scratcher.

After messing with it for a while, I decided (like you) to use the Image Builder in PowerCLI to package the Dell OMSA VIB along with the ESXi 5 install.  My iso installs flawlessly and the OMSA is installed just like previously BUT still no connectivity to OMSA.  Let me know if you have any luck with the install.  Otherwise, hopefully someone else has solved this issue and could shed some light.

0 Kudos
AndreTheGiant
Immortal
Immortal

What are you using as a OMSA "proxy"? I've only tried with a Windows Server 2008 R2, and I'm sure that with XP does not work at all (it give internal server error)

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos
nsarmien
Contributor
Contributor

I managed to install OpenManage 6.5 on my R710 after hours of struggling.

Step 1: Download the Offline Bundle from the link below

http://en.community.dell.com/dell-groups/dtcmedia/m/mediagallery/19928975/download.aspx

Step 2: Install the vSphere CLI 5 client on your workstation/server you will use

Step 3: Upload the Offline Bundle file to your DataStore. I placed the file within a folder named "Install" on my DataStore

Step 4: Connect to your ESXi 5.0 server with the vSphere Client and click the Configuration Tab. Click on Storage, select your DataStore from within the DataStores window pane. Take note of the Location:

Capture12.JPG

Step 5: Put your server in "Maintenance Mode"

Step 6: Install OpenManage 6.5 using the following command: esxcli --server IP Address software vib install -d "Location Path Your Took note Of"/Install/Dell_OpenManage_ESXi_OM650-offline_bundle-467660.zip

My command was: esxcli --server IP Address software vib install -d /vmfs/volumes/4ed790fa-53e451ba-dbfc-782bcb5b872a/Install/Dell
_OpenManage_ESXi_OM650-offline_bundle-467660.zip

Enter your root credentials and voila!

Step: 7 Reboot your server and exit Maintenance Mode. No need to enable CIM OEM providers, it's turned on by default.

0 Kudos
gbannoff
Contributor
Contributor

Thanks for your post.  It worked perfectly on one machine, but not on the second ESXi 5.0 machine.  But, it turns out that you can use [datastore] in place of the GUID, making it a bit easier.

Internal server IP address is: 172.16.9.99

Datastore is (creatively) called: datastoreA

I downloaded Dell OpenManage Server Administrator (OMSA) monitoring agent from

http://en.community.dell.com/techcenter/systems-management/w/wiki/1977.aspx

and copied it to the datastore, in a newly-created directory:  Dell

This is the command I used:

C:\Program Files\VMware\VMware vSphere CLI>esxcli --server 172.16.9.99 software vib install -d [datastoreA]/Dell/OM-SrvAdmin-Dell-Web-6.5.0-542907.VIB-ESX50i_A02.zip

and it seemed to work:

Enter username: root
Enter password:
Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed: Dell_bootbank_OpenManage_6.5-0000
   VIBs Removed:
   VIBs Skipped:
0 Kudos
stevenfoo
Contributor
Contributor

How much memory will this VIB agent use up in ESXi5 ??

I read it need 3GB? Is this true?

0 Kudos
stevenfoo
Contributor
Contributor

I installed Dell_OpenManage_ESXi_OM650-offline_bundle-467660.zip into a vsphere 5.0 host.

Then I installed the Server Administrator 6.5.0 into another windows 2003 server. The I launch the site and enter the hostname, user and password using IE 8.

However I still get the error Login Failed, certificate error.

I already accepted the certficate at the broswer level and save it.

Any idea how to resolve this?

0 Kudos
stevenfoo
Contributor
Contributor

I manage to clear the Logon Failed, Certificate error.

However now I get the Logon Failed, Internal Error.

Any ideas how to resovled? Still can't manage to get into OM.

The server where OM Admin is installed run on win 2003.

0 Kudos
stevenfoo
Contributor
Contributor

Appreciated if any reply of help. We are stuck with this Dell OMSA issue. Thanks.

0 Kudos
gbannoff
Contributor
Contributor

I got stuck at the same point. I figured I'll have to take it up with Dell Support when I get some free time. Sorry I can't be more helpful.

..Geoff

0 Kudos
EricChris
Contributor
Contributor

I am having the same problem. The  Dell VIB installs fine but I can't access it from Server Adminstrator or from a browser at https:\\<eix5 host ip>:1311. I did a port scan and nothing is running on port 1311. It seems like the web service on esxi is not running. Is there a way to check this?

Clipboard01.jpg

0 Kudos
jb12345
Enthusiast
Enthusiast

Try 'esxcli network connection list' from your host & see what ports are open.

0 Kudos
nsarmien
Contributor
Contributor

I discovered that it can be a bit buggy, since OMSA 6.5 wasn't fully and officially supported in ESXi 5.0 enviroments by Dell.

In December they released a supported OMSA agent for ESXi 5.0, that can be downloaded from here.

http://en.community.dell.com/techcenter/systems-management/w/wiki/1977.aspx

Make sure your ESXi 5.0 hosts are running on the latest version/patches as well.

0 Kudos
EricChris
Contributor
Contributor

Nothing on on port 1311. I have verified that wsman service is running by /etc/init.d/wsman status. It does not seem to be loading the OMSA VIB

0 Kudos
jb12345
Enthusiast
Enthusiast

You confirmed that OMSA installed? - 'esxcli software vib list |grep open' and confirmed that the CIMoemProviderEnabled field is set to 1?

verify that the services are enabled and working: /usr/lib/ext/dell/srvadmin/bin/dataeng status

0 Kudos
stevenfoo
Contributor
Contributor

I have all the stuff running and up as below. However still I am not able to connected via OMSA 6.5.0 installed on a windows 2003 server.

~ # /etc/init.d/wsman status
openwsmand is running

~ #  /usr/lib/ext/dell/srvadmin/bin/dataeng status
dsm_sa_datamgrd (pid 3470 ) is running
dsm_sa_eventmgrd (pid 3511 ) is running
dsm_sa_snmpd (pid 3522 ) is running

~ # esxcli software vib list |grep Open
OpenManage            6.5-0000                            Dell    VMwareAccepted    2012-01-19

CIMoemProviderEnabled is set to 1.

I still getting the error "Logon Failed, Internal Error". Not sure what does the error means. There is no log file really mention what is actual issue here.

0 Kudos