NAME

inquiry.conf - SCSI inquiry strings for Oracle HSM device types

SYNOPSIS

∕etc∕opt∕SUNWsamfs∕inquiry.conf

AVAILABILITY

SUNWsamfs

DESCRIPTION

The inquiry configuration file, inquiry.conf, maps a SCSI device to an Oracle HSM device type. The inquiry.conf file contains the vendor identification and product identification reported by a SCSI device in response to an inquiry command.

Entries in the file are made up of three quoted fields separated by a comma and∕or white space and optionally followed by a comment. These entries have the following format:

"vendor_id", "product_id", "Oracle HSM_name" #comment

The vendor_id and product_id are the vendor identification (8 characters) and product identification (16 characters) as reported in the inquiry data. The Oracle HSM_name is the Oracle HSM device name as described subsequently on this man page.

Trailing spaces do not need to be supplied in the vendor_id or the product_id fields. Any occurrence of a quotation mark ("), a comma (,), or a back slash (\fB\\) in any _id field should be prefaced with the escape character, which is a back slash (\fB\\). Blank lines and lines beginning with a pound character (#) are ignored.

The following device names are supported within the Oracle HSM environment:

Device Name: Device Type
acl2640: ACL 2640 tape library
acl452: ACL 4∕52 tape library
adic448: ADIC 448 tape library
adic100: ADIC Scalar 100 tape library. Quantum Scalar i500 tape library.
adic1000: ADIC Scalar 1000 and Scalar 10K tape libraries. Quantum Scalar i2000 and i6000 tape libraries.
archdat: Archive Python 4mm DAT drive
atl1500: Oracle StorEdge L25 and L100 and ATL M1500 and M2500 libraries.
atlp3000: ATL P3000, P4000 and P7000 tape library
cyg1803: Cygnet Jukebox 1803 library
dlt2000: Digital Linear Tape (2000, 4000, 7000, 8000 and SuperDLT series) drive
dlt2700: Digital Linear Tape Media Changer∕Stacker (2000, 4000, 7000, 8000 and SuperDLT series)
docstor: DISC automated library
exb210: Exabyte 210 tape library
exbx80: Exabyte X80 tape library
exb8505: Exabyte 8505 8mm cartidge tape drive
exbm2: Exabyte Mammoth-2 8mm cartidge tape drive
fujitsu_128: Fujitsu M8100 128 track tape drive
hpc7200: HP L9∕L20∕L60 series libraries
hpslxx: HP SL48 tape library
hpc1716: HP erasable optical disk drive
hpoplib: HP optical library
ibmatl: IBM ATL library
ibm0632: IBM multifunction optical disk drive
ibm3570: IBM 3570 tape drive
ibm3570c: IBM 3570 media changer
ibm3580: IBM 3580, Seagate Viper 200 and HP Ultrium (LTO) tape drives
ibm3584: IBM 3584, TS3500 and TS4500 tape libraries
ibm3590: IBM 3590 tape drive
ibm3592: IBM 3592, TS1120 and TS1150 tape drives
lms4100: Laser Magnetic Laserdrive 4100
lms4500: Laser Magnetic Laserdrive 4500
metd28: Metrum D-28 tape library
metd360: Metrum D-360 tape library
qual82xx: Qualstar 42xx, 62xx and 82xx series tape library
quantumc4: Quantum PX500 and StorEdge C4 tape library
rap4500: Laser Magnetic RapidChanger 4500
rsp2150: Metrum RSP-2150 VHS video tape drive
sonyait: Sony AIT tape drive
sonysait: Sony Super AIT tape drive
sonydms: Sony Digital Mass Storage tape library
sonycsm: Sony CSM-20S tape library
sonydtf: Sony DTF tape drive
speclog: Spectra Logic Libraries
stk4280: StorageTek 4280 Tape drive
stk9490: StorageTek 9490 Tape drive
stk9840: StorageTek 9840 Tape drive
stktitan: StorageTek Titanium Tape drive
stkapi: StorageTek API library
stkd3: StorageTek D3 Tape drive
stk97xx: StorageTek 97xx Media Libraries
stklxx: StorageTek L20, L40, L80 and L500 Tape Libraries and StorEdge L7 and L8 autoloaders.
odi_neo: Overland Data Inc. Neo Series Tape Libraries

EXAMPLES

The following is an example configuration file:

"HP",       "Ultrium 1", "ibm3580"   # HP Ultrium Tape
"HP",       "Ultrium 2", "ibm3580"   # HP Ultrium Tape
"HP",       "Ultrium 3", "ibm3580"   # HP Ultrium Tape
"Plasmon",  "G-Enterprise","plasmong"   # Plasmon G Enterprise
"Plasmon",  "UDO",      "plasmonUDO"    # Plasmon UDO 30GB optical drive
"STK",      "L700",     "stk97xx"   # STK L700 series SCSI
"STK",      "L180",     "stk97xx"   # STK L180 series SCSI
"STK",      "SL500",    "stklxx"    # STK SL500
"STK",      "T10000A",  "stktitan"  # STK titanium drive T10000A

The existence of a device in the previous example file does not imply that the device is supported by Oracle HSM.

NOTES

Whenever a new version of Oracle HSM is installed, the existing inquiry.conf file is copied to inquiry.conf.MMDDYY for reference and back-up purposes.

During device identification, the vendor_id and product_id values are only compared through the length of the string supplied in the inquiry.conf file. To insure an exact match, the entries should be ordered with longer names first.

WARNINGS

This interface is supplied to circumvent problems that occur when hardware vendors change the vendor_id and product_id values returned. For example, some hardware vendors return a different value for a product_id if the hardware is supplied by an OEM.

Oracle does not support mapping untested hardware to an Oracle HSM name.