<?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 iSCSI and multiple paths in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/iscsi-and-multiple-paths/m-p/4205379#M4961</link>
    <description>All - &lt;BR /&gt;&lt;BR /&gt;My organization has implemented a LeftHand Networks iSCSI SAN.  I have configured and presented a few volumes to my HP 9000 N-class server running HP-UX 11.11, and so far it is working great.  I would now like to add a 2nd NIC to my HP-UX server to be used in this configuration.  Do I need to create a 2nd IQN name for this NIC, or will the 2nd NIC use the same IQN if the primary NIC fails? &lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;James</description>
    <pubDate>Tue, 27 May 2008 13:42:16 GMT</pubDate>
    <dc:creator>James Colby</dc:creator>
    <dc:date>2008-05-27T13:42:16Z</dc:date>
    <item>
      <title>iSCSI and multiple paths</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/iscsi-and-multiple-paths/m-p/4205379#M4961</link>
      <description>All - &lt;BR /&gt;&lt;BR /&gt;My organization has implemented a LeftHand Networks iSCSI SAN.  I have configured and presented a few volumes to my HP 9000 N-class server running HP-UX 11.11, and so far it is working great.  I would now like to add a 2nd NIC to my HP-UX server to be used in this configuration.  Do I need to create a 2nd IQN name for this NIC, or will the 2nd NIC use the same IQN if the primary NIC fails? &lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;James</description>
      <pubDate>Tue, 27 May 2008 13:42:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/iscsi-and-multiple-paths/m-p/4205379#M4961</guid>
      <dc:creator>James Colby</dc:creator>
      <dc:date>2008-05-27T13:42:16Z</dc:date>
    </item>
  </channel>
</rss>

