Jason Brooks
Dabbler
- Joined
- Jul 16, 2013
- Messages
- 23
Hello,
I have inherited a freenas system running as a vm under vmware. It is using vmdk files located on a Nimble storage server. the nimble storage system is connected to all of the esxi systms using fibrechannel. I really don't like that they did this. But I need to explore options. I'd like to get away from using the vmdk files.
The back-end filer (Nimble) only has fibrechannel Luns available, I don' t think it does iscsi.
freenas 11.1-u5
vsphere 6.7
I could:
Build a custom LUN to vmware and make them available to freenas with raw device mapping so only freenas would use them?
( I remember RDM was a problem but I wasn't certain it meant only with vmdk files....)
Does freenas (freebsd) support a virtual fibrechannel device so I could connect the LUN directly to freenas? (at least that way vmware would just pass the signals)
What do you all think?
Thank you for your time...
--jason
I have inherited a freenas system running as a vm under vmware. It is using vmdk files located on a Nimble storage server. the nimble storage system is connected to all of the esxi systms using fibrechannel. I really don't like that they did this. But I need to explore options. I'd like to get away from using the vmdk files.
The back-end filer (Nimble) only has fibrechannel Luns available, I don' t think it does iscsi.
freenas 11.1-u5
vsphere 6.7
I could:
Build a custom LUN to vmware and make them available to freenas with raw device mapping so only freenas would use them?
( I remember RDM was a problem but I wasn't certain it meant only with vmdk files....)
Does freenas (freebsd) support a virtual fibrechannel device so I could connect the LUN directly to freenas? (at least that way vmware would just pass the signals)
What do you all think?
Thank you for your time...
--jason