Dell OMSA 6.5 VIB Installation on ESXi 5?

[DenshiKenshi]

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.

[AndreTheGiant]

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

There isn't a daemon on this port.

You need another OMSA that act as a proxy: http://vinfrastructure.it/2011/12/installare-dell-omsa-web-server-in-una-vm/

PS: seems that there are some problems if the "proxy" a Windows Server 2003 32 bit. I've tested on a 2008 R2 and it works without issues

[EricChris]

Yes, I have the Dell Server Administrator Web Server running on a 32bit Windows 2003 server. It seems others are having the same problem. Login Failed Internal Error.

[SCMHenry]

I've encountered the same issue trying to launch the OMSA 6.5 web browser from XP ProfessionalWorkstation.

Finally, I installed OMSA 6.5 on a W2K8 Server, and was successful !

Interestingly, in my experience, OMSA 6.5 on XP Professional does not have difficulties communicating with ESXi 4.1 hosts.... only ESXi 5 hosts are problematic.

[stevenfoo]

For those running on windows 2003. Please try the below. It works for me. This solution is from Dell Support.

1.       Edit the file  /etc/vmware/hostd/config.xml

2.       Locate the  <vmacore>...</vmacore> tags in the file

3.       Within the vmacore  element, locate the <ssl>...</ssl> tags

4.       Within the ssl  element, add the following  element:
       <cipherList>HIGH:RC4-SHA:RC4-MD5</cipherList>

5.       Save the file and  restart hostd (/sbin/services.sh restart)

[gbannoff]

Your solution works great!  Thank you.

I'm experienced in Windows, but not in Unix, so editing the file was a bit tricky for me.  For anyone following this thread, here's how to do it:

- connect using SSH (I used the SSH client built into Trilead VMX, but presumably there are more direct ways of doing this)

- use the VI editor that is built into ESXi  - VI instruction manual here: http://www.washington.edu/computing/unix/vi.html

  - make a backup copy first:

    cp  /etc/vmware/hostd/config.xml  /etc/vmware/hostd/config.bak

  - start the editor

    vi /etc/vmware/hostd/config.xml

  - scroll down to the <vmacore> section, then to the <ssl> section within that

  - added a blank line (in VI command mode, type a lower-case "o")

  - added your info (in VI command mode, type "i", then entered the text of the line)

  - <esc> to get back to command mode

  - save the file and exit (in VI command mode, type ":w" [return], then ":q" [return])

- still in SSH, restarted the Management Agents using your script

and it all works.

One might expect that Dell could provide all these steps to make this a bit more straightforward.  Everyone who runs ESXi on a Dell server wants to know the status of the machine components.

[paule1234]

Thanks for this.  I finally got my Dell PowerEdge 2950 III with ESXi 5.0 U1 working with OMSA.  I had to install the latest OMSA 7.1 "OM-SrvAdmin-Dell-Web-WIN-7.1.0-5304_A00.exe" on my Windows 2003 management server to be able to connect to the Dell version 7.1 VIB "OM-SrvAdmin-Dell-Web-7.1.0-5304.VIB-ESX50i_A00".  The version 7.0 OMSA would not connect. The OMSA GUI is painfully slow to populate all the server assets, but at least it works, I can see and manage the PERC 6/i which was my main goal...

Been working on this on and off for two weeks, what an ordeal.  Dell's info is all over the place with dead links, old links, a dozen different blog instructions.  When I discovered that OpenManage Essentials REQUIRES Server 2008 w/IIS 7 I just about lost it.  Unbelievable.

Oh, and be careful adding the <cipherList> tag -- I would suggest manually typing it and not copy paste it -- the ESXi management network on the host would not start -- I saw something about malformed XML in the vmware log -- probably an invisible tab character or something weird -- so I went back in and deleted the cipherList line and manually typed it, rebooted and all was well.

[vmroyale]

Just in case others find this discussion, I have a blog entry that may be helpful with this process:

http://communities.vmware.com/people/vmroyale/blog/2012/07/26/how-to-use-dell-dset-with-esxi