Please advice - LIF

[Prashant Zanwar_4]

Hi,
I have a query. I am pasting some output below about my server. I just wanna confirm if my server is alright as far as booting is concerned. Please advice on the below:

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Root: lvol3 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Swap: lvol2 on: /dev/dsk/c1t2d0
/dev/dsk/c2t2d0
Dump: lvol2 on: /dev/dsk/c1t2d0, 0

# lifls /dev/rdsk/c1t2d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO HPUX ISL
AUTO LABEL

root@crdushp5:/var/adm/sox

# lifls /dev/rdsk/c2t2d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD
SLDEV SLDRIVERS SLSCSI MAPPER IOTEST
PERFVER PVCU SSINFO ISL AUTO
HPUX PAD LABEL

The LIF information is differing. There is PAD file on secondary but not on Primary. And also the files do differ by name. Please advise on this issue. Let me know if any other information needed. And Also if anything which I can do without making the server down.
Thanks
Rgdz
Prashant

[Rick Garland]

Do not see any problems.

What else are you trying to do? Or what else are you wanting to know without rebooting?

[Geoff Wild]

Interesting, I have PAD on both my disks - how did you setup mirroring? Also, what OS level is this?

This is how I do it:

1. Create a bootable LVM disk to be used for the mirror.
pvcreate -B /dev/rdsk/c3t6d0
2. Add this disk to the current root volume group.
vgextend /dev/vg00 /dev/dsk/c3t6d0
3. Make the new disk a boot disk.
mkboot -l /dev/rdsk/c3t6d0
4. Copy the correct AUTO file into the new LIF area.
mkboot -a "hpux -lq (;0)/vmunix" /dev/rdsk/c3t6d0
5. Mirror the boot, root and primary swap logical volumes to the new
bootable disk. Ensure that all devices in vg00, such as /usr, /swap,
etc., are mirrored.
The following is an example of mirroring the boot logical volume:
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c3t6d0
The following is an example of mirroring the primary swap logical
volume:
lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c3t6d0
The following is an example of mirroring the root logical volume:
lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c3t6d0
6. Update the boot information contained in the BDRA for the mirror
copies of boot, primary swap and root.
/usr/sbin/lvlnboot -b /dev/vg00/lvol1
/usr/sbin/lvlnboot -s /dev/vg00/lvol2
/usr/sbin/lvlnboot -r /dev/vg00/lvol3
7. Check if the BDRA is correct.
/usr/sbin/lvlnboot -R /dev/vg00
8. Verify that the mirrors were properly created.
lvlnboot -v /dev/vg00
The output of this command is shown in a display like the following:
Boot Definitions for Volume Group /dev/vg00:
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (1/0/0/3/0.6.0) -- Boot Disk
/dev/dsk/c3t6d0 (1/0/1/0/0/1/1.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0
/dev/dsk/c3t6d0
Root: lvol3 on: /dev/dsk/c0t6d0
/dev/dsk/c3t6d0
Swap: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c3t6d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0


Rgds...Geoff

[Patrick Wallek · Accepted solution]

When you mirrored, it appears that one of the steps you did was to use the 'updatediaglif' command.

I bet you did something like:

# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t2d0

Now, if this machine is running 64-bit HP-UX, you should have used updatediaglif2.

updatediaglif is for 32-bit systems. updatediaglif2 is for 64-bit systems.

You might try this and see if your lifls output matches:

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t2d0

[Prashant Zanwar_4]

Thanks guys for responses.
I am just new to this project. It was done sometimes back when I wasnt in here. I just started working recently.
I have both the files

# ls -al /usr/sbin/diag/lif/updatediaglif*
-r--r--r-- 1 bin bin 848896 Jan 26 2004 /usr/sbin/diag/lif/updatediaglif
-r--r--r-- 1 bin bin 1033216 Jan 26 2004 /usr/sbin/diag/lif/updatediaglif2

The command which you mentioned, can that be executed on system without any harm when system is up. What can be problem while I do that. And which file I shall use,
updatediaglif or updatediaglif2.

Thanks and regards
Prashant

[Patrick Wallek]

updatediaglif/updatediaglif2 can be executed while the system is up.

Which one you use depends entirely on what type of system you have and what HP-UX "bitness" you are running.

# getconf KERNEL_BITS

If the output above is 64, then /dev/rdsk/c2t2d0 needs to be modified as I mentioned above with updatediaglif2.

If the output above is 32, then /dev/rdsk/c1t2d0 needs to be modified as I described above with updatediaglif.

[Steven E. Protter]

Looks okay but if you REALLY want to be sure, get up a maintenance window and test it.

SEP

[Prashant Zanwar_4]

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t2d0.
I have executed the above command and after that all other part matches as below except the PAD file. I want to ask..
-What is the PAD file?
# lifls /dev/dsk/c1t2d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO HPUX ISL
AUTO LABEL
# lifls /dev/dsk/c2t2d0
ODE MAPFILE SYSLIB CONFIGDATA SLMOD2
SLDEV2 SLDRV2 SLSCSI2 MAPPER2 IOTEST2
PERFVER2 PVCU SSINFO ISL AUTO
HPUX PAD LABEL
-Does it really required in boot process.
Please reply
Thanks and regards
Prashant

[Sundar_7]

Prashant,

PAD file is just a space-filler, as the name implies.

Even if PAD file is missing, you will still be able to boot.

So, dont bother if this file is missing from the LIF volume.

-- Sundar.

[Prashant Zanwar_4]

I am closing this thread as per above comments. i have to test the boot yet.
Thanks and regards
Prashant