| Each Virtual Partition is an independent host. As such, vPars have unique hostnames and are viewed by SAM as independent systems. Figure 11-1 shows SAM running on two different vPars with the respective hostnames in the top of the SAM windows. Figure 11-1. Partial SAM Windows of Two vPars on the Same Computer  The hostnames used are actappd1(this is also the name of the first vPar) and ecvpard2 (this is also the name of the second vPar.) Using the same name for both the host and vPar is recommended when configuring Virtual Partitions to reduce confusion. I'll use the name vPar 1 for the first vPar and vPar 2 for the second vPar throughout this section. Since the concept of isolation is very important in the world of Virtual Partitions we would expect to see only the information related to vPar 1 when working in SAM on this vPar. The same is true of vPar 2, that is, we'd expect to see only information related to vPar 2 when working in SAM on this vPar.  | Let's start by running vparstatus to see which components are associated with vPar 1 and which components are associated with vPar 2, as shown in the following listing: |
root@actappd1[/.root] > vparstatus -v [Virtual Partition Details] Name: actappd1 <-- begininng of vPar 1 information State: Up Attributes: Dynamic,Manual Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 2/2 Bound [Path]: 33 37 Unbound [Path]: [IO Details] 0.0.1.1.2.0 BOOT 0.0.4.0 CONSOLE 0.0 0.0.2.0.2.0 ALTBOOT [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 2048 [Virtual Partition Details] Name: ecvpard2 <-- beginning of vPar 2 information State: Up Attributes: Dynamic,Autoboot Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 2/2 Bound [Path]: 97 101 Unbound [Path]: [IO Details] 0.12.0.0.1.0, BOOT 0.8 [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 1920 root@actappd1[/.root] > | | I took the information for vPars 1 and 2 from the vparstatus output and summarize it below: |
vPar 1 name ecvpard1 <-- we'll call this vPar 1 processors two bound added by path (I/O intensive app) 33 and 37 memory 2048 MB LAN 0/0/0/0 boot disk 0/0/1/1.2.0 kernel /stand/vmunix console 0/0/4/0 vPar 2 name ecvpard2 <-- we'll call this vPar 2) processors two bound added by path (I/O intensive app) 97 and 101 memory 2048 MB LAN 0/0/8/0 boot disk 0.12.0.0.1.0 kernel /stand/vmunix We'll refer to some of these components in upcoming SAM screen shots. Let's now look at Peripheral Devices - Cards functional area of SAM in Figure 11-2 and see if indeed only the components related to vPar 1 are shown when working with this vPar and that the components of vPar 2 are shown when working with this vPar in SAM. Figure 11-2. Peripheral Devices - Cards for vPar 1 and vPar 2  All of the components associated with the Core I/O card are part of vPar 1. All of the components of the Core I/O card must be part of the same vPar since they are on the same Local Bus Adapter (LBA) and are shown in the top window of Figure 11-2. The second vPar has in it the cards specified when the vPar was created, including boot disk (0/12) and LAN (0/8.) The cards shown for the respective vPars can be manipulated only in the SAM window to which the cards are dedicated. These cards have many devices associated with them as well. Figure 11-3 shows the Peripheral Devices - Device List functional area of SAM for vPar 1 and vPar 2. Figure 11-3. Peripheral Devices - Device List for vPar 1 and vPar 2  There are many devices associated with the Core I/O card that are part of vPar 1. Also shown for vPar 1 are the two processors and memory. Note that there are four internal disk drives associated with vPar 1. We specified only a boot disk at 0/0/1/1.2.0; however, the three additional internal disks are shown. These are associated with the Core I/O LBA and can therefore be used by vPar 1. If we run an ioscan on vPar 1 and look for its disks only, we'll see all four internal disks as well as the DVD-ROM: root@actappd1[/.root] > ioscan -f | grep disk disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC disk 2 0/0/2/0.0.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC disk 3 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC disk 4 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305 The second vPar has in it all of the devices on 0/12 and 0/8 as well as its two processors and memory. All of the disks on LBA 0/12 are shown as vPar 2 devices, just as all of the internal disk devices were associated with vPar 1. As with the cards, the devices are isolated between the two Virtual Partitions even though they are on the same computer. Some devices on the system, such as the Memory Controller (192) and System Bus Adapter (0), are under the control of the Virtual Partition Monitor and appear under both vPars. We could perform the same checks for many additional areas of SAM, however; we've seen that the isolation we'd expect by vPars when using SAM is indeed in place. This means that the work you perform on one vPar in SAM will not affect the other vPars running on your system. We can also use SAM to view all aspects of the kernel and make changes to the kernel for vPars. Keep in mind that running SAM in different vPars is like running SAM on different systems. Figure 11-4 shows a screen shot of SAM displaying drivers for vPar cable1 (hostname of cvhdcon4 shown in the top of all of the SAM windows): Figure 11-4. SAM Showing Virtual Console-Related Drivers  Chapter 4 covers many aspects of performing vPar kernel-related work at the command line. All of this kernel-related work can also be performed in SAM. The background portion of this chapter covers many aspects of kernel-related work in SAM. | 
