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

Troubleshooting, Proper Function

Page 15 highlights

4 Troubleshooting In the discussion that follows, all programs (and drivers) attempt to communicate with the local system BMC. No RMCP is used, no -d argument is used, and the shell environment variable EZBMC_DEVICE is not set. Proper Function In a properly functioning system the following should be observed: • No errors occur during installation of hpmgmtbase. • Three IPMI kernel modules are visible from lsmod. • An IPMI character device major number is visible from cat /proc/devices • The character device files /dev/ipmi0 and /dev/ipmidev/0 exist with the major number seen in the previous item. • The hpipmid and hprasd daemons are running. • When run as root, hpbmc Summary runs to completion without error. • Any additional HP-supported programs (such as SNMP agents) run without any BMC or IPMI errors. The HP Management Base installation performs two major steps to determine the appropriate kernel modules. HP Management Base ships with a set of binary modules compiled for the known releases from the major vendors. The installation script examines the run-time environment and selects the correct module set. However, if there is already a set of IPMI modules loaded from some other source (by other user actions), then HP Management Base assumes these are functioning properly, is properly reloaded at reboot, and takes no further action (by trying to use precompiled modules). When HP Management Base is started using the command, /etc/init.d/hpmgmtbase start, the following actions are taken: 1. The module set designated by the installation process is loaded. 2. The major number allocated to the driver is used in the creation of the following device files: /dev/ipmi0 /dev/ipmidev/0 These are well-known names in the Open IPMI community and are the defaults for hpbmc as well as open source programs such as ipmitool. 3. The BMC SDRR is read and cached in a file. This takes over 20 seconds on certain HP Integrity servers, but it speeds up all subsequent operations. 4. The hpipmid and hprasd daemons are started. The hpmgmtbase script is linked into the appropriate /etc/rcX.d directories to ensure early start-up. Proper Function 15

  • 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

4 Troubleshooting
In the discussion that follows, all programs (and drivers) attempt to communicate with the local
system BMC. No RMCP is used, no
-d
argument is used, and the shell environment variable
EZBMC_DEVICE
is not set.
Proper Function
In a properly functioning system the following should be observed:
No errors occur during installation of
hpmgmtbase
.
Three IPMI kernel modules are visible from
lsmod
.
An IPMI character device major number is visible from
cat /proc/devices
The character device files
/dev/ipmi0
and
/dev/ipmidev/0
exist with the major number
seen in the previous item.
The
hpipmid
and
hprasd
daemons are running.
When run as
root
,
hpbmc Summary
runs to completion without error.
Any additional HP-supported programs (such as SNMP agents) run without any BMC or
IPMI errors.
The HP Management Base installation performs two major steps to determine the appropriate
kernel modules. HP Management Base ships with a set of binary modules compiled for the
known releases from the major vendors. The installation script examines the run-time environment
and selects the correct module set.
However, if there is already a set of IPMI modules loaded from some other source (by other user
actions), then HP Management Base assumes these are functioning properly, is properly reloaded
at reboot, and takes no further action (by trying to use precompiled modules).
When HP Management Base is started using the command,
/etc/init.d/hpmgmtbase
start
, the following actions are taken:
1.
The module set designated by the installation process is loaded.
2.
The major number allocated to the driver is used in the creation of the following device files:
/dev/ipmi0
/dev/ipmidev/0
These are well-known names in the Open IPMI community and are the defaults for
hpbmc
as well as open source programs such as
ipmitool
.
3.
The BMC SDRR is read and cached in a file. This takes over 20 seconds on certain HP Integrity
servers, but it speeds up all subsequent operations.
4.
The
hpipmid
and
hprasd
daemons are started.
The
hpmgmtbase
script is linked into the appropriate
/etc/rcX.d
directories to ensure
early start-up.
Proper Function
15