| The attributes we may consider changing include the dynamic nature of configuration changes to a partition as well as changes to the boot commands used to boot HP-UX. 3.10.1 Changing configuration attributes The two configuration options we are considering can be seen in the Attributes field of vparstatus :
root @uksd3 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================ ===== ========== ========================= ===== vPar0 Up Dyn,Auto /stand/vmunix vPar1 Up Dyn,Auto /stand/vmunix [Virtual Partition Resource Summary] CPU Num Memory (MB) CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== vPar0 1/ 5 1 2 9 0/ 0 2048 vPar1 1/ 2 1 0 6 0/ 0 2048 root @uksd3 #
Dyn means that dynamic configuration changes to the hardware configuration of the partition are allowed (limited to adding/removing unbound CPUs at present). This can be changed to static with the vparmodify command:
root @uksd3 # vparmodify -p vPar1 -S static root @uksd3 # root @uksd3 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================ ===== ========== ========================= ===== vPar0 Up Dyn,Auto /stand/vmunix vPar1 Up Stat ,Auto /stand/vmunix [Virtual Partition Resource Summary] CPU Num Memory (MB) CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== vPar0 1/ 5 1 2 9 0/ 0 2048 vPar1 1/ 2 1 0 6 0/ 0 2048 root @uksd3 #
Auto refers to the autoboot attribute for the partition. If the attribute is set to manual , the virtual partition halts after a vparreset and does not boot when vpmon is loaded. It must then be booted manually with the vparboot command.
root @uksd3 # vparmodify -p vPar1 -B manual root @uksd3 # root @uksd3 # vparstatus [Virtual Partition] Boot Virtual Partition Name State Attributes Kernel Path Opts ============================ ===== ========== ========================= ===== vPar0 Up Dyn,Auto /stand/vmunix vPar1 Up Stat,Manl /stand/vmunix [Virtual Partition Resource Summary] CPU Num Memory (MB) CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== vPar0 1/ 5 1 2 9 0/ 0 2048 vPar1 1/ 2 1 0 6 0/ 0 2048 root @uksd3 #
Let's see what effect that has made on vPar1:
root @uksd5 # root @uksd5 # setboot Primary bootpath : 2/0/4/0/0.8.0 Alternate bootpath : <none> Autoboot is OFF (disabled) Autosearch is OFF (disabled) Note: The interpretation of Autoboot and Autosearch has changed for systems that support hardware partitions. Please refer to the manpage. root @uksd5 #
As you can see, the partition autoboot attribute has a direct effect on the setboot autoboot attribute. This is because the process of booting HP-UX is now controlled by vpmon , which reads boot related settings from the Virtual Partition Database (/stand/vpdb ). Personally, I think the default configuration attributes for virtual partitions of “B auto and “S dynamic are, more often than not, appropriate defaults. This leads us to the next type of attribute change we may want to consider. 3.10.2 Changing boot-related attributes We may need to consider changing boot-related attributes for individual vPars. The boot-related attributes I am thinking of include boot paths and the boot string used to boot a Virtual Partition. The configuration of boot paths for Virtual Partitions is controlled by the setboot command.
root @uksd3 # setboot Primary bootpath : 2/0/1/0/0.0.0 Alternate bootpath : 2/0/11/0/0.3.0 Autoboot is ON (enabled) Autosearch is ON (enabled) Note: The interpretation of Autoboot and Autosearch has changed for systems that support hardware partitions. Please refer to the manpage. root @uksd3 #
A Virtual Partition has only two boot paths : the Primary and Alternate Boot Path . As with any other server, we should consider configuring the Alternate Boot Path to be the mirror of our root disk. When considering things like mirroring, we should automatically consider the boot string issued by vpmon to boot HPUX. This is normally stored in the AUTO file on our boot disk. The boot string for a Virtual Partition is stored in /stand/vpdb (remember the AUTO file on our boot disk is configured to boot /stand/vpmon when the server/nPar is booted). To change the boot string for a Virtual Partition, we use the vparmodify command:
root @uksd3 # vparmodify -p vPar1 -o "-lq" root @uksd3 # root @uksd3 # vparstatus -vp vPar1 [Virtual Partition Details] Name: vPar1 State: Up Attributes: Dynamic,Autoboot Kernel Path: /stand/vmunix Boot Opts: -lq [CPU Details] Min/Max: 1/2 Bound by User [Path]: 2.12 Bound by Monitor [Path]: Unbound [Path]: [IO Details] 2.0.4 2.0.6 2.0.9 2.0.8 2.0.4.0.0.8.0 BOOT 2.0.14 [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 2048 root @uksd3 #
The “o option effectively stores the options we would pass to the hpux secondary loader. To change the name of the default kernel to boot, we can use the “b option to vparmodify :
root @uksd3 # vparmodify -p vPar1 -b "/stand/vmunix.test" root @uksd3 # root @uksd3 # vparstatus -vp vPar1 [Virtual Partition Details] Name: vPar1 State: Up Attributes: Dynamic,Autoboot Kernel Path: /stand/vmunix.test Boot Opts: -lq [CPU Details] Min/Max: 1/2 Bound by User [Path]: 2.12 Bound by Monitor [Path]: Unbound [Path]: [IO Details] 2.0.4 2.0.6 2.0.9 2.0.8 2.0.4.0.0.8.0 BOOT 2.0.14 [Memory Details] Specified [Base /Range]: (bytes) (MB) Total Memory (MB): 2048 root @uksd3 #
| 