<?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: Node WWN and Port WWN in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608978#M175</link>
    <description>Hi Oliver,&lt;BR /&gt;&lt;BR /&gt;I am havng the same question as Oscar. &lt;BR /&gt;&lt;BR /&gt;As your mentioned, in OS other than HP-UX, how does setting the Node WWN equal for all HBAs in a server, help prevent routes from different HBAs over the same ISLs and force using different ISLs for I/O traffic ?&lt;BR /&gt;&lt;BR /&gt;Can you give me more insight on this?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
    <pubDate>Mon, 26 Apr 2010 06:50:05 GMT</pubDate>
    <dc:creator>arkie</dc:creator>
    <dc:date>2010-04-26T06:50:05Z</dc:date>
    <item>
      <title>Node WWN and Port WWN</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608976#M173</link>
      <description>What is the difference between the Node World Wide Name and the Port World Wide Name in a Fiber Channel environment ?</description>
      <pubDate>Wed, 07 Nov 2001 14:04:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608976#M173</guid>
      <dc:creator>Jdamian</dc:creator>
      <dc:date>2001-11-07T14:04:41Z</dc:date>
    </item>
    <item>
      <title>Re: Node WWN and Port WWN</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608977#M174</link>
      <description>Hello Damian,&lt;BR /&gt;the Port WWN is used for login of the device to the switch to get a 24Bit address (NPortID). The switch recognizes the node with the Port WWN. The Node WWN is used for upper layer protocols. With other OS then HP-UX the Node WWN will be set equal for all HBAs located in a server. The reason is to prevent routes from different HBAs over the same ISLs and to force using different ISLs for I/O traffic (this works with Emulex HBAs). With HP-UX the Node WWN will be the same for different ports of one single HBA (i.e. on a 2port HBA which is not yet sold be HP)&lt;BR /&gt;&lt;BR /&gt;Hope that helps&lt;BR /&gt;&lt;BR /&gt;-Oliver-</description>
      <pubDate>Wed, 07 Nov 2001 17:44:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608977#M174</guid>
      <dc:creator>Oliver Haensel</dc:creator>
      <dc:date>2001-11-07T17:44:07Z</dc:date>
    </item>
    <item>
      <title>Re: Node WWN and Port WWN</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608978#M175</link>
      <description>Hi Oliver,&lt;BR /&gt;&lt;BR /&gt;I am havng the same question as Oscar. &lt;BR /&gt;&lt;BR /&gt;As your mentioned, in OS other than HP-UX, how does setting the Node WWN equal for all HBAs in a server, help prevent routes from different HBAs over the same ISLs and force using different ISLs for I/O traffic ?&lt;BR /&gt;&lt;BR /&gt;Can you give me more insight on this?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Mon, 26 Apr 2010 06:50:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608978#M175</guid>
      <dc:creator>arkie</dc:creator>
      <dc:date>2010-04-26T06:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: Node WWN and Port WWN</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608979#M176</link>
      <description>... 9 years later!&lt;BR /&gt;&lt;BR /&gt;@arkie, open your own thread!</description>
      <pubDate>Mon, 26 Apr 2010 09:11:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/node-wwn-and-port-wwn/m-p/2608979#M176</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-04-26T09:11:17Z</dc:date>
    </item>
  </channel>
</rss>

