I have to setup another instance with 9.2.1.9 and using in my system now as it is almost impossible to use 9.3 at its state.Abcslayer, could you please retry after setting sysctl kern.icl.coalesce=0 .
Device
t10.FreeBSD_iSCSI_Disk______000c29e873c1010
_________________ performance has improved.
I/O latency reduced from 53563 microseconds to
10519 microseconds.
Device
t10.FreeBSD_iSCSI_Disk______000c29e873c1010
_________________ performance has
deteriorated. I/O latency increased from average
value of 2464 microseconds to 53563
microseconds.
Feb 9 00:55:21 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 00:56:16 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 00:57:36 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 00:58:00 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 00:58:42 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:35:45 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:35:58 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:36:08 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:37:05 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:37:30 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:37:57 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:38:28 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:38:54 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:39:33 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:40:10 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 9 01:40:42 nas WARNING: 192.168.253.5 (iqn.2015-01.de.wqfw.h.esxi:esxi): no ping reply (NOP-Out) after 5 seconds; dropping connection
The issue happened on the newest update too (9.3-STABLE-3a01482-4663c83-3dbc203)Mar 11 12:48:23 freenas ctld[3499]: 192.168.10.2 (iqn.1998-01.com.vmware:5436d81
2-1b9d-676a-6755): requested target "iqn.2011-03.freenas:ipxe" not found
Mar 11 12:48:23 freenas ctld[1836]: child process 3499 terminated with exit stat
us 1
Yes, I am still on the way with the wildcards (0.0.0.0 for the 2nd portal) as FreeNAS 9.3 best feature is snapshot for boot volume, I can easily switch back to the known-work snapshot. As it works with older snapshots and on logic side it should work so I consider the newer updates have bug(s). I will keep wildcard for awhile till I fix the IP for 2nd portal (I prepare it to expose it outside of the ESXi vSwitch network).What issue has actually happened? Was reported target exposed to the portal where connection was established? Or you are still experimenting with wildcards, that I discouraged?