How to add a disk to a vpar
One of the firsts tasks with vPars is to establish how much hardware you have in your current non vPar server (or nPar). This can be a process of various ioscans from the non vPar server. What you need to make sure is that you have assigned the LBA (Local Bus Adapter) (specific interface card) that controls the new Hard Drives to the vPar that you want to have the disks. If the controller is assigned to another vPar, then there is no way to do this, but to unassigned the controller from that other vPar.
When you initially create a vPar, you will add all the I/O devices that the vPar will handle.
The following resouces will be assigned to vPar 0:
- Physical Memory: 2GB
- Total Number of CPU: 2
- Total number of bound cpus: 1 (2/10)
- Total number of Unbound CPUS: 1
- Assigned LBA
- Boot Device: 2/0/1/0/0.0.0
- Alternate Boot Device: 2/0/11/0/0.3.0
In order to create this vPar you need to run this command:
# vparcreate -p vPar0 –a cpu::2 -a cpu:::1:2 -a cpu:2/10 -a mem::2048 -a io:2/0/0 -a io:2/0/1 - a io:2/0/2 -a io:2/0/3 -a io:2/0/10 -a io:2/0/11 -a io:2/0/12 -a io:2/0/14 -a io:2/0/1/0/0.0.0:BOOT -a io:2/0/11/0/0.3.0:ALTBOOT
As you can see all the LBAs or IO devices are assigned with the -a io: option.
So if you are able to see the disks once you have inserted them into the server, with an ioscan from vPar in question, then should be able to add them with the vparmodify command if they belong to SCSI controller initially assigned to the vPar, if the controller has not been assigned to the vPar, then you should add it also.
In order to make the changes to the vPar a SHUT DOWN is REQUIRED!!!. Make sure you are working from another vPar to do the vparmodify command:
Vpar0# shutdown -h now
Vpar1# vparmodify -p vPar0 -a io:<HW/Path> -a io:<HW/Path> where <HW/Path> is the Hardware Path of the devices that you want to add.
To check if the new disks have been assigned to the vPar use this command:
Vpar1# vparstatus -vp vPar0 (where vPar0 is the name of the vPar with the new disks) [Virtual Partition Details] Name: vPar0 State: Up Attributes: Dynamic,Autoboot Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 1/2 Bound by User [Path]: 2.10 Bound by Monitor [Path]: Unbound [Path]: 2.11 [IO Details] 2.0.0 2.0.1 2.0.2 2.0.3 2.0.10 2.0.11 2.0.12 2.0.14 3.0.1 220.127.116.11.0.0.0 BOOT 18.104.22.168.0.3.0 ALTBOOT 22.214.171.124.0.0.0 '''---->New disk''' 126.96.36.199.0.1.0 '''---->New disk''' [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 2048
After verifying the data make sure to boot the vPar:
Vpar1# vparboot -p vPar0
Just in case if you want to check which resources are not assigned to any vPars you can run vparstatus -A.
vPar0# vparstatus -A [Unbound CPUs (path)]: 2.11 2.13 [Available CPUs]: 0 [Available I/O devices (path)]: 2.0.14 ---> All LBAs not assigned to a vPar appear in here [Unbound memory (Base /Range)]: 0x8000000/64 (bytes) (MB) 0x84000000/1984 [Available memory (MB)]: 0
- HP-UX Virtual Partitions Administrator’s Guide http://docs.hp.com/en/T1335-90083/index.html
- HP-UX CSE Official Study Guide and Desk Reference - Chapter 3