<?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 FlexFabric Module: Server Profile SAN Fabric configuration in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/flexfabric-module-server-profile-san-fabric-configuration/m-p/2372449#M33136</link>
    <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Aric had a Virtual Connect FlexFabric configuration question:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an enclosure with 4 Virtual Connect FlexFabric modules (Bay 1, 2, 5 and 6).&amp;nbsp; For a number of reasons, it was proposed that the modules be used in the following fashion:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Bay 1 and 2 dedicated to traditional Ethernet traffic and iSCSI traffic&lt;/LI&gt;&lt;LI&gt;Bay 5 and 6 dedicated to fibre channel SAN access&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As it turns out, it appears that there is some challenge with this.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;We need access to all 8 possible FlexNICs associated with the LOMs connected to Bay 1 and 2.&lt;/LI&gt;&lt;LI&gt;When assigning SAN fabrics to a server profile, it appears that I &lt;STRONG&gt;MUST&lt;/STRONG&gt; create linkages (even if left as Unassigned) to Bay 1 and 2 before I can create a linkage to Bay 5 and 6 (aka sequential assignment is required).&lt;/LI&gt;&lt;LI&gt;In performing this linkage to Bay 1 and 2 (which of course link to the LOMs), I also lose the ability to a FlexNIC from each LOM as it appears as a FC HBA.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to know if this is expected behavior and if so why?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Mike had some info for Aric:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;******************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi Aric,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Virtual Connect team confirms that this is expected behavior. The assignment algorithm used is as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;FCoE connections are assigned first (before iSCSI or Ethernet)&lt;/LI&gt;&lt;LI&gt;iSCSI connections are assigned second (after FCoE, before Ethernet)&lt;/LI&gt;&lt;LI&gt;Ethernet connections are assigned last (after FCoE and iSCSI)&lt;/LI&gt;&lt;LI&gt;For each class of connection, connections are assigned in round robin fashion to LOM1a, LOM1b, MEZ1a, MEZ1b, MEZ2a, MEZ2b.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, it is not currently possible to force all FCoE connections to be assigned to the mezz card(s).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*****************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Vincent also joined the conversation:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You actually lose 2 physical functions (LOM1:b and LOM2:b). You’d still be getting 12 FlexNICs (6 from LOM, 6 from mezz) on a half-height ProLiant, instead of 14. Hopefully that should be enough for your customer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Comments or suggestions? Here is the link to the VC FlexFabric cookbook.&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" rel="nofollow" href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02616817/c02616817.pdf"&gt;NEW! - Virtual Connect FlexFabric Cookbook&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 18 Apr 2011 20:30:18 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2011-04-18T20:30:18Z</dc:date>
    <item>
      <title>FlexFabric Module: Server Profile SAN Fabric configuration</title>
      <link>https://community.hpe.com/t5/bladesystem-general/flexfabric-module-server-profile-san-fabric-configuration/m-p/2372449#M33136</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Aric had a Virtual Connect FlexFabric configuration question:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an enclosure with 4 Virtual Connect FlexFabric modules (Bay 1, 2, 5 and 6).&amp;nbsp; For a number of reasons, it was proposed that the modules be used in the following fashion:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Bay 1 and 2 dedicated to traditional Ethernet traffic and iSCSI traffic&lt;/LI&gt;&lt;LI&gt;Bay 5 and 6 dedicated to fibre channel SAN access&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As it turns out, it appears that there is some challenge with this.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;We need access to all 8 possible FlexNICs associated with the LOMs connected to Bay 1 and 2.&lt;/LI&gt;&lt;LI&gt;When assigning SAN fabrics to a server profile, it appears that I &lt;STRONG&gt;MUST&lt;/STRONG&gt; create linkages (even if left as Unassigned) to Bay 1 and 2 before I can create a linkage to Bay 5 and 6 (aka sequential assignment is required).&lt;/LI&gt;&lt;LI&gt;In performing this linkage to Bay 1 and 2 (which of course link to the LOMs), I also lose the ability to a FlexNIC from each LOM as it appears as a FC HBA.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to know if this is expected behavior and if so why?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Mike had some info for Aric:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;******************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hi Aric,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Virtual Connect team confirms that this is expected behavior. The assignment algorithm used is as follows:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;FCoE connections are assigned first (before iSCSI or Ethernet)&lt;/LI&gt;&lt;LI&gt;iSCSI connections are assigned second (after FCoE, before Ethernet)&lt;/LI&gt;&lt;LI&gt;Ethernet connections are assigned last (after FCoE and iSCSI)&lt;/LI&gt;&lt;LI&gt;For each class of connection, connections are assigned in round robin fashion to LOM1a, LOM1b, MEZ1a, MEZ1b, MEZ2a, MEZ2b.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So, it is not currently possible to force all FCoE connections to be assigned to the mezz card(s).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*****************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Vincent also joined the conversation:&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;*********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You actually lose 2 physical functions (LOM1:b and LOM2:b). You’d still be getting 12 FlexNICs (6 from LOM, 6 from mezz) on a half-height ProLiant, instead of 14. Hopefully that should be enough for your customer.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**********************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#000000"&gt;Comments or suggestions? Here is the link to the VC FlexFabric cookbook.&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" rel="nofollow" href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02616817/c02616817.pdf"&gt;NEW! - Virtual Connect FlexFabric Cookbook&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Apr 2011 20:30:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/flexfabric-module-server-profile-san-fabric-configuration/m-p/2372449#M33136</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2011-04-18T20:30:18Z</dc:date>
    </item>
  </channel>
</rss>

