Bob.Snively at Eng.Sun.COM
Wed Oct 1 08:26:18 PDT 1997
* From the T10 (formerly SCSI) Reflector (t10 at symbios.com), posted by:
* Bob Snively <Bob.Snively at Eng.Sun.COM>
The answers are contained in the SES document.
> * From the T10 (formerly SCSI) Reflector (t10 at symbios.com), posted by:
> * Terry Braun <tab at talking.com>
> There seems to be no correspondence between enclosure service access
> devices and enclosures in the spec. Also, there seems to be no
> correspondence between enclosures and buses. With the following results:
> 1. Any number of access devices (of both kinds) can sit on a SCSI bus-
> limited only by the number of LUN's available.
> 2. Each access device can be associated with the same enclosure or each to
> a different enclosure, or any combination of the two.
> 3. Each enclosure could be associated with the same SCSI bus or a different
> SCSI bus or any combination of the two.
Your software has to help you. The enclosure logical name is provided
and is independent of the WWN of the access device, but the same for
information passed through any access device. Sub-enclosures have the
same sub-enclosure id relative to the enclosure logical name. All SCSI
devices in the enclosure have a device id associated with them, although
it may not necessarily be the same as the device id actually obtained in
an FC-AL environment. The report bits identify the access path actually
being used to transfer/create a particular set of information.
You better not have two independent systems fighting over which one
is to manipulate the control functions. Any independent system can
access status information. Again, this is a case where the software has to
The tools are there, but your software has to use them.
Terry is working on a mapping of these functions to an appropriate MIF or MIB.
Hope that clarifies the question.
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at symbios.com
More information about the T10