FCP-2 Table 4 Clearing Effects

[Lawrence Chen]

* From the T10 Reflector (t10 at t10.org), posted by:
* Lawrence Chen <Larry.Chen at EBay.Sun.COM>
*
Thanks Charles.

one final word to HBA folks ...
get rid of full-login on Lip ASAP so Device Reservations are not cleared
unnecessarily.

 >X-Authentication-Warning: storage.network.com: majordom set sender to
owner-fc at network.com using -f
 >From: "Binford, Charles" <cbinford at lsil.com>
 >To: t10 at t10.org, fc at network.com
 >Subject: RE: FCP-2 Table 4 Clearing Effects
 >Date: Fri, 11 Aug 2000 08:45:36 -0500
 >MIME-Version: 1.0
 >
 >LOGO/PLOGI and PRLI/PRLO has *always* been treated as a reset who's scope is
 >limited to that initiator.  Look at original FCP - is says PRLI causes a
 >device to post a power up unit attention.  That event has always cleared
 >reservations.
 >
 >As far as LIP(f7) causing your reservations to be cleared, I'd say it
 >another way.  The actions the host driver chose for its post-lip processing
 >cleared the reservation.  The standards (starting with PLDA) describe using
 >ADISC or PDISC as the post-lip processing.  Had your host driver chosen this
 >action the reservations would have been left intact.
 >
 >Charles Binford
 >LSI Logic Storage Systems
 >(316) 636-8566
 >
 >
 >> -----Original Message-----
 >> From: Lawrence Chen [mailto:Larry.Chen at ebay.sun.com]
 >> Sent: Thursday, August 10, 2000 7:38 PM
 >> To: t10 at t10.org
 >> Cc: rsnively at Brocade.COM; fc at network.com; larry.chen at ebay.sun.com
 >> Subject: FCP-2 Table 4 Clearing Effects
 >>
 >>
 >> *
 >> * From the fc reflector, posted by:
 >> * Lawrence Chen <Larry.Chen at ebay.sun.com>
 >> *
 >> Looking at FCP-2 Rev 04,
 >> Table 4 - Clearing Effects of SCSI Initiator Actions
 >>
 >> Can someone explain the rational for clearing Device Reservations for
 >> LOGO/PLOGI and PRLI/PRLO ??
 >>
 >> For many pieces of FC hardware as of today, this means that Lip(F7)s
 >> will cause Device Reservations to be cleared. I think this
 >> behavior is too drastic in cluster configs; i.e.,  if one host is
 >> rebooting
 >> then the other "alive" host's Device Reservation can get
 >> effected due to
 >> a
 >> Lip(F7). Shouldn't the reboot be as transparent as possible to the
 >> "alive"
 >> host ??
 >>
 >> Lastly, I realize the Persistent Reservations do NOT behave this way
 >> (but this won't help me here).
 >>
 >> --
 >> Larry Chen
 >> Sun Microsystems, Inc.
 >> Network Storage Division
 >> Email: larry.chen at ebay.sun.com
 >> Phone: (510) 574-9779  Fax: (510) 574-9822
 >>


--
Larry Chen
Sun Microsystems, Inc.
Network Storage Division
Email: larry.chen at ebay.sun.com
Phone: (510) 574-9779  Fax: (510) 574-9822

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