Here's what I've found with the latest initiator from Microsoft on a Windows XP machine:
First, I define a new iSCSI target. The following exchange happens: <> SYN/SYN-ACK/ACK -> iSCSI Login Command (T=0x1, CSG=0x00, NSG=0x01) <= iSCSI Login Response (Success) -> iSCSI Login Command (T=0x1, CSG=0x01, NSG=0x11) <= iSCSI Login Response (Success) -> iSCSI Text Command (SendTargets=All) <= iSCSI Text Response (my iqn) -> iSCSI Logout Command <= iSCSI Logout Response <> FIN/ACK... Looks good. Now I attempt to logon to the target: <> SYN/SYN-ACK/ACK -> iSCSI Login Command (T=0x1, CSG=0x00, NSG=0x01) <= iSCSI Login Response (Success) -> iSCSI Login Command (T=0x1, CSG=0x01, NSG=0x11) <= iSCSI Login Response (Success) -> iSCSI Report LUNs (LUN=0x00) <= iSCSI Data In (LUN=0x00) Report LUN Response (LUN=0x00, good) -> iSCSI LUN Inquiry (LUN=0x00) <= iSCSI Data In (LUN=0x00) Inquiry Response (SCSI transfer limited due to allocation_length too small: SCSI truncated) -> iSCSI LUN Inquiry (LUN=0x00) <= iSCSI Data In (LUN=0x00) Inquiry Response (LUN=0x00, good) -> RST/ACK At this point, another session starts: <> SYN/SYN-ACK/ACK -> iSCSI Login Command (T=0x1, CSG=0x00, NSG=0x01) <= iSCSI Login Response (Success) -> iSCSI Login Command (T=0x1, CSG=0x01, NSG=0x11) <= iSCSI Login Response (Success) -> iSCSI Report LUNs (LUN=0x00) <= iSCSI Data In (LUN=0x00) Report LUN Response (LUN=0x00, good) -> iSCSI LUN Inquiry (LUN=0x00) <= iSCSI Data In (LUN=0x00) Inquiry Response (LUN=0x00, good) -> RST/ACK This sequence repeats over and over. It seems that the first attempt failure throws the Microsoft driver into an odd state where it doesn't retry the inquiry. I will post more later today... This message posted from opensolaris.org _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
