I note that in the FAQ (Q18) http://www.rocketdivision.com/faq.html?pr_id=2 that for devices connected with the SPTI,
StarWind should redirect all RESERVE/RELEASE op-codes directly to the device.
However, I'm not sure that this is happening?
I am using StarWind 3.5.1 and StarPort 3.5.4 and the following screen shot shows a device analyser monitoring
the Initiator (left side tab, addrs = .2) and the Target (right side tab, addrs= .3).
The Initiator has issued a series of SCSI CDBs and these IO requests have been trapped and displayed.
I think I see that the Initiator has issued a Reserve/Release pair (counter 6 & 13 - highlighted).
However, these commands are not reflected at the Target? Where have they gone?

First thoughts - Initiator or Target problem? So I watch the network between the two. This next screen shot shows that trace.

From this, I conclude that the Reserve/Release op-codes are leaving the Initiator and are, in fact are being acknowledged by the Target (counters 1228/9 & 1278/9 - highlighted).
Working from this information, I have to conclude that the StarWind service is taking it upon itself to handle the Reserve/Release commands - contrary to FAQ, Q18?
Any advice that would reconcile/correct this option will be much appreciated.
Best regards,
Martin