| Running ioscan on your vPars system will show you only the components that are contained in the vPar. The following ioscan searches for disks on a vPar named cable1 and shows only the disks connected to the LBA 0/0. 0/0 was the lone I/O component of cable1 when it was created with -a io:0/0: # ioscan -funC disk Class I H/W Path Driver S/W State H/W Type Description ===================================================================== disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 304 /dev/dsk/c0t1d0 /dev/rdsk/c0t1d0 disk 1 0/0/1/1.0.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC /dev/dsk/c1t0d0 /dev/rdsk/c1t0d0 disk 2 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC /dev/dsk/c1t2d0 /dev/rdsk/c1t2d0 disk 3 0/0/2/0.0.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC /dev/dsk/c2t0d0 /dev/rdsk/c2t0d0 disk 4 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST173404LC /dev/dsk/c2t2d0 /dev/rdsk/c2t2d0 # This listing shows that the four internal disks are at SBA 0, LBA 0, and SCSI busses 1 and 2, respectively. At the time of this writing these disks have to be in the same vPar because they are on the same LBA. There are many more disks connected to this server beyond those shown in the previous listing, however; those disks are connected to LBAs that are not part of cable1 and therefore don't appear in the listing. The following output of sar -d shows only performance data for the one disk configured into cable1. The disk off which the other vPar on this system (cable2) is running at the time this output was produced is not shown in this output: # sar -d 4 3 HP-UX cvhdcon3 B.11.11 U 9000/800 10/15/01 14:28:42 device %busy avque r+w/s blks/s avwait avserv 14:28:46 c1t2d0 0.25 0.50 1 3 0.49 8.29 14:28:50 c1t2d0 0.50 0.50 1 2 1.49 8.77 14:28:54 Average c1t2d0 0.25 0.50 1 2 0.92 8.50 You would have to connect to the other vPar, in this case cable2, and run ioscan and sar -d to get a list of devices and performance data for the disk off which cable2 is running. This is a clear example of the way in which vPars running on the same server are like separate servers. All of the vPars are running their own instance of HP-UX 11i and applications and must be analyzed as though they are separate servers. |