HP Insight Management Agents 9.10 Managing ProLiant Servers with Linux HOW TO Whitepaper

Table 9 ProLiant BL Rack Upgrade Utility parameters
DescriptionParameter
This optional parameter considers only enclosures with address1, address2, and so on.
The list of addresses must be composed of 16-bit quantities separated by commas. The
-a address1,address2,…
addresses can be obtained by running q (see below). No white spaces are allowed
in between the commas and the addresses. If a no comma-separated list is given, all
possible addresses in the rack are considered.
This optional parameter considers only enclosures with positions chassis1, chassis2,
and so on that is counted from the bottom. The list must be composed of small numbers
-c chassis, chassis2,…
that are legal positions in the rack. No white spaces are allowed in between the commas
and the numbers. A list such as 1, 2, 5 signifies the bottom, second-to-bottom, and
fifth-to-bottom enclosures.
This parameter disregards the local enclosure (for example, the enclosure containing
the server from which you flash) in the flashing. This parameter is given in conjunction
with –a or –c.
-e
This parameter disregards anything but the local enclosure (for example, the enclosure
containing the server from which you flash). This parameter should not be given with
–a or –c.
-l
This parameter queries the chassis positions, their serial numbers and their firmware
status, and returns their addresses.
-q
The manpage for this utility may be viewed by entering man cpqblru at the command prompt.
Note the following while upgrading ProLiant BL p-Class enclosure management controllers:
During a flash upgrade, only the primary firmware image is reflashed. All controllers have a
backup image. The backup image is used for recovery purposes when a flash upgrade is
interrupted or otherwise fails. Restoring the backup firmware image is rarely needed and is
covered in the Integrated Lights-Out User Guide located at http://h18013.www1.hp.com/
manage/ilo-description.html
When updating enclosure management controllers in more than one enclosure, the new image
must be transmitted twice (first to the local enclosure and second to the remote enclosures
using broadcast mode). The update process can take 10 minutes or more. The update process
notifies the user if the update succeeded or failed.
The reflash operation consumes all bandwidth of the bus connecting the management
controllers. Consequently, other software components, such as the ProLiant Rack Agent might
not report up-to-date information during the flash upgrade.
HP OpenIPMI Driver (hp-OpenIPMI)
The hp-OpenIPMI device driver is a derivative work of the IPMI device driver that ships with the
standard Linux kernel. This driver has been enhanced to include bug fixes in addition to supporting
a PCI Base Management Controller (BMC), such as the one provided by the HP Integrated Lights-Out
2 (iLO 2) management controller. The file /opt/hp/hp-OpenIPMI/IPMI.txt is also a derivative
of the Documentation/IPMI.txt file included with the standard Linux kernel. This file has been
enhanced to document the additional parameters that can be passed to the ipmi_si.ko driver. The
hp-OpenIPMI device driver enhancements are expected to be incorporated into the OpenIPMI
device driver (http://openipmi.sourceforge.net/) and subsequently, the standard Linux kernel. This
driver can be used with other applications in addition to the HP Advanced System Management
XL (hpasmxl) application.
HP ProLiant Channel Interface Device Driver for iLO/iLO 2/iLO 3/iLO
4(hp-ilo)
The HP ProLiant Channel Interface Device Driver for iLO/iLO 2/iLO 3/iLO 4 (hp-ilo) enables
iLO data collection and integration with the ProLiant Management Agents and the rack infrastructure
HP OpenIPMI Driver (hp-OpenIPMI) 15