sesio(7I) Ioctl Requests sesio(7I)NAME
sesio - enclosure services device driver interface
SYNOPSIS
#include <sys/sesio.h>
DESCRIPTION
The ses device driver provides the following ioctls as a means to access SCSI enclosure services devices.
IOCTLS
The ses driver supports the following ioctls:
SES_IOCTL_GETSTATE This ioctl obtains enclosure state in the ses_ioctl structure.
SES_IOCTL_SETSTATE This ioctl is used to set parameters on the enclosure services device. The ses_ioctl structure is used to pass
information into the driver.
ERRORS
EIO The ses driver was unable to obtain data from the enclosure services device or the data transfer could not be completed.
ENOTTY The ses driver does not support the requested ioctl function.
ENXIO The enclosure services device does not exist.
EFAULT The user specified a bad data length.
STRUCTURES
The ses_ioctl structure has the following fields:
uint32_t; /* Size of buffer that follows */
uint8_t page_code: /* Page to be read/written */
uint8_t reserved[3]; /* Reserved; Set to 0 */
unit8t buffer[1]; /* Size arbitrary, user specifies */
EXAMPLES
Example 1 Using the SES_IOCTL_GETSTATE ioctl
The following example uses the SES_IOCTL_GETSTATE ioctl to recover 20 bytes of page 4 from a previously opened device.
char abuf[30];
struct ses_ioctl *sesp;
int status;
sesp = (ses_ioctl *)abuf;
sesp->size = 20;
sesp->page_code = 4;
status = ioctl(fd, SES_IOCTL_GETSTATE, abuf);
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |SPARC |
+-----------------------------+-----------------------------+
SEE ALSO ses(7D), ioctl(9E)SunOS 5.11 27 Mar 1997 sesio(7I)
Check Out this Related Man Page
SES(4) BSD Kernel Interfaces Manual SES(4)NAME
ses -- SCSI Environmental Services driver
SYNOPSIS
device ses
DESCRIPTION
The ses driver provides support for all SCSI devices of the environmental services class that are attached to the system through a supported
SCSI Host Adapter, as well as emulated support for SAF-TE (SCSI Accessible Fault Tolerant Enclosures). The environmental services class gen-
erally are enclosure devices that provide environmental information such as number of power supplies (and state), temperature, device slots,
and so on.
A SCSI Host adapter must also be separately configured into the system before a SCSI Environmental Services device can be configured.
KERNEL CONFIGURATION
It is only necessary to explicitly configure one ses device; data structures are dynamically allocated as devices are found on the SCSI bus.
A separate option, SES_ENABLE_PASSTHROUGH, may be specified to allow the ses driver to perform functions on devices of other classes that
claim to also support ses functionality.
IOCTLS
The following ioctl(2) calls apply to ses devices. They are defined in the header file <cam/scsi/scsi_ses.h> (q.v.).
SESIOC_GETNOBJ Used to find out how many ses objects are driven by this particular device instance.
SESIOC_GETOBJMAP Read, from the kernel, an array of SES objects which contains the object identifier, which subenclosure it is in, and the
ses type of the object.
SESIOC_GETENCSTAT Get the overall enclosure status.
SESIOC_SETENCSTAT Set the overall enclosure status.
SESIOC_GETOBJSTAT Get the status of a particular object.
SESIOC_SETOBJSTAT Set the status of a particular object.
SESIOC_GETTEXT Get the associated help text for an object (not yet implemented). ses devices often have descriptive text for an object
which can tell you things like location (e.g, "left power supply").
SESIOC_INIT Initialize the enclosure.
EXAMPLE USAGE
The files contained in <usr/share/examples/ses> show simple mechanisms for how to use these interfaces, as well as a very stupid simple moni-
toring daemon.
FILES
/dev/sesN The Nth SES device.
DIAGNOSTICS
When the kernel is configured with DEBUG enabled, the first open to an SES device will spit out overall enclosure parameters to the console.
HISTORY
The ses driver was written for the CAM SCSI subsystem by Matthew Jacob. This is a functional equivalent of a similar driver available in
Solaris, Release 7.
BSD January 29, 2000 BSD