My Experience Deploying HPE Nimble Storage dHCI – Part 1

This week HPE Nimble Storage dHCI officially became GA, and started to ship from manufacturing to excited customers around the world. Since the platform was announced some 6 weeks ago at HPE Discover, we’ve been met with widespread approval from partners and customers alike… and already taken quite a few orders already from customers excited to get their hands on the next innovation from HPE Nimble Storage.

What has been interesting is the controversy the name has caused from industry greybeards and competitors who proclaim “but it’s not really HCI!”. I had a very heated series of messages inbound from an ex-colleague now at Nutanix who was outraged at the concept (drinking Coolaid 101 – we’re all guilty of it)…

Indeed, Nimble dHCI is a platform converging servers, network and flash storage with the full stack management integration (and single-click firmware upgrade operations) that HCI brings – hence the naming – but without the management gotchas of converged OR the scalability gotchas of hyperconverged. And that is a good thing! It also ties together Infosight full-stack analytics for all components (the first vendor in the industry to do so), as well as HPE Cloud Data Services for multi-cloud connectivity and DRaaS.

dHCI suite of apps and integrations

dHCI Deployment – 15 mins “from rack to app”

I was lucky enough to be able to get my hands on the tech over the last two weeks, and thought i’d write a quick blog or two detailing my experience. In short, i’m impressed with what Engineering have created, especially as a 1.0 release… And it really does have that “Nimble” feel of quality to it all the way through, which is nice to see.

So, we start with the basics; as mentioned above, this is a converged stack consisting of:

  • HPE Proliant DL360/380 Gen9 or Gen10 servers
    • Deployed new, OR already installed / in production.
    • New dHCI-enabled Proliant servers come pre-configured with HPE’s vSphere image, as well as Nimble toolkits installed (and some other customised bits)
  • VMware vSphere 6.7
    • dHCI requires a minimum licensing edition containing vSphere HA, but certainly encourages DRS functionality for 1-click upgrades
    • vCenter is also mandatory
  • Redundant iSCSI 10Gb switching
    • Cisco Nexus 3K/5K/9K, HPE 57xx/59xx, StoreFabric M, Aruba 832x all certified
  • dHCI-enabled Nimble Gen5 AF/HF array
    • It’s not possible to convert a standard array to dHCI, it’s a new factory image.

But there is only ONE point of management for all components – and that is a native vCenter plugin for hosts/network/storage.

After proceeding with the simple task of racking/cabling we are ready to go. First, we configure the Nimble array with standard array configuration details (Group/array names, subnets/IP addresses, DNS, Infosight configuration etc).

Once complete, dHCI redirects us to a new “Stack Setup Manager”. Here, it details what we will do in the setup, as well as parsing some recommended configuration steps for the nework (nice!).

The Stack Setup welcome screen

Next, it will ask us for vCenter information and Cluster information. Here’s a nice touch: If there is no vCenter already deployed (say, this is a new environment being deployed from scratch), Nimble dHCI can push and configure a new vCenter Appliance directly from the array controller into your dHCI cluster, as we bundle the VCSA image in the dHCI code from the factory 🙂

dHCI vCenter screen
Configuring vCenter screen
Configuring Cluster screen

Next, Nimble dHCI will go out onto the network to discover the Proliant DL360/380 servers that are applicable to join a dHCI cluster. It will use SLP to discover the servers, and looks for a series of settings to ensure that the hosts can be added. If the conditions aren’t met, then the server is not able to join a dHCI cluster. These conditions are:

  • HPE Proliant DL360/DL380 G9 or G10
  • HPE ESXi Image (vSphere 6.5 or 6.7
  • dHCI default passwords set
  • Nimble Connection Manager installed
  • 4x 10Gb NICs (2 for prod/mgmt/vMotion, 2 for iSCSI)
  • SLP Enabled

If the host is already deployed with VMware, it also looks for validation conditions, for example vSwitch configuration.

Here you can see that I had discovered 3 eligible HPE servers running DHCP (I blanked out the server serials and model), and 1 “Unsupported Server” discovered – this is a Intel whitebox which doesnt have the right settings, and thus it’s not eligible to be part of dHCI.

After discovering the hosts, it then allows me to push network/subnet settings to the hosts. dHCI will then jump in and configure my ILO, ESXi networking as well as deeper vSwitch / VMKernels / iSCSI configuration. It will also verify the networking to ensure it won’t cause networking conflicts.

Finally, we’re onto configuring what storage we’d like to present to the dHCI cluster. We have the option of deploying VMFS and/or vVols for storage (of course – vVols are the way forward!). Here we can enter the settings for the datastores, as well as any snapshot/replication policy you wish to assign.

dHCI will also create two system reserved VMFS datastores, which is the minimum needed for vSphere HA. An example here could be for VDI, with 2TiB and 90 days worth of daily snapshots being retained.

Moving on to the final screen; a summary of the configuration settings. I’ve chosen two deploy 2 ESXi hosts in my dHCI cluster, with the associated network settings for production as well as iSCSI, and finally you can see a custom VMFS and vVol datastore being provisioned.

dHCI Configuration Summary

If all is good, then we can send the wizard on it’s way to deploy everything for us. I timed exactly how long the wizard took to deploy and configure the whole stack for us – just over 5 minutes for everything, deployed to complete best practices and ready for production!

You can see that we get two options for UI; the vCenter UI (for full-stack management) or to jump into the Nimble UI for further configuration tweaks such as Encryption @ Rest, AD integration, Cloud Volumes integration, Peer Persistence (aka Sync Rep) setup as a few examples (expect these to make their way into the dHCI plugin soon).

As this is a standard Nimble array, we also support provisioning iSCSI storage to non-dHCI servers at this stage.

Pretty cool huh?

In part 2 of this blog, i’ll walkthrough the full-stack dHCI management within vCenter and show off some of the unique coolness we’ve built to make lives simpler for VMware and Cloud admins worldwide!

As always, I’d love to hear from you, so feel free to post a question or comment below 🙂

Cheers for now, and stay Nimble!

16 thoughts on “My Experience Deploying HPE Nimble Storage dHCI – Part 1

  1. Nick, thanks for sharing. i did not see any reference to the switch configuration tasks. will you please add more info?

    Thanks so very much

  2. 2 questions,

    1) what is the DHCI Default passwords. I have 2 brand new DL 360 Gen 10 sold with the DHCI SKEW that came with esxi preinstalled, and i can’t log into them because i don’t know this

    2)I am deploying a DHCI environment into and replacing an existing environment. The existing environment is a Nimble storage along with 2 HPE hosts. The new DHCI will replace all of that. I Don’t want to build a new vCenter and cluster because the existing system has dependencies (Veeam backups, Azure Repplication, etc) that will break and need to be rebuilt\set up if i move my to a new vCenter. How do i add my new DHCI Hosts to the Cluster and migrate off of the old hosts\Cluster? There really seems to be little info for this out in HPE. plus as stated above, i have no clue what the default root password is for the hosts.

    1. Hi!

      1. You shouldn’t have to login to the dHCI imaged ESXi hosts, the new dHCI enabled Nimble array will detect it and deploy for you – and in fact this is exactly how you should go about the install of the hosts and the new dHCI enabled array… That said, the default password is “Prostack123!”

      2. You can easily deploy a new dHCI cluster using an existing vCenter. Check out this video to see how. This will ensure you will still have your current Nimble array and vSphere cluster running, and it will introduce the new dHCI enabled cluster… meaning that you can then go ahead and Storage vMotion the VMs from the old environment to the new.

  3. Hi Nick,

    Thank you for the valuable article.
    I’m stuck with the network configuration. Can You provide more info?

    Have nice day!


      1. Yes, I contacted the support. They say that I should configure the network part on my side.
        I have two hosts (DL360) and a Nimble HF20H. The guys told me That I should create three subnets:
        1- ISCI-1
        2- ISCI-2
        3- Management (need to be routable)

        And 18x CAT6A for 10 Base-T for the networkring.
        Thank you!

    1. Hello,

      There is dHCI training available for accredited HPE Partners. We’re working on a 1-day course for end users as I write this.

Leave a Reply

Your email address will not be published. Required fields are marked *