Hard reset and multiple port devices

Kevin D Butt kdbutt at us.ibm.com
Mon Oct 7 14:06:47 PDT 2002


* From the T10 Reflector (t10 at t10.org), posted by:
* "Kevin D Butt" <kdbutt at us.ibm.com>
*

Rob,

I think a is the correct answer.

Kevin D. Butt
Fibre Channel & SCSI Architect
IBM Tape Microcode,
6TYA, 9000 S. Rita Rd., Tucson, AZ  85744
Tie-line 321; Office: 520-799-5280, Lab: 799-2869, Fax: 799-4138, Email:
kdbutt at us.ibm.com


                                                                                                                                     
                      "Elliott, Robert                                                                                               
                      (Server Storage)"        To:       <t10 at t10.org>                                                               
                      <Elliott at hp.com>         cc:                                                                                   
                      Sent by:                 Subject:  Hard reset and multiple port devices                                        
                      owner-t10 at t10.org                                                                                              
                                                                                                                                     
                                                                                                                                     
                      10/04/2002 04:37                                                                                               
                      PM                                                                                                             
                                                                                                                                     
                                                                                                                                     



* From the T10 Reflector (t10 at t10.org), posted by:
* "Elliott, Robert (Server Storage)" <Elliott at hp.com>
*
If a multiported target device, perhaps with target ports of different
protocols, detects a hard reset with one of its target ports, SAM-3
describes how all the logical units are reset and that the transport
protocol defines protocol-specific actions in response.
See sam2r03 6.1 and 6.3.2.

What should happen to the other target ports in the target device?
Which
ports should perform those protocol-specific actions?

Possibilities include:
a) only the target port that reported the hard reset
b) all target ports in the target device
c) all target ports in the target device that are in the same SCSI
    domain as the one reporting the hard reset
d) all target ports in the target device that share the same transport
    protocol and are in the same domain
e) all target ports in the target device that share the same
    transport protocol


The same question applies to initiator devices, which are advised to
terminate all outstanding Execute Command () RPCs.

Should that mean:
a) only Execute Command()s that were using the initiator port that
    reported the hard reset;
n) all Execute Command(s) on all initiator ports in the initiator device
c) all Execute Command()s on all initiator ports in the initiator device

    that are in the same SCSI domain as the one reporting hard reset
d) all Execute Command(s) on all initiator ports that share the same
    transport protocol and are in the same domain
e) all Execute Command(s) on all initiator ports that share the same
    transport protocol


I think b) is the correct approach for both sides.

--
Rob Elliott, elliott at hp.com
Industry Standard Server Storage Advanced Technology
Hewlett-Packard

*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org





*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org




More information about the T10 mailing list