VMware Cloud Community
simonsecho
Contributor
Contributor

Combining hardware and software iSCSI initiators

We have just implemented a new hybrid storage array within a 5-host cluster.

Of the 5 hosts, two are currently configured to use hardware iSCSI initiators, and the other three are software initiators. Until now this has operated without issue

We have experienced a strange problemwith the new array whereby some datastores were not visible to one of the two hosts which are configured with hardware initiators. On discussing this with the array vendors, they apparently fixed the issue by adding a software initiator into this host, and adding the discovery IP's for the new array. They also took the opportunity to mention that hardware-only initiators are not fully supported!

So, I am looking for some objective views on what is our best approach. As I see it, we have a number of options:

  1. Add software initiators to the two hosts, and then
    1. Remove the discovery IP's for the new array only from the hardware initiators, and retain them as-is to access our existing MSA, or
    2. Strip the config from the hardware initiators and move entirely to using software initiators only.
  2. Add the software initiators, and the discovery IP's in the software initiators and leave them in the hardware initiators too (and yes, I am aware this is not supported by VMware, but have listed it only to cover all the bases).

However, I have some supplementary concerns. When the array vendor added in the software initiator, they did not include the VMKernel port bindings. If we were to retain the configured hardware initiators, should the port bindings not also be included? Or does this cause some kind of conflict with the port bindings on the hardware initiators?

All our hosts are currently on ESXi 5.1

So, can anyone shed some light on the most advisable course of action, and indicate whether the suggested changes come with any warnings?

Cheers!

Reply
0 Kudos
0 Replies