#NIMBLE STORAGE VMWARE INTEGRATION GUIDE UPDATE#
#NIMBLE STORAGE VMWARE INTEGRATION GUIDE FULL#

a.Д¬lick the Log in to vSphere Web Client (Flash) link Note: If you get a security warning, click ADVANCED then click on the Proceed to link. Type in the address field and press enter. Launch the Chrome browser by clicking on its icon on the Taskbar. Note: If you get a certificate warning, just click Yes to continueД«asic vCenter Configuration Task 1: Register the Nimble Plug-inДЎ. Use the following login credentials and click OK: Type in the IP address provided to you by the lab administrator. Launch a Remote Desktop Connection (RDP) from your client os. The Nimble vCenter plugins allow you to do the following:Д¬reate, clone, grow, and edit datastores Take, clone, and delete snapshots Add Nimble-specific capabilities to vCenter server which can be used to create vCenter roles Edit protection schedules It is part of the NimbleOS but must be registered with vCenter. Registering the vCenter plugin with vCenter allows vCenter to manage VMware datastores on an array. Both provide the same functionality, with slight variances in the user views, and other minor enhancements. You can use either the desktop vCenter plugin, or the web-based vCenter plugin. VMWARE INTEGRATION Background Nimble Storage provides a plugin that works specifically with vCenter to manage datastores residing on Nimble arrays. 16 Task 6: Create a VM on a Nimble-backed Datastore. 14 Task 5: Grow a Nimble-based Datastore. 11 Task 4: Clone a Nimble-based Datastore. 4 Task 3: Create a Nimble-backed Datastore. We attributed this to the fact that CDM uses a single queue depth for their sequential tests causing deflated and non-real world like numbers.Contents VMWARE INTEGRATION. After the updated policies on all paths, we were seeing 400+Mbps for sequential reads/writes using SQLio, but still ~100Mbps using CrystalDiskMark. We had additionally tested with SQLio and found nearly identical results to CrystalDiskMark. We had to ensure we were applying the Round Robin properties to ALL presented iSCSI devices, rather than just the one volume we were targetting for speed testing purposes. After spending a few hours with Nimble support, we finally got to the bottom of it.

#NIMBLE STORAGE VMWARE INTEGRATION GUIDE UPDATE#

Wanted to provide an update on this issue.

#NIMBLE STORAGE VMWARE INTEGRATION GUIDE FULL#

The Windows MPIO may be able to connect to different targets/IPs at once, making full use of all available paths. You could also try to disable RR and switch to MRU, keeping a single path on your ESXi host too and see if that will cause any significant decrease in performance. I don't know how your storage or network is setup, much less how Nimble iSCSI storage works in detail, but this could explain why your maximum throughput never exceeds what a single 1GbE link can offer. It also could be possible that all the iSCSI initiator NICs connect to the same target IP on your Nimble storage, limiting the effective throughput to this one path on the storage side. In my opinion it's actually quite impressive that you have noticeably better numbers on your random access patterns. Please use the well known IOmeter benchmarking tool and compare these numbers with what others in a similar configuarion have posted here:ДЄn important metric missing in the numbers you posted is latency.ДЄnyways, you also shouldn't mind sequential maximum throughput performance numbers too much, those are generally not realistic workloads (as are 512KB IOs). He already mentioned that he used different IOPS settings in his first post, so this shouldn't be the issue. I am at a loss and Nimble Storage have spoken with me and troubleshot this thing and can't figure out what could be wrong.ДЄny input or suggestions would be awesome! Here is the kicker! When I use the iSCSI Initiator with MPIO enabled on my Windows box, on the SAME network, I am seeing increased throughput with even fewer paths connected, except with slightly slower Random Reads/Writes. The Sequential Read and Write are, by their standards, about 1/4th of what they would expect to see. OS : Windows Server 2012 Server Standard Edition (full installation) (ењ†4) I am told by the vendor that we have configured the unit to best practice standards and that nothing is wrong, but the throughput number we are saying are WAY off from what they would normally expect.Дuring a speed test using CrystalDiskMark, we are seeing the following: As far as I can tell, the traffic is being distributed evenly across the NICs at about 22.8MBps or roughly 90MBps combined. I have configured ESXi 5.1 with MPIO and Round Robin enabled, I have tried settings the IOPS to 0, 1, 4 and default of 1000, neither option makes any difference to the throughput.

1x Nimble CS220 12TB iSCSI unit with 4 Active NICS and 4 failover NICs.

2x HP DL560 G8's with 2 8-core Xeons and 128GB of RAM, I have 4 NIC ports dedicated to iSCSI traffic, they are connected to Brocade enterprise class 1GBe switches.

Nimble storage vmware integration guide