User manual

SANtools® S.M.A.R.T. Disk Monitor (SMARTMon-UX)4
SANTOOLS® is registered in US Patent and Trademark Office No 3,107,854 All rights reserved.
the operator supplies the program with a list of devices to run against, the program builds that list and issues the
commands to verify that the devices exist and are not offline. If no list of devices is supplied, the software will initiate
a device discovery. This discovery can take several seconds up to over a minute if you have a large UNIX
configuration.
If your system's peripheral configuration is rather static, you should bypass the discovery by supplying a list of devices
to the program, and modify any scripts you have created to use a hard list of devices.
Device Initialization Phase (IBM AIX):
· The program builds a list of device candidates by issuing "lsdev | grep Available | cut -f 1 -d ' ' |
grep -e disk -e cd -e sas -e ses".
Device Initialization Phase (Apple OS X 10.2.3 and higher):
· This software supports fibre channel devices using the AsteraTech fibre channel HBA only. The drivers must be
dated after February 15th, 2003, as that is when they released drivers that communicate with our software. There
is no support for SCSI peripherals.
· ATA devices are scanned by enumerating the BSD /dev names. If the device is an IDE (SATA or ATA) disk drive, it
will be added to the list for processing.
· We build a numeric list of device candidates by performing direct pass-through calls to the AsteraTech driver, and
requesting that it returns information for every fibre channel device it discovers on all controllers and ports. This list
is a numeric list that starts from 0.
· As only fibre-channel devices are supported, no scanning for parallel SCSI, fire wire, or ATA devices is performed.
Device Initialization Phase (HP-UX):
· The program builds a list of device candidates by issuing the /sbin/ioscan -FknC disk and /sbin/ioscan
-FknC tape commands, along with enumerating devices in the /dev/rscsi directory.
Device Initialization Phase (IRIX):
· The program builds a list of device candidates by searching for /hw/scsi entries and parsing out the SCSI and
fibre channel disk entries which are returned. Then it appends the list with tapes using the wildcard
/hw/tape/*nrs. The program continues in the same way that the LINUX release does, as described earlier in
this section.
Device Initialization Phase (LINUX):
· The program builds a list of device candidates by issuing the /sbin/sfdisk command and parsing out entries
beginning with /dev/s. Then it appends the first SCSI tape device, /dev/st0. IDE devices are detected by
scanning /dev/hda through /dev/hdl. (This is not done if SMARTMon-ux is invoked with a list of specific disks
to monitor).
· For each IDE disk device discovered: (/dev/hda ... /dev/hdl)
· Device information is read and stored.
· If the disk has S.M.A.R.T. firmware capability, it is enabled. Otherwise the program reports that it cannot enable
it for the specific device.
· Initial S.M.A.R.T. values and thresholds are read to establish a baseline.
· Drive information is displayed and placed into log file in format specified in command-line operations or
defaults.
· For each SCSI (or Fibre channel or SSA device found):
· Two SCSI Inquiries are issued. The first is a standard inquiry. The second is an inquiry on an optional
vendor-specific page to determine the device's unique serial number. (The SCSI specification unfortunately
does not require disks to report a serial number programmatically).
· If the manufacturer is listed as "Promise", the card is an IDE-based Promise RAID controller. SMARTMon-ux
issues the vendor-specific commands to extract make model and serial number information for the drives which
make the Promise RAID-0 or RAID-1 data set. (Promise RAID controllers do not support S.M.A.R.T. polling).
· If the disk has S.M.A.R.T. firmware capability, it is enabled. Otherwise the program reports that it cannot enable
it for the selected device. Note also that SCSI devices support a performance bit which is a S.M.A.R.T. setting
that lets the drive run internal S.M.A.R.T. diagnostics without interrupting data flow. If you are in a
high-throughput environment such as video streaming, you should invoke this program with the -P option.
19