Re: [Scst-devel] ib_srpt duplicate scsi_id / possible bug ?

[Bart V. A. <bva...@ac...>]

 On Mon, Jan 31, 2011 at 9:34 PM, steve <hi...@wv...> wrote:

>  [ ... ]
>
> seems i was a little be confused :-)
> You are right , enumerating the active sessions on the Target is the
> easiest way .
>
> Regarding the Initiator name in the group setup :
> > The trick here is to find out the initiator names - this is the initiator
> HCA port GUID expanded to a 128-bit number )
> i have checked my logfiles and find out that the the initiator name is
> generated
> by Target GUID and Initiator GUID ( which is ok )
>
> Is this behaivor controlled by the module parameter
> "use_port_guid_in_session_name"
> in ib_srpt ? ( is the default value for this "true" ? )
>

Hello Steve,

The default behavior is use_port_guid_in_session_name=n. The
use_port_guid_in_session_name parameter is a hack that was added for the
Windows SRP initiator.

Actually it's the initiator that generates session names. The Linux SRP
initiator (ib_srp) generates these session names as follows:
- The first eight bytes are the identifier extension ('initiator_ext'
parameter specified in the login string echoed into the sysfs file
'add_target').
- The last eight bytes are the GUID of the initiator HCA port used to
communicate with the target.

Bart.