The Itanium-based system's boot process involves the execution of four softwar e components: + CMOS x.

efi After the processor is reset, firmware initializes and tests processors and pl atform. During initialization, the firmware lets a user interrupt and configure CMOS and option ROMs. Then transfers control to E FI, the Extensible Firmware Interface. EFI, in turn, initializes EFI boot and runtime services and launches the Boot Manager. The B oot Manager, which allows loading of EFI application or drivers from EFI defined file system, loads and transfers control to hpux.efi, the HP-UX-specific bootstrap loader. hpux.efi then loads the HP-UX kernel object file from the HP-UX file system to memory and transfers control to the loaded kernel image. The Series 700 and 800 bootstrap process involves the execution of three softwa re components: + pdc (see pdc(1M), + isl (see isl(1M), and + hpux. + option ROM + EFI + Boot Manager + hpu

After the processor is RESET, pdc, the processor-dependent code (firmware), per forms a self-test and initializes the processor. It then loads and transfers control to isl, the operating-system- independent init ial system loader. isl, in turn, loads and transfers control to the hpux utility, the HP-UX-specific bootstrap loader. hpux then dow nloads the HP-UX kernel object file from an HP-UX file system and transfers control to the loadded kernel images. Before installing Service Guard you need to set up a few things in order for the system to work effectively. You will need to mirror the boot disks on both machines, set up Network Time Protocol (NTP), and setup Domain Name Service (DNS ). Export and Import VG from A to b: Export the affected VG completely on host B. On host A create map files and use them to import the VG on host B. Say, the affect VG is vg01. #vgexport vg01 host A: #vgexport -p -v -s -m /tmp/vg01.map vg01 #ll /dev/vg01/group Note the minor number say 0x010000. Copy /tmp/vg01.map onto host B into /tmp. No te the 'p' option. It only does a preview export. host B: #vgexport vg01 #mkdir /dev/vg01 #mknod /dev/vg01/group c 64 0x010000 #vgimport -v -s -m /tmp/vg01.map vg01 Don't run any 'vgchange' commands as the VG is already activated on host A.

1. Create a mapfile: node1# vgexport ??v ??p ??s ??m /tmp/vg01.map vg01 Warning messages indicating that the VG is active should be ignored. 2. Copy mapfile to each other node (rcp, ftp, etc.) node1# rcp /tmp/vg01.map node2:/tmp/vg01.map 3. Note VG minor number and permissions/ownership: apps1:toor-/>ls -al /dev/vg01 4. Export the VG: node2# vgexport vg01 5. Re-create VG directory: node2# mkdir /dev/vg01 6. Re-create VG group special file, use minor number noted above. node2# mknod /dev/vg01/group c 64 0x010000

7. Run vgimport using the copied mapfile: node2# vgimport ??v ??s ??m /tmp/vg01.map vg01 Messages indicating that no backup for this VG may exist should be ignored. 8. Change permissions and ownership of the VG directory and its device special f iles according to the information noted above. 9. Test the activation of the VG in read-only mode and perform vgcfgbackup: node2# vgchange ??a r vg01 node2# vgcfgbackup vg01 node2# vgchange ??a n vg01 After installing Service Guard, check that all the software and patches are inst alled correctly using the following command: # swlist l fileset a state grep i service