Creating the Second Virtual Partition
After
booting the first virtual partition, the second will be created. Most
of the options for creating the vPar are similar to those specified
when creating the first vPar. Of particular interest, though, is the
fact that the boot and alternate boot devices are no longer under the
same LBA. This provides an additional level of availability, as the
failure of the PCI device under LBA 6/0/8 will not make the vPar unbootable. Instead, the PCI device under the LBA
6/0/9 can be used as an alternate boot device. This configuration assigns 6/0/8, 6/0/9, and 6/0/10 to the zoo25 vPar. The first two LBAs are implicitly assigned and the last one is explicitly assigned.
Listing 9. Create Second Virtual Partition Command
# vparcreate -p zoo25 \
> -a cpu::1 \
> -a cpu:::1:3 \
> -a mem::1024 \
> -a io:6/0/8/0/0.8.0:boot \
> -a io:6/0/9/0/0.8.0:altboot \
> -a io:6/0/10
|
At this point, both vPars have been created. The vparstatus output shown in Listing 10 shows both vPars exist but the zoo25 vPar has not been booted; it is in the down state. If the boot disk specified in the vparcreate command for zoo25
already contains the HP-UX operating system and the vPar software, then
the vPar may be booted from its primary boot disk using the vparboot command. In this case, the boot disk does not contain an operating system so it must be installed using Ignite-UX.
Listing 10. Status of Virtual Partitions
# vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path
Opts
============================== ===== ========== =============
zoo24 Up Dyn,Auto /stand/vmunix
zoo25 Down Dyn,Auto /stand/vmunix
[Virtual Partition Resource Summary]
CPU Num
CPU Bound/ IO
Virtual Partition Name Min/Max Unbound devs Total MB
============================== ================ ==== ========
zoo24 1/ 3 1 0 4 1024
zoo25 1/ 3 1 0 5 1024
|
Booting the Second Virtual Partition
The zoo25 vPar can now be booted from an Ignite-UX server with the hostname of seminole.
In this example, there is only one remaining vPar to be installed with
Ignite-UX. In situations where multiple vPars have been created and
require an operating system to be installed, the process of installing
operating systems can be streamlined by using the approach shown in Listing 11. Each vPar that requires installation of an operating system can be booted in parallel from an Ignite-UX server.
tip
Multiple operating systems may be installed in parallel after booting the first vPar. The vparboot command with the –I
option can be used for each vPar requiring an operating system to be
installed. This results in provisioning the operating systems for each
vPar in parallel.
The output shown in Listing 11 illustrates the process of booting the newly created zoo25 vPar from an Ignite-UX server. Notice the <ctrl-a> in the listing after the vPar is loaded. The <ctrl-a> command was manually issued at the console to toggle between the vPar consoles. In this case, the vparboot command was issued from the zoo24 operating system on the physical console assigned to zoo24.
The
consoles for all the vPars in a server are accessible from the physical
console. From the physical console, each of the individual vPar
consoles can be accessed using the <ctrl-a> keys. This command cycles through the consoles for all of the vPars in the server.
The output shown at the end of the listing is that of the standard Ignite-UX interface. The operating system for zoo25
is configured and installed just as any operating system would be in a
non-vPar environment, assuming the Ignite-UX depot contains the vPar
software.
warning
Booting
vPars from an Ignite-UX server provides a streamlined installation
process. However, the Ignite-UX depots must be properly configured with
the vPar software and its dependencies in order for the operating
system to boot in a vPar environment.
Listing 11. Booting of Second Virtual Partition
# vparboot -p zoo25 -I seminole,WINSTALL
vparboot: Booting zoo25. Please wait...
#
[MON] zoo25 loaded
<ctrl-a>
[zoo25]
.
.
.
Welcome to Ignite-UX!
Use the <tab> key to navigate between fields, and the arrow
Keys within fields. Use the <return/enter> key to select
an item. Use the <return> or <space-bar> to pop-up a choices
list. If the menus are not clear, select the "Help" item
for more information.
Hardware Summary: System Model: 9000/800/SD64000
+---------------------+----------------+-------------------+
| Disks: 2 ( 33.9GB) | Floppies: 0 | LAN cards: 1 |
| CD/DVDs: 0 | Tapes: 0 | Memory: 942Mb |
| Graphics Ports: 0 | IO Buses: 2 | CPUs: 3 |
+---------------------+----------------+-------------------+
[ Install HP-UX ]
[ Run a Recovery Shell ]
[ Advanced Options ]
[ Reboot ] [ Help ]
|
Listing 12
shows the status of the vPars after the installation of the HP-UX
operating system is complete and the vPar has been booted. Notice both zoo24 and zoo25 are in the up state.
Listing 12. Status of Final Virtual Partition Configuration
# vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path
Opts
============================== ===== ========== =============
zoo24 Up Dyn,Auto /stand/vmunix
zoo25 Up Dyn,Auto /stand/vmunix
[Virtual Partition Resource Summary]
CPU Num
CPU Bound/ IO
Virtual Partition Name Min/Max Unbound devs Total MB
============================== ================ ==== ========
zoo24 1/ 3 1 0 4 1024
zoo25 1/ 3 1 0 5 1024
#
|
