<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Please advice - LIF in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858537#M625871</link>
    <description># mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t2d0. &lt;BR /&gt;I have executed the above command and after that all other part matches as below except the PAD file. I want to ask..&lt;BR /&gt;-What is the PAD file? &lt;BR /&gt;# lifls /dev/dsk/c1t2d0 &lt;BR /&gt;ODE          MAPFILE      SYSLIB       CONFIGDATA   SLMOD2       &lt;BR /&gt;SLDEV2       SLDRV2       SLSCSI2      MAPPER2      IOTEST2      &lt;BR /&gt;PERFVER2     PVCU         SSINFO       HPUX         ISL          &lt;BR /&gt;AUTO         LABEL        &lt;BR /&gt;# lifls /dev/dsk/c2t2d0 &lt;BR /&gt;ODE          MAPFILE      SYSLIB       CONFIGDATA   SLMOD2       &lt;BR /&gt;SLDEV2       SLDRV2       SLSCSI2      MAPPER2      IOTEST2      &lt;BR /&gt;PERFVER2     PVCU         SSINFO       ISL          AUTO         &lt;BR /&gt;HPUX         PAD          LABEL&lt;BR /&gt;-Does it really required in boot process. &lt;BR /&gt;Please reply &lt;BR /&gt;Thanks and regards&lt;BR /&gt;Prashant</description>
    <pubDate>Mon, 30 Aug 2004 13:37:18 GMT</pubDate>
    <dc:creator>Prashant Zanwar_4</dc:creator>
    <dc:date>2004-08-30T13:37:18Z</dc:date>
    <item>
      <title>Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858530#M625864</link>
      <description>Hi, &lt;BR /&gt;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: &lt;BR /&gt;&lt;BR /&gt;# lvlnboot -v &lt;BR /&gt;Boot Definitions for Volume Group /dev/vg00:&lt;BR /&gt;Physical Volumes belonging in Root Volume Group:&lt;BR /&gt;        /dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk&lt;BR /&gt;        /dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk&lt;BR /&gt;Boot: lvol1     on:     /dev/dsk/c1t2d0&lt;BR /&gt;                        /dev/dsk/c2t2d0&lt;BR /&gt;Root: lvol3     on:     /dev/dsk/c1t2d0&lt;BR /&gt;                        /dev/dsk/c2t2d0&lt;BR /&gt;Swap: lvol2     on:     /dev/dsk/c1t2d0&lt;BR /&gt;                        /dev/dsk/c2t2d0&lt;BR /&gt;Dump: lvol2     on:     /dev/dsk/c1t2d0, 0&lt;BR /&gt;&lt;BR /&gt;# lifls /dev/rdsk/c1t2d0 &lt;BR /&gt;ODE          MAPFILE      SYSLIB       CONFIGDATA   SLMOD2       &lt;BR /&gt;SLDEV2       SLDRV2       SLSCSI2      MAPPER2      IOTEST2      &lt;BR /&gt;PERFVER2     PVCU         SSINFO       HPUX         ISL          &lt;BR /&gt;AUTO         LABEL        &lt;BR /&gt;&lt;BR /&gt;root@crdushp5:/var/adm/sox&lt;BR /&gt;&lt;BR /&gt;# lifls /dev/rdsk/c2t2d0 &lt;BR /&gt;ODE          MAPFILE      SYSLIB       CONFIGDATA   SLMOD        &lt;BR /&gt;SLDEV        SLDRIVERS    SLSCSI       MAPPER       IOTEST       &lt;BR /&gt;PERFVER      PVCU         SSINFO       ISL          AUTO         &lt;BR /&gt;HPUX         PAD          LABEL        &lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;Thanks&lt;BR /&gt;Rgdz&lt;BR /&gt;Prashant&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Aug 2004 13:08:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858530#M625864</guid>
      <dc:creator>Prashant Zanwar_4</dc:creator>
      <dc:date>2004-08-27T13:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858531#M625865</link>
      <description>Do not see any problems.&lt;BR /&gt;&lt;BR /&gt;What else are you trying to do? Or what else are you wanting to know without rebooting?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Aug 2004 13:12:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858531#M625865</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2004-08-27T13:12:31Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858532#M625866</link>
      <description>Interesting, I have PAD on both my disks - how did you setup mirroring?  Also, what OS level is this?&lt;BR /&gt;&lt;BR /&gt;This is how I do it:&lt;BR /&gt;&lt;BR /&gt;1. Create a bootable LVM disk to be used for the mirror.&lt;BR /&gt;pvcreate -B /dev/rdsk/c3t6d0&lt;BR /&gt;2. Add this disk to the current root volume group.&lt;BR /&gt;vgextend /dev/vg00 /dev/dsk/c3t6d0&lt;BR /&gt;3. Make the new disk a boot disk.&lt;BR /&gt;mkboot -l /dev/rdsk/c3t6d0&lt;BR /&gt;4. Copy the correct AUTO file into the new LIF area.&lt;BR /&gt;mkboot -a "hpux -lq (;0)/vmunix" /dev/rdsk/c3t6d0&lt;BR /&gt;5. Mirror the boot, root and primary swap logical volumes to the new&lt;BR /&gt;bootable disk. Ensure that all devices in vg00, such as /usr, /swap,&lt;BR /&gt;etc., are mirrored.&lt;BR /&gt;The following is an example of mirroring the boot logical volume:&lt;BR /&gt;lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c3t6d0&lt;BR /&gt;The following is an example of mirroring the primary swap logical&lt;BR /&gt;volume:&lt;BR /&gt;lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c3t6d0&lt;BR /&gt;The following is an example of mirroring the root logical volume:&lt;BR /&gt;lvextend -m 1 /dev/vg00/lvol3 /dev/dsk/c3t6d0&lt;BR /&gt;6. Update the boot information contained in the BDRA for the mirror&lt;BR /&gt;copies of boot, primary swap and root.&lt;BR /&gt;/usr/sbin/lvlnboot -b /dev/vg00/lvol1&lt;BR /&gt;/usr/sbin/lvlnboot -s /dev/vg00/lvol2&lt;BR /&gt;/usr/sbin/lvlnboot -r /dev/vg00/lvol3&lt;BR /&gt;7. Check if the BDRA is correct.&lt;BR /&gt;/usr/sbin/lvlnboot -R /dev/vg00&lt;BR /&gt;8. Verify that the mirrors were properly created.&lt;BR /&gt;lvlnboot -v /dev/vg00&lt;BR /&gt;The output of this command is shown in a display like the following:&lt;BR /&gt;Boot Definitions for Volume Group /dev/vg00:&lt;BR /&gt;Boot Definitions for Volume Group /dev/vg00:&lt;BR /&gt;Physical Volumes belonging in Root Volume Group:&lt;BR /&gt;/dev/dsk/c0t6d0 (1/0/0/3/0.6.0) -- Boot Disk&lt;BR /&gt;/dev/dsk/c3t6d0 (1/0/1/0/0/1/1.6.0) -- Boot Disk&lt;BR /&gt;Boot: lvol1 on: /dev/dsk/c0t6d0&lt;BR /&gt;/dev/dsk/c3t6d0&lt;BR /&gt;Root: lvol3 on: /dev/dsk/c0t6d0&lt;BR /&gt;/dev/dsk/c3t6d0&lt;BR /&gt;Swap: lvol2 on: /dev/dsk/c0t6d0&lt;BR /&gt;/dev/dsk/c3t6d0&lt;BR /&gt;Dump: lvol2 on: /dev/dsk/c0t6d0, 0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Fri, 27 Aug 2004 13:17:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858532#M625866</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2004-08-27T13:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858533#M625867</link>
      <description>When you mirrored, it appears that one of the steps you did was to use the 'updatediaglif' command.  &lt;BR /&gt;&lt;BR /&gt;I bet you did something like:&lt;BR /&gt;&lt;BR /&gt;# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t2d0&lt;BR /&gt;&lt;BR /&gt;Now, if this machine is running 64-bit HP-UX, you should have used updatediaglif2.&lt;BR /&gt;&lt;BR /&gt;updatediaglif is for 32-bit systems.  updatediaglif2 is for 64-bit systems.&lt;BR /&gt;&lt;BR /&gt;You might try this and see if your lifls output matches:&lt;BR /&gt;&lt;BR /&gt;#  mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t2d0</description>
      <pubDate>Fri, 27 Aug 2004 13:24:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858533#M625867</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2004-08-27T13:24:48Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858534#M625868</link>
      <description>Thanks guys for responses. &lt;BR /&gt;I am just new to this project. It was done sometimes back when I wasnt in here. I just started working recently. &lt;BR /&gt;I have both the files &lt;BR /&gt;&lt;BR /&gt;# ls -al /usr/sbin/diag/lif/updatediaglif* &lt;BR /&gt;-r--r--r--   1 bin        bin         848896 Jan 26  2004 /usr/sbin/diag/lif/updatediaglif&lt;BR /&gt;-r--r--r--   1 bin        bin        1033216 Jan 26  2004 /usr/sbin/diag/lif/updatediaglif2&lt;BR /&gt;&lt;BR /&gt;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, &lt;BR /&gt;updatediaglif or updatediaglif2. &lt;BR /&gt;&lt;BR /&gt;Thanks and regards&lt;BR /&gt;Prashant&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 27 Aug 2004 13:57:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858534#M625868</guid>
      <dc:creator>Prashant Zanwar_4</dc:creator>
      <dc:date>2004-08-27T13:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858535#M625869</link>
      <description>updatediaglif/updatediaglif2 can be executed while the system is up.  &lt;BR /&gt;&lt;BR /&gt;Which one you use depends entirely on what type of system you have and what HP-UX "bitness" you are running.&lt;BR /&gt;&lt;BR /&gt;# getconf KERNEL_BITS&lt;BR /&gt;&lt;BR /&gt;If the output above is 64, then /dev/rdsk/c2t2d0 needs to be modified as I mentioned above with updatediaglif2.&lt;BR /&gt;&lt;BR /&gt;If the output above is 32, then /dev/rdsk/c1t2d0 needs to be modified as I described above with updatediaglif.</description>
      <pubDate>Fri, 27 Aug 2004 14:27:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858535#M625869</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2004-08-27T14:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858536#M625870</link>
      <description>Looks okay but if you REALLY want to be sure, get up a maintenance window and test it.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 27 Aug 2004 14:46:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858536#M625870</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-08-27T14:46:31Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858537#M625871</link>
      <description># mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c2t2d0. &lt;BR /&gt;I have executed the above command and after that all other part matches as below except the PAD file. I want to ask..&lt;BR /&gt;-What is the PAD file? &lt;BR /&gt;# lifls /dev/dsk/c1t2d0 &lt;BR /&gt;ODE          MAPFILE      SYSLIB       CONFIGDATA   SLMOD2       &lt;BR /&gt;SLDEV2       SLDRV2       SLSCSI2      MAPPER2      IOTEST2      &lt;BR /&gt;PERFVER2     PVCU         SSINFO       HPUX         ISL          &lt;BR /&gt;AUTO         LABEL        &lt;BR /&gt;# lifls /dev/dsk/c2t2d0 &lt;BR /&gt;ODE          MAPFILE      SYSLIB       CONFIGDATA   SLMOD2       &lt;BR /&gt;SLDEV2       SLDRV2       SLSCSI2      MAPPER2      IOTEST2      &lt;BR /&gt;PERFVER2     PVCU         SSINFO       ISL          AUTO         &lt;BR /&gt;HPUX         PAD          LABEL&lt;BR /&gt;-Does it really required in boot process. &lt;BR /&gt;Please reply &lt;BR /&gt;Thanks and regards&lt;BR /&gt;Prashant</description>
      <pubDate>Mon, 30 Aug 2004 13:37:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858537#M625871</guid>
      <dc:creator>Prashant Zanwar_4</dc:creator>
      <dc:date>2004-08-30T13:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858538#M625872</link>
      <description>Prashant,&lt;BR /&gt;&lt;BR /&gt;  PAD file is just a space-filler, as the name implies.&lt;BR /&gt;&lt;BR /&gt;  Even if PAD file is missing, you will still be able to boot.&lt;BR /&gt;&lt;BR /&gt;  So, dont bother if this file is missing from the LIF volume.&lt;BR /&gt;&lt;BR /&gt;-- Sundar.</description>
      <pubDate>Mon, 30 Aug 2004 13:42:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858538#M625872</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2004-08-30T13:42:12Z</dc:date>
    </item>
    <item>
      <title>Re: Please advice - LIF</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858539#M625873</link>
      <description>I am closing this thread as per above comments. i have to test the boot yet. &lt;BR /&gt;Thanks and regards&lt;BR /&gt;Prashant</description>
      <pubDate>Wed, 08 Sep 2004 08:46:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/please-advice-lif/m-p/4858539#M625873</guid>
      <dc:creator>Prashant Zanwar_4</dc:creator>
      <dc:date>2004-09-08T08:46:55Z</dc:date>
    </item>
  </channel>
</rss>

