<?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 Nimble and Nimble dHCI differences in HPE Nimble Storage Solution Specialists</title>
    <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167161#M560</link>
    <description>&lt;P&gt;Hi everyone, could someone please explain to me the differences between Nimble and Nimble dHCI? From what I know Simplivity is true HCI, so the storage is provided by local disks by the DL380 servers and exposed to the other servers through a virtual machine in a VMware environment. With Nimble dHCI instead the DL380 servers use the storage provided by Nimble via iSCSI protocol ... so I don't understand what HCI has to do with it since there are no local disks. Initially I thought VVOLs were involved, but VVOLs are also supported by Nimble or Primera ... i.e. they are not a unique feature of dHCI ... so I don't understand ...&lt;/P&gt;</description>
    <pubDate>Fri, 27 May 2022 03:35:21 GMT</pubDate>
    <dc:creator>Lucavmw</dc:creator>
    <dc:date>2022-05-27T03:35:21Z</dc:date>
    <item>
      <title>Nimble and Nimble dHCI differences</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167161#M560</link>
      <description>&lt;P&gt;Hi everyone, could someone please explain to me the differences between Nimble and Nimble dHCI? From what I know Simplivity is true HCI, so the storage is provided by local disks by the DL380 servers and exposed to the other servers through a virtual machine in a VMware environment. With Nimble dHCI instead the DL380 servers use the storage provided by Nimble via iSCSI protocol ... so I don't understand what HCI has to do with it since there are no local disks. Initially I thought VVOLs were involved, but VVOLs are also supported by Nimble or Primera ... i.e. they are not a unique feature of dHCI ... so I don't understand ...&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2022 03:35:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167161#M560</guid>
      <dc:creator>Lucavmw</dc:creator>
      <dc:date>2022-05-27T03:35:21Z</dc:date>
    </item>
    <item>
      <title>Re: Nimble and Nimble dHCI differences</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167162#M561</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2060213"&gt;@Lucavmw&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;The idea with dHCI is that it is &lt;EM&gt;like&lt;/EM&gt; HCI, except with the added flexibility of the storage being "disaggregated" and not tied to your server hosts.&lt;/P&gt;&lt;P&gt;So, as compared to non-dHCI Nimble or Alletra 6000 storage, you get added benefits such as the following:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;single support call to Nimble Storage Support for the whole stack (servers/storage/switches)&lt;/LI&gt;&lt;LI&gt;easy server host management (additions/configuration, removals, updates) via the dHCI vCenter plugin&lt;/LI&gt;&lt;LI&gt;server hosts added into InfoSight without the need for iLO Amplifier Pack&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 26 May 2022 16:19:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167162#M561</guid>
      <dc:creator>SprinkleJames</dc:creator>
      <dc:date>2022-05-26T16:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Nimble and Nimble dHCI differences</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167184#M562</link>
      <description>&lt;P&gt;In addition to what&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1503940"&gt;@SprinkleJames&lt;/a&gt;&amp;nbsp;said:&lt;BR /&gt;Unified updates across the stack: Nimble OS, ESXi HPE image, SPP, iLo firmware&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 22:13:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167184#M562</guid>
      <dc:creator>mamatadesaiNim</dc:creator>
      <dc:date>2022-05-26T22:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: Nimble and Nimble dHCI differences</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167205#M563</link>
      <description>&lt;P&gt;Thank you James and Nim,&amp;nbsp;for sure I will have to study and deepen the dHCI, but I would like to take the opportunity to clarify some important points:&lt;BR /&gt;- "single support call": let me understand: if I buy a DL380G10 and a Nimble, the support is different than a dHCI (which from the hardware point of view would be the same thing?)&lt;BR /&gt;- "dHCI vCenter plugin": this is interesting and I will deepen it!&lt;BR /&gt;- "InfoSight": I don't know exactly what the "iLO Amplifier Pack" is but I suppose it is necessary for a Nimble or Alletra if I want to integrate them with Infosight? Is it?&lt;BR /&gt;- If I buy a Nimble and DL380 (single components and not bundled dHCI) I could use the Nimble with any physical Hypervisor and server, while in the dHCI version I can only use them with VMware, am I right?&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2022 07:36:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167205#M563</guid>
      <dc:creator>Lucavmw</dc:creator>
      <dc:date>2022-05-27T07:36:06Z</dc:date>
    </item>
    <item>
      <title>Re: Nimble and Nimble dHCI differences</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167246#M564</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2060213"&gt;@Lucavmw&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;- "single support call": let me understand: if I buy a DL380G10 and a Nimble, the support is different than a dHCI (which from the hardware point of view would be the same thing?)&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;If you buy a DL380 Gen10 and a Nimble, and, for example, something in your server fails, you have to open a case with regular HPE support as per your warranty or contract. With dHCI, if that server is part of the dHCI cluster, you have the option to open the case with the Nimble Support group and they would be able to handle it. I would prefer the Nimble Support, as it's often a better experience in general.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;- "InfoSight": I don't know exactly what the "iLO Amplifier Pack" is but I suppose it is necessary for a Nimble or Alletra if I want to integrate them with Infosight? Is it?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;iLO Amplifier Pack is a&amp;nbsp;free virtual appliance which is intended to help automate server firmware management, among other things. It collects the health data from your servers and sends it to InfoSight, and is necessary if you want to integrate your non-dHCI&amp;nbsp;servers with InfoSight. iLO Amplifier Pack is not needed for the storage arrays, and it's also not needed for the&amp;nbsp;&lt;EM&gt;servers&lt;/EM&gt; that are part of your dHCI cluster because the dHCI storage array handles the InfoSight integration for those servers.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;- If I buy a Nimble and DL380 (single components and not bundled dHCI) I could use the Nimble with any physical Hypervisor and server, while in the dHCI version I can only use them with VMware, am I right?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;dHCI requires the storage array and at least two servers running VMware to form the dHCI cluster. Once you have that intially set up and running, you can do anything else with the Nimble that you could with a non-dHCI Nimble, such as attaching other servers that are outside of your dHCI cluster.&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2022 15:38:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167246#M564</guid>
      <dc:creator>SprinkleJames</dc:creator>
      <dc:date>2022-05-27T15:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: Nimble and Nimble dHCI differences</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167323#M567</link>
      <description>&lt;P&gt;Thank you very much!&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2022 06:18:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7167323#M567</guid>
      <dc:creator>Lucavmw</dc:creator>
      <dc:date>2022-05-30T06:18:34Z</dc:date>
    </item>
    <item>
      <title>Re: Nimble and Nimble dHCI differences</title>
      <link>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7241369#M1358</link>
      <description>&lt;P&gt;no a DHCI array can still have ISCSI and FC hosts that are not part of vmware environment.&amp;nbsp; &amp;nbsp;A DHCI array can do anything a standard nimble/alletra 5/6k can but has integration with vcenter and the whole DHCI environment can be upgraded with 1 click.&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2025 20:41:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-nimble-storage-solution/nimble-and-nimble-dhci-differences/m-p/7241369#M1358</guid>
      <dc:creator>Emil Velez_2</dc:creator>
      <dc:date>2025-05-01T20:41:53Z</dc:date>
    </item>
  </channel>
</rss>

