<?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: new hba presentation in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933286#M287680</link>
    <description>Hi Xavier,&lt;BR /&gt;&lt;BR /&gt;         As I have mentioned earlier, disabling the port from the switch end for the new HBA should most likely get you booting. I guess, the Server is hung querying the new luns during the boot process. So by disabling the server is not allowed to see those luns anymore, and you can bypass the hung state. Once we boot up , we can run cstm commands on the fc card and check its validity or do some other troubleshooting, But troubleshooting when having multiple times at a time sounds like .."Beating around a wrong bush, Bush never-the-less".... So take it one step at a time....&lt;BR /&gt;</description>
    <pubDate>Fri, 26 Jan 2007 07:39:53 GMT</pubDate>
    <dc:creator>Senthil Kumar .A_1</dc:creator>
    <dc:date>2007-01-26T07:39:53Z</dc:date>
    <item>
      <title>new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933281#M287675</link>
      <description>Hi everybody:&lt;BR /&gt;&lt;BR /&gt;Ok, here is my problem.&lt;BR /&gt;&lt;BR /&gt;I have a two node hpux11.23 ia cluster.&lt;BR /&gt;In each i had one hba with two fibre ports.&lt;BR /&gt;One of them was attached to the switch, the other was not.&lt;BR /&gt;I noted that powerpath was not install either.&lt;BR /&gt;&lt;BR /&gt;The port tha was not attaches got fixed and the disks are now presented by both ways.&lt;BR /&gt;&lt;BR /&gt;here is my ioscan result:&lt;BR /&gt;&lt;BR /&gt;&amp;gt;ioscan -fnC disk&lt;BR /&gt;Class     I  H/W Path        Driver     S/W State   H/W Type     Description&lt;BR /&gt;=============================================================================&lt;BR /&gt;disk      0  0/0/2/0.0.0.0   sdisk      CLAIMED     DEVICE       TEAC    DV-28E-C&lt;BR /&gt;                            /dev/dsk/c0t0d0   /dev/rdsk/c0t0d0&lt;BR /&gt;disk      1  0/1/1/0.0.0     sdisk      CLAIMED     DEVICE       HP 36.4GMAU3036NC&lt;BR /&gt;                            /dev/dsk/c2t0d0     /dev/dsk/c2t0d0s2   /dev/rdsk/c2t0d0    /dev/rdsk/c2t0d0s2&lt;BR /&gt;                            /dev/dsk/c2t0d0s1   /dev/dsk/c2t0d0s3   /dev/rdsk/c2t0d0s1  /dev/rdsk/c2t0d0s3&lt;BR /&gt;disk      2  0/1/1/0.1.0     sdisk      CLAIMED     DEVICE       HP 36.4GMAU3036NC&lt;BR /&gt;                            /dev/dsk/c2t1d0     /dev/dsk/c2t1d0s2   /dev/rdsk/c2t1d0    /dev/rdsk/c2t1d0s2&lt;BR /&gt;                            /dev/dsk/c2t1d0s1   /dev/dsk/c2t1d0s3   /dev/rdsk/c2t1d0s1  /dev/rdsk/c2t1d0s3&lt;BR /&gt;disk      3  0/2/1/0.5.12.0.0.0.0  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t0d0   /dev/rdsk/c5t0d0&lt;BR /&gt;disk      4  0/2/1/0.5.12.0.0.0.1  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t0d1   /dev/rdsk/c5t0d1&lt;BR /&gt;disk      5  0/2/1/0.5.12.0.0.1.0  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t1d0   /dev/rdsk/c5t1d0&lt;BR /&gt;disk      6  0/2/1/0.5.12.0.0.1.1  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t1d1   /dev/rdsk/c5t1d1&lt;BR /&gt;disk      7  0/2/1/0.5.12.0.0.1.2  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t1d2   /dev/rdsk/c5t1d2&lt;BR /&gt;disk      8  0/2/1/0.5.12.0.0.1.3  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t1d3   /dev/rdsk/c5t1d3&lt;BR /&gt;disk      9  0/2/1/0.5.12.0.0.1.4  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t1d4   /dev/rdsk/c5t1d4&lt;BR /&gt;disk     10  0/2/1/0.5.12.0.0.1.6  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t1d6   /dev/rdsk/c5t1d6&lt;BR /&gt;disk     11  0/2/1/0.5.12.0.0.1.7  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t1d7   /dev/rdsk/c5t1d7&lt;BR /&gt;disk     12  0/2/1/0.5.12.0.0.2.0  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t2d0   /dev/rdsk/c5t2d0&lt;BR /&gt;disk     13  0/2/1/0.5.12.0.0.2.1  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t2d1   /dev/rdsk/c5t2d1&lt;BR /&gt;disk     14  0/2/1/0.5.12.0.0.2.2  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t2d2   /dev/rdsk/c5t2d2&lt;BR /&gt;disk     15  0/2/1/0.5.12.0.0.2.3  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c5t2d3   /dev/rdsk/c5t2d3&lt;BR /&gt;disk     16  0/2/1/1.6.12.0.0.0.0  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;                            /dev/dsk/c6t0d0   /dev/rdsk/c6t0d0&lt;BR /&gt;disk     17  0/2/1/1.6.12.0.0.1.0  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     18  0/2/1/1.6.12.0.0.1.1  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     19  0/2/1/1.6.12.0.0.1.2  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     20  0/2/1/1.6.12.0.0.1.3  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     21  0/2/1/1.6.12.0.0.1.4  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     22  0/2/1/1.6.12.0.0.1.6  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     23  0/2/1/1.6.12.0.0.1.7  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     24  0/2/1/1.6.12.0.0.2.0  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     25  0/2/1/1.6.12.0.0.2.1  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     26  0/2/1/1.6.12.0.0.2.2  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;disk     27  0/2/1/1.6.12.0.0.2.3  sdisk      CLAIMED     DEVICE       EMC     SYMMETRIX&lt;BR /&gt;&lt;BR /&gt;As you can see, there are not dispositive files.&lt;BR /&gt;&lt;BR /&gt;I tried to start my SGCLUSTER and the machine halted.&lt;BR /&gt;&lt;BR /&gt;I am not sure what steps do i have to do, ones the disks are presented the new way.&lt;BR /&gt;&lt;BR /&gt;Could you pleas help me ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Jan 2007 05:27:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933281#M287675</guid>
      <dc:creator>Ignacio Javier</dc:creator>
      <dc:date>2007-01-26T05:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933282#M287676</link>
      <description>first you must run insf -e to create the relevant device files&lt;BR /&gt;Then you need to add th erelevant Alternate Link into it's proper VG with the vgextend command, and then import those changes to the other node</description>
      <pubDate>Fri, 26 Jan 2007 05:50:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933282#M287676</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2007-01-26T05:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933283#M287677</link>
      <description>&lt;BR /&gt;Hi:&lt;BR /&gt;&lt;BR /&gt;I have made the insf -e command before you answered. I reboot the system and know is in &lt;BR /&gt;a boot crash cycle.&lt;BR /&gt;&lt;BR /&gt;    System Console is on the Built-In Serial Interface&lt;BR /&gt;Logical volume 64, 0x3 configured as ROOT&lt;BR /&gt;Logical volume 64, 0x2 configured as SWAP&lt;BR /&gt;Logical volume 64, 0x2 configured as DUMP&lt;BR /&gt;    Swap device table:  (start &amp;amp; size given in 512-byte blocks)&lt;BR /&gt;        entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608&lt;BR /&gt;Starting the STREAMS daemons-phase 1&lt;BR /&gt;msgcnt 1 vxfs: mesg 037: vx_metaioerr - vx_dirlook - /dev/root file system meta&lt;BR /&gt;data read error in block 200688&lt;BR /&gt;msgcnt 2 vxfs: mesg 017: vx_dirlook - / file system inode 2812 marked bad incore&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000000        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000010        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000020        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000030        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000040        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000050        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000060        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000070        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000080        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x00000090        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x000000a0        0        0        0        0&lt;BR /&gt;?vxfs msgcnt 2 offset 0x000000b0        0        0&lt;BR /&gt;The device file /dev/rroot does not exist or is not correct.&lt;BR /&gt;Automatic checks of the root file system not performed.&lt;BR /&gt;Calling function e0000000010f73c0 for Shutdown State 8 type 0x2&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;What should i do know ? I guess to start up in lvm mode right ?&lt;BR /&gt;&lt;BR /&gt;Could you be a little more specific with the comands i have to execute ? Or if you know any documentation where is described ??&lt;BR /&gt;&lt;BR /&gt;Thanks a lot&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Jan 2007 06:08:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933283#M287677</guid>
      <dc:creator>Ignacio Javier</dc:creator>
      <dc:date>2007-01-26T06:08:07Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933284#M287678</link>
      <description>Hi Javier,&lt;BR /&gt;&lt;BR /&gt;    First you need to get the system booting before you can do any remedies to the io_tree or device files. So if you have access to the SAN switch conencted to this host login ito it and disable the switch port from the switch end and let the system boot completely. Or if you have a SAN team ask them to disable the switch port connected to new HBA. By booting the system we might get more opportunity to troubleshoot and also an opportunity to install powerpath if required. &lt;BR /&gt;&lt;BR /&gt;     If it were a brocade silkworm switch...&lt;BR /&gt;&lt;BR /&gt;Admin&amp;gt;alishow *HOSTNAME* (find the nport)&lt;BR /&gt;Lets say nport is 0x5f6400 then, the port is connected to switch with domain id "95" and aread id "100". login to that switch and run switchshow and find the "slot and port" of the area ID 100 and issue the following command.&lt;BR /&gt;&lt;BR /&gt;Admin&amp;gt; portdisable slot_id/port_id&lt;BR /&gt;&lt;BR /&gt;Then get your system booting......</description>
      <pubDate>Fri, 26 Jan 2007 06:35:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933284#M287678</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2007-01-26T06:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933285#M287679</link>
      <description>&lt;BR /&gt;Hi:&lt;BR /&gt;&lt;BR /&gt;More info.&lt;BR /&gt;&lt;BR /&gt;First of all I installed powerpath, but i didnÂ´t made the insf -e command, the vgextend and export to other nodes as the previos answers tells.&lt;BR /&gt;Powerpath was not "seeing" the new alternate path. &lt;BR /&gt;I made then the insf -e command and then powermt display displayed the correct information. &lt;BR /&gt;&lt;BR /&gt;Finally i reboot the system and know i am blocked because of the boot error.&lt;BR /&gt;&lt;BR /&gt;Could you please help me booting the system ? I could i correct the boot problem ?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Jan 2007 06:48:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933285#M287679</guid>
      <dc:creator>Ignacio Javier</dc:creator>
      <dc:date>2007-01-26T06:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933286#M287680</link>
      <description>Hi Xavier,&lt;BR /&gt;&lt;BR /&gt;         As I have mentioned earlier, disabling the port from the switch end for the new HBA should most likely get you booting. I guess, the Server is hung querying the new luns during the boot process. So by disabling the server is not allowed to see those luns anymore, and you can bypass the hung state. Once we boot up , we can run cstm commands on the fc card and check its validity or do some other troubleshooting, But troubleshooting when having multiple times at a time sounds like .."Beating around a wrong bush, Bush never-the-less".... So take it one step at a time....&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Jan 2007 07:39:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933286#M287680</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2007-01-26T07:39:53Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933287#M287681</link>
      <description>My itention is to let you revert back the changes.....before we proceed further...</description>
      <pubDate>Fri, 26 Jan 2007 07:40:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933287#M287681</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2007-01-26T07:40:39Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933288#M287682</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;Hi:&lt;BR /&gt;&lt;BR /&gt;Ok, i will talk with the SAN group but...i did not post the worse part....:(&lt;BR /&gt;&lt;BR /&gt;System Panic:&lt;BR /&gt;&lt;BR /&gt;panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????&lt;BR /&gt;Stack Trace:&lt;BR /&gt;  IP                  Function Name&lt;BR /&gt;  0xe000000000f46580  vfs_mountroot+0x1d0&lt;BR /&gt;  0xe000000001247220  im_preinitrc+0x300&lt;BR /&gt;  0xe000000001614350  DoCalllist+0x3a0&lt;BR /&gt;End of Stack Trace&lt;BR /&gt;&lt;BR /&gt;linkstamp:          Thu Jan 25 15:49:33 MET 2007&lt;BR /&gt;_release_version:   @(#) $Revision: vmunix:    B11.23_LR FLAVOR=perf Fri Aug 29&lt;BR /&gt;22:35:38 PDT 2003 $&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;It seems that there is a problem with the disk...&lt;BR /&gt;&lt;BR /&gt;what do you think ?&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Fri, 26 Jan 2007 07:58:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933288#M287682</guid>
      <dc:creator>Ignacio Javier</dc:creator>
      <dc:date>2007-01-26T07:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: new hba presentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933289#M287683</link>
      <description>Javier,&lt;BR /&gt;&lt;BR /&gt;   Sounds like, its failing to configure some drivers, thus failing to recognize or mount the FS. I would wait for more experienced admin to respond with their past experience before, you start following my previous suggestions....&lt;BR /&gt;&lt;BR /&gt;   Have you tried calling in HP support center. Passing on this error messages to them , can get you solutions faster sometimes, because they can get WTEC engineers, if it were more serious...</description>
      <pubDate>Fri, 26 Jan 2007 09:17:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/new-hba-presentation/m-p/3933289#M287683</guid>
      <dc:creator>Senthil Kumar .A_1</dc:creator>
      <dc:date>2007-01-26T09:17:10Z</dc:date>
    </item>
  </channel>
</rss>

