logo       

RE: IET does not handle Text Requestsafterentering FFP: msg#00137

Subject: RE: IET does not handle Text Requestsafterentering FFP
Hello Arne

The keys that can be exchanged are:
InitiatorName
TargetAlias
InitiatorAlias
TargetAddress
TargetPortalGroupTag
SessionType
And Vendor Extensions

The above list is as per 3720

Thanks for your help. 

Regards
Syed Khaleelulla
Consultant - Storage Solutions
Wipro Technologies
Ph: +91-80-51381007

-----Original Message-----
From: iscsitarget-devel-admin@xxxxxxxxxxxxxxxxxxxxx
[mailto:iscsitarget-devel-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Arne
Redlich
Sent: Thursday, February 16, 2006 2:43 PM
To: syed Khaleelulla (WT01 - Computing Systems & Storage)
Cc: iscsitarget-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Iscsitarget-devel] IET does not handle Text
Requestsafterentering FFP

Am Donnerstag, den 16.02.2006, 14:18 +0530 schrieb
syed.khaleelulla@xxxxxxxxx:
> Hello
> 
> Am Donnerstag, den 16.02.2006, 08:22 +0530 schrieb
> syed.khaleelulla@xxxxxxxxx:
> > Hello
> > 
> >  
> > 
> > IET does not handle Text Requests after entering into FFP.
> 
> Yep. Well, more precisely, FFP of normal sessions. ;-)
> 
> Syed> I had not elaborated on that, thanks for doing so.
> 
> Anyway, the problem is that IET does the text PDU parsing (during
login
> phase and discovery FFP) in user space, while a normal session's FFP
is
> handled in kernel space. So it's a bit tricky to implement it cleanly,
> especially without having an initiator around making use of it.
> 
> Syed> It is the parsing of Key=Value and updating the specific
attribute
> Syed> that need to be done. At my first glance it looks, this needs to
> be
> Syed> done for six attributes.

That's more than I'm aware of. AFAIK, the only legal text keys an
initiator may send during FFP are InitiatorAlias, MaxRxDSL, SendTargets
and vendor (extension) keys - what are the remaining ones?

> Do you actually have an initiator (which one?) requiring this? If so,
> which key(s) does it send? How does it cope with IET's
> Reject/ISCSI_REASON_UNSUPPORTED_COMMAND?
> 
> Syed> I am making UNH to negotiate a Operational Parameter while in
FFP.

See above. IIRC (need to have a look at the spec again, though), most
operational params may not be (re-)negotiated during FFP, with the
exception of MaxRxDSL, which may be re-declared.

> Syed> I am using the iscsi-test module to do the above stuff.
> Syed> With ERL=0, Session break. Not tried with ERL>0

IET doesn't support ERL > 0, anyway.

Arne
-- 
Arne Redlich
Xiranet Communications GmbH



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Iscsitarget-devel mailing list
Iscsitarget-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642


<Prev in Thread] Current Thread [Next in Thread>