ESX 3.5 & OMSA 5.4, can't get systems management device drivers to load

[cougar694u]

I scripted a full install of esx 3.5, which included the altiris agent, dell OpenIPMI drivers, OMSA, etc. The cl I use "srvadmin-openipmi.sh install-force dkms install --force -m openipmi" and "srvadmin-install.sh -b -w -r -s". After it builds, I can look at the logs and see the following from the ipmi & om install:

Executing action: Installing/upgrading OpenIPMI driver
- DKMS install: Installing/upgrading DKMS RPM version 2.0.13-1
warning: RPMS/supportRPMS/dkms-2.0.13-1.noarch.rpm: V3 DSA signature: NOKEY, key ID 23b66a9d
Preparing... ##################################################
dkms ##################################################
- OpenIPMI install: Installing/upgrading OpenIPMI driver RPM version 35.13
warning: RPMS/supportRPMS/openipmi-35.13.RHEL3-2dkms.noarch.rpm: V3 DSA signature: NOKEY, key ID 23b66a9d
Preparing... ##################################################
openipmi ##################################################
Loading kernel module source and prebuilt module binaries (if any)
Installing prebuilt kernel module binaries (if any)
Preparing kernel 2.4.21-57.ELvmnix for module build:
(This is not compiling a kernel, just preparing kernel symbols)
Storing current .config to be restored when complete
Running Generic preparation routine
make mrproper......
using /lib/modules/2.4.21-57.ELvmnix/build/configs/kernel-2.4.21-i686.config
make oldconfig....
make dep................
applying patch fixup_includes.patch...patching file ipmi.h
patching file ipmi_bt_sm.c
patching file ipmi_devintf.c
patching file ipmi_imb.c
patching file ipmi_kcs_intf.c
patching file ipmi_kcs_sm.c
patching file ipmi_msghandler.c
patching file ipmi_poweroff.c
patching file ipmi_si.c
patching file ipmi_smb_intf.c
patching file ipmi_smi.h
patching file ipmi_smic_sm.c
patching file ipmi_watchdog.c
Building module:
cleaning build area....
make KERNELRELEASE=2.4.21-57.ELvmnix -C /lib/modules/2.4.21-57.ELvmnix/build SUBDIRS=/var/lib/dkms/openipmi/35.13.RHEL3/build modules......
cleaning build area....
cleaning kernel tree (make mrproper)....
DKMS: build Completed.
Running module version sanity check.
Running the pre_install script:
Module version 35.13 is not newer than 39 already found in the kernel.
pre_install failed, aborting install.
You may override by specifying force.
Your DKMS tree now includes:
openipmi, 35.13.RHEL3, 2.4.21-37.ELhugemem, i686: built
openipmi, 35.13.RHEL3, 2.4.21-37.ELsmp, i686: built
openipmi, 35.13.RHEL3, 2.4.21-37.EL, i686: built
openipmi, 35.13.RHEL3, 2.4.21-37.EL, ia32e: built
openipmi, 35.13.RHEL3, 2.4.21-4.ELhugemem, i686: built
openipmi, 35.13.RHEL3, 2.4.21-4.ELsmp, i686: built
openipmi, 35.13.RHEL3, 2.4.21-4.EL, i686: built
openipmi, 35.13.RHEL3, 2.4.21-15.EL, ia32e: built
openipmi, 35.13.RHEL3, 2.4.21-57.ELvmnix, i686: built

Running module version sanity check.
Running the pre_install script:
Module version 35.13 is not newer than 39 already found in the kernel.
ipmi_si_drv.o:
- Original module
- Found /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/ipmi_si_drv.o
- Storing in /var/lib/dkms/openipmi/original_module/2.4.21-57.ELvmnix/i686/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/
ipmi_msghandler.o:
- Original module
- Found /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/ipmi_msghandler.o
- Storing in /var/lib/dkms/openipmi/original_module/2.4.21-57.ELvmnix/i686/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/
ipmi_devintf.o:
- Original module
- Found /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/ipmi_devintf.o
- Storing in /var/lib/dkms/openipmi/original_module/2.4.21-57.ELvmnix/i686/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/
ipmi_watchdog.o:
- Original module
- Found /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/ipmi_watchdog.o
- Storing in /var/lib/dkms/openipmi/original_module/2.4.21-57.ELvmnix/i686/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/
ipmi_poweroff.o:
- Original module
- Found /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/ipmi_poweroff.o
- Storing in /var/lib/dkms/openipmi/original_module/2.4.21-57.ELvmnix/i686/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/char/ipmi/
Running post_install:
[60G[ [0;32mOK
---

WARNING: the IPMI drivers may be in use by an application,
and could not be unloaded. The IPMI driver has been updated
on disk, but the older driver is still running in memory.
Please stop all applications which are using the IPMI
drivers before continuing.
The following applications may be using the IPMI drivers:
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
cimprovag 2431 root 6u CHR 246,0 73188 /dev/ipmi0
After stopping these applications, you can remove and reload the IPMI drivers
using this command:
/etc/init.d/ipmi restart
Alternately, you may reboot your system.
depmod....
DKMS: install Completed.
[H [JInstalling the selected packages.
warning: instsvc-drivers-5.4.0-231.i386.rpm: V3 DSA signature: NOKEY, key ID 23b66a9d
Preparing... ##################################################
srvadmin-omilcore ##################################################
To start all installed services without a reboot,
enter the following command: srvadmin-services.sh start
srvadmin-syscheck ##################################################
srvadmin-deng ##################################################
srvadmin-omauth ##################################################
srvadmin-omacore ##################################################
srvadmin-jre ##################################################
srvadmin-ipmi ##################################################
srvadmin-hapi ##################################################
srvadmin-isvc ##################################################
srvadmin-rac5-components ##################################################
instsvc-drivers ##################################################
srvadmin-cm ##################################################
srvadmin-iws ##################################################
srvadmin-omhip ##################################################
srvadmin-racadm5 ##################################################
srvadmin-racdrsc5 ##################################################
srvadmin-storage ##################################################

You can see the WARNING from IPMI, asking me to stop the app, then restart ipmi; OR reboot the system.

Well, rebooted the system and when logging into the web access for OMSA, you can clearly see it didn't load right. I cannot expand anything under storage, it doesn't even list the model of the server in the top right (2950). I ran a srvadmin-openipmi.sh and it says the OpenIPMI driver module is installed and recommends I do nothing. I ran srvadmin-install.sh and all components have an X indicating they're installed and says there's nothing to add.

I tried the srvadmin-services.sh start and it shows this:

Starting Systems Management Device Drivers:
Building dell_rbu using DKS:
Check /var/log/dell_rbu.dks.log for build error.
Starting ipmi driver:
Starting Systems Management Device Drivers:
Building dell_rbu using DKS:
Check /var/log/dell_rbu.dks.log for build error.
Starting ipmi driver:
Starting DSM SA Shared Services: OK
Starting DSM SA Connection Service:

this is the log file:

Building dell_rbu...
cp: cannot stat `/opt/dell/srvadmin/hapi/drivers/x86/dks/dell_rbu/.c': No such file or directory
cp: cannot stat `/opt/dell/srvadmin/hapi/drivers/x86/dks/dell_rbu/.h': No such file or directory
cp: cannot stat `/opt/dell/srvadmin/hapi/drivers/x86/dks/dell_rbu/kernel24/*.h': No such file or directory
KDIR=`echo 2.4.21-57.ELvmnix`; \
KVER=`echo 2.4.21-57.ELvmnix | cut -f 1 -d '-' -`; \
BVER=`echo 2.4.21-57.ELvmnix | cut -f 2 -d '-' -`; \
mkdir -p $/modules; \
ln -sf ../$-generic/Makefile $/Makefile; \
ln -sf ../$-generic/Rules.make $/Rules.make; \
ln -sf ../$-generic/arch $/arch; \
ln -sf ../$-generic/scripts $/scripts; \
for i in esm; do \
ln -s ../$i $/$i ; \
done; \
if ; then \
cp $/kernel-$-i686.config $/.config; \
fi; \
make -C $ SUBDIRS="esm" COMPILE_VERSION="-DSYSTEM_TYPE_LINUX" EXTRAVERSION=-$ INSTALL_MOD_PATH=`pwd`/$ modules; \
make -C $ SUBDIRS="esm" COMPILE_VERSION="-DSYSTEM_TYPE_LINUX" EXTRAVERSION=-$ INSTALL_MOD_PATH=`pwd`/$ modules_install; \
for i in esm; do \
rm $/$i ; \
done; \
rm $/modules/*; \
rmdir $/modules; \
make[1]: Entering directory `/opt/dell/srvadmin/hapi/drivers/x86/dks/build/2.4.21-57.ELvmnix'
make -C esm CFLAGS="-Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -DSYSTEM_TYPE_LINUX -fno-strict-aliasing -pipe -freorder-blocks -mpreferred-stack-boundary=2 -march=pentium3 -DMODULE -include /opt/dell/srvadmin/hapi/drivers/x86/dks/build/2.4.21-57.ELvmnix/include/linux/version.h -DMODVERSIONS -include /opt/dell/srvadmin/hapi/drivers/x86/dks/build/2.4.21-57.ELvmnix/include/linux/modversions.h -I../common/include -I../common/include/linux -I../esm/common/include -I../esm" MAKING_MODULES=1 modules
make[2]: Entering directory `/opt/dell/srvadmin/hapi/drivers/x86/dks/build/esm'
make[2]: *** No rule to make target `/opt/dell/srvadmin/hapi/drivers/x86/dks/build/2.4.21-57.ELvmnix/include/linux/modversions.h', needed by `dell_rbu.o'. Stop.
make[2]: Leaving directory `/opt/dell/srvadmin/hapi/drivers/x86/dks/build/esm'
make[1]: *** Error 2
make[1]: Leaving directory `/opt/dell/srvadmin/hapi/drivers/x86/dks/build/2.4.21-57.ELvmnix'
make[1]: Entering directory `/opt/dell/srvadmin/hapi/drivers/x86/dks/build/2.4.21-57.ELvmnix'
make[1]: Leaving directory `/opt/dell/srvadmin/hapi/drivers/x86/dks/build/2.4.21-57.ELvmnix'
rm: cannot lstat `2.4.21-57.ELvmnix/modules/*': No such file or directory
make: Nothing to be done for `dkslink'.
dell_rbu binary not found

Anyone have any ideas how to fix this? It seems clear some .h & .c file are missing, but why, and how do I fix it for future builds?

[cougar694u]

Bump. Anyone?

[Texiwill]

Hello,

I would speak directly with Dell on this one.

There are several issues, one is that unless the driver is specifically for ESX installing it may not work. As you have discovered. Also, while they may load they may not get the data they expect. Hence why they need to be specific to ESX to work.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[cougar694u]

Originally, I thought I had the wrong versions, or they weren't supported. I downloaded the document from Dell on installing OMSA 5.x on ESX 3.x and followed those procedures, but they had the same results. I think I rebuilt this server 4 times trying different things.

I'm on vacation all this week, but it's bugging the crap outta me trying to figure it out. I guess I'll talk to Dell next week if I don't get anything.

[Schorschi · Accepted solution]

Install the additional IPMI drivers from VMware, then install OMSA 5.4, via srvadmin-install.sh -b -w -r -s. We do this on 2950s, 6850s, and R900s, never have had an issue.

[cougar694u]

*EDIT*

Okay, I did more testing. I did a base install of ESX 3.5 u2 (post 8/12/2008 :smileygrin: ) and ran "srvadmin-openipmi.sh status" BEFORE running the install script off the OMSA 5.4 disk and it said IPMI was already installed and needs nothing. As it appears, the version of IPMI on the dell 5.4 disk is older than what's already on ESX 3.5 u2.

I commented out the line, ran my post install script and everything seems to be working.

[Schorschi]

Great! Another ESX 3.5 Update 2 quirk.

Schor-

[Darryl_R]

what line did you comment out to get it working?

I have 20 new servers and getting this same problem on 8 of them.

[plsntn_rules1]

Cougar;

Any chance you can post your script for soem of us newbies?

I am trying to do the exact same thing you are on a R900 and have no idea how to do so.

Will be eternally grateful.

thanks

[acspeed]

Just do the srvadmin-install.sh -b -w -s don't do the srvadmin-openipmi.sh install, that's where the problem is at. You don't need to do that part.