Re: Re-sending a command
Julian Satran <[email protected]>
| Newsgroups | gmane.ietf.ips |
|---|---|
| Message-ID | <OFB3EF42E2.9A84440F-ONC22571C6.001D35D5-C22571C6.0022A6C3@il.ibm.com> |
Eddy, The LU reset "plugs the holes" in command sequence and the old CmdSN should not be used (it is definitely an initiator bug). If you have seen it Mallikarjun may want to mention that dropping the command is the expected behavior of the target after all the task management commands that "plug the holes" in the implementation guide. Julo "Eddy Quicksall" <[email protected]> 10/08/06 01:34 To <[email protected]> cc Amit Kumar <[email protected]> Subject [Ips] Re-sending a command It was brought to my attention that one initiator being tested will re-issue a "timed out" command using the same CmdSN after it has issued a LU Reset. When this happens the command is dropped. Note that this is on a single connection session. I'm wondering if this could be an initiator bug or if there is a case where it is actually valid (in the report I have I don't know if the initiator also reissued the command with a valid CmdSN or not). Does anyone know? Eddy_______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips _______________________________________________ Ips mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ips