HP Integrity rx1620 HP Management Base Installation and User's Guide for Linux - Page 16

Improper Function, etc/init.d/hpmgmtbase stop

Get HP Integrity rx1620 PDF manuals and user guides View all HP Integrity rx1620 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 16 highlights

Improper Function Almost all problems with HP Management Base are related to the version and loading of the three kernel modules that make up the Open IPMI driver. Specifically, it is the System Interface (SI) module that causes the problems. Kernel 2.4 (old) 2.4 (recent) 2.6 Distributions RHEL 2.1, SLES 8 RHEL 3 RHEL 4, RHEL 5, SLES 9, SLES 10, SLES 11 SI Module Name ipmi_kcs_drv.o ipmi_si_drv.o ipmi_si.ko The other two modules are always named impi_msghandler and ipmi_devintf. The SI module shipped with the distributions has been out of synchronization with HP Integrity server hardware for most of its life. Sometimes the SI module does not load at all; in other cases it loads but functions improperly. Sometimes other user or system actions cause the distribution's drivers to be loaded before HP Management Base is installed, which is incorrect. Use the following steps to remedy the situation: 1. Stop any HP IPMI programs that might be running: # /etc/init.d/hpima stop # /etc/init.d/hpwebm stop # /etc/init.d/hpmgmtbase stop 2. Erase the current knowledge of appropriate IPMI drivers: # /etc/init.d/hpmgmtbase unconfigure 3. Show any IPMI driver modules that may have been loaded before HP Management Base was originally installed: # lsmod | grep ipmi 4. For each of the modules listed above, rmmod ipmi_msghandler must be last. This removes any offending IPMI modules. 5. Probe and select appropriate IPMI modules: /etc/init.d/hpmgmtbase configure If messages indicating you must rebuild your IPMI driver are displayed, see the corresponding section of this document. 6. To cache the SDRR and start hpipmid: # /etc/init.d/hpmgmtbase start Wait 30 seconds, and then verify that hpipmid is running. If that works, then you must disable whatever mechanism was loading the offending IPMI modules. 16 Troubleshooting

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
Improper Function
Almost all problems with HP Management Base are related to the version and loading of the
three kernel modules that make up the Open IPMI driver. Specifically, it is the System Interface
(SI) module that causes the problems.
SI Module Name
Distributions
Kernel
ipmi_kcs_drv.o
RHEL 2.1, SLES 8
2.4 (old)
ipmi_si_drv.o
RHEL 3
2.4 (recent)
ipmi_si.ko
RHEL 4, RHEL 5, SLES 9, SLES 10,
SLES 11
2.6
The other two modules are always named
impi_msghandler
and
ipmi_devintf
.
The SI module shipped with the distributions has been out of synchronization with HP Integrity
server hardware for most of its life. Sometimes the SI module does not load at all; in other cases
it loads but functions improperly.
Sometimes other user or system actions cause the distribution's drivers to be loaded before HP
Management Base is installed, which is incorrect. Use the following steps to remedy the situation:
1.
Stop any HP IPMI programs that might be running:
#
/etc/init.d/hpima stop
#
/etc/init.d/hpwebm stop
#
/etc/init.d/hpmgmtbase stop
2.
Erase the current knowledge of appropriate IPMI drivers:
#
/etc/init.d/hpmgmtbase unconfigure
3.
Show any IPMI driver modules that may have been loaded before HP Management Base
was originally installed:
#
lsmod | grep ipmi
4.
For each of the modules listed above,
rmmod ipmi_msghandler
must be last. This removes
any offending IPMI modules.
5.
Probe and select appropriate IPMI modules:
/etc/init.d/hpmgmtbase configure
If messages indicating you must rebuild your IPMI driver are displayed, see the
corresponding section of this document.
6.
To cache the SDRR and start
hpipmid
:
#
/etc/init.d/hpmgmtbase start
Wait 30 seconds, and then verify that
hpipmid
is running. If that works, then you must disable
whatever mechanism was loading the offending IPMI modules.
16
Troubleshooting