vparmodify2.1m (2012 03)

v
vparmodify2(1M)
For OA Based Partition Management Systems
vparmodify2(1M)
NOTE: When using socket local syntax (socket
:socket_id:cpu::num), only the number of cores on
the given socket may be entered, not the hardware paths of the individual cores.
io_path for:
1) Blade resident I/O is specified as enclosure#
/blade#/IO_hub#/root_complex#
/root_port#
For example:
Short form: 3/6/0/1/2
Medium form: iorp-3/6/0/1/2
Long form: enclosure3/blade6/iohub0/iorc1/iorp2
2) I/O bay resident I/O is specified as enclosure#
/IO_bay#/IO_hub#/root_complex#
/root_port#
For example:
Short form: 7/1/0/1/2
Medium form: iorp-7/1/0/1/2
Long form: enclosure7/iobay1/iohub0/iorc1/iorp2
ioslot_path for:
1) Blade resident I/O is specified as enclosure#
/blade# /io_slot#
For example:
Short form: 3/6/1
Medium form: ioslot-3/6/1
Long form: enclosure3/blade6/ioslot1
2) I/O bay resident I/O is specified as enclosure#
/iobay# /
io_slot#
For example:
Short form: 7/1/4
Medium form: ioslot-7/1/4
Long form: enclosure7/iobay1/ioslot4
Note that there is a one-to-one correspondence between root ports (specified along with io_path) and
ioslots (specified along with ioslot_path) on SD2 servers. The verbose output of blades and iobays
displayed by parstatus shows the correspondence between rootports and ioslots.
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.
Note that cpu related modifications may be effected on a vPar even in UP state. For any other
resource modifications (such as ioslot or memory), the vPar must be in DOWN state.
SECURITY RESTRICTIONS
When invoked from the OS, this command is restricted to processes owned by superuser having appropri-
ate
parperm privilege. An OA user with operator privilege level or above can modify virtual partitions
from the OA.
RETURN VALUE
The
vparmodify command exits with one of the following values:
0 Successful completion.
1 One or more error conditions occurred.
EXAMPLE
Change the name of the virtual partition called
Oslo to Bergen:
vparmodify -p Oslo -P Bergen
Add two processors to the virtual partition Oslo (cpu and core syntax):
vparmodify -p Oslo -a cpu::2
vparmodify -p Oslo -a core::2
Add two socket-local processors from enclosure 3, blade 6, socket 0 to the virtual partition Oslo (cpu and
core syntax):
HP-UX 11i Version 3: March 2012 3 Hewlett-Packard Company 3