Defining and Configuring the Four vPars

   

HP-UX Virtual Partitions
By Marty Poniatowski

Table of Contents
Appendix B.  Superdome Virtual Partitions


After having run the ioscan in then Partition on our Superdome, we have determined that the following configurations will exist in our four vPars:

vPar bvvpard1

 name         bvvpard1  processors   min of one (bound) max of three (two unbound)  memory       2048 MB  LBA Core I/O 5/0/0 (all components on 0/0 are implied)  LAN          5/0/9  boot disk    5/0/12/0/0.0.0  kernel       /stand/vmunix (this is default)  autoboot     off (manual)  console      on core I/O at 5/0/0 

vPar bvvpard2

 name         bvvpard2  processors   min of one (bound) max of four (two unbound)  memory       2048 MB  LAN          5/0/14  boot disk    5/0/6/0/0.0.0  kernel       /stand/vmunix (this is default)  autoboot     off (manual)  console      virtual 

vPar extappd2

 name         extappd2  processors   min of one (bound) max of four (two unbound)  memory       2048 MB  LAN          5/0/3  boot disk    5/0/4/0/0.0.0  kernel       /stand/vmunix (this is default)  autoboot     off (manual)  console      virtual 

vPar intappd2

 name         intappd2  processors   min of one (bound) max of four (two unbound)  memory       2048 MB  LAN          5/0/2  boot disk    5/0/1/0/0.0.0  kernel       /stand/vmunix (this is default)  autoboot     off (manual)  console      virtual 

We have all the software we need on our vPars disks, including HP-UX, vPars software, patches, and so on.

graphics/chic02.gif

Now that we have the full ioscan of all the components in the nPartition and have mapped out the components we'd like to have in our four vPars, we can issue the vparcreate commands to create the four vPars.

 vparcreate -p bvvpard1 -B manual -b /stand/vmunix -a cpu:::1:3  -a mem::2048 -a io:5/0/9 -a io:5/0/12 -a io:5/0/12/0/0.0.0:boot  -a io:5/0/0 -a io:5/0/11  vparcreate -p bvvpard2 -B manual -b /stand/vmunix -a cpu:::1:4  -a mem::2048 -a io:5/0/6 -a io:5/0/14 -a io:5/0/6/0/0.0.0:boot  vparcreate -p extappd2 -B manual -b /stand/vmunix -a cpu:::1:4  -a mem::2048 -a io:5/0/4 -a io:5/0/3 -a io:5/0/4/0/0.0.0:boot  vparcreate -p intappd2 -B manual -b /stand/vmunix -a cpu:::1:4  -a mem::2048 -a io:5/0/1 -a io:5/0/2 -a io:5/0/1/0/0.0.0:boot 

These commands use the same form covered in chapters earlier in the book. Chapter 2 covered several examples of using vparcreate its options.

Notice that vPar bvvpard1 has in it the core I/O card at 5/0/0, which give it console access, and the tape and DVD-ROM interface at 5/0/11, because this vPar will be used as an Ignite-UX server

graphics/chic14.gif

After having created and booted all four vPars, we can check the status of each and view their respective components with vparstatus -v as shown in the following listing:

 # vparstatus -v  [Virtual Partition Details]  Name:         bvvpard2            <-- vPar bvvpard2  State:        Up  Attributes:   Dynamic,Manual  Kernel Path:  /stand/vmunix  Boot Opts:  [CPU Details]  Min/Max:  1/4  Bound by User [Path]:  Bound by Monitor [Path]:  5.10  Unbound [Path]:  [IO Details]     5.0.6     5.0.14     5.0.6.0.0.0.0  BOOT  [Memory Details]  Specified [Base  /Range]:            (bytes) (MB)  Total Memory (MB):  2048  [Virtual Partition Details]  Name:         bvvpard1            <-- vPar bvvpard1  State:        Up  Attributes:   Dynamic,Manual  Kernel Path:  /stand/vmunix  Boot Opts:  [CPU Details]  Min/Max:  1/3  Bound by User [Path]:  Bound by Monitor [Path]:  5.11  Unbound [Path]:  [IO Details]     5.0.9     5.0.12     5.0.12.0.0.0.0  BOOT     5.0.0  [Memory Details]  Specified [Base  /Range]:            (bytes) (MB)  Total Memory (MB):  2048  [Virtual Partition Details]        <-- vPar extappd2  Name:         extappd2  State:        Up  Attributes:   Dynamic,Manual  Kernel Path:  /stand/vmunix  Boot Opts:  [CPU Details]  Min/Max:  1/4  Bound by User [Path]:  Bound by Monitor [Path]:  5.12  Unbound [Path]:  [IO Details]     5.0.4     5.0.3     5.0.4.0.0.0.0  BOOT  [Memory Details]  Specified [Base  /Range]:            (bytes) (MB)  Total Memory (MB):  2048  [Virtual Partition Details]  Name:         intappd2            <-- vPar intappd2  State:        Up  Attributes:   Dynamic,Manual  Kernel Path:  /stand/vmunix  Boot Opts:  [CPU Details]  Min/Max:  1/4  Bound by User [Path]:  Bound by Monitor [Path]:  5.13  Unbound [Path]:  [IO Details]     5.0.1     5.0.2     5.0.1.0.0.0.0  BOOT  [Memory Details]  Specified [Base  /Range]:            (bytes) (MB)  Total Memory (MB):  2048  # 

graphics/chic14.gif

We now have four vPars set up with the components that we have specified. The output of this vparstatus command is identical to that we viewed in the earlier L-Class and N-Class examples in the book except that the paths employed are those from a Superdome.


       
    Top
     



    HP-UX Virtual Partitions
    HP-UX Virtual Partitions
    ISBN: 0130352128
    EAN: 2147483647
    Year: 2002
    Pages: 181

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net