|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: Target ResetJohn, I understand the danger of issuing a target reset and I agree that it should not be a part of the an initiator's normal error recovery procedure. However, looking at this from a management perspective I'd like to see a standardized way of resetting a target. I don't want to see a variety of vendor unique methods of resetting targets sprout up. If resetting a target using the protocol is not desirable from your perspective would incorporating this feature into the MIB be acceptable? (MIBs are for management after all) ---------------------------------------------------------------- David Dillard david_dillard@adaptec.com Management Software Group Adaptec, Inc. www.adaptec.com -----Original Message----- From: John Hufferd [mailto:hufferd@us.ibm.com] Sent: Sunday, April 22, 2001 4:59 AM To: ips@ece.cmu.edu Subject: Target Reset I thought we had a number of discussion previously about Target Reset (Warm or Cold). I thought there was general feeling that this command is so dangerous that it should not be supported by iSCSI. The long distance capability of iSCSI makes the risks involved unmanageable. There should only be an Admin way to do this. Some folks have said that we could permit it and have special authorization etc. This would probably cause a separate section in the spec. to define the authorization approach, and what ever other security is needed to prevent this from inappropriately being used. All for what purpose? This can not be part of error recovery from a normal initiator. The wide spread effect is too great for that. I would like to hear from the list about their feeling on this item. . . . John L. Hufferd Senior Technical Staff Member (STSM) IBM/SSG San Jose Ca (408) 256-0403, Tie: 276-0403, eFax: (408) 904-4688 Internet address: hufferd@us.ibm.com
Home Last updated: Tue Sep 04 01:04:56 2001 6315 messages in chronological order |