Support Notes for Red Hat Enterprise Linux AS 4.7 for HP Integrity Servers
3. Enter the reset command.
— HP Smart Setup
The HP Smart Setup utility can be used to automatically configure your server's ACPI
settings. For specific instructions, see the HP Integrity Essentials Foundation Pack for Linux
User's Guide:
http://www.docs.hp.com/en/5992-3193/index.html
• Powering off nPartitions with shutdown or poweroff commands
The default behavior on rx7620, rx7640, rx8620, or rx8640 servers is for an nPartition to be
made inactive (all cells are in a boot-is-blocked state) when shutdown -h or poweroff is
issued from the RHEL command line. This behavior is established with the acpiconfig
disable powerdown setting, which is the default setting for the single-pci-domain
ACPI configuration.
To change the default behavior and shutdown nPartitions automatically, run the acpiconfig
enable softpowerdown command from the EFI shell, and then reset the nPartition to
force the new ACPI configuration take effect.
When softpowerdown is enabled on an any of these servers, if only one nPartition is defined
in the server, then halting the operating system powers off the server cabinet including all
cells and the I/O chassis. On an rx7620 or rx8620 server with multiple nPartitions, halting
the operating system from an nPartition with softpowerdown enabled causes only the
resources on the local nPartition to be powered off. You can run the acpiconfig command
with no arguments to verify the current setting and the softpowerdown setting; the
softpowerdown information is displayed only when different from the default behavior.
To power on hardware that has been powered off, use the PE command at the MP command
menu. To make an inactive nPartition active, use the MP BO command to boot the nPartition
past the boot-is-blocked state.
NOTE: On HP Integrity Superdome servers, an nPartition is always made inactive when
halted from the operating system (for example, after shutdown -h is executed), and this
behavior cannot be changed.
• System panics resulting from Fibre Channel storage arrays directly connected to the
system
System panics may occur on HP Integrity servers running RHEL when Fibre Channel storage
arrays are directly connected to the system.
If you plan to connect Fibre Channel storage arrays to HP Integrity servers running RHEL,
you must connect through a Fibre Channel switch. For the BL860c Server Blade, you must
use either the Fibre Channel switch module (AE370A, AE371A, or AE372A) or an external
Fibre Channel switch.
• Machine check aborts (MCA) occurring on cell-based servers
HP mid-range and high-end (cellular) systems can be configured with varying amounts of
cell local memory (logical memory ranges mapped to contiguous physical memory on the
cell) or interleaved memory (logical memory ranges distributed across physical memory in
all cells).
If a system does not allocate enough cell local memory (CLM) to any given cell, an MCA
could occur. Should this happen, try one of the following to resolve the issue:
— Change the memory configuration so that the memory in each cell is equal.
— Change the CLM setting to increase the size of contiguous memory.
If the system was working previously, issue the pdt command at the EFI prompt. If there
are PDT entries, consider replacing the bad memory.
Known Issues 15