<?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 Boot-from SAN with host profiles/auto-deploy in Array Setup and Networking</title>
    <link>https://community.hpe.com/t5/array-setup-and-networking/boot-from-san-with-host-profiles-auto-deploy/m-p/6982423#M382</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My team is currently working on deploying vSphere 6.&amp;nbsp; We are wanting to move to boot from SAN in our UCS environment.&amp;nbsp; We have (2) CS-500 FC arrays that are in a cluster together.&amp;nbsp; I have presented a boot volume, then the guy building the server installed ESX and it installed and worked perfectly.&amp;nbsp; The problem is that we want to create host profiles to be able to apply to the other 35 hosts so I can build all the volumes and assign the datastores in one large automated batch.&amp;nbsp; How do we determine within the host profile to look for a specific volume on the Nimble?&amp;nbsp; We can't give it the wwn because it will be different for every boot volume.&amp;nbsp; I have 10 different datastore volumes that will be shared among the hosts all from the Nimble cluster.&amp;nbsp; I need to know how to determine to tell the host that is being installed how to find its boot volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 18 Aug 2015 17:55:13 GMT</pubDate>
    <dc:creator>scole7626</dc:creator>
    <dc:date>2015-08-18T17:55:13Z</dc:date>
    <item>
      <title>Boot-from SAN with host profiles/auto-deploy</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/boot-from-san-with-host-profiles-auto-deploy/m-p/6982423#M382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My team is currently working on deploying vSphere 6.&amp;nbsp; We are wanting to move to boot from SAN in our UCS environment.&amp;nbsp; We have (2) CS-500 FC arrays that are in a cluster together.&amp;nbsp; I have presented a boot volume, then the guy building the server installed ESX and it installed and worked perfectly.&amp;nbsp; The problem is that we want to create host profiles to be able to apply to the other 35 hosts so I can build all the volumes and assign the datastores in one large automated batch.&amp;nbsp; How do we determine within the host profile to look for a specific volume on the Nimble?&amp;nbsp; We can't give it the wwn because it will be different for every boot volume.&amp;nbsp; I have 10 different datastore volumes that will be shared among the hosts all from the Nimble cluster.&amp;nbsp; I need to know how to determine to tell the host that is being installed how to find its boot volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Aug 2015 17:55:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/boot-from-san-with-host-profiles-auto-deploy/m-p/6982423#M382</guid>
      <dc:creator>scole7626</dc:creator>
      <dc:date>2015-08-18T17:55:13Z</dc:date>
    </item>
    <item>
      <title>Re: Boot-from SAN with host profiles/auto-deploy</title>
      <link>https://community.hpe.com/t5/array-setup-and-networking/boot-from-san-with-host-profiles-auto-deploy/m-p/6982424#M383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Stanton,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure if you are referring to UCS Service profiles with a SANboot policy or ESXi host profiles (or both).&amp;nbsp; But in any case you should be fine.&amp;nbsp;&amp;nbsp; Let me dive into some details.&lt;/P&gt;&lt;P&gt;1) There is a single WWNN / WWPN name space with Nimble Storage.&amp;nbsp; So all FC zoning is predicable for every UCS blade /ESX host. (Uses the same target WWPNs in every case)&lt;/P&gt;&lt;P&gt;2) Volume (LUN) masking is done at the initiatorgroup level.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;3) For boot volumes, every initiatorgroup on the Nimble side needs to only include the WWPNs from the correct Service Profile / ESXi host. &lt;/SPAN&gt; &lt;/P&gt;&lt;P&gt;4) Boot volumes are typically all mapped to the same LUN id (0).&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;-&amp;gt; This allows you to use the same LUN id for the UCS service boot policy (or ESXi host profile) regardless of how many boot volumes are created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So long story short, the only thing you need to worry about with the volume creation is just to have an individual initiatorgroup for every Service Profile.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Here is a reference on the UCS side of the house which will show you how to setup appropriate zoning and boot policy.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.nimblestorage.com/Nimble-Storage-SmartStack-FC-GSG.pdf" title="https://www.nimblestorage.com/Nimble-Storage-SmartStack-FC-GSG.pdf"&gt;https://www.nimblestorage.com/Nimble-Storage-SmartStack-FC-GSG.pdf&lt;/A&gt;&amp;nbsp; (&lt;SPAN style="font-size: 13.3333330154419px;"&gt;Reference figure 73 or 74)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let Nimble Support know if you have any further questions.&amp;nbsp; We will be happy to help.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Aug 2015 22:15:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-setup-and-networking/boot-from-san-with-host-profiles-auto-deploy/m-p/6982424#M383</guid>
      <dc:creator />
      <dc:date>2015-08-18T22:15:56Z</dc:date>
    </item>
  </channel>
</rss>

