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. ;-)
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.
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?
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
|
