parcreate(1M)parcreate(1M)NAMEparcreate - create a new partition
SYNOPSIS
[celltype]use_on_next_boot]failure_usage][
[celltype]use_on_next_boot]failure_usage] path] path] path]
cell] cell]... flag] s_lock] IPaddress] clm_value] Partition‐
Name]
username
DESCRIPTION
The command creates a new partition. By default the new partition is
created on the local complex. Either the or the option can be speci‐
fied to create a partition on the specified target (local or remote)
complex. The command takes the specified cells (and any attached I/O
chassis) and assigns them to the new partition. At least one of the
cells specified must be attached to an I/O chassis that contains core
I/O. The command finds an available partition ID and assigns it to the
new partition. It displays the partition ID of the newly created par‐
tition on stdout.
By the nature of its operation, this command modifies the configuration
of its target complex. Operation can be affected by the state of the
target complex's nPartition Configuration Privilege. If the nPartition
Configuration Privilege is unrestricted (the default), or the complex
is accessed using the option, creation of new partitions is allowed.
Otherwise the command fails. The option is unaffected by the state of
the nPartition Configuration Privilege. Note: The state of the nPar‐
tition Configuration Privilege can only be changed at the service pro‐
cessor's Command menu.
Superuser permission is required to run this command on the local par‐
tition. If the option is used to access a remote partition or complex,
superuser permission is not required on the local system, and the local
system need not exist on an nPartition. If the option is specified,
username on the remote host must have superuser permission or the com‐
mand will fail.
Please refer to the for a description of the partition management terms
used in this man page.
Options and Arguments
recognizes the following command line options and arguments:
Specifies that the new partition be booted. The default is not to
boot. Note: On Itanium-based platforms this option has no effect,
because boot paths cannot be set on the new partition. Therefore, the
partition cannot boot automatically. You must manually boot up the
partition from the SP console interface.
Specifies the primary boot path.
path specifies a physical hardware path. Note: On Itanium-based
platforms, boot paths cannot be set or modified on a non-local
partition. You must use the SP console interface to set any
boot path of the newly created partition.
Identifies a cell to be assigned to the partition. To assign multiple
cells to
the partition, multiple options should be used.
cell specifies the cell ID. It can be specified either in the
local (cabinet#/slot#) or global (cell#) format. For example,
the cell located in cabinet 0, slot 1 is identified in the local
format as 0/1 or in the global format as 1.
celltype specifies the type of the cell. The valid celltype
values for a cell are:
This is the default if
celltype is not specified. A base cell in a parti‐
tion participates in interleaved memory.
A floating cell in a partition does not participate in inter‐
leaved memory
(all of the cell's memory is used as CLM). A float‐
ing cell cannot be a partition's core cell.
use_on_next_boot specifies whether the cell will participate in
a reboot. The valid values for use_on_next_boot are:
participate in reboot. This is the default. However if the
slot is missing
or the cell does not exist or the cell is powered off then
it defaults to
do not participate in reboot.
At least one of the cells specified using the option must con‐
tain core I/O with the use_on_next_boot flag set to
failure_usage field is used by system firmware when a partition
is booted. If a CPU selftest failure or a DIMM deallocation
occurs during the power-on self-test process, then this flag is
used by the system firmware to determine whether or not and how
the cell should be integrated into the partition at boot time.
The valid failure_usage values for a cell are:
reactivate with memory interleave. Specifies to integrate the
cell as it
would normally be integrated. This is the default
for base cells.
this is the default value for floating cells.
If the user specifies ri for a floating cell, the
command displays an error and exits.
deconfigure.
no interleave.
clm_value specifies the amount of the memory that will be con‐
figured as local (non-interleaved) memory for the cell. The
clm_value specified using the option takes precedence over the
clm_value specified using the option. The command will issue a
warning if the specified clm_value exceeds the total memory of
the cell.
Note: On PA platforms, the amount of memory allocated for CLM
may not match the amount of CLM requested due to some memory
being reserved exclusively by the operating system.
If no clm_value is specified, maximum interleaved memory (no
CLM) is assumed for cells. The command will issue a warning if
100% CLM is specified for all the cells in the partition. The
clm_value can be expressed in two forms:
· As a percentage (ratio). The percent number can be any num‐
ber in the range 0 - 100 with a suffix of "%". This number
will be rounded up to 12.5%, 25%, 37.5%, 50%, 62.5%, 75%, 87%
or 100%. If the cell contains less than 4 GB memory, then
the percentage will be rounded to 25%, 50%, 75% or 100%. The
specified percentage is applied each time the partition
boots, thus resulting in a different value if the working
memory in the cell is different. For example, a cell in a
partition has 8 GB memory and the user specifies 50% CLM.
When the partition boots, 4 GB of that cell's memory will be
used as CLM. Later the user shuts down the partition, adds
another 8 GB memory to that cell. When the partition is
booted again, the cell now has 16 GB of memory, so 8 GB (50%)
is allocated as CLM.
· As an absolute number (default). This can also be optionally
suffixed by "GB". The clm_value is interpreted as an abso‐
lute number of gigabytes of memory. Numbers other than inte‐
gers and halves are rounded up to the nearest 0.5 GB. For
example, 2.5 GB will not be rounded up. However 2.3 GB will
be rounded up to 2.5 GB. For example, a cell in a partition
has 8 GB memory and the user specifies 4 GB CLM. When the
partition boots 4 GB of that cell's memory will be used as
CLM. Later the user shuts down the partition, adds another 8
GB memory to that cell. When the partition is booted again,
the cell now has 16 GB of memory, but the CLM is still 4 GB.
Allows access to the complex specified by the
option. The accessed complex is then considered the target com‐
plex. Access is through the service processor's LAN port.
The option is required if this option is used.
If this option is specified, the command prompts for the pass‐
word.
If an error is reported when you attempt to connect using this
option, check to see that IPMI LAN access has not been disabled
on the remote service processor. Access to the complex through
IPMI over LAN can be enabled or disabled by logging on to the
service processor and using the command from the Command Menu.
The options are mutually exclusive.
This option should only be used in combination with either the
option. IPaddress|hostname specifies the IP address or hostname
of the target partition or complex
Specifies the IP address that should be used by management tools such
as
to address this partition. This value must be consistent with
the IP address that is assigned to the partition once HP-UX is
installed and networking is configured.
Specifies a lock key for the Stable Complex Configuration Data provided
by
Note: The option is intended for use by system management tools
which invoke the command programmatically. Command line users
should avoid this option.
Specifies the amount of the memory that will be used as local (non-
interleave)
memory per cell. The clm_value specified using the option takes
precedence over the clm_value specified using the option.
Please refer to the explanation of the option for details of the
clm_value formats.
Specifies the name of the new partition. The characters which can
appear in
a valid partition name are (dash), (underscore), " " (space) and
(period). If the partition name includes space then the name
should be enclosed within double quotes. The partition name can
have a maximum of 64 characters. The partition name should not
start with a dash
Specifies the core cell choices. A core cell choice is a configured
cell
which has attached core IO. If the core cell of a partition is
deleted then the firmware will select the first core cell choice
as the next core cell. One to four core cell choices can be
specified. The first cell specified is the first core cell
choice, the second cell specified is the second core cell
choice, the third cell specified is the third core cell choice
and the fourth cell specified is the fourth core cell choice.
A cell can be specified either in the local (cabinet#/slot#) or
global (cell#) format. For example, the cell located in cabinet
0, slot 1 is identified in the local format as 0/1 or in the
global format as 1.
Specifies the secondary boot path.
path specifies a physical hardware path. Note: On Itanium-based
platforms, boot paths cannot be set or modified on a non-local
partition. You must use the SP console interface to set any
boot path of the newly created partition.
Specifies whether Hyper-Threading should be enabled or not (only if
cell support this feature). By default Hyper-Threading is dis‐
abled. The valid values for flag are:
enables Hyper-Threading, which allows multiple threads to run
concurrently
on each CPU.
disables Hyper-Threading, this is the default value.
Specifies the alternate boot path.
path specifies a physical hardware path. Note: On Itanium-based
platforms, boot paths cannot be set or modified on a non-local
partition. You must use the SP console interface to set any
boot path of the newly created partition.
Specifies the required authorization to access a partition other than
the local system (but can also be used as a loopback access to
the local partition).
The option is required if this option is used.
If this option is specified, the command prompts for the pass‐
word.
username specifies a configured user name on the target parti‐
tion.
Note: This command is a Web-Based Enterprise Management (WBEM)
Client Application. The option accesses the target partition
using a Secure Sockets Layer (SSL) connection. If errors are
reported, check that the conditions described in the section are
satisfied.
Mapping of Global Cell Numbers to Local Cell Numbers
The cabinets in a complex are numbered starting from 0. The cell slots
in each cabinet are also numbered starting from 0. Each cabinet can
have a maximum of 8 cells. For example, the cells located in cabinet 0
will have the following cell numbers in global format: 0, 1, 2, 3, 4,
5, 6, 7. The cell numbers in corresponding local format will be 0/0,
0/1, 0/2, 0/3, 0/4, 0/5, 0/6, 0/7.
Similarly the cells located in cabinet 1 will have the following cell
numbers in global format: 8, 9, 10, 11, 12, 13, 14, 15. The cell num‐
bers in corresponding local format will be 1/0, 1/1, 1/2, 1/3, 1/4,
1/5, 1/6, 1/7.
From the above convention the cell located in cabinet 1, slot 0 is
identified in the local format as 1/0 or in the global format as 8.
The command displays the above cell as "cab1,cell0". The cell located
in cabinet 1, slot 4 is identified in the local format as 1/4 or in the
global format as 12. The command displays the above cell as
"cab1,cell4". See parstatus(1).
RETURN VALUE
The command exits with one of the following values:
Successful completion.
Error condition occurred.
EXAMPLES
Create a new partition with two cells. One of the cells is located in
cabinet 0, slot 4. The celltype for the cell is The failure_usage pol‐
icy for this cell is The CLM value for this cell is 1 GB.
The other cell is located in cabinet 0, slot 6. The celltype and fail‐
ure_usage are not specified for this cell. The use_on_next_boot for
both cells is
Create a new partition with two cells. The cells are located in cabi‐
net 0, slot 0 and slot 1. This example uses the default values for the
cells. The default celltype will be
The default failure_usage policy will be The default use_on_next_boot
will be By default there will be no CLM for the cells.
WARNINGS
Activation of Instant Capacity (iCAP) components (cells and CPUs) is
possible with the command. This may result in the requirement to pur‐
chase such components to stay in compliance with a customer's iCAP con‐
tract.
DEPENDENCIES
This command uses the Web-Based Enterprise Management (WBEM) product
and some of its configuration settings. If you encounter connection
errors when using the option, check that the following two conditions
are satisfied:
· Use the command (see cimconfig(1M) in the WBEM product documenta‐
tion) to verify (and correct if necessary) the setting of the fol‐
lowing two variables:
·
·
· The target partition's digital certificate has been appended to the
local partition's Shared Authentication Store. For the nPartition
commands, the Shared Authentication Store is stored in the file:
This file is used by all the clients, which use SSL based certifi‐
cates. If these clients trust a target partition, then the nParti‐
tion commands will also trust the target partition.
Refer to the WBEM documents specified in the section below for further
information.
AUTHOR
was developed by the Hewlett-Packard Company.
SEE ALSOfruled(1), parstatus(1), cplxmodify(1M), frupower(1M), parconfig(1M),
parmgr(1M), parmodify(1M), parolrad(1M), parremove(1M), parunlock(1M),
partition(5).
on
on
on
parcreate(1M)
