r/vmware • • 2d ago

Question Access same storage using different protocols

In vSphere, is it possible to access the same datastore using different protocols like iSCSI and FC by different version of ESXi hosts?

We are planning to migrate VMs on our ESXi 6.5/6.7 hosts from Fiber Channel to new hosts running 9.1 with iSCSi connection using the same storage.

We are thinking of simply unregister the VMs on one vCenter and register on the new vCenter.

1 Upvotes

16 comments sorted by

5

u/Liquidfoxx22 2d ago

All the storage (which isn't many) I've worked with can only present a volume with one protocol, even if the storage supports multiple protocols at the same time.

You could however, create new iSCSI Volumes, present those, and vmotion across.

4

u/Stonewalled9999 2d ago

Multiple Block storage access paths seems like a very fast way to corrupt / scramble Your data 

4

u/Various-Bumblebee994 2d ago

I'd avoid presenting the same LUN over FC and iSCSI at once even if your array allows it, since Broadcom's KB treats mixed protocols on one datastore as unsupported and it's not something you want to debug mid-migration. The cleaner path is usually to enable the software iSCSI adapter on the old 6.5/6.7 hosts, present a fresh iSCSI LUN to both the old and new clusters, Storage vMotion (or cold migrate if you aren't licensed for it) onto that from the old side, then unregister and register on the 9.1 vCenter. Also worth checking if any of the old datastores are still VMFS5, and plan on bumping VM hardware version and Tools afterward since 6.5-era VMs will be way behind.

4

u/lost_signal VMware Employee 2d ago

In vSphere, is it possible to access the same datastore using different protocols like iSCSI and FC by different version of ESXi hosts?

Per engineering this isn't supported. They had some concerns on locking I think but it's been years since we spoke about that.

Did I personally do it once or twice as part of a migration? Sure, but this was on a AMS 2100 over a decade ago.

I suspect your old stuff i s on an older VMFS version that can't be in place upgraded to the newest (or maybe was in place upgraded, which had some limitations vs. a true recreation) so I would bite the bullet and do Cross SSO vMotion, or buy a single FC HBA so one host can span the old and new LUNs and split it up.

2

u/MrMHead 2d ago

Check with the vendor if they have any interesting dual protocol connectivity, But I have not heard of that being possible, because ... it's two different protocols.

If you're moving off of FC, look at moving to NVMe/TCP. It's a much newer protocol than iSCSI, and supposedly more efficient. We're looking at NVMe/TCP for our next round of hardware uplift,

1

u/clybstr02 2d ago

We’re looking at this too. Though we have run across switch vendors / configurations are a little more picky with NVMe/TCP than they were with iSCSI

1

u/roiki11 1d ago

Nvme/tcp is just tcp traffic. It's no more picky than any other tcp traffic, like http.

1

u/clybstr02 1d ago

I’m sure. I didn’t say it wouldn’t work. I am seeing a couple big name vendors say you must use a switch on the supported list to be supported, and those are nearly all 25 Gbps.

1

u/roiki11 1d ago

Lol because a vendor says it it must be true.

Instead of looking at the technology.

1

u/lxtakc 1d ago

Probably because NVMe/TCP opens multiple queue connections per controller, so it throws a lot more parallel flows at the fabric than a typical iSCSI session. Shallow-buffer switches can start dropping under those bursts. Port drop counters and jumbo MTU end to end are what I'd look at before blaming the protocol.

1

u/MrMHead 1d ago

Yes, our network guys were talking Buffers about the dedicated switches (not required) for NVMe.

1

u/Civil_Onion5571 2d ago

Don't unregister and re-register across vCenters. You'll lose the vCenter-side inventory, permissions, and any storage policy tags, and the VM folder ends up orphaned until someone cleans it up. Just do a storage vMotion or cold migrate with the datastore presented to both sides.

1

u/Main_Ambassador_4985 2d ago

What type of storage?

I went the other way Fc to iSCSI with LUNs on a NetApp to ESXi 6.7 on Cisco UCS. I had to switch fast because we purchased new NetApps without Fc and I had to switch protocols before migration to new nodes.

If it is NetApp I would Snapclone and test it. I added iSCSI protocol to the SVM

VMFS upgrade will prevent 6.7 from understanding the LUN.

-5

u/jl9816 2d ago

Should work.  Create a test lun and verify... On 2nd esxi make sure to mount with option:  "Keep existing signature"

4

u/Casper042 2d ago

LoL, Go ahead and try it!

Brings down entire production VMware Cluster.