27 Oct 14 EFI boot configuration rx7640 san boot vpmon example
EFI boot configuration
This example uses AUTO file to boot vpmon. This example happens to use HP-UX B.11.23 but the procedure is the same for B.11.31 though the disk paths will look different.
AUTO
boot /stand/vpmon
map –r
The bootable disks show Part1 on the disk list (highlighted). Local disks (which should not be used are SCSI, SAN disks show a WWN(also bold) output is truncated.
fs0 : Acpi(HWP0002,PNP0A03,100)/Pci(3|0)/Scsi(Pun6,Lun0)/HD(Part1,Sig80AE9EAE-9DB5-11DE-8000-D6217B60E588)
fs1 : Acpi(HWP0002,PNP0A03,100)/Pci(3|0)/Scsi(Pun6,Lun0)/HD(Part3,Sig80AE9F12-9DB5-11DE-8000-D6217B60E588)
fs2 : Acpi(HWP0002,PNP0A03,101)/Pci(1|0)/Pci(4|1)/Scsi(Pun6,Lun0)/HD(Part1,Sig2B540C3C-01A8-11DD-8002-D6217B60E588)
fs3 : Acpi(HWP0002,PNP0A03,0)/Pci(3|0)/Scsi(Pun6,Lun0)/HD(Part1,Sig89D238D4-9FB4-11E1-8002-D6217B60E588)
fs4 : Acpi(HWP0002,PNP0A03,0)/Pci(3|0)/Scsi(Pun6,Lun0)/HD(Part3,Sig89D23906-9FB4-11E1-8004-D6217B60E588)
fs5 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(4|1)/Scsi(Pun5,Lun0)/HD(Part1,SigBE2E924E-A068-11E1-8002-D6217B60E588)
fs6 : Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(4|1)/Scsi(Pun5,Lun0)/HD(Part3,SigBE2E928A-A068-11E1-8004-D6217B60E588)
fs7 : Acpi(HWP0002,PNP0A03,6)/Pci(1|0)/Pci(4|0)/Fibre(WWN50060E80166F4213,Lun4000000000000000)/HD(Part1,SigB790304C-43E0-11E3-8002-D6217B60E588)
fs8 : Acpi(HWP0002,PNP0A03,6)/Pci(1|0)/Pci(4|0)/Fibre(WWN50060E80166F4213,Lun4000000000000000)/HD(Part3,SigB7903088-43E0-11E3-8004-D6217B60E588)
fs9 : Acpi(HWP0002,PNP0A03,6)/Pci(1|0)/Pci(4|0)/Fibre(WWN50060E80166F4213,Lun4001000000000000)/HD(Part1,Sig1177FB50-5AD6-11E4-8002-D6217B60E588)
fsA : Acpi(HWP0002,PNP0A03,6)/Pci(1|0)/Pci(4|0)/Fibre(WWN50060E80166F4213,Lun4001000000000000)/HD(Part3,Sig1177FB82-5AD6-11E4-8004-D6217B60E588)
fsB : Acpi(HWP0002,PNP0A03,E)/Pci(1|0)/Pci(4|1)/Fibre(WWN50060E80166F4273,Lun4000000000000000)/HD(Part1,SigB790304C-43E0-11E3-8002-D6217B60E588)
fsC : Acpi(HWP0002,PNP0A03,E)/Pci(1|0)/Pci(4|1)/Fibre(WWN50060E80166F4273,Lun4000000000000000)/HD(Part3,SigB7903088-43E0-11E3-8004-D6217B60E588)
fsD : Acpi(HWP0002,PNP0A03,E)/Pci(1|0)/Pci(4|1)/Fibre(WWN50060E80166F4273,Lun4001000000000000)/HD(Part1,Sig1177FB50-5AD6-11E4-8002-D6217B60E588)
fsE : Acpi(HWP0002,PNP0A03,E)/Pci(1|0)/Pci(4|1)/Fibre(WWN50060E80166F4273,Lun4001000000000000)/HD(Part3,Sig1177FB82-5AD6-11E4-8004-D6217B60E588)
To set a boot disk you need to fs#:
Then cd /EFI/HPUX and run the bcfg command
In this example, the boot disks for the vpar are fs7: and fsB:
fs7:
cd EFI
cd HPUX
fs7: \EFI\HPUX> bcfg boot add 1 hpux.efi “HPUX primary vpar boot”
fsB: \EFI\HPUX> bcfg boot add 2 hpux.efi “HPUX alternate vpar boot”
Boot menu should look like this:
HPUX primary vpar boot
HPUX alternate vpar boot
LAN [Acpi(HWP0002,PNP0A03,101)/Pci(1|0)/Pci(6|1)/Mac(001F296EAD7
LAN [Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(6|0)/Mac(001E0B83F25E)
LAN [Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(6|1)/Mac(001E0B83F25F)
EFI Shell [Built-in]
Internal DVD (Upper) Cabinet 0 [Acpi(HWP0002,PNP0A03,100)/Pci(3|
Internal DVD (Lower) Cabinet 0 [Acpi(HWP0002,PNP0A03,0)/Pci(3|1)
LAN [Acpi(HWP0002,PNP0A03,101)/Pci(1|0)/Pci(6|0)/Mac(001F296EAD7
HPUX Vpar
Boot Option Maintenance Menu
Recommendation: test both your options.
AUTO file was edited on the OS as follows:
efi_cp -d /dev/rdsk/c18t0d0s1 -u /EFI/HPUX/AUTO AUTO
<edit with vi>
efi_cp -d /dev/rdsk/c18t0d0s1 AUTO /EFI/HPUX/AUTO
Repeat for both boot disks.
root@myvpmon0# lvlnboot -v
Current path “/dev/dsk/c20t0d0s2” is an alternate link, skip.
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c18t0d0s2 (0/0/6/1/0/4/0.1.128.0.0.0.0) — Boot Disk
/dev/dsk/c20t0d0s2 (0/0/14/1/0/4/1.1.140.0.0.0.0)
Boot: lvol1 on: /dev/dsk/c18t0d0s2
/dev/dsk/c20t0d0s2
Root: lvol3 on: /dev/dsk/c18t0d0s2
/dev/dsk/c20t0d0s2
Swap: lvol2 on: /dev/dsk/c18t0d0s2
/dev/dsk/c20t0d0s2
Dump: lvol2 on: /dev/dsk/c18t0d0s2, 0
Tags: AUTO file, efi configuration, efi_cp, hpux, san boot, vpmon
22 Oct 14 fun vpar facts: see vpmon/monitor boot disk path.
When running vpmon/vpar virtualization, any changes made to the vpar database vpardb are automatically saved to:
/stand/vpdb
In fact you can boot vpmon of a disk, stand up the vpars, and reven remove the original vpmon system and boot disk and the database will maintain integrity on the remaining systems.
To sync/verify the vpardb
vparstatus -D /stand/vpdb
vparstatus -m
Console path: No path as console is virtual
Monitor boot disk path: 1.0.4.0.0.0.0.4.0.0.0.1.128.0.0.0.0
Monitor boot filename: /stand/vpmon
Database filename: /stand/vpdb
Memory ranges used: 0x0/349069312 monitor
0x14ce6000/327680 firmware
0x14d36000/417792 monitor
0x14d9c000/925696 firmware
0x14e7e000/1417216 monitor
0x14fd8000/50495488 firmware
0x18000000/134213632 monitor
0x3ffec000/81920 firmware
0x79ffc000000/67108864 firmware
0x89ffc000000/67108864 firmware
will show you what hardware was actually used to boot the vpmon. You may find your monitor disk path no longer exists and your vpars are running just fine.
Tags: hpux vpars, vpar, vparstatus, vpmon
