« Coming soon: A New Multi-Vendor Blog Post from NetApp, EMC, HP, Dell, and VMware | Main | VMware Communities Roundtable Presents a Multivendor iSCSI Podcast »

September 21, 2009

Comments

flooredbystorage

Great blog. One question--are you guys (NetApp and others) recommending one storage protocol over the others? I haven't seen any thing clear cut on protocol selection or have missed it.

Also any pointers on how you envision doing DR from the storage side with iSCSI?

Vaughn Stewart

Floored - great question - I'm writing up the post for next week. As for DR - SRM makes DR with every protocol easy, and NetApp's SRA for SRM allows FC, iSCSI, and NAS data to be executed in the same Recovery Plan!

cheers!

DK

Very informative writeup. My question:

In both this blog entry and in the TR-3749 document, it is mentioned that one best practice is to use flow control w/ "send on" for the endpoints (NetApp/NSeries, ESXi) and "receive desired" or "receive on" for the switches the endpoints connect to.

Setting the flow control on the NetApp/NSeries storage is pretty straightforward, as it is on most switches (e.g., Cisco 6506).

However, so far I haven't been able to find any good documentation on how to set flow control on an ESXi 4 host's vmnic via ESXi 4 or vCenter 4. Is there a way to do this, or should it just not be done at all?

Sander Biemans

Great article,

Any news if iscsi port binding and VMware Vsphere 4 UPDATE 1 is supported by vmware?

I created this setup with one of our customers and it seems to work (2 portgroups, each with a vmkernel and cli added vmkernels to the vmhba33 iscsi initiator).

For the customer it is important that it is supported.

Hope someone can help.

Thanks in advanced.

Kind regards,

Sander Biemans

The comments to this entry are closed.

TRUSTe CLICK TO VERIFY