<?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: Reusing WWNs in Virtual Connect in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262824#M17047</link>
    <description>I am guessing that you may have been using the factor default WWN that was on the mezz card that you replaced and not virtual VC generated WWNs. If that is true, then really nothing that you can do to avoid changing the SAN configuration. However, if you were indeed using virtual VC generated WWNs, then it should work. I have personally moved profiles across blades and changed mezz cards on many occasions and the original WWNs get used and it all works like a charm.&lt;BR /&gt;&lt;BR /&gt;Please double check and provide more details.</description>
    <pubDate>Tue, 16 Nov 2010 13:03:38 GMT</pubDate>
    <dc:creator>SunnyS</dc:creator>
    <dc:date>2010-11-16T13:03:38Z</dc:date>
    <item>
      <title>Reusing WWNs in Virtual Connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262822#M17045</link>
      <description>All,&lt;BR /&gt;We have an dual-port HBA that only has one port working in the fabric.  We've replaced the HBA and discovered that the problem is with the profile in Virtual Connect.  We'd created a new profile and that solved the problem of the ports communicating with the SAN.  The only issue is that we would have to re-zone/mask them at the SAN.  Is there a way to manually assign/reuse the old virtual WWN's on the new profile?</description>
      <pubDate>Mon, 15 Nov 2010 19:48:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262822#M17045</guid>
      <dc:creator>Brett Simpson</dc:creator>
      <dc:date>2010-11-15T19:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: Reusing WWNs in Virtual Connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262823#M17046</link>
      <description>Hi Brett,&lt;BR /&gt;&lt;BR /&gt;if i understand your issue correctly, you do use one of the HP predefined WWN adress ranges, correct ? (and not the FC HBA factory default WWN's )&lt;BR /&gt;&lt;BR /&gt;Not sure then why this does not work b/c re-applying the original profile should just write the WWN from that profile into the new FC HBA and you should be all set.... Apparently this did not work for you.&lt;BR /&gt;&lt;BR /&gt;Never ran in to this issue, replaced FC HBA cards before but it worked as expected in my case.&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Nov 2010 08:29:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262823#M17046</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2010-11-16T08:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: Reusing WWNs in Virtual Connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262824#M17047</link>
      <description>I am guessing that you may have been using the factor default WWN that was on the mezz card that you replaced and not virtual VC generated WWNs. If that is true, then really nothing that you can do to avoid changing the SAN configuration. However, if you were indeed using virtual VC generated WWNs, then it should work. I have personally moved profiles across blades and changed mezz cards on many occasions and the original WWNs get used and it all works like a charm.&lt;BR /&gt;&lt;BR /&gt;Please double check and provide more details.</description>
      <pubDate>Tue, 16 Nov 2010 13:03:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262824#M17047</guid>
      <dc:creator>SunnyS</dc:creator>
      <dc:date>2010-11-16T13:03:38Z</dc:date>
    </item>
    <item>
      <title>Re: Reusing WWNs in Virtual Connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262825#M17048</link>
      <description>Kris,&lt;BR /&gt;You are correct that we are using the pre-defined, virtual WWN's and not the actual HBA WWN's.  &lt;BR /&gt;&lt;BR /&gt;Here's the issue:  The profile that we were using is the problem.  When we created a different profile, both ports of the HBA worked, but had different virtual WWN's.  We want to blow away the original profile and reuse the WWN's associated with it so that we don't have to remask/rezone on the SAN side.  BTW, we're still using the original HBA.</description>
      <pubDate>Tue, 16 Nov 2010 14:14:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262825#M17048</guid>
      <dc:creator>Brett Simpson</dc:creator>
      <dc:date>2010-11-16T14:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: Reusing WWNs in Virtual Connect</title>
      <link>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262826#M17049</link>
      <description>I spoke with HP support and was informed that this feature is not available at this time.</description>
      <pubDate>Tue, 16 Nov 2010 18:11:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/reusing-wwns-in-virtual-connect/m-p/5262826#M17049</guid>
      <dc:creator>Brett Simpson</dc:creator>
      <dc:date>2010-11-16T18:11:24Z</dc:date>
    </item>
  </channel>
</rss>

