hello,
I am trying to test vsphere with iSCSI.
I deployed a iSCSI target service on CentOS 7 with test steps:
1. disable firewalld, disable Selinux
2. yum -y install targetcli, and start up target service
3. configure iSCSI target
a. create block storage:
b. create iqn:
c. create LUN mapping to the block storage:
d. I did not create ACL on iSCSI target, I just want to everyone have access to this iSCSI. I do not know if it correct or not to not configure ACL on iSCSI, hope someone could give me some hint here.
4. I check the iSCSI server port 3260 is listennning.
After I deploy an iSCSI server as above. I go to configure vsphere vcenter.
I did these steps:
1. I created a new virtual standard switch vSwitch 1 with vmkernel, and uplink vmnic 5.
2. I start a software iSCSI storage adapter
4. I bind the vmnic 5 with iSCSI storage adapter vmhba64
5. I use dynamic discover the iSCSI target,
6. Then the vsphere find this
as you can see there, the devices tab, path tab, there is nothing there, I do not know if it is normal (but I created a LUN 0 on iSCSI target server before.)
I have a question about the iSCSI name, is this iSCSI name (on vsphere) should be the same name as iqn which I create on iSCSI target server ?
7. Finally I try to create a datastore with the iSCSI, I can not find the iSCSI corresponding disk device on vsphere
questions:
1. On iSCSI server I did not configure ACL, I hope everyone can connected to the iSCSI server, does it affect something or leading some error?
2. Should the iSCSI Name on vsphere be the same as the iqn of iSCSI target server that I configured.
3. The vsphere find the iSCSI target server, but Why I can not find the corresponding disk devices LUN 0 on iSCSI target server?
I really need someone's helps, a million thanks to all of you.
Best regards
shengping
Fixed. Had to add the following line on the centos box using targetcli and restart the service using systemctl restart target.service
set attribute authentication=0 demo_mode_write_protect=0
You should be able to see the devices under target before you proceed to adding the Datastore.
if you can share the vmkernel log form host after adding the targets using static discovery .. not dynamic
Did you perform rescan on adapter for new devices ? This should work without setting up ACL for everyone. Rescan the host adapter and then check if it discover new disk device there else check connectivity between both initiator and target host.
these 2 KBs should be a good start to troubleshoot
Hi,
Your IP of your VMK1 is bad.
Check on SSH from your esxihost :
# vmkping -I vmk1 <IPv4ofYourArray>
Source : https://kb.vmware.com/s/article/1003728
Thank you,
I see, the IP configuration of VMKernel seems to be set to automatic which acquired APIPA. This need to be static with referenced subnet.
I followed this guide and managed to get ESXi to see the target -> Configure iSCSI Target & Initiator on CentOS 7 / RHEL7
Try disabling CHAP authentication.
My main issue though is that I'm unable to create a datastore using this disk. Trying to figure out why atm.
Fixed. Had to add the following line on the centos box using targetcli and restart the service using systemctl restart target.service
set attribute authentication=0 demo_mode_write_protect=0
hello,
I found this Configure iSCSI Target & Initiator on CentOS 7 / RHEL7 yesterday as well, and get the exactly the same problem with you posted.
I guess I configured the iSCSI target wrong before. it cause the vsphere can not find LUN device in iSCSI server.
Thank you for all of yours help :smileygrin: