| United States-English |
|
|
|
![]() |
Installing and Managing HP-UX Virtual Partitions (vPars) > Chapter 4 Planning Your Virtual Partitions and Installing
vParsPlanning Your Virtual Partitions |
|
Before you install vPars, you should have a plan of how you want to create virtual partitions within your computer. Below is a possible partition plan based on the example N-class computer:
The next few sections will describe how we arrived at each portion of the partition plan.
For performance reasons, HP recommends the following:
The maximum number of partitions for the L3000 and N-class computers is the number of CPUs given the following limitations:
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 partition names, but they are not internally related. For our example computer, we have chosen the names of our 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) and should not be used. Every bootable virtual partition must have at least:
Although not required for booting a partition, you might want to add LAN card(s) as required for networking. For your partitions, use the number of CPUs, amount of memory, boot disk configuration, and lan cards as is appropriate for your OS and applications. For detailed information on CPU allocation, please read “CPU Allocation”. The ioscan output for the example N-class shows the following processors:
For this example, winona1 will have two bound CPUs, winona2 will have two bound CPUs where the hardware paths will be 41 and 45, and winona3 will have one bound CPU.
Unbound CPUs are assigned in quantity. We have three CPUs that were not assigned to any of the partitions, so we will have three unbound CPUs available.
For detailed information on memory allocation, please read “Memory Allocation”. In this example, we will use the following sizes:
For detailed information on I/O Assignments, see “I/O Allocation”. For simplified I/O block diagrams of the LBA to physical slot relationship, see Appendix A “Hardware Path to Physical I/O Slot Correspondence”. For our example computer, the ioscan output shows the LBAs as:
Looking at the full ioscan output to verify that we have the desired I/O for each partition, we will assign the I/O at the LBA level. (When assigning hardware at the LBA level to a partition, all hardware at and below the specified LBA is assigned to the partition.):
In our example computer, the hardware console port is at 0/0/4/0, which uses the LBA at 0/0. The LBA 0/0 is owned by the partition winona1:
When we create the virtual partitions, we will create winona1 first.
Autoboot allows a partition to be booted automatically on a cold boot of the computer. By default, autoboot is set to AUTO for all partitions.
For more information, see the vparmodify(1M) manpage.
Combining all parts above, the resultant partition plan is the following:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||