<?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: Alternate Link in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432292#M649370</link>
    <description>from the information you have provided, I believe you have a NIKE array connected to the system.&lt;BR /&gt;If this is so, I also believe that you do not have auto trespass set on on the array, as I believe the array will not allow you to present a pv with the scsi address different on the two array controllers, i.e. c1t0d0 should be c2t0d0 and c1t1d0 should be seen as c2t2d0.&lt;BR /&gt;I think I am right in this assumption, but it is a long timew since I played with a NIKE array. If this is the case, then the disk at c1t0d0 is NOT the same as the disk at c2t1d0.&lt;BR /&gt;check your array for it's configuration settings.</description>
    <pubDate>Mon, 24 Jul 2000 09:50:05 GMT</pubDate>
    <dc:creator>melvyn burnard</dc:creator>
    <dc:date>2000-07-24T09:50:05Z</dc:date>
    <item>
      <title>Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432288#M649366</link>
      <description>When i am trying to configure the alternate link to VG vgtr,&lt;BR /&gt;&lt;BR /&gt;# vgextend vgtr /dev/dsk/c2t1d0 &lt;BR /&gt;&lt;BR /&gt;getting the following massage: &lt;BR /&gt;&lt;BR /&gt;vgextend: Physical Volume "/dev/dsk/c2t1d0" contains no LVM information.&lt;BR /&gt;&lt;BR /&gt;VG vgtr is currently on /dev/dsk/c1t1d0 and &lt;BR /&gt;/dev/dsk/c2t1d0 &amp;amp; /dev/dsk/c2t1d0 represents the same disk.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Jul 2000 06:33:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432288#M649366</guid>
      <dc:creator>warghade</dc:creator>
      <dc:date>2000-07-24T06:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432289#M649367</link>
      <description>Double check the hardware address of both disks and make sure that both are pointing to the same physical disks. &lt;BR /&gt;&lt;BR /&gt;1. Perform diskinfo on both disks and look for size&lt;BR /&gt;2. Physically check that, the disk is being shared across the both channels.</description>
      <pubDate>Mon, 24 Jul 2000 06:48:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432289#M649367</guid>
      <dc:creator>Manju Kampli</dc:creator>
      <dc:date>2000-07-24T06:48:37Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432290#M649368</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;what is the output from:&lt;BR /&gt;pvdisplay /dev/dsk/c1t1d0&lt;BR /&gt;and&lt;BR /&gt;pvdisplay /dev/dsk/c2t1d0&lt;BR /&gt;Could you see the devices by&lt;BR /&gt;ioscan -fnC disk ?&lt;BR /&gt;Please post the vgdisplay -v vgtr to the forum to see more detail.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Mon, 24 Jul 2000 06:49:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432290#M649368</guid>
      <dc:creator>Andreas Voss</dc:creator>
      <dc:date>2000-07-24T06:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432291#M649369</link>
      <description>Currnetly VG vgtr is on /dev/dsk/c1t0d0.&lt;BR /&gt;# pvdisplay /dev/dsk/c1t0d0&lt;BR /&gt;--- Physical volumes ---&lt;BR /&gt;PV Name                     /dev/dsk/c1t0d0&lt;BR /&gt;VG Name                     /dev/vgtr&lt;BR /&gt;PV Status                   available&lt;BR /&gt;Allocatable                 yes&lt;BR /&gt;VGDA                        2&lt;BR /&gt;Cur LV                      13&lt;BR /&gt;PE Size (Mbytes)            4&lt;BR /&gt;Total PE                    12615&lt;BR /&gt;Free PE                     0&lt;BR /&gt;Allocated PE                12615&lt;BR /&gt;Stale PE                    0&lt;BR /&gt;IO Timeout (Seconds)        default&lt;BR /&gt;&lt;BR /&gt;# pvdisplay /dev/dsk/c2t1d0&lt;BR /&gt;  pvdisplay: Couldn't find the volume group to which&lt;BR /&gt;physical volume "/dev/dsk/c2t1d0" belongs.&lt;BR /&gt;pvdisplay: Cannot display physical volume "/dev/dsk/c2t1d0". &lt;BR /&gt;&lt;BR /&gt;# ioscan -fnCdisk&lt;BR /&gt;Class     I  H/W Path    Driver      S/W State H/W Type  Description&lt;BR /&gt;=====================================================================&lt;BR /&gt;disk      0  8/4.5.0     sdisk       CLAIMED   DEVICE    SEAGATE ST34572WC&lt;BR /&gt;                        /dev/dsk/c0t5d0   /dev/rdsk/c0t5d0&lt;BR /&gt;disk      1  8/4.8.0     sdisk       CLAIMED   DEVICE    SEAGATE ST34572WC&lt;BR /&gt;                        /dev/dsk/c0t8d0   /dev/rdsk/c0t8d0&lt;BR /&gt;disk      2  8/8.0.0     sdisk       CLAIMED   DEVICE    DGC     C2300WDR5&lt;BR /&gt;                        /dev/dsk/c1t0d0   /dev/rdsk/c1t0d0&lt;BR /&gt;disk      3  8/8.0.1     sdisk       CLAIMED   DEVICE    DGC     C2300WDR5&lt;BR /&gt;                        /dev/dsk/c1t0d1   /dev/rdsk/c1t0d1&lt;BR /&gt;disk      4  8/12.1.0    sdisk       CLAIMED   DEVICE    DGC     C2300WDR5&lt;BR /&gt;                        /dev/dsk/c2t1d0   /dev/rdsk/c2t1d0&lt;BR /&gt;disk      6  8/16/5.2.0  sdisk       CLAIMED   DEVICE    TOSHIBA CD-ROM XM-5701T&lt;BR /&gt;A &lt;BR /&gt;</description>
      <pubDate>Mon, 24 Jul 2000 09:09:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432291#M649369</guid>
      <dc:creator>warghade</dc:creator>
      <dc:date>2000-07-24T09:09:45Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432292#M649370</link>
      <description>from the information you have provided, I believe you have a NIKE array connected to the system.&lt;BR /&gt;If this is so, I also believe that you do not have auto trespass set on on the array, as I believe the array will not allow you to present a pv with the scsi address different on the two array controllers, i.e. c1t0d0 should be c2t0d0 and c1t1d0 should be seen as c2t2d0.&lt;BR /&gt;I think I am right in this assumption, but it is a long timew since I played with a NIKE array. If this is the case, then the disk at c1t0d0 is NOT the same as the disk at c2t1d0.&lt;BR /&gt;check your array for it's configuration settings.</description>
      <pubDate>Mon, 24 Jul 2000 09:50:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432292#M649370</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2000-07-24T09:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432293#M649371</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Do a vgchange -a y /dev/vgtr. Use the command  strings /etc/lvmtab check the output for /dev/vgtr. Copy /etc/lvmtab to /etc/lvmtab.2407 and then use vgscan to scan all physical volumes in order to allow for recovery of the lvm configuration file (/etc/lvmtab).</description>
      <pubDate>Mon, 24 Jul 2000 10:03:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432293#M649371</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-07-24T10:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432294#M649372</link>
      <description>Just another quick item.  LVM commands want the full absolute path to all devices on the command line.  Your command should be # vgextend /dev/vgtr /dev/dsk/c2t1d0</description>
      <pubDate>Mon, 24 Jul 2000 14:07:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432294#M649372</guid>
      <dc:creator>Tim Malnati</dc:creator>
      <dc:date>2000-07-24T14:07:02Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432295#M649373</link>
      <description>Yet no improvement...&lt;BR /&gt;&lt;BR /&gt;Thanks to all of you.</description>
      <pubDate>Tue, 25 Jul 2000 04:34:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432295#M649373</guid>
      <dc:creator>warghade</dc:creator>
      <dc:date>2000-07-25T04:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432296#M649374</link>
      <description>Okay, you have a Nike.&lt;BR /&gt;&lt;BR /&gt;As pointed out, you MUST have autotrespass feature enabled. From your ioscan it seems it is not the case (LUN 0 is always "seen" on both controllers (SPs), but not accessible). To enable autotrespass, set your system option package to 2 (can be done from Grid Manager, in FE mode I believe).&lt;BR /&gt;&lt;BR /&gt;Once autotrespass is enabled, you should have no problem to do your vgextend.&lt;BR /&gt;&lt;BR /&gt;One important point: be sure to set the primary link thru the controller (SP) which is the DEFAULT owner of the LUN (by default the SP which created the LUN). Otherwise you will have performance issues.&lt;BR /&gt;&lt;BR /&gt;Hope it helps, Emmanuel</description>
      <pubDate>Tue, 25 Jul 2000 11:32:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432296#M649374</guid>
      <dc:creator>Emmanuel Eyer</dc:creator>
      <dc:date>2000-07-25T11:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432297#M649375</link>
      <description>For a disk which has a primary and an alternate link only the controller part of the the device file will change that is cXtYdZ Here Y and Z will remaim the same.&lt;BR /&gt;From your pvdisplay it says the device file as /dev/dsk/c1t0d0 so the alternate link may be /dev/dsk/c2t0d0 so try to extend the vg ti this device file.&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Aug 2000 00:37:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432297#M649375</guid>
      <dc:creator>R D SUNDAR RAJAN</dc:creator>
      <dc:date>2000-08-11T00:37:05Z</dc:date>
    </item>
    <item>
      <title>Re: Alternate Link</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432298#M649376</link>
      <description>Have a look at this response for all the info you need relating to configuration of a Nike array.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x696e7e990647d4118fee0090279cd0f9,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x696e7e990647d4118fee0090279cd0f9,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Fri, 06 Jul 2001 09:09:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/alternate-link/m-p/2432298#M649376</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2001-07-06T09:09:17Z</dc:date>
    </item>
  </channel>
</rss>

