HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)

Because the local copy is now /stand/vpdb.sim, you do not need to specify the -D
/stand/vpdb.sim option when performing vPars Monitor commands. For example, to set
the static attribute for the partition winsim2, the command is:
winsim2# vparmodify -p winsim2 -S static
This change will be synchronized to the local copies of /stand/vpdb.sim. (If
/stand/vpdb.sim does not exist, as in this case on winsim2, the file will be automatically
created during synchronization).
4. To return to using /stand/vpdb, do the same steps as above, except on the ISL command
line in Step 3 is:
ISL> hpux /stand/vpmon -a
By default, the file /stand/vpdb is read as the partition database file.
When working with an alternate partition database file using -D filename, note the following:
• filename must reside in /stand when the server boots because the vPars Monitor can only
traverse HFS file systems of the boot disk.
• Be careful when creating partitions using the -D option. Fewer checks on configuration are
being performed. It is possible to create a partition configuration that is not valid.
• All LVM rules still apply. For example, you cannot migrate I/O only by re-assigning the I/O
to a different partition; you must still vgexport and vgimport the volume groups.
• (pre A.03.02) Although there is no command that displays which partition database file was
read when the vPars Monitor was booted, because the local copies of the active database
are synchronized every five seconds, you should be able to tell which database file was read
and is active based on the time stamps of the various database files in /stand.
Managing Resources With Only One Virtual Partition
In some cases, adding and deleting I/O and memory resources to and from a virtual partition
requires the virtual partition to be in the down state. Therefore, if you have configured only one
virtual partition, you cannot run vparmodify from that virtual partition to modify its I/O and
memory resources.
In this situation, you should do the following:
1. Boot into standalone (PA-RISC) or nPars (Integrity) mode.
2. Add or delete the resources using vparmodify.
3. Reboot the nPartition into the vPars (PA-RISC) environment or vPars (Integrity) mode.
NOTE: Beginning with A.05.01, the vPar does not have to be in the down state if memory is
being added, or float memory is being deleted. The vPar must be in the down state only if base
memory is being deleted.
Managing Resources With Only One Virtual Partition 169