<?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 Pathing problem with NetApp in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736152#M548368</link>
    <description>This may not be the right area to post this but I hope someone can help.&lt;BR /&gt;&lt;BR /&gt;We have 2 11.31 boxes connected to a NetApp in a SAN config with 2 FC switches with 8 paths to each LUN created on the NA (4 paths per switch). I created the LUN's on the NA and then used agile naming to refer to the disk/paths. That is, when I added the disk to the VG, I added it via agile naming  to minimize management (1 disk path listed (/dev/disk/disk123 versus 8 paths for each LUN (/dev/dsk/c1t1d1, etc.). &lt;BR /&gt;&lt;BR /&gt;Anyway, now when we look at the pathing via a NA utility (sanlun), 4 paths are marked as primary and 4 are marked as alternate which makes sense. The problem is, 2 of the primary paths should be alternate and 2 of the alternates should be primary due to the way the cabling is laid out on the switches. &lt;BR /&gt;&lt;BR /&gt;Has anyone used sanlun (a NA utility) or have any suggestions on how I can fix these paths so they are correct?&lt;BR /&gt;&lt;BR /&gt;Points will be given!&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;-Gonzo&lt;BR /&gt;</description>
    <pubDate>Mon, 10 Jan 2011 15:06:49 GMT</pubDate>
    <dc:creator>Kevin (Gonzo) Bushman</dc:creator>
    <dc:date>2011-01-10T15:06:49Z</dc:date>
    <item>
      <title>Pathing problem with NetApp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736152#M548368</link>
      <description>This may not be the right area to post this but I hope someone can help.&lt;BR /&gt;&lt;BR /&gt;We have 2 11.31 boxes connected to a NetApp in a SAN config with 2 FC switches with 8 paths to each LUN created on the NA (4 paths per switch). I created the LUN's on the NA and then used agile naming to refer to the disk/paths. That is, when I added the disk to the VG, I added it via agile naming  to minimize management (1 disk path listed (/dev/disk/disk123 versus 8 paths for each LUN (/dev/dsk/c1t1d1, etc.). &lt;BR /&gt;&lt;BR /&gt;Anyway, now when we look at the pathing via a NA utility (sanlun), 4 paths are marked as primary and 4 are marked as alternate which makes sense. The problem is, 2 of the primary paths should be alternate and 2 of the alternates should be primary due to the way the cabling is laid out on the switches. &lt;BR /&gt;&lt;BR /&gt;Has anyone used sanlun (a NA utility) or have any suggestions on how I can fix these paths so they are correct?&lt;BR /&gt;&lt;BR /&gt;Points will be given!&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;-Gonzo&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jan 2011 15:06:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736152#M548368</guid>
      <dc:creator>Kevin (Gonzo) Bushman</dc:creator>
      <dc:date>2011-01-10T15:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: Pathing problem with NetApp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736153#M548369</link>
      <description>WHat does:&lt;BR /&gt;&lt;BR /&gt;sanlun lun show -p&lt;BR /&gt;&lt;BR /&gt;show?&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jan 2011 15:50:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736153#M548369</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-01-10T15:50:26Z</dc:date>
    </item>
    <item>
      <title>Re: Pathing problem with NetApp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736154#M548370</link>
      <description>It sounds to me like the paths in question were zoned backwards.  May be a matter of removing those zoned paths and putting them back in correctly.&lt;BR /&gt;&lt;BR /&gt;I'd recommend you check with your SAN person...&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Rita&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jan 2011 15:53:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736154#M548370</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2011-01-10T15:53:20Z</dc:date>
    </item>
    <item>
      <title>Re: Pathing problem with NetApp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736155#M548371</link>
      <description>BTW.. did you install  the Netapp Santoolkit from &lt;A href="http://now.netapp.com.?" target="_blank"&gt;http://now.netapp.com.?&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Two utilities there would be of interest to you: ntap_config_paths (for PV Link vg's) and enable_ontap_pvlinks (for agile disks, HP-UX 11.31). &lt;BR /&gt;&lt;BR /&gt;Cheers!&lt;BR /&gt;&lt;BR /&gt;We'ce a new NetApp filer but we've slated it to be used for vSPhere/ESX environments at this time.&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jan 2011 15:59:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736155#M548371</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-01-10T15:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: Pathing problem with NetApp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736156#M548372</link>
      <description>Alzhy - You da' man (woman?)!&lt;BR /&gt;&lt;BR /&gt;sanlun shows primary/alternate paths as I described. That's where I got my info to post the question! I'm new to the NA world as we've always used HP arrays in the past, so I'm just figuring out the utilities to manage our new NA. Anyway, sanlun and snapdrive are the only ones I've really used - so far...&lt;BR /&gt;&lt;BR /&gt;We do have the host utilities loaded. I just looked at the man pages for the two utilities you listed (ntap_config_paths and enable_ontap_pvlinks) and they are the solution I am looking for I believe. It will take me some time to figure out how to use them exactly, but they appear to be the solution as they address the exact problem I described.&lt;BR /&gt;&lt;BR /&gt;I'll post back what I find so others can use this info as well.&lt;BR /&gt;&lt;BR /&gt;Thanks so much.&lt;BR /&gt;&lt;BR /&gt;-Gonzo&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jan 2011 16:45:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736156#M548372</guid>
      <dc:creator>Kevin (Gonzo) Bushman</dc:creator>
      <dc:date>2011-01-10T16:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Pathing problem with NetApp</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736157#M548373</link>
      <description>Gonzo,&lt;BR /&gt;&lt;BR /&gt;Alzhy is genderless (for now).&lt;BR /&gt;</description>
      <pubDate>Mon, 10 Jan 2011 16:49:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/pathing-problem-with-netapp/m-p/4736157#M548373</guid>
      <dc:creator>Alzhy</dc:creator>
      <dc:date>2011-01-10T16:49:20Z</dc:date>
    </item>
  </channel>
</rss>

