<?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: FlexFabric Server Profile FlexHBA in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5296897#M32704</link>
    <description>&lt;P&gt;&amp;nbsp;A FlexFabric Adapter&amp;nbsp;FCoE connection&amp;nbsp;cannot be presented to the blade operating system as a Native FC HBA.&amp;nbsp; It will be presented as an FCoE HBA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only way to get a native FC HBA to be presented in the blade operating system is to add a Native FC HBA Mezz card and connect it to a Fibre Channel Interconnect Module.&lt;/P&gt;</description>
    <pubDate>Wed, 10 Aug 2011 18:47:15 GMT</pubDate>
    <dc:creator>HEM_2</dc:creator>
    <dc:date>2011-08-10T18:47:15Z</dc:date>
    <item>
      <title>FlexFabric Server Profile FlexHBA</title>
      <link>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5296405#M32703</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are planning on setting up our c7000 enclsoures we recently procured and had a question regarding the FlexHBA that can be assigned to a server profile. &amp;nbsp;We undersatnd that the SAN traffic within a FlexFabric moduel is FCoE that is converted to nomral FC on exiting the module. &amp;nbsp;The question we had was in the FlexFabric cookbook (&lt;A target="_blank" href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02616817/c02616817.pdf"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02616817/c02616817.pdf&lt;/A&gt;﻿) the scenarios all provision a FCoE card to a profile. &amp;nbsp;I though there was also the ability to assigan a FC FLexHBA to the profile so the OS on the blades sees a FC card not a FCoE HBA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;LI-SPOILER&gt;&amp;nbsp;&lt;/LI-SPOILER&gt;</description>
      <pubDate>Wed, 10 Aug 2011 12:06:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5296405#M32703</guid>
      <dc:creator>asheth</dc:creator>
      <dc:date>2011-08-10T12:06:29Z</dc:date>
    </item>
    <item>
      <title>Re: FlexFabric Server Profile FlexHBA</title>
      <link>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5296897#M32704</link>
      <description>&lt;P&gt;&amp;nbsp;A FlexFabric Adapter&amp;nbsp;FCoE connection&amp;nbsp;cannot be presented to the blade operating system as a Native FC HBA.&amp;nbsp; It will be presented as an FCoE HBA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only way to get a native FC HBA to be presented in the blade operating system is to add a Native FC HBA Mezz card and connect it to a Fibre Channel Interconnect Module.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Aug 2011 18:47:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5296897#M32704</guid>
      <dc:creator>HEM_2</dc:creator>
      <dc:date>2011-08-10T18:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: FlexFabric Server Profile FlexHBA</title>
      <link>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5307073#M32705</link>
      <description>&lt;P&gt;Thanks, &amp;nbsp;we talked to our HP sales engineer. &amp;nbsp;Even though it is a FCoE card the transport layer is still native fiber from the server to the FLex Fabric module. &amp;nbsp;FCoE is how the FlexFabric module transports the traffic within itself. &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 21 Aug 2011 21:15:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5307073#M32705</guid>
      <dc:creator>asheth</dc:creator>
      <dc:date>2011-08-21T21:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: FlexFabric Server Profile FlexHBA</title>
      <link>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5324919#M32706</link>
      <description>Yes and no.&lt;BR /&gt;&lt;BR /&gt;No: Its FCoE leaving the server and Native FC leaving the uplink.&lt;BR /&gt;&lt;BR /&gt;Yes: The Server sees 2 distinct peices of Hardware though, an FC Adapter and a NIC Adapter and the FC Adapter is treated just like any other FC Adapter. Emulex even uses the same Driver stack for traditional FC and FCoE CNAs.&lt;BR /&gt;&lt;BR /&gt;So even though its really FCoE, if you went into Device Manager on Windows for example, you would see 2 FC Cards under Storage and 6 Network cards under Network. Your OS doesn't really need to know about FCoE as long as Emulex/HP provides the aproptiate drivers.</description>
      <pubDate>Wed, 07 Sep 2011 20:32:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/flexfabric-server-profile-flexhba/m-p/5324919#M32706</guid>
      <dc:creator>Casper42</dc:creator>
      <dc:date>2011-09-07T20:32:07Z</dc:date>
    </item>
  </channel>
</rss>

