![how to add hosts to the iscsi storage in vcenter 6.5 how to add hosts to the iscsi storage in vcenter 6.5](https://i.ytimg.com/vi/nRVabvHFH4Q/maxresdefault.jpg)
- #HOW TO ADD HOSTS TO THE ISCSI STORAGE IN VCENTER 6.5 SOFTWARE#
- #HOW TO ADD HOSTS TO THE ISCSI STORAGE IN VCENTER 6.5 PASSWORD#
It happened when I went into the ESXi, defined the new CHAP password and the clicked the discover button in VMware's GUI. It wasn't long afterward that I felt like I was home again after a long rocky journey into NFS land.
![how to add hosts to the iscsi storage in vcenter 6.5 how to add hosts to the iscsi storage in vcenter 6.5](http://vcloud-lab.com/files/images/VMware-vsphere-vcenter-esxi-software-iscsi-storage-configuration-diagram-multipathing-3260-port-iqn-iscsi-initiator-configuration.png)
I setup the target, portal, initiator, authorized access (CHAP), device extent and then associated the target with the extent. Then the other day I went into my FreeNAS box and decided to have another look at iSCSI configuration.
![how to add hosts to the iscsi storage in vcenter 6.5 how to add hosts to the iscsi storage in vcenter 6.5](https://www.jorgedelacruz.es/wp-content/uploads/2016/06/esxi-html50-30-005-700x348.png)
Although you can still receive this via NFS (or other networking protocols) it requires the configuration of a plugin.įurthermore talking with VMware, and having had some experience with iSCSI myself (and a great one at that), I, like many other people in the world was very quick to jump on the networking protocol bandwagon thinking that it was supposed to be better. I never really thought about it much, but it is true that iSCSI protocol gives VMware important logging information and other features because of VMware's VAAI by default. iSCSI (tried and true) Multipathing and logging.
#HOW TO ADD HOSTS TO THE ISCSI STORAGE IN VCENTER 6.5 SOFTWARE#
You know the drill concerning open source software - it's community supported which is why we speak.Ĥ. NFS4.1 Very solid with pay-for-products but not necessarily with FreeNAS. NFS4.0 never had a life worth mentioning and was very quicly replaced by NFS4.1 due to some major issues early on.ģ. I will attempt to explain as briefly as I can:Ģ. So I had a great conversation with a support person from VMware concerning NFS3 vs NFS4 vs NFS4.1 vs iSCSI. I was going on the notion that perhaps creating the mount with NFS3, deleting then recreating as NFS4.1 may have been a work around - but I haven't been able to reproduce this solution. Have been able to consistently duplicate it is any various miss match of versions below. Lrwxr-xr-x 1 root root 35 Jun 1 13:45 SSDArray -> 5eafd18e-9e60111a-0000-000000000000ĮSXI/FREENAS was giving it a different UUID for the symlink - but if I went to add node server into the other datastore (1) it would say it already exists - even though they are different UUID's. Lrwxr-xr-x 1 root root 35 Jun 1 14:02 SSDArray -> esxcfg-nas -lĭatastoreSS (1) is /mnt/SSDMirror/NFS from 192.168.2.118 mounted available SSDArray is /mnt/SSDPool/NFS from 192.168.2.33 mounted available Since VMware never highlights what has changed between releases in their official Configuration Maximum 6.5 documentation, I thought I would compare the document with the 6.0 version and list the changes between the versions here.NFS is /NFS from 192.168.2.30 mounted available VSphere 6.5 is now available and with every release VMware makes changes to the configuration maximums for vSphere.