Jason,
This happens every time I've attempted to connect from GlobalSAN to
a Solaris iSCSI target, so I'm not sure what might be causing the
initiator to "lose contact" with the target daemon. It certainly
seems to be repeatable.
I see that on Feb 1 you claim to have tested this scenario
successfully, many times, without failure. I can't help but wonder
what could be different between our setups.
Whoever opened bug 6800065 also claims repeated success with
GlobalSAN version 3.3.0.43, which is the same I'm using.
Bug CR 6800065 has been updated. There is no work-around once
GlobalSAN starts sending TargetName before InitiatorName, the reason
GlobalSAN starts doing this are unknown.
This CR will be resolved soon, allowing iSCSI login with Initiator and
Target names in either order.
- Jim
Thanks,
Jason
--
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
