We are having some problems with the solaris 10 initiator. Everything works quite well but as soon as we remove or create a target in the web interface, all our iscsi connections are dropped.
this is what happens:
I've mounted a volume on /mnt, next I either remove or add add a new target
the logs shows:
Oct 7 15:56:51 rbgz02 iscsi: WARNING: iscsi connection(55) login failed - can't accept MaxOutstandingR2T 0
Oct 7 15:56:51 rbgz02 iscsi: NOTICE: iscsi session(54) iqn.2006-09.com.iw:iscsi.target1 offline
Oct 7 15:56:57 rbgz02 scsi: WARNING: /iscsi/disk@0000iqn.2006-09.com.iw%3Aiscsi.target1FFFF,5 (sd5):
Oct 7 15:56:57 rbgz02 transport rejected fatal error
Oct 7 15:57:02 rbgz02 ufs: WARNING: Error writing master during ufs log roll
Oct 7 15:57:02 rbgz02 ufs: WARNING: ufs log for /mnt changed state to Error
Oct 7 15:57:02 rbgz02 ufs: WARNING: Please umount(1M) /mnt and run fsck(1M)
Oct 7 15:57:50 rbgz02 iscsi: NOTICE: iscsi session(54) iqn.2006-09.com.iw:iscsi.target1 online
the first and most interesting thing is the message: login failed - can't accept MaxOutstandingR2T 0
after I run format: the logs show: NOTICE: iscsi session(54) iqn.2006-09.com.iw:iscsi.target1 online
now I can unmount and remount the volume to get it back online
We are running the latest open-e server (same problem with the last 2 releases). Our initiators run on solaris 10 with the latest patch level and iscsi patch 119091-20
some more strange things:
root@rbgz02:~# iscsiadm list static-config
Static Configuration Target: iqn.2006-09.com.iw:iscsi.target1,192.168.0.220:3260
This code also returns true if the 'value' == 0 as is the case. We can argue if this programming is corrent (strcmp return either: positive, negative or zero and the if statement is a boolean check) but the RFC (section 12.17) states:
After adding removing targets the IET is restarted - this is how our iSCSI works. We have reviewd logs and nothing was noticable. Remko, for furture assistence could you please contact our UK office for technical assistence:
Europe, Asia, Africa and Australia.
Monday through Friday, 9:00 to 18:00 (German time), (excluding German national holidays)
Telephone: +49 (89) 800 777 - 16
FYI - Our company has been using Cisco's version of the iscsi initiator for Solaris without any issues. It is much easier to setup than Sun's version. It is based on Solaris 8 and we have not tried it on Solaris 10. In the iscsi.conf, the only line you really need is DiscoveryAddress=x.x.x.x . You can't get much simpler than that.