| There are some restrictions related to the devices on which we can load the operating system and other software used by Virtual Partitions. You'll want to read two upcoming chapters that cover hardware in detail when you get to the point of creating and working with vPars: Chapter 2 covers working with vPars and Chapter 5 covers vPars and devices. In this section, however; we do need to cover the basics of selecting disks on which to load software so that you meet the restrictions at the time of this writing and load the software on disks that meet the requirements of vPars. Let's take a look at an ioscan output that shows the disks on a system (ioscan and issues related to hardware and vPars in general are covered in detail in Chapters 2 and 5 as mentioned earlier.) At the time of this writing, components that are at or below the Local Bus Adapter (LBA) level are devoted to a partition. This means that the disks on which you load the software for two different vPars must be on two different LBAs. Let's take a brief look at the LBAs and disks on a system in order to select the disks on which we'll load software. If you need more detail than is covered here, please refer to the chapters that cover this topic in more detail. Also please keep in mind that the layout of systems varies depending on the model and that you need to become familiar with the layout of your system to the extent that you can determine the location of components in your system relative to the LBA level. Let's take a look at an L-Class system to view the System Bus Adapter (SBA) and multiple LBAs. # ioscan -f | grep ba L-Class cvhdcon3:/ # ioscan -f | grep ba ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (803) ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 6 0/8 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 7 0/9 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 8 0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) ba 9 0/12 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782) cvhdcon3:/ # This L-Class has only one SBA, as indicated by the leading 0 on all of the buses in the previous listing, and it has two SCSI buses on LBA 0/0. The internal disks are normally mirrored across these two different SCSI buses. There are then many additional LBAs. Let's now see what disks are connected to this system and determine with what LBA they are associated. cvhdcon3:/# ioscan -f | grep disk disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 304 disk 1 0/0/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC disk 2 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC disk 3 0/0/2/0.0.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC disk 4 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC disk 7 0/8/0/0.8.0.5.0.0.0 sdisk CLAIMED DEVICE HP A5277A disk 10 0/8/0/0.8.0.5.0.0.1 sdisk CLAIMED DEVICE HP A5277A disk 11 0/8/0/0.8.0.5.0.0.2 sdisk CLAIMED DEVICE HP A5277A disk 12 0/8/0/0.8.0.5.0.0.3 sdisk CLAIMED DEVICE HP A5277A disk 15 0/8/0/0.8.0.5.0.1.0 sdisk CLAIMED DEVICE HP A5277A disk 17 0/8/0/0.8.0.5.0.2.0 sdisk CLAIMED DEVICE HP A5277A disk 18 0/8/0/0.8.0.5.0.3.0 sdisk CLAIMED DEVICE HP A5277A disk 5 0/9/0/0.8.0.4.0.0.0 sdisk CLAIMED DEVICE HP A5277A disk 6 0/9/0/0.8.0.4.0.0.1 sdisk CLAIMED DEVICE HP A5277A disk 8 0/9/0/0.8.0.4.0.0.2 sdisk CLAIMED DEVICE HP A5277A disk 9 0/9/0/0.8.0.4.0.0.3 sdisk CLAIMED DEVICE HP A5277A disk 13 0/9/0/0.8.0.4.0.1.0 sdisk CLAIMED DEVICE HP A5277A disk 14 0/9/0/0.8.0.4.0.2.0 sdisk CLAIMED DEVICE HP A5277A disk 16 0/9/0/0.8.0.4.0.3.0 sdisk CLAIMED DEVICE HP A5277A cvhdcon3:/ # This listing shows first the DVD-ROM, then the four internal disks, and finally, the 14 Logical UNits (LUNs) configured on our external storage enclosure. The internal disks are all on the same LBA as indicated by the leading 0/0. The first 0 is for the SBA and the second 0 is for LBA 0. These disks must all be part of the same vPar since they are associated with the same LBA. We have many LUNs connected to two other LBAs at 8 and 9. This means that we could have as many as three vPars on this system since there are potential boot volumes connected to three different LBAs. An example of two devices on which we might load our operating system and vPars software would be the internal disk at path 0/0/1/1.2.0 and the device at path 0/8/0/0.8.0.5.0.0.0. Using these devices, which meet the separate LBA requirement, we can now proceed to loading software. | 
