vparresources2.5 (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

vparresources2(5) vparresources2(5)

(For OA Based Partition Management Systems)

NAME

vparresources - description of virtual partition resources and their requirements

Platform Support Remarks

This

vparresources

describes functionality on systems with Onboard Administrator (OA) based parti-

tion management. For

vparresources

on systems not running OA based partition management, refer

to vparresources1(1M) by typing

man vparresources1

DESCRIPTION

Hardware resources are the most important property of a virtual partition (vPar). These resources are

divided into ﬁve major categories, or types:

• CPU-cores

• Memory

• I/O devices, such as disks, terminals, tapes and printers.

• Blades, hardware containers of CPU-cores, memory, and I/O devices.

• I/O bays, hardware containers of I/O devices.

The essence of virtual partitions is the allocation and distribution of a set of resources among multiple

instances of the HP-UX operating system, each running in its own software environment. Resources,

once assigned to a vPar, belong only to that vPar and are not visible or accessible to other virtual parti-

tions except through the use of vPars commands such as

vparstatus to view them, or

vparmodify to

change the assignment of one or more resources. For example, if the I/O device at resource path 7/1/0/1/2

is assigned to vPar A, it cannot be accessed by vPar B. A user on vPar B can use the

vparstatus com-

mand to display the conﬁguration of vPar A, including this device, but cannot otherwise use the device.

Resource path is the key to identify physical resources on platforms that support Onboard Administrator

based partition management.

Resource paths can be speciﬁed in three different formats - short, medium and long. Refer to resour-

cepath (5) manpage on HP-UX or "Help resourcepath" on OA for additional information.

The table below shows the example for the paths in the medium format.

Resource Short Form Medium Form

Socket 3/6/0 cpusocket-3/6/0

CPU-core 3/6/0/2 cpucore-3/6/0/2

Root Port:

Blade 3/6/0/1/2 iorp-3/6/0/1/2

I/O Bay 7/1/0/1/2 iorp-7/1/0/1/2

I/O Slot:

Blade 3/6/5 ioslot-3/6/5

I/O Bay 7/1/4 ioslot-7/1/4

The table below shows the example for the paths in the long format.

Resource Short Form Long Form

Socket 3/6/0 enclosure3/blade6/cpusocket0

CPU-core 3/6/0/2 enclosure3/blade6/cpusocket0/cpucore2

Root Port:

Blade 3/6/0/1/2 enclosure3/blade6/iohub0/iorc1/iorp2

I/O Bay 7/1/0/1/2 enclosure7/iobay1/iohub0/iorc1/iorp2

I/O Slot:

Blade 3/6/5 enclosure3/blade6/ioslot5

I/O Bay 7/1/4 enclosure7/iobay1/ioslot4

The parstatus command displays detailed information about the resources under the blades and I/O

bays which can be used to create vPars.

Platforms that have OA based partition management support partition speciﬁcations or

parspecs.A

parspec is a collection of data from the customer that deﬁnes the conﬁguration of a speciﬁc nPar, includ-

ing the vPars in the nPar if the customer has deﬁned any vPars.

Following are the key features of parspecs.

• Every parspec deﬁnes only one nPar.

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (18 pages)

PAGE 1
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) NAME vparresources - description of virtual partition resources and their requirements Platform Support Remarks This vparresources describes functionality on systems with Onboard Administrator (OA) based partition management. For vparresources on systems not running OA based partition management, refer to vparresources1(1M) by typing man vparresources1.
PAGE 2
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) • • • • • • • Multiple nPars must be described in multiple parspecs. An nPartition can be created from a specified parspec. Every nPar that exists has a parspec associated with it (referred to as a current parspec), and there can be only one current parspec for a given nPar. Any parspec not associated with an existing nPartition is an alternate parspec. Every parspec has a unique name (scope of uniqueness is a complex).
PAGE 3
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Where performance is not a consideration, specify only generic assignments and allow the system to manage assignment of CPU-cores. For DOWN vPars, any CPU-core assigned to a vPar can be deleted the same way it was assigned or by specifying the resource path. For example, if you have configured a vPar as follows: -a cpu::4 -a cpu:3/1/0/2 -a socket:3/2/0:cpu::2 you will have seven CPU-cores in your vPar configuration.
PAGE 4
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) [CPU Details] Min/Max: 0/16 User assigned [Path]: 3/1/0/2 Boot processor [Path]: 3/1/0/2 System assigned [Path]: 3/1/0/0 3/1/0/1 3/1/0/3 3/1/1/0 3/2/0/0 3/2/0/1 Non-socket-specific: User assigned [Count]: 1 System assigned [Count]: 4 Socket-specific [Count]: Socket-ID/Count 3/2/0 2 Note that in the path displays, the user assigned CPU-core is also the boot processor, and so has been shown in the Boot processor line.
PAGE 5
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Memory Granularity The nPartition memory is sliced into multiple memory granules by firmware for ease of memory assignment to vPars. The size of these memory granules can be optionally specified by the user. Memory granularity refers to the maximum amount of memory that will be in each of these memory granules. Note that memory granules should not be confused with actual memory DIMMs.
PAGE 6
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.
PAGE 7
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Table I.
PAGE 8
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) • Please note that unlike nPartitions, vPartition ilm_size and size are specified in MB (megabytes). The commands round ilm_size and size upward as required to the granule increment in effect for that memory type. ilm_size and size may be specified in decimal or in hexadecimal. A hex specification should be preceded by 0x, as in 0x8000000. Table II.
PAGE 9
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) 7) For vPars that are DOWN, -m socket:socket_id :cpu::num or -m socket:socket_id :core::num specifies that the total socket specific cores from socket socket_id in the target vPar be set to num. This operation may result in addition or deletion of CPU-cores.
PAGE 10
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) 4) -m socket:socket_id:mem::size specifies that the SLM from socket socket_id in the target vPar be set to size MB. This operation may result in assignment or deletion of SLM. The -m option is internally mapped to either a -a or -d option. The difference in the current memory size and the specified memory size is rounded up before the addition or deletion.
PAGE 11
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Table III.b. Explanation Value Usage Restrictions Usage Guidelines Tasks: -a cpu:cpu_path -a core:core_path Assigns a CPU-core at a specific path to the vPar’s configuration.
PAGE 12
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Task: -a io:io_path Assigns an I/O resource at a specific path to the vPar’s configuration. io_path (Blade): enclosure#/blade#/IO_hub#/root_complex#/root_port# Table III.e.
PAGE 13
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Table III.i. Explanation Value Usage Restrictions Value Usage Restrictions Values Usage Restrictions Tasks: -m cpu:::[min][ :[max]] -m core:::[min][ :[max]] Specifies the minimum and maximum number of CPUs allowed for the vPar. This operation does not allocate any CPUs, but specifies the limits of other allocation tasks. You can change only min or max by not specifying the other field.
PAGE 14
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Task: -m mem::ilm_size Specifies the total amount of ILM in megabytes rounded upward to the next ILM granule multiple, to be allocated to the target vPar. This memory is taken from unspecified ranges of unassigned ILM when the target vPar boots.
PAGE 15
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Table III.n. Explanation Value Usage Restrictions Value Usage Restrictions -d cpu::num -d core::num For vPars that are DOWN, deletes num non-SLPs from the vPar. For vPars that are UP, deletes num CPU-Cores from the vPar, which can potentially delete user specified and socket specific CPU-Cores also.
PAGE 16
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) Task: -d io: io_path Deletes the specified I/O resource from the target vPar. io_path (Blade): enclosure#/blade#/IO_hub#/root_complex#/root_port# Table III.q.
PAGE 17
vparresources2(5) vparresources2(5) (For OA Based Partition Management Systems) SEE ALSO On OA: "help parcreate", "help parmodify", "help parstatus", "help vparcreate", "help vparmodify", "help vparstatus", "help parspec", "help resourcepath". On HP-UX: parcreate2(1M), parmodify2(1M), parstatus2(1M), vparcreate2(1M), vparmodify2(1M), vparstatus2(1M), parspec(5), resourcepath(5).
PAGE 18
(Notes) A (Notes) vA 18 Hewlett-Packard Company −1− HP-UX 11i Version 3: March 2012