Route based IP has vs Route based on Originating Virtual Port

Have a question on those two load balance policy. I know Route based on originating virtual port is recommended for iscsi.

1- Is it best practice to use route based IP hash on iscsi or is it allowed to use ip hash?
if it is yes
2- Can we do muti path?

3 What is direfrencce between multi-path and port binding ?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
1. neither - no teaming - not supported.
2. yes, that is best practice.
3. mutli-path, is more than a single path, two or more to the iSCSI storage, e.g. traffic is leaving the server's VMKernel Portgroups, and passing through different paths to the SAN. Port Binding, is where we bind the iSCSI to a VMKernel Portgroup and NIC, so that nic is used for iSCSI traffic.

so you can have two or more nics, sending iSCSI traffic at the same time to the SAN, causing Active I/O, if a path should fail, service still continues. (and if if you follow my article, you can see how to create it, and if one path fails)

The supported method for iSCSI setup is Port Binding and Multi-path, e.g. no teaming!

see my EE Article, step by step tutorial with screenshots

HOW TO: Add an iSCSI Software Adaptor and Create an iSCSI Multipath Network in VMware vSphere Hypervisor ESXi 5.0

Valid for all versions of ESXi 5.x and 6.x.
sara2000Author Commented:
I have seen in one of my client network , they have  netapp storage configured the vif with alias ip.
He uses "route based ip hash" , is it because multiple target ip in which you are not allowed to port bind and use ip hash?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
We've been doing Best Practice and iSCSI Multi-path, with port binding, since iSCSI was implemented in VMware vSphere. Originally, many admins, configured their storage networks, using teaming, trunking, etherchannel, but this is regarded as legacy design these days.

All our files, have VIFS, vLANS, different IP Addresses

We have all our NetApp, EMC, Dell, verified with Vendor Support before production, and they all commented it is the correct method to do it.

Teaming polices are only specific to multiple nics on a vSwitch.

We can only recommend Best Practice. we cannot comment, on why your client, has it setup this way. - old fashioned ?

Apples and Pears, we still see documents, that have all methods detailed.

If you look here (you'll need to login to NetApp Now Support site)

this latest Express document, just mentions multi-path and port binding now

but in older document dated 2011, the older methods are listed.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sara2000Author Commented:
Thanks for the link  Andrew.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.