Seagate ST3655N Bedienungsanleitung Seite 241

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 263
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 240
Frequenty Asked Questions 235
SANTOOLS® is registered in US Patent and Trademark Office No 3,107,854 All rights reserved.
Everything. It works just fine, provided all of the adapter-specific drivers are properly installed and configured. If they
are not, then the software simply will not report anything for the adapters that do not have the library files installed.
7.3 Where are the configuration files stored on my UNIX/LINUX machine.
The runtime library files are ordinarily stored in /usr/lib. The file, /etc/hba.conf instructs the library how to
cross-reference the description of the card with the specific library file. See the below example:
# contents of file /etc/hba.conf
#
# This file contains names and references to HBA libraries
#
# Format:
#
# <library name> <library pathname>
#
# The library name should be pre pended with the domain of
# the manufacturer or driver author.
org.snia.sample32 /usr/lib/libsample.so
com.jni.fibrestar32 /usr/lib/libhbaapijni.so
com.qlogic.qla32 /usr/lib/libhbaapiqla.so
com.emulex.lightpulse32 /usr/lib/libhbaapiemu.so
com.jni.fibrestar64 /usr/lib/sparcv9/libhbaapijni.so
com.emulex.lightpulse64 /usr/lib/sparcv9/libhbaapiemu.so
7.3 Where are the configuration files stored on my Windows-family PC?
Registry entries are made to provide the windows-specific implementation of the /etc/hba.conf file. The HBA library
installers created by all the HBA vendors automatically do this for you. They are also supposed to append additional
entries for other HBAs as needed.
4.6 Windows Device Naming Conventions
With the advent of release 1.25, we believe we have introduced a better solution to problems unique to the Windows
family operating systems and device naming conventions. Specifically, the operating system does not always assign
the same physical device name to a device on every boot-up, particularly with fibre channel disks on a SAN. If you
have devices such as SCSI processors (I.e., RAID controllers) or SES processors, it will assign a device such as
\\.\SCSI2 to all devices on the same SCSI controller. The convention is only applicable to devices which use the SCSI
interface, which would include fibre channel peripherals and SCSI processors and enclosures. The change was
necessitated by Microsoft's new STORPORT drivers which have a slightly different mechanism for direct I/O.
What we have done is added a second naming convention for physical devices which should be much more constant
between reboots and hot plugging and unplugging storage. The program will still recognize device names such as
\\.\PHYSICALDRIVE3 or \\.\SCSI2, and will work as before with those device names for compatibility purposes.
However, you can now address devices by a more descriptive name that ties the device name to the hardware paths,
rather than some pseudo-randomly defined order based on when the O/S discovers a device.
The new device names take the format \\.\SCSIaPortbPathcTargetdLune where letters a,b,c,d, and e represent the
hardware paths which tend to stay constant, even in a SAN environment were devices could be inserted or removed
for the SAN at any time. The program will still support the older \\.\PHYSICALDRIVEn format if you care to use it, but
the software will always default to the \\.\SCSI type format if you do not specifically put in a device path which instructs
SMARTMonUX to scan for devices.
Determining Device Names
The best way to see both formats of device names for your peripherals is to enter smartmon-ux -I from the command
line. By not supplying a list of devices, the software will scan for everything it can discover. By design, it also creates a
scratch file, called FileList.txt which will be saved in the current directory.
On this machine, if we type out FileList.txt, we see ...
\\.\SCSI2Port2Path0Target4Lun0 path=0 port=2 id=4 lun=0 type=0 [SEAGATE ] [ST336753FC ] [0002] \\.\SCSI2Port2Path0Target4Lun0
Seitenansicht 240
1 2 ... 236 237 238 239 240 241 242 243 244 245 246 ... 262 263

Kommentare zu diesen Handbüchern

Keine Kommentare