Installing and Managing HP-UX Virtual Partitions (includes A.04.02)

Planning Your System for Virtual Partitions

Planning Your Virtual Partitions

Chapter 3

NOTE When you create a partition, the vPars Monitor assumes you will boot and use the partition.

Therefore, even if a partition is down, the resources assigned to the partition cannot be used by

any other partition.

The next few sections will describe how we arrived at each portion of the partition plan.

Number of Virtual Partitions

For the latest information on the recommended and maximum number of virtual partitions per system or

nPartition, please see the document HP-UX Virtual Partitions Ordering and Configuration Guide available

at:

http://docs.hp.com/hpux/11i/index.html#Virtual%20Partitions

Virtual Partition Names

All virtual partitions must be given text names that are used by the vPars commands. The names can consists

of only alphanumeric characters and periods (’.’). The maximum length of a name is 239 characters.

HP recommends using the corresponding hostnames for virtual partition names, but they are not internally

related.

For our cellular server, we have chosen the names of our virtual partitions to be keira1, keira2, and keira3:

For our non-cellular server, we have chosen the names of our virtual partitions to be winona1, winona2, and

winona3:

Although the underscore (_) is a legal character within the name of a virtual partition, it is not a legal

character within the Domain Name System (DNS).

TIP Virtual Partitions on nPartitions

If you are using vPars on a complex, you may want to distinguish the names of your virtual

partitions from the names of your nPartitions to avoid confusion.

Minimal Hardware Configuration

Every bootable virtual partition must have at least:

•1 CPU

console port

(PA-RISC Only)

owned by winona1

Autoboot

AUTO AUTO AUTO

Partition

Name

keira1 keira2 keira3

Partition

Name

winona1 winona2 winona3