<?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: lifls command in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466096#M210895</link>
    <description>HP document LVMKBRC00005103, How to create a Mirrored Boot Disk on PA-RISC Systems - Cookbook, has information on how to mirror a root disk, at the bottom is a way to update the LIF files on a boot disk. The relevant section of the cookbook is below.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Installation of Offline Diagnostics (ODE) on Mirrored Boot Disks&lt;BR /&gt;&lt;BR /&gt;The following hardware support tools are distributed on the Support Plus Media in the OnlineDiag swinstall bundle:&lt;BR /&gt;&lt;BR /&gt;Support Tools Manager (STM) &lt;BR /&gt;EMS Hardware Monitors &lt;BR /&gt;HP Predictive Support tools (Series 800 only) &lt;BR /&gt;LIF-resident offline diagnostics (ODE) &lt;BR /&gt;There is an easy way to install the ODE to the mirror if you have already installed the OnlineDiag bundle.&lt;BR /&gt;&lt;BR /&gt;First, check if your system is a pure 64 bit system:&lt;BR /&gt;&lt;BR /&gt; # getconf HW_CPU_SUPP_BITS&lt;BR /&gt;The result is either 32, 32/64 or 64. If the system is a pure 64 bit systems (e.g. N-Class) the result is 64.&lt;BR /&gt;&lt;BR /&gt;Check the existence of the updatediaglif and updatediaglif2 files:&lt;BR /&gt;&lt;BR /&gt;# ll /usr/sbin/diag/lif/updatediaglif*&lt;BR /&gt;&lt;BR /&gt;-r--r--r--   1 bin   bin   848896 May  7 17:29 /usr/sbin/diag/lif/updatediaglif&lt;BR /&gt;-r--r--r--   1 bin   bin   865280 May  7 17:29 /usr/sbin/diag/lif/updatediaglif2&lt;BR /&gt;&lt;BR /&gt;We will use the updatediaglif2 file only for pure 64 bit systems (e.g. N-Class). For 32 bit systems or systems that support both CPU types (e.g K-Class) we use the updatediaglif file.&lt;BR /&gt;&lt;BR /&gt;List the contents of the LIF directory of the mirror:&lt;BR /&gt;&lt;BR /&gt; # lifls -l /dev/rdsk/c0t5d0&lt;BR /&gt;volume ISL10 data size 7984 directory size 8 96/05/28 04:10:13&lt;BR /&gt;filename   type   start   size     implement  created&lt;BR /&gt;===============================================================&lt;BR /&gt;ISL        -12800 584     240      0          96/05/28 04:10:13&lt;BR /&gt;AUTO       -12289 824     1        0          96/05/28 04:10:13&lt;BR /&gt;HPUX       -12928 832     848      0          96/05/28 04:10:13&lt;BR /&gt;PAD        -12290 1680    1652     0          96/05/28 04:10:14&lt;BR /&gt;LABEL      BIN    3336    8        0          99/01/25 06:00:41&lt;BR /&gt;&lt;BR /&gt;Install the ODE LIF files with mkboot and protect (-p) the existing LIF files which you detected with lifls as described above.&lt;BR /&gt;&lt;BR /&gt;For 32 bit and systems that support both 32 and 64 bit:&lt;BR /&gt;&lt;BR /&gt; # mkboot -b /usr/sbin/diag/lif/updatediaglif \&lt;BR /&gt; -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c0t5d0&lt;BR /&gt;For pure 64 bit systems:&lt;BR /&gt;&lt;BR /&gt; # mkboot -b /usr/sbin/diag/lif/updatediaglif2 \&lt;BR /&gt; -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c0t5d0&lt;BR /&gt;Check with&lt;BR /&gt;&lt;BR /&gt; # lifls /dev/rdsk/c0t5d0&lt;BR /&gt;One will find additional LIF files.&lt;BR /&gt;&lt;BR /&gt;volume ISL10 data size 7984 directory size 8 96/05/28 04:10:13&lt;BR /&gt;filename   type   start   size     implement  created&lt;BR /&gt;===============================================================&lt;BR /&gt;ODE        -12960 584     880      0          03/05/06 20:27:48&lt;BR /&gt;MAPFILE    -12277 1464    128      0          03/05/06 20:27:48&lt;BR /&gt;SYSLIB     -12280 1592    353      0          03/05/06 20:27:48&lt;BR /&gt;CONFIGDATA -12278 1952    249      0          03/05/06 20:27:48&lt;BR /&gt;SLMOD      -12276 2208    133      0          03/05/06 20:27:48&lt;BR /&gt;SLDEV      -12276 2344    204      0          03/05/06 20:27:48&lt;BR /&gt;SLDRIVERS  -12276 2552    496      0          03/05/06 20:27:48&lt;BR /&gt;SLSCSI     -12276 3048    117      0          03/05/06 20:27:48&lt;BR /&gt;MAPPER     -12279 3168    234      0          03/05/06 20:27:48&lt;BR /&gt;IOTEST     -12279 3408    208      0          03/05/06 20:27:48&lt;BR /&gt;PERFVER    -12279 3616    198      0          03/05/06 20:27:48&lt;BR /&gt;PVCU       -12801 3816    64       0          03/05/06 20:27:48&lt;BR /&gt;SSINFO     -12286 3880    2        0          03/05/06 20:27:48&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
    <pubDate>Wed, 19 Jan 2005 09:00:55 GMT</pubDate>
    <dc:creator>Geoff Wild</dc:creator>
    <dc:date>2005-01-19T09:00:55Z</dc:date>
    <item>
      <title>lifls command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466090#M210889</link>
      <description>The vg00 is mirored between /dev/dsk/c0t6d0 and /dev/dsk/c3t6d0, when I used lifls command to show the HD information,&lt;BR /&gt;&lt;BR /&gt;test#[/]lifls /dev/rdsk/c0t6d0&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;test#[/]lifls /dev/rdsk/c3t6d0&lt;BR /&gt;ISL          AUTO         HPUX         PAD          LABEL&lt;BR /&gt;&lt;BR /&gt;I wondered why the information was different between these two mirrored harddisks?&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Jan 2005 01:54:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466090#M210889</guid>
      <dc:creator>eric2</dc:creator>
      <dc:date>2005-01-19T01:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: lifls command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466091#M210890</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;#diskinfo /dev/rdsk/c0t6d0&lt;BR /&gt;#diskinfo /dev/rdsk/c3t6d0&lt;BR /&gt;&lt;BR /&gt;what's the o/p of both the commands?</description>
      <pubDate>Wed, 19 Jan 2005 02:13:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466091#M210890</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2005-01-19T02:13:19Z</dc:date>
    </item>
    <item>
      <title>Re: lifls command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466092#M210891</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;see the following link.it clearly describes about this problem&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=92005" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=92005&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regds,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Jan 2005 02:22:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466092#M210891</guid>
      <dc:creator>bhavin asokan</dc:creator>
      <dc:date>2005-01-19T02:22:25Z</dc:date>
    </item>
    <item>
      <title>Re: lifls command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466093#M210892</link>
      <description>diskinfo command only show the hardware infor about the harddisk, I think it doesn't concern this.&lt;BR /&gt;&lt;BR /&gt;test#diskinfo /dev/rdsk/c0t6d0&lt;BR /&gt;SCSI describe of /dev/rdsk/c0t6d0:&lt;BR /&gt;             vendor: HP 36.4G&lt;BR /&gt;         product id: STXXXXXXXX&lt;BR /&gt;               type: direct access&lt;BR /&gt;               size: 35566480 Kbytes&lt;BR /&gt;   bytes per sector: 512&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Jan 2005 02:29:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466093#M210892</guid>
      <dc:creator>eric2</dc:creator>
      <dc:date>2005-01-19T02:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: lifls command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466094#M210893</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Propably you might have dumped this command while creating mirror&lt;BR /&gt;&lt;BR /&gt;mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p LABEL /dev/rdsk/c3t6d0</description>
      <pubDate>Wed, 19 Jan 2005 02:45:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466094#M210893</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2005-01-19T02:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: lifls command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466095#M210894</link>
      <description>It is correct, only the following LIF files are required on both disks:&lt;BR /&gt;ISL; AUTO; HPUX; PAD&lt;BR /&gt;The rest are diagnostic utilities for HP-UX.&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Jan 2005 03:04:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466095#M210894</guid>
      <dc:creator>twang</dc:creator>
      <dc:date>2005-01-19T03:04:25Z</dc:date>
    </item>
    <item>
      <title>Re: lifls command</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466096#M210895</link>
      <description>HP document LVMKBRC00005103, How to create a Mirrored Boot Disk on PA-RISC Systems - Cookbook, has information on how to mirror a root disk, at the bottom is a way to update the LIF files on a boot disk. The relevant section of the cookbook is below.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Installation of Offline Diagnostics (ODE) on Mirrored Boot Disks&lt;BR /&gt;&lt;BR /&gt;The following hardware support tools are distributed on the Support Plus Media in the OnlineDiag swinstall bundle:&lt;BR /&gt;&lt;BR /&gt;Support Tools Manager (STM) &lt;BR /&gt;EMS Hardware Monitors &lt;BR /&gt;HP Predictive Support tools (Series 800 only) &lt;BR /&gt;LIF-resident offline diagnostics (ODE) &lt;BR /&gt;There is an easy way to install the ODE to the mirror if you have already installed the OnlineDiag bundle.&lt;BR /&gt;&lt;BR /&gt;First, check if your system is a pure 64 bit system:&lt;BR /&gt;&lt;BR /&gt; # getconf HW_CPU_SUPP_BITS&lt;BR /&gt;The result is either 32, 32/64 or 64. If the system is a pure 64 bit systems (e.g. N-Class) the result is 64.&lt;BR /&gt;&lt;BR /&gt;Check the existence of the updatediaglif and updatediaglif2 files:&lt;BR /&gt;&lt;BR /&gt;# ll /usr/sbin/diag/lif/updatediaglif*&lt;BR /&gt;&lt;BR /&gt;-r--r--r--   1 bin   bin   848896 May  7 17:29 /usr/sbin/diag/lif/updatediaglif&lt;BR /&gt;-r--r--r--   1 bin   bin   865280 May  7 17:29 /usr/sbin/diag/lif/updatediaglif2&lt;BR /&gt;&lt;BR /&gt;We will use the updatediaglif2 file only for pure 64 bit systems (e.g. N-Class). For 32 bit systems or systems that support both CPU types (e.g K-Class) we use the updatediaglif file.&lt;BR /&gt;&lt;BR /&gt;List the contents of the LIF directory of the mirror:&lt;BR /&gt;&lt;BR /&gt; # lifls -l /dev/rdsk/c0t5d0&lt;BR /&gt;volume ISL10 data size 7984 directory size 8 96/05/28 04:10:13&lt;BR /&gt;filename   type   start   size     implement  created&lt;BR /&gt;===============================================================&lt;BR /&gt;ISL        -12800 584     240      0          96/05/28 04:10:13&lt;BR /&gt;AUTO       -12289 824     1        0          96/05/28 04:10:13&lt;BR /&gt;HPUX       -12928 832     848      0          96/05/28 04:10:13&lt;BR /&gt;PAD        -12290 1680    1652     0          96/05/28 04:10:14&lt;BR /&gt;LABEL      BIN    3336    8        0          99/01/25 06:00:41&lt;BR /&gt;&lt;BR /&gt;Install the ODE LIF files with mkboot and protect (-p) the existing LIF files which you detected with lifls as described above.&lt;BR /&gt;&lt;BR /&gt;For 32 bit and systems that support both 32 and 64 bit:&lt;BR /&gt;&lt;BR /&gt; # mkboot -b /usr/sbin/diag/lif/updatediaglif \&lt;BR /&gt; -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c0t5d0&lt;BR /&gt;For pure 64 bit systems:&lt;BR /&gt;&lt;BR /&gt; # mkboot -b /usr/sbin/diag/lif/updatediaglif2 \&lt;BR /&gt; -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c0t5d0&lt;BR /&gt;Check with&lt;BR /&gt;&lt;BR /&gt; # lifls /dev/rdsk/c0t5d0&lt;BR /&gt;One will find additional LIF files.&lt;BR /&gt;&lt;BR /&gt;volume ISL10 data size 7984 directory size 8 96/05/28 04:10:13&lt;BR /&gt;filename   type   start   size     implement  created&lt;BR /&gt;===============================================================&lt;BR /&gt;ODE        -12960 584     880      0          03/05/06 20:27:48&lt;BR /&gt;MAPFILE    -12277 1464    128      0          03/05/06 20:27:48&lt;BR /&gt;SYSLIB     -12280 1592    353      0          03/05/06 20:27:48&lt;BR /&gt;CONFIGDATA -12278 1952    249      0          03/05/06 20:27:48&lt;BR /&gt;SLMOD      -12276 2208    133      0          03/05/06 20:27:48&lt;BR /&gt;SLDEV      -12276 2344    204      0          03/05/06 20:27:48&lt;BR /&gt;SLDRIVERS  -12276 2552    496      0          03/05/06 20:27:48&lt;BR /&gt;SLSCSI     -12276 3048    117      0          03/05/06 20:27:48&lt;BR /&gt;MAPPER     -12279 3168    234      0          03/05/06 20:27:48&lt;BR /&gt;IOTEST     -12279 3408    208      0          03/05/06 20:27:48&lt;BR /&gt;PERFVER    -12279 3616    198      0          03/05/06 20:27:48&lt;BR /&gt;PVCU       -12801 3816    64       0          03/05/06 20:27:48&lt;BR /&gt;SSINFO     -12286 3880    2        0          03/05/06 20:27:48&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Wed, 19 Jan 2005 09:00:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lifls-command/m-p/3466096#M210895</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2005-01-19T09:00:55Z</dc:date>
    </item>
  </channel>
</rss>

