nPartition Administrator's Guide
You can specify time in the format hh:mm, in which hh is the hour (one or two digits)
and mm is the minute of the hour (two digits); or in the format +m, in which m is the
number of minutes delay until shutdown; or specify now to immediately shut down.
— shutdown -h time — Shuts down Linux and performs a shutdown for reconfig of the
nPartition. All cells are reset and nPartition reconfiguration occurs as needed. All cells
then remain at a "wait at BIB" state and the nPartition is inactive.
The required time argument specifies when the Linux shutdown is to occur.
On HP rx7620, rx7640, rx8620, and rx8640 servers with an ACPI configuration setting
of single-pci-domain, a "wait at BIB" state is the default OS shutdown for reconfig
behavior, but the acpiconfig enable softpowerdown EFI Shell command can be
used to instead cause all nPartition hardware to power off.
For details see Chapter 5 (page 87).
Complex Profile
The configurable aspects of a server complex are represented in a set of data called the "Complex
Profile", which determines how hardware is assigned to and used by nPartitions within a server.
The Complex Profile consists of three parts, or groups of data, which are described in detail in
Table 1-5 (page 40):
• “Stable Complex Configuration Data” (page 40) — This group contains complex-wide
settings, including the complex name, serial number, the nPartition assignment for each
cell, and other details that apply to the entire server complex.
The Complex Profile contains one Stable Complex Configuration Data entry.
• “Dynamic Complex Configuration Data” (page 40) — Architecturally reserved data.
• “Partition Configuration Data” (page 40) — This group contains individual nPartition
settings, including the nPartition name, core cell choices, and other details that are specific
to an nPartition.
The Complex Profile contains a Partition Configuration Data entry for each possible
nPartition. (A server complex may have a maximum of sixteen nPartitions, globally numbered
from 0-15.)
The master copy of all parts of the Complex Profile resides on the service processor (MP or GSP)
for the complex. Each cell in the complex also has a copy of the Stable Complex Configuration
Data and a copy of the Partition Configuration Data for the nPartition to which it is assigned.
The service processor (MP or GSP) in the server manages all Complex Profile data and keeps all
copies of the data coherent using a locking mechanism, as described in the next sections.
Changing the Server Complex Profile
To modify the Complex Profile and thus change the server complex configuration, you use an
administration tool such as Partition Manager or one of the nPartition commands. See
“Administration Tools for nPartitions” (page 18) for details. You cannot directly edit the Complex
Profile data for a server.
The service processor maintains a set of locks that are used to ensure that only one set of changes
to the Complex Profile occurs at a time.
When you configure nPartitions, the administration tools you use revise the Complex Profile for
the server in coordination with the service processor. The tools acquire and release locks as
needed when modifying Complex Profile entries. You do not directly manage Complex Profile
locks under normal circumstances, but you can force an entry to be unlocked if required.
Complex Profile 37