What Is Hyperconvergence Or Hci Or Dhci Today Why Its All Worth Knowing – This week HPE Nimble Storage dHCI officially became GA, and began shipping from manufacturing to excited customers around the world. Since the platform was announced at HPE Discover about 6 weeks ago, we’ve received widespread approval from partners and customers alike… and before customers excited to get their hands on the next HPE Nimble Storage innovation. Have already taken some orders. .
Interestingly, the name has caused controversy from industry graybeards and competitors who announce
What Is Hyperconvergence Or Hci Or Dhci Today Why Its All Worth Knowing
. I had a very heated stream of messages from a former colleague now at Nutanix who was outraged at the concept (drinking the Coolaid 101 – we’re all guilty of it)…
Hyper-converged Infrastructure Modernize Your Datacenter
– hence the name – but without the management of converged or the scalability gotchas of hyperconverged. And that’s a good thing! It also connects Infosight full-stack analytics to HPE Cloud Data Services for multi-cloud connectivity and DRaaS across all components (the first vendor to do so in the industry).
I was lucky enough to get my hands on the tech over the last couple of weeks, and thought I’d write a quick blog or two detailing my experience. In short, I’m impressed with what the engineering has created, especially as a 1.0 release… and it really has a “Nimble” quality feel to it, which is nice to see.
But there is only one point of management for all components – and that is a native vCenter plugin for host/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.).
Hpe Nimble Storage Device Database
Once done, dHCI redirects us to a new “Stack Setup Manager”. Here, it details what we’ll be doing in the setup, as well as analyzing some recommended configuration steps for NewWork (nice!).
Next, it will ask us for vCenter information and cluster information. Here’s a nice touch: if no vCenter is already deployed (say it’s a new environment being deployed from scratch), Nimble dHCI pushes a new vCenter appliance directly from the array controller to your dHCI cluster. And can configure, as we bundle. VCSA image in dHCI code from factory 🙂
Next, Nimble will navigate to the dHCI network to discover Proliant DL360/380 servers that are eligible to join the dHCI cluster. It will use SLP to discover servers, and look for a series of settings to ensure that hosts can be added. If the conditions are not met, the server is not able to join the DHCP cluster. These are the conditions:
If the host is already deployed with VMware, it also looks for validation conditions, for example vSwitch configuration.
Iscsi Cloud Storage For Your It Infrastructure
Here you can see that I discovered 3 eligible HPE servers running DHCP (I blanked out the server serials and model), and discovered 1 “unsupported server” – it’s an Intel white box. which does not have the correct settings, and thus is not eligible. To be part of dHCI.
After discovering the hosts, it then allows me to pass the network/subnet settings to the hosts. dHCI will then jump in and configure my ILO, ESXi networking as well as deep vSwitch/VMKernels/iSCSI configuration. It will also verify networking to ensure that it will not cause networking conflicts.
Finally, we are configuring which storage we want to serve to the dHCI cluster. We have the option to deploy VMFS and/or vVols for storage (of course – vVols is the way forward!) Here we list the settings for the datastores as well as any snapshot/replication policies you want to assign. can do
DHCI will also create two system-reserved VMFS datastores, which is the minimum required for vSphere HA. An example here would be for VDI, which maintains 2TiB and 90 days worth of daily snapshots.
Hyperconvergence Infrastructure Systems & Solutions
Move to the final screen; Summary of configuration settings. I’ve chosen two deployed 2 ESXi hosts in my dHCI cluster, with connected network settings for production as well as iSCSI, and finally you can see a custom VMFS and vVol datastore arrangement. what is being done
If everything is fine, we can send the wizard through how to deploy everything for us. I timed exactly how long the wizard took to deploy and configure the entire stack for us – just over 5 minutes for everything, to complete the best practices deployed and ready for production. !
You can see that we get two options for the UI. Jumping into vCenter UI (for full stack management) or Nimble UI for more configuration tweaks like Encryption @ Rest, AD integration, Cloud Volumes integration, Peer Persistence (aka Sync Rep) setup to name a few examples (expect them Make your way into the dHCI plugin soon).
Since this is a standard Nimble array, we also support iSCSI storage provisioning for non-dHCI servers at this stage.
Hci Optimized For Edge, Part 5: Space And Scalability
In Part 2 of this blog, I’ll do a walkthrough of full-stack dHCI management within vCenter and show some unique coolness designed to make lives easier for VMware and cloud admins around the world!
As always, I’d love to hear from you, so feel free to post a question or comment below 🙂
1-click (1) 3PAR (1) permission list (1) arctic wolf (2) backup (1) blacklist (1) ci (2) cloud volume (4) containers (1) cyber (1) cyber security (2) data breach (1) data transfer (2) demo (1) denier (1) dhci (7) hci (3) hpe (5) infosight (4) Kubernetes (1) Lifecycle Management (1) ) nimble dhci (2) nimbleos (3) nimble storage (17) organizations (1) PeerCopy (1) ransomware (1) recovery (1) RMC (1) security (3) siem (1) snapshots (2) soar ( 1) ssl certificate (1) storage (2) upgrade (1) upgrade catalog (1) upgrade (3) vmware (6) vmworld (2) vsphere 7 (1) vvol (1) vvols (6) webinar ( 1) Whitelist (1)
Nick is a field CTO covering Nimble Storage and Cloud Data Services, working for the HPE Intelligent Storage division. Nick was acquired into business by Nimble Storage in 2017. In a recent article, we looked at one of the more exciting technologies currently being deployed in the data center: disaggregated hyperconverged infrastructure (dHCI). In particular, we looked at HPE’s implementation of dHCI as they are a leader in this technology. In essence, dHCI is similar to hyperconverged infrastructure (HCI) in that it allows storage, compute, and networking to be managed from a single management plane (in HPE’s case, from vCenter Server). ; However, unlike HCI, dHCI does not require storage to be deployed in lockstep with compute. dHCI vendors have deliberately decoupled storage from compute to give data centers the freedom to fully scale their deployments, thereby avoiding the resource-stranding problem associated with HCI deployments. This imbalance with HCI deployments is due to fewer applications outgrowing compute requirements than storage speeds. In this article, we’ll dive deeper into the storage aspect of dHCI and see if it can be efficiently managed from the same pane of compute.
Pdf) Study Of Converged Infrastructure & Hyper Converge Infrastructre As Future Of Data Centre
To get a better understanding of storage in a dHCI environment and how HPE’s dHCI solution automates and simplifies the process of configuring and managing dHCI, we deployed it in an environment that contained vCenter Server. were We felt that this would replicate the experiences that users would have when doing an initial dHCI deployment. Our initial dHCI cluster will consist of two compute nodes connected to an HPE Nimble Storage array and managed using vSphere with the HPE dHCI plug-in.
For the compute nodes, we used HPE DL360 Gen10 servers. These servers have dual Intel Xeon 6130 procs, 128GB of RAM, and redundant drives for the OS. VMware ESXi 6.7u1 and the Nimble toolkit come pre-installed on these systems.
For storage, we used HPE Nimble from their AF line. Specifically, an AF20Q array with 12 960GB SSD drives, giving us 5.8 TiB of usable storage. For connectivity, the AF20Q has four 10Gb ports, two of which we used as iSCSI targets, while the other two we used for management.
To connect all the systems, we used HPE FF570 32XGT. The switch has 32 10Gb Base-T, eight 10Gb SFP+, and two 40 Gb QSFP+ ports.
What Is Dhci, Part 1: Topology, Benefits And A Look At Hpe’s Solution — Virtualization Review
Following the HPE Nimble Storage dHCI and VMware vSphere Deployment Guide, we first installed and configured Nimble Storage, then created and added compute nodes, and finally created the cluster. In the sections below, we’ll provide a walkthrough of our experience with this process.
We connected our laptop to the same network as the Nimble Storage Array. Then, we brought up a browser and entered the serial number of the postfixed array with local. This brings up the web-based Nimble Configuration Wizard.
We selected the Sort this array (but do not join a group) option and clicked Next. From the wizard, we created an array name, specific networking parameters, and a password for the array. It took a few minutes to initialize the array, after which it brought up the stack configurator. We logged in as
. The wizard was on top
Related Post "What Is Hyperconvergence Or Hci Or Dhci Today Why Its All Worth Knowing"