vparresources2.5 (2012 03)

v
vparresources2(5) vparresources2(5)
(For OA Based Partition Management Systems)
I/O Devices
The vPar assignable IO resources are rootports or ioslots in the blades and I/O bays. Rootports and
ioslots have a one-to-one mapping and either of them can be assigned to a vPar. The rootport (RP) or
ioslot is specified in the resource path format. Typically disk devices or LAN devices get attached to a
rootport. On blades, iLO is also of a rootport.
Blades
Blades consist of CPU-cores, memory, and I/O devices. Blades are not vPar assignable resources. They
cannot be added to or deleted from virtual partitions in their entirety. However, CPU- core, memory and
I/O resources on blades can be allocated among different virtual partitions. For example, given a blade
containing four CPU-cores, one CPU-core can be allocated to each of four virtual partitions, all four to one
vPar, or any other possible combination.
Two additional syntax forms allow you to specify that available resources should be allocated from a
specific blade:
•
-a socket:socket_id :cpu::num or
-a socket:socket_id :core::num
allocates num CPU-cores on socket_id to the target vPar. The socket_id is specified as
enclosure#
/blade# /cpusocket#, where cpusocket# is the actual socket# .
•
-a socket:socket_id :mem::size
allocates size MB (megabytes) SLM from socket_id to the target vPar. If size is not an integral number
of granules, it is first rounded upward to the next integral value. Whether rounded upward or not, the
memory must have been previously configured as SLM by the
parcreate or parmodify com-
mands. See parcreate2 (1M) and parmodify (1M).
I/O Bays
I/O bays are nPartition assignable I/O resources and cannot be added or deleted from virtual partitions in
their entirety. They are located in the I/O expander chassis. Each I/O bay has 6 rootports, which can be
allocated among different virtual partitions.
COMMANDS AND THEIR RESOURCE SPECIFICATIONS
Each vPar can be configured with a subset of total system hardware resources such that any given physi-
cal resource is assigned to at most one vPar. This job is managed by two of the virtual partition com-
mands:
•
vparcreate, used when creating a new vPar. (Resources can only be added)
•
vparmodify, used when modifying an existing vPar configuration. (Resources can be added,
modified, or deleted)
Each command has specific resource syntax and semantic requirements. For example, some syntax forms
can be specified once.
The general form of a resource specification is up to five positional fields delimited by colons (
:). No whi-
tespace is allowed within any field.
Table I summarizes the three categories (CPU-core, I/O, and memory) and all the allowable forms
for each.
Table II specifies which forms are allowed for each of the three tasks (add, modify, or delete).
Table III is a detailed description of each syntax form and the conditions required for its use.
6 Hewlett-Packard Company − 6 − HP-UX 11i Version 3: March 2012