Hello all,
I'am testing with iSCSI on VMware ESX Server 3.01. It works fine now, but when i was testing i created a couple of iSCSI datastores.
now i can see two targets vmhba40:4:0:0 and vmhba40:5:1:0
this are the only targets i use abd are named : SCSI Target 4 and SCSI Target 5.
My question is : What happened with with The SCSI Targets 0, 1,2 and 3 ? Is there some file in wich this is recorded/configured and not cleaned up ? I just want to use SCSI Targets 0 and 1 (or 1 and 2 if target 0 does not exists)
Thanx for helping...
Modify/delete the stale entries in:
/var/lib/iscsi/vmkbindings
/var/lib/iscsi/vmkdiscovery
Paul
What SAN are you using for iSCSI connection? Does it have fiber and iSCSI connections both?
It could be using 4 and 5, to my understanding and someone please correct me if im wrong, because the other SP ports 0,1,2,3 are assigned to fiber connections.... OR.... its just a matter of editing out the unused ones as mentioned in the previous reply.
I am using openfiler as my "Virtual SAN".
I am connecting through the virtual iSCSI adapter in ESX server 3.01.
i am going to try cleaning up both files as stated in the previous reply..
i will post the results..
i cleaned up the target entrys from the files
/var/lib/iscsi/vmkbindings
/var/lib/iscsi/vmkdiscovery
after that i rescanned all HBA and VMFS the files
/var/lib/iscsi/vmkbindings
/var/lib/iscsi/vmkdiscovery
the old target entrys were back .... nothing has been changed
Paul i tried your solution but after a rescan the entrys were back ? did i forget something else ?
Remove the entries in the iSCSI adapter settings (under SendTargets) and then remove the entries in those two files. Reboot the ESX server and then re-add the iSCSI target back in. You should be good after this.
Paul
Hi Paul,
"Remove the entries in the iSCSI adapter settings (under SendTargets)"
you mean the file /etc/iscsi.conf ?
i did not use that file, i used dynamic discovery... where in the file is SendTargets ? i could not find it....
is there a way to do this without rebooting ESX ? it only cleans up after a reboot ?
Hello,
I had the same issue. I deleted the entries, then rebooted the ESX server. I also had to perform the following commands after the reboot to rediscover the existing partition.
esxcfg-advcfg -s 1 /LVM/EnableResignature
esxcfg-rescan vmhba40
esxcfg-advcfg -d /LVM/EnableResignature
I found this in the following thread:
http://www.vmware.com/community/thread.jspa?messageID=688228
I now have a new problem in that the old name for my LUN still exists somewhere (probably in Virtual Center) that I have to go delete so I can rename the snap-00000002-[i]MYVMFS[/i][/b] to the original name MYVMFS[/i].