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

Rebuilding the Kernel

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 17 highlights

5 Rebuilding the Kernel The HP Management Base scripts examine the running kernel version to assist in the selection of the appropriate binaries for the HP-supplied Open IPMI modules. If the kernel version is changed, the selection process will probably need to be executed again. This situation might not be apparent until a reboot of the new kernel when hpmgmtbase fails to initialize or when other programs that are dependent on the Open IPMI driver fail to start. A careful examination of boot time logs can help to isolate this behavior. This version change can happen because of a planned, supported kernel upgrade (such as, an errata from Red Hat) or user-initiated patching and rebuild. After the new kernel is installed, hpmgmtbase can be reconfigured to recognize the new version, as follows: 1. Shut down any other products and programs that rely on Open IPMI (such as, the HP Insight Manager SNMP agents). 2. Stop HP Management Base: # /etc/init.d/hpmgmtbase stop 3. Reconfigure HP Management Base: # /etc/init.d/hpmgmtbase reconfigure 4. Start HP Management Base: # /etc/init.d/hpmgmtbase start After a short time (up to 30 seconds) hpipmid should be running and hpbmc Summary should work (as outlined in the Chapter 4 (page 15). If this fails, then the changes made to the kernel may require a complete rebuild of the IPMI modules. Remember that the source modules shipped with your distribution might not actually work on your particular model of HP Integrity Server. HP does not expect the source to be synchronized until RHEL4.4 or SLES 10. To fulfill GPL requirements, HP Management Base includes the HP-modified source in /opt/hp/hpmgmtbase/OpenIPMI/src. These files are not patches but full source files for each of the source components. To incorporate them into your new kernel, the source files must be fully copied into your kernel source tree, as follows: 1. Copy the appropriate source files from /opt/hp/hpmgmtbase/src to ../drivers/ char/ipmi in your kernel source tree. • For any 2.6 kernel, use the source files under kernel 2.6. • For a 2.4 kernel and RHEL3, use the source files under kernel2.4/K22. Red Hat backported some of the 2.4.22 kernel source into their kernel, even though it identifies itself as 2.4.21 base. • For other 2.4.21 kernels, use the source files under kernel2.4/K21 2. Rebuild and install your modules in the fashion appropriate for your kernel major/minor release (2.4 is slightly different than 2.6). 3. Implement a mechanism that loads your newly compiled modules at boot time (an /etc/ init.d/rcX.d script) and runs before the HP Management Base scripts. 4. Enter one of the following: # modprobe ipmi_si (2.6 kernel) or # modprobe ipmi_si_drv or # ipmi_kcs_drv. 17

  • 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
5 Rebuilding the Kernel
The HP Management Base scripts examine the running kernel version to assist in the selection
of the appropriate binaries for the HP-supplied Open IPMI modules. If the kernel version is
changed, the selection process will probably need to be executed again. This situation might not
be apparent until a reboot of the new kernel when
hpmgmtbase
fails to initialize or when other
programs that are dependent on the Open IPMI driver fail to start. A careful examination of boot
time logs can help to isolate this behavior.
This version change can happen because of a planned, supported kernel upgrade (such as, an
errata from Red Hat) or user-initiated patching and rebuild. After the new kernel is installed,
hpmgmtbase
can be reconfigured to recognize the new version, as follows:
1.
Shut down any other products and programs that rely on Open IPMI (such as, the HP Insight
Manager SNMP agents).
2.
Stop HP Management Base:
#
/etc/init.d/hpmgmtbase stop
3.
Reconfigure HP Management Base:
#
/etc/init.d/hpmgmtbase reconfigure
4.
Start HP Management Base:
#
/etc/init.d/hpmgmtbase start
After a short time (up to 30 seconds)
hpipmid
should be running and
hpbmc Summary
should
work (as outlined in the
Chapter 4 (page 15)
. If this fails, then the changes made to the kernel
may require a complete rebuild of the IPMI modules. Remember that the source modules shipped
with your distribution might not actually work on your particular model of HP Integrity Server.
HP does not expect the source to be synchronized until RHEL4.4 or SLES 10.
To fulfill GPL requirements, HP Management Base includes the HP-modified source in
/opt/hp/hpmgmtbase/OpenIPMI/src
. These files are not patches but full source files for
each of the source components. To incorporate them into your new kernel, the source files must
be fully copied into your kernel source tree, as follows:
1.
Copy the appropriate source files from
/opt/hp/hpmgmtbase/src
to
../drivers/
char/ipmi
in your kernel source tree.
•
For any 2.6 kernel, use the source files under
kernel 2.6
.
•
For a 2.4 kernel and RHEL3, use the source files under
kernel2.4/K22
. Red Hat
backported some of the 2.4.22 kernel source into their kernel, even though it identifies
itself as 2.4.21 base.
•
For other 2.4.21 kernels, use the source files under
kernel2.4/K21
2.
Rebuild and install your modules in the fashion appropriate for your kernel major/minor
release (2.4 is slightly different than 2.6).
3.
Implement a mechanism that loads your newly compiled modules at boot time (an
/etc/
init.d/rcX.d
script) and runs before the HP Management Base scripts.
4.
Enter one of the following:
#
modprobe ipmi_si
(2.6 kernel)
or
#
modprobe ipmi_si_drv
or
#
ipmi_kcs_drv
.
17