procedure to recover vg00 for integrity server

[kholikt]

I am writing some procedure for rx4640, rp3440 and rx2600. I am not too sure whether this procedure is applicable for server running vpar and npar. All these boxes are connected to symmetrix and vg00 is boot from FC. We are going to move the servers to new location as a result the disk path is going to change due to zoning but the data in the storage will be still in place as it is using Symmetrix SRDF.

Here what I think I should do to re-configure the vg00 again.
For PA-RISC machine it is straight

1. Boot up from HPUX OS CDROM
2. Go to Recovery Shell
3. At recovery shell run ‘ioscan –funCdisk’ to identiy boot disk
4. Run “lifls /dev/dsk/” to confirm.
5. reboot
6. Interrupt the boot process by hitting any key on the console keyboard so that autoboot/autosearch will not boot the system automatically. The boot console handle (BCH) will display its main menu.

7. From the BCH interface’s main menu, issue the ‘SEA’ or ‘SEARCH’ command to list bootable devices. Locate the boot disk address and type ‘BO ’

8. After you issue the BOOT command, the BCH interface prompts you to specify whether you want to interact with ISL, simply answer ‘Y’

9. From the ISL prompt, enter ‘hpux –lm’ to boot into LVM maintenance mode

10. vgexport /dev/vg00

11. mkdir /dev/vg00

12. mknod /dev/vg00/group c 64 0x000000

13. vgimport –v /dev/vg00 /dev/dsk/

14. mv /etc/lvmtab /etc/lvmtab.old

15. strings /etc/lvmtab #verify the PV path mismatch.

16. vgscan –a –v #this will generate the new lvmtab file

17. vgchange –a y vg00

18. vgdisplay –v vg00

19. lvlnboot –v

20. lvlnboot –r /dev/vg00/lvol3 # for root

21. lvlnboot –s /dev/vg00/lvol2 # for swap

22. lvlnboot –d /dev/vg00/lvol2 # for swap/dump

23. lvlnboot –b /dev/vg00/lvol1

24. lvlnboot –R /dev/vg00

25. lvlnboot –v /dev/vg00

26. vgchange –a n /dev/vg00

27. setboot –p ‘pri path’

28. setboot –a ‘alt path’

29. setboot # to display the boot paths and auto flags:

30. reboot

My questions are:
what is the equivalent procedure for IA machine as I am not familiar with the integrity server?
Instead of boot from recovery shell to check the bootlif can I simply do 'SEA IPL' from the BCH.
For the PA-RISC procedure above, do I need to do anything for the autoboot portion?
Do I really need to remove the lvmtab file and regenerate again, what will happen to other vg which already has an entry inside the /etc/lvmtab file?

[Steven E. Protter]

Shalom,

Depending on the OS version, the lvm portion e.g the part you do after you boot is the same on IA as PA-RISC.

The SEA IPL doesn't work on itanium.

It has a totally different, menu based method of doing this setup.

Docs:
http://docs.hp.com/en/B2355-60105/hpux.efi.1M.html
http://docs.hp.com/en/5991-1247/ch05.html

SEP

[kholikt]

I am running 11.23 for the IA server

[Ivan Krastev]

For setboot autosearch/autoboot you can use (after 28):

setboot -s on -b on


Also add "l pri_path" and "l alt_path" in /stand/bootconf if you change the disks


regards,
ivan

[Torsten.]

Hi,

you wrote
"as a result the disk path is going to change due to zoning" - I don't think so.
The path will change if you are using other switches or ports.

Steps 1 to 5 are good. Note down the pathes, because the search routine won't find the FC devices, you will see the HBAs only.

Different steps in 5 to 8 for Integrity:

Stop the boot process and go to the EFI shell prompt.

Shell> fs0:

where fs0 is the mapping index for the boot device

fs0:\> hpux
(C) Copyright 2004 Hewlett-Packard Development Company, L.P.All rights reserved
HP-UX Boot Loader for IPF -- Revision 2.027
Press Any Key to interrupt Autoboot
\efi\hpux\AUTO ==> boot vmunix
Seconds left till autoboot - 9
Type 'help' for help
HPUX>

HPUX> boot â lm /stand/vmunix

Be aware to use the "s2" devices as the HPUX portion of a boot disk, e.g. c0t6d0s2

See this document, most of the steps regarding the changed pathes are applicable for you

http://docs.hp.com/en/7685/upgrade.pdf

[kholikt]

Just wondering, what is equivalent for integrity of sea, I don't see the attachment mention anything about it. I want to list out all device so that I can choose the disk to boot from

[kholikt]

I have combined the multiple information that I found in various places. As we are changing the fiber switch as well, that's why all address will be changed. I have put in the procedure for integrity as well as 9000. Any comment is welcome