[ofw] SRP miniport will not start with gen2 SRP Target

[Leonid Keller]

Yes, it does not solve the problem, we've checked it.
The flaws were at the target side.
They had been fixed, but I'm not sure about the comitting of the fixes.
Rob, did you try the last version of OFED ?

> -----Original Message-----
> From: ofw-bounces at lists.openfabrics.org 
> [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Fab Tillier
> Sent: Wednesday, November 28, 2007 7:16 PM
> To: rob at systemfabricworks.com; ofw at lists.openfabrics.org
> Subject: RE: [ofw] SRP miniport will not start with gen2 SRP Target
> 
> If the SRP initiator gets to pick the 'IDENTIFIER EXTENSION' 
> field, it should be able to use whatever value it feels is 
> appropriate to 'ensure that all SRP initiator port 
> identifiers are unique'.  What is wrong with using the 
> extension ID - does this violate the spec somehow?
> 
> I'd be weary of making changes to the initiator based on a 
> flaw in the target.  The SRP initiator in Windows works 
> successfully with other SRP targets, which would seem to 
> indicate a target-side issue with the Mellanox SRPT implementation.
> 
> -Fab
> 
> -----Original Message-----
> From: ofw-bounces at lists.openfabrics.org 
> [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of 
> Robert H.B. Netzer
> Sent: Wednesday, November 28, 2007 5:06 AM
> To: ofw at lists.openfabrics.org
> Subject: RE: [ofw] SRP miniport will not start with gen2 SRP Target
> 
> Does anyone know if this inter-operability problem was ever 
> debugged?  The WinOF 1.0.1 release seems to still suffer from it.
> 
> If not, would anyone with knowledge of the SRP initiator or 
> target be willing to offer me some tips on what to look for 
> if I were to attempt to debug it in the next couple of weeks?
> 
> Rob Netzer
> System Fabric Works, Inc.
> 
> > -----Original Message-----
> > From: On Behalf Of ssufficool at rov.sbcounty.gov 
> (Sufficool, Stanley)
> > Sent: Monday, August 13, 2007 1:36 PM
> > Subject: [ofw] SRP miniport will not start with gen2 SRP Target
> >
> > Looks like WinIB srp initiator is sending 
> [TargetGUID]:[InitiatorGUID] 
> > in the request init_port_id struct instead of 
> > [InitiatorExt]:[InitiatorGUID]. I beleive this is causing 
> the Mellanox 
> > referenced SRPT to produce an invalid nexus and break the 
> connection.
> >
> > These are the logs from the Mellanox IB_SRPT kernel module 
> for Win64 & 
> > Linux x64 initiator scenarios.
> >
> > --- Windows Inititator (WinIB Gen1 SRP) 
> > ===================================
> > ib_srpt: Host i_port_id=0x44d00cffff4b1a00:0xf4f700ffffbb1900 login 
> > with t_port_id=0x44d00cffff4b1a00:0x44d00cffff4b1a00 it_iu_len=340
> >
> > Result: no disk in disk manager
> > ===================================
> >
> > --- Linux Initiator (OFED Gen2 SRP) -
> > ===================================
> > ib_srpt: Host i_port_id=0x0:0x45d00cffff4b1a00 login with 
> > t_port_id=0x44d00cffff4b1a00:0x44d00cffff4b1a00 it_iu_len=260
> >
> > Result, successful connection and /dev/sda is created.
> > ===================================
> >
> > srp_connection.c
> > ====================
> > Is there a reason to set the init_port_id.field1 to the target port 
> > GUID? Per the SRP R16 (Pg 66), this is set to the Initiator ID 
> > extension (0x0 in above Linux scenario). "The IDENTIFIER EXTENSION 
> > field shall be chosen by the SRP initiator port to ensure 
> that all SRP 
> > initiator port identifiers are unique". Linux SRP sets this to the 
> > initiator_ext (ib_srp.c line 342)
> >
> > line 802 - 815
> >        switch( p_profile->io_class )
> >         {
> >         case SRP_IO_CLASS_R10:
> >                 p_connection->init_port_id.field1 = ca_guid;
> >                 p_connection->init_port_id.field2 = ext_id;
> >                 p_connection->targ_port_id.field1 = 
> p_profile->ioc_guid;
> >                 p_connection->targ_port_id.field2 = ext_id;
> >                 break;
> >
> >         case SRP_IO_CLASS:
> >                 p_connection->init_port_id.field1 = ext_id;
> >                 p_connection->init_port_id.field2 = ca_guid;
> >                 p_connection->targ_port_id.field1 = ext_id;
> >                 p_connection->targ_port_id.field2 = 
> p_profile->ioc_guid;
> >                 break;
> >
> >         default:
> >                 return IB_INVALID_PARAMETER;
> >         }
> >
> >
> >
> >
> >
> > ________________________________
> > From: ofw-bounces at lists.openfabrics.org 
> > [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Sufficool, 
> > Stanley
> > Sent: Tuesday, August 07, 2007 10:12 AM
> > To: ofw at lists.openfabrics.org
> > Subject: [ofw] SRP miniport will not start with gen2 SRP Target
> >
> >
> > I noted this thread from May:
> >
> > http://lists.openfabrics.org/pipermail/ofw/2007-May/001565.html
> >
> > I am having the same issue. Vu at Mellanox says it has 
> something to do 
> > with the SRP initiator not recognizing the LUNs on the target. ( 
> > 
> http://lists.openfabrics.org/pipermail/general/2007-July/037986.html )
> >
> > Is there anything being done with this? The linux 
> initiators are said 
> > to work with this target.
> > -------------- next part -------------- An HTML attachment was 
> > scrubbed...
> > URL:
> > 
> http://lists.openfabrics.org/pipermail/ofw/attachments/20070813/755c7a
> > 2c/a
> > ttachment.htm
> 
> _______________________________________________
> ofw mailing list
> ofw at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
> _______________________________________________
> ofw mailing list
> ofw at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
>