Device and Network Interfaces acl2640(7) NAME acl2640 - The ACL2640 Automated Tape Library AVAILABILITY SUNWsamfs DESCRIPTION The ACL2640 tape library supports 264 DLT tape cartridges and 3 DLT tape drives. The library has a import/export unit that may be used to import or export media into the library. The import unit takes one cartridge at a time and the export unit will hold up to 12 cartridge. CONFIGURATION The ACL2640 should NOT be configured with auto-clean when running Sun StorEdge SAM-FS and Sun SAM-QFS software. IMPORT/EXPORT MEDIA To import media the door on the ACL2640 must first be opened. To open the door issue the import(1M) command, then follow the instructions in the ACL2640 operator's Guide. To export media, use the export(1M) command to move media into the export unit then follow the instructions in the ACL2640 Operator's Guide. FILES mcf The configuration file for Sun StorEdge SAM-FS and Sun SAM-QFS software. SEE ALSO export(1M), import(1M), sam-robotsd(1M). mcf(4). Sun Microsystems Last change: 02 Jun 2004 Device and Network Interfaces acl452(7) NAME acl452 - The ACL 4/52 Automated Tape Library AVAILABILITY SUNWsamfs DESCRIPTION The ACL 4/52 tape library supports 48 DLT tape cartridges and 4 DLT tape drives. The library has a 4 slot import/export unit that may be used to import or export media into the library. These import/export slots may also be used as storage slots thus extending the storage capacity to 52 slots. CONFIGURATION The ACL 4/52 should NOT be configured with auto-clean or auto-load when running Sun StorEdge SAM-FS and Sun SAM-QFS software. Auto-load may be used during initial loading of cartridges as long as the Sun StorEdge SAM-FS and Sun SAM-QFS software is not running. IMPORT/EXPORT MEDIA To import media, the door on the ACL 4/52 must first be opened. To open the door, issue the export(1M) command, then push the OPEN button on the ACL 4/52 front panel. The door should open and you may place media in any of the slots. You may then close the door by pressing the CLOSE button then manually closing the door when the ACL 4/52 display indicates that it is ready. The Sun StorEdge SAM-FS and Sun SAM-QFS software will not recognize the new media until the import(1M) command is issued. Anytime you close the door, you must issue the import function. To export media, use the move(1M) command to move media into the import/export unit then issue the export(1M) command. Push the OPEN button on the ACL 4/52 front panel to open the door. If the door is already open, you must close the door and issue the import command before attempting to move media into the import/export unit. The slot numbers for the import/export unit are 48, 49, 50 and 51. Note: After opening or closing the door, the ACL 4/52 goes offline until it has re-initialized. This will cause delays since the library must become online before any commands may be issued. FILES mcf The configuration file for the Sun StorEdge SAM-FS and Sun SAM-QFS software SEE ALSO export(1M), import(1M), move(1M), sam-robotsd(1M). mcf(4). Sun Microsystems Last change: 02 Jun 2004 Device and Network Interfaces fujitsulmf(7) NAME fujitsulmf - The Fujitsu LMF Automated Tape Library AVAILABILITY SUNWsamfs DESCRIPTION fujitsulmf is the Sun StorEdge SAM-FS and Sun SAM-QFS software interface to the Fujitsu LMF library. This inter- face utilizes the LMF interface supplied by Fujitsu. For more information on LMF, see the LMF MTL Server/Client User's Guide supplied by Fujitsu. CONFIGURATION It is assumed that the site has the LMF server configured and operating with the LMF library. The "equipment identifier" field in the mcf file, (see mcf(4)), is the full path name to a parameters file used by fujitsulmf. This file consists of a list of keyword = value pairs or a keyword followed by a drivename = value pair. All keywords and values are case-sensitive and must be entered as shown. lmfdrive There is one lmfdrive line for every drive assigned to this client. Following the lmfdrive keyword is a drivename = path, where: drivename is the drivename as configured in LMF. path is the pathname to the device. This name must match the "equipment identifier" of an entry in the mcf file. EXAMPLE Here are sample parameters files and mcf entries for an LMF library. # # This is file: /etc/opt/SUNWsamfs/lmf50 # # the name "LIB001DRV000" is from the LMF configuration # lmfdrive LIB001DRV000 = /dev/rmt/0cbn # a comment # # the name "LIB001DRV001" is from the LMF configuration # lmfdrive LIB001DRV001 = /dev/rmt/1cbn # a comment The mcf file entries. # # Sample mcf file entries for an LMF library # /etc/opt/SUNWsamfs/lmf50 50 fj fj50 - /var/opt/SUNWsamfs/catalog/fj50_cat /dev/rmt/0cbn 51 fd fj50 - /dev/samst/c2t5u0 /dev/rmt/1cbn 52 fd fj50 - /dev/samst/c2t6u0 IMPORT/EXPORT Since the physical adding and removing of media in the LMF library is done with LMF utilities, the import/export com- mands will only affect the library catalog. The import com- mand has an optional parameter (see import(1M)) (-v) for supplying the volser to be added. fujitsulmf will verify that LMF knows about the volser before updating the catalog with the new entry. The export command (see export(1M)) will remove the entry from the catalog. CATALOG There are two utilities used to maintain the library catalog used by LMF. build_cat (see build_cat(1M)) is used to build the catalog. dump_cat (see dump_cat(1M)) and build_cat together are used to change the size of the catalog. To initialize a catalog with 1000 slots run: build_cat /tmp/catalog_file < /dev/null then move /tmp/catalog_file to the path pointed to in the mcf file for this media changer. Use import to populate the catalog with the volumes allowed by DAS. Or, you can create a file with the list of volumes and supply it as input to build_cat (see build_cat(1M)) for the format of the input file. If the size of the catalog needs to be increased, execute something like: dump_cat file1 | build_cat -s 2000 /tmp/file2 This would create a new catalog file (/tmp/file2) with room for 2000 entries and initialize it with the entries from file1. This should only be done when the Sun StorEdge SAM-FS and Sun SAM-QFS software is not running and sam-amld has been shutdown (see sam-amld(1M)). FILES mcf The configuration file for the Sun StorEdge SAM-FS and Sun SAM-QFS software. /opt/SUNWsamfs/lib/liblmf2.so The LMF library supplied by Fujitsu. SEE ALSO build_cat(1M), dump_cat(1M), export(1M), import(1M), sam- robotsd(1M). mcf(4). Sun Microsystems Last change: 02 Jun 2004 Device and Network Interfaces grauaci(7) NAME grauaci - The ADIC/Grau Automated Tape Library through the ACI AVAILABILITY SUNWsamfs DESCRIPTION grauaci is the Sun StorEdge SAM-FS and Sun SAM-QFS software interface to the ADIC/Grau Network-attached library. This interface utilizes the DAS/ACI 3.10E interface supplied by ADIC. For more information on DAS/ACI, see the DAS/ACI 3.10E Interfacing Guide and the DAS Administration Guide. Both manuals are supplied by ADIC. CONFIGURATION Sun assumes that your site has the DAS server configured and operating with the ADIC/Grau library. In the DAS configura- tion file for this client, the avc (avoid volume contention) and the dismount parameters should both be set to true. The Equipment Identifier field in the mcf file is the full path name to a parameters file used by grauaci. This file consists of a list of keyword = value pairs or a keyword followed by a drivename = value pair. For more information on the mcf file, see the mcf(4) man page. All keywords and values, including the following, are case sensitive and must be entered as shown: Keyword Value client This is the name of this client as defined in the DAS configuration file. This is a required param- eter. server This is the hostname of the server running the DAS server code. This is a required parameter. acidrive There is one acidrive line for every drive assigned to this client. Following the acidrive keyword is a drivename = path, string that is as follows: drivename The drive name as configured in the DAS configuration file. path The path name to the device. This name must match the Equipment Identifier of an entry in the mcf file. If the library contains different media types, then there must be a separate media changer for each of the media types. Each media changer must have a unique client name in the DAS configuration, a unique library catalog and a unique parameters file. EXAMPLE The following example shows sample parameters files and mcf entries for a ADIC/Grau library supporting DLT tape and HP optical drives. The catalog files are placed in the default directory, which is /var/opt/SUNWsamfs/catalog. # # This is file: /etc/opt/SUNWsamfs/gr50 # client = grau50 server = DAS-server # # the name "drive1" is from the DAS configuration file # acidrive drive1 = /dev/rmt/0cbn # a comment # # the name "drive2" is from the DAS configuration file # acidrive drive2 = /dev/rmt/1cbn # a comment # # This is file: /etc/opt/SUNWsamfs/gr60 # client = grau60 server = DAS-server # # the name "DH03" is from the DAS configuration file # acidrive DH03 = /dev/samst/c1t1u0 The mcf file entries. # # Sample mcf file entries for an ADIC/Grau library - DLT # /etc/opt/SUNWsamfs/gr50 50 gr gr50 - gr50cat /dev/rmt/0cbn 51 lt gr50 - /dev/samst/c2t5u0 /dev/rmt/1cbn 52 lt gr50 - /dev/samst/c2t6u0 # # Sample mcf file entries for an ADIC/Grau library - HP optical # /etc/opt/SUNWsamfs/gr60 60 gr gr60 - gr60cat /dev/samst/c1t1u0 61 od gr60 - IMPORT/EXPORT The physical adding and removing of cartridges in an ADIC/Grau network-attached library is accomplished using the DAS utilities. The import(1M) and export(1M) commands affect only the library catalog. Therefore, importing and exporting cartridges with the ADIC/Grau network-attached library consists of the following two-step process: 1) Physically import or export the cartridge using the DAS utilities. 2) Virtually update the automated library catalog using the Sun StorEdge SAM-FS or Sun SAM-QFS import and export utilities. The import(1M) command has an optional -v parameter for sup- plying the VSN to be added. The grauaci interface verifies that DAS knows about the VSN before updating the catalog with the new entry. The export(1M) command removes the entry from the catalog. For more information on importing and exporting, see the import and export(1M) man pages. CATALOG There are several methods for building a catalog for an ADIC/Grau network-attached library. You should use the method that best suits your system configuration, and this is typically determined by the size of the catalog that is needed. Method 1: Create a catalog with existing VSN entries. (Please note this method only works for tapes. It does not work for barcoded optical media.) You can build a catalog that contains entries for many tapes by using the build_cat(1M) command. As input to build_cat(1M), you need to create a file that contains the slot number, VSN, bar- code, and media type. For example, file input_vsns follows: 0 TAPE01 TAPE01 lt 1 TAPE02 TAPE02 lt 2 TAPE03 TAPE03 lt The input_vsns file can be used as input to the build_cat(1M) command, as follows: build_cat input_vsns /var/opt/SUNWsamfs/grau50cat Method 2: Create a null catalog and import VSN entries. You can create an empty catalog and populate it. To create a catalog that will accommodate 1000 slots, use the build_cat command, as follows: build_cat -s 1000 /dev/null /var/opt/SUNWsamfs/catalog/grau50cat Use the import(1M) command to add VSNs to this catalog, as follows: import -v TAPE01 50 For ADIC/Grau optical media, it is very important to import the A side of barcoded optical media. The Sun StorEdge SAM-FS and Sun SAM-QFS software queries the ADIC/Grau data- base to find the barcode for the B side and fills in the catalog entry for the B side appropriately. The A side of optical media in the ADIC/Grau automated library is the left side of a slot as you face the slots. Method 3: Use the default catalog and import VSN entries. If a catalog path name is not specified in the mcf file, a default catalog is created in /var/opt/SUNWsamfs/catalog/family_set_name when the Sun StorEdge SAM-FS or Sun SAM-QFS software is initialized. Following initialization, you must import VSN entries to this catalog. Use the import(1M) command, as follows: import -v TAPE01 50 In the preceding import(1M) command, 50 is the Equipment Identifier of the automated library as specified in the mcf file. FILES mcf The configuration file for the Sun StorEdge SAM-FS and Sun SAM-QFS software. /opt/SUNWsamfs/lib/libaci.so The ACI library supplied by ADIC. SEE ALSO build_cat(1M), dump_cat(1M), export(1M), import(1M), sam- robotsd(1M). mcf(4). Sun Microsystems Last change: 02 Jun 2004 Device and Network Interfaces historian(7) NAME historian - The Sun StorEdge SAM-FS and Sun SAM-QFS his- torian AVAILABILITY SUNWsamfs DESCRIPTION historian is a catalog that keeps track of volumes that have been exported from an automated library or that have been unloaded from manually loaded devices. CONFIGURATION The historian catalog is similar to the catalog for an automated library but since there are no devices associated with it, has no family set name. If there is no historian catalog configured in the mcf file (see mcf(4)) one will be created as: historian n+1 hy - - /var/opt/SUNWsamfs/catalog/historian Where n+1 is the highest equipment number defined in the mcf file plus 1. The historian catalog will be created with 32 entries when the catalog server initializes and can grow during execu- tion. Each time the catalog fills, 32 entries of approxi- mately 200 bytes each will be added. Make sure the historian's catalog resides on a file system large enough to hold the expected size. Since the catalog is needed before a sam file system can be mounted, DO NOT put the catalog on a Sun StorEdge SAM-FS or Sun SAM-QFS file system. Two configuration parameters in the defaults.conf file (see defaults.conf(4)) affect the way the system will react to requests for media or requests to add media to the historian catalog. If exported_media is set to unavailable, then any media exported from a media changer will be set to unavail- able in the historian. Any request for media flagged as unavailable will receive an ESRCH error. If attended is set to "no" (operator is NOT available), then any request for media in the historian catalog will be sent back to the file system with an error (ESRCH). Any request for media currently loaded in a manually loaded drive will be accepted no matter what the state of the attended or unavailable flags are. EFFECTS OF HISTORIAN Whenever the file system receives the error ESRCH for a stage request, it will automatically generate a stage request for the next archived copy (unless the last stage request was for the last copy). For a removable media request, the error ESRCH will be returned to the user. IMPORT/EXPORT import (see import(1M)) is used to insert entries to the historian catalog. export (see export(1M)) is used to remove entries from the historian catalog. You may export by slot or vsn. CATALOG The catalog server will create a new, empty catalog in the default file location if none exists or no catalog is speci- fied in the mcf file. Alternately, the build_cat command (see build_cat(1M)) may be used to build the initial cata- log. To initialize a catalog with 32 slots run: build_cat - /tmp/catalog_file < /dev/null then move /tmp/catalog_file to the path pointed to in the mcf file for the historian. Or, you can create a file with the list of volumes and supply it as input to build_cat (see build_cat(1M)) for the format of the input file. FILES mcf The configuration file for the Sun StorEdge SAM-FS and Sun SAM-QFS software. defaults.conf Default information. /var/opt/SUNWsamfs/catalog/historian Default historian catalog file. SEE ALSO build_cat(1M), dump_cat(1M), export(1M), sam-robotsd(1M). defaults.conf(4), mcf(4). Sun Microsystems Last change: 02 Jun 2004 Device and Network Interfaces ibm3494(7) NAME ibm3494 - The IBM3494 interface through lmcpd AVAILABILITY SUNWsamfs DESCRIPTION ibm3494 is the Sun StorEdge SAM-FS and Sun SAM-QFS interface to the IBM 3494 library. This interface utilizes the lmcpd interface supplied by IBM. For more information on confi- guration and interfacing the IBM libraries, see the documen- tation supplied with the IBM hardware and for lmcpd. CONFIGURATION It is assumed that the site has the lmcpd daemon configured and operating with the 3494 library. The "equipment identifier" field in the mcf file, (see mcf(4)), is the full path name to a parameters file used by ibm3494. This file consists of keyword = value and path_name = value pairs. All keyword/path_name/values are case-sensitive. The keywords are: name This is the name assigned by the system administra- tor and configured in the /etc/ibmatl.conf file and the symbolic name of the library. This parameter must be supplied, there is no default. category The category is a hex number between 0x0001 and 0xfeff. Media controlled by Sun StorEdge SAM-FS or Sun SAM-QFS will have its category set to this value. The default for category is 4. access Access to the library may be shared or private. If private, then any media imported into the library (category = 0xff00) will be added to the catalog and its category will be changed to that specified by category above. If shared, then the import command (see import(1M)) will have to be used to add media to the catalog. The default for access is private. device_path_name There is one device_path_name entry for every drive in the library attached to this machine. This name must match the Equipment Identifier of an entry in the mcf file. Following the device_path_name is the "device number" as described in the IBM documenta- tion. The system administrator can determine this number by running the IBM supplied utility mtlib. Following the device number is the shared parameter. This parameter is optional and is used to indicate the drive is shared with other Sun StorEdge SAM-FS or Sun SAM-QFS servers. See examples below. EXAMPLE The example uses the following file and information obtained from the IBM supplied utility mtlib. Both are documented in the materials supplied by IBM. # # This is file: /etc/ibmatl.conf # Set this file up according the documentation supplied by IBM. 3493a 198.174.196.50 test1 After lmcpd is running, run mtlib to get the device numbers. mtlib -l 3493a -D 0, 00145340 003590B1A00 1, 00145350 003590B1A01 Here is a sample parameters file and mcf entries for a IBM 3494 library. # # This is parameters file /etc/opt/SUNWsamfs/ibm60. # name = 3493a # From /etc/ibmatl.conf /dev/rmt/1bn = 00145340 # From mtlib output /dev/rmt/2bn = 00145350 shared # From mtlib output access=private category = 5 # These are the mcf file entries. # # IBM 3494 library # /etc/opt/SUNWsamfs/ibm60 60 im ibm3494e - ibmcat /dev/rmt/1bn 61 tp ibm3494e /dev/rmt/2bn 62 tp ibm3494e IMPORT/EXPORT Import media into the library by placing the new media into the I/O slots and closing the door. The library will lock the door and move the media into the storage area. Only 100 volumes can be imported at one time. If you are running with access=private, the library will inform the daemon as the media is moved and the media will be added to the cata- log. If running with access=shared, then an import (see import(1M)) command will need to be executed to add the media to the catalog. Exporting media (in all modes) is performed by the export (see export(1M)) command. This command will move the media to the I/O area and the output mode light on the operator panel will light. The operator can then remove the media from the I/O area. CATALOG If running with access=shared then a catalog will need to be built before starting Sun StorEdge SAM-FS or Sun SAM-QFS. There are two utilities used to maintain the library cata- log. build_cat (see build_cat(1M)) is used to build the catalog. dump_cat (see dump_cat(1M)) and build_cat together are used to change the size of the catalog. To initialize a catalog with 1000 slots run: build_cat /tmp/catalog_file < /dev/null then move /tmp/catalog_file to the path pointed to in the mcf file for this library. (In this case /var/opt/SUNWsamfs/catalog/ibmcat). Use import to populate the catalog with the volumes. Or, you can create a file with the list of volumes and supply it as input to build_cat (see build_cat(1M) for the format of the input file). If the size of the catalog needs to be increased, execute something like: dump_cat file1 | build_cat -s 2000 /tmp/file2 This would create a new catalog file (/tmp/file2) with room for 2000 entries and initialize it with the entries from file1. This can only be done when the Sun StorEdge SAM-FS or Sun SAM-QFS software is not running and sam-amld has been shutdown (see sam-amld(1M)). FILES mcf The configuration file for the Sun StorEdge SAM-FS and Sun SAM-QFS software. /etc/ibmatl.conf Configuration file used by lcmpd. /opt/SUNWsamfs/lib/libibmlmcp.so A shared object version of the runtime library supplied by IBM SEE ALSO build_cat(1M), dump_cat(1M), export(1M), import(1M), sam- robotsd(1M). mcf(4). Sun Microsystems Last change: 02 Jun 2004 Device and Network Interfaces ibm3584(7) NAME ibm3584 - Describes using the IBM 3584 UltraScalable Tape Library with Sun StorEdge SAM-FS or Sun SAM-QFS software AVAILABILITY SUNWsamfs DESCRIPTION The IBM 3584 UltraScalable tape library can be used by Sun StorEdge SAM-FS and Sun SAM-QFS software with few modifications to its typical operations. This man page describes the steps you need to take to use this library effectively. The following topics are described: o Cleaning o Using the IBM 3584 tape library's partitioning feature CLEANING The IBM 3584 UltraScalable Tape Library can be used in a Sun StorEdge SAM-FS or Sun SAM-QFS environment, but you need to disable automatic cleaning and enable hosted cleaning. No other modifications need to be made to this library's default configuration. Host cleaning enables the host to detect the need to clean an Ultrium Tape Drive and to control the cleaning process. Host cleaning with a cleaning cartridge is only supported when you disable automatic cleaning and only for the logical library in which each cleaning cartridge is stored. When you enable automatic cleaning, or when the cleaning cartridge is stored in a different logical library, the host application does not have access to the cleaning cartridge. When automatic cleaning is disabled, the library continues to detect the need to clean a tape drive. When the need is detected, the library displays the physical location of the drive in the following message: CLEAN [Fx,Rzz] The preceding message is interpreted as follows: o F represents the frame, and x represents its number o R represents the row, and xx represents its number The message clears after you clean the drive by using the supported cleaning method. The cleaning cycle takes less than 2 minutes. When you enable or disable automatic cleaning, the selected setting is stored in nonvolatile memory and becomes the default during later power-on cycles. To disable automatic cleaning, perform the following steps: 1. Ensure that a cleaning cartridge is loaded in the library. 2. From the library's activity screen, press MENU. The main menu displays, as follows: -------------------------------------------------------------------------- Main Menu Panel 0002 Library Status Manual Operations Settings Usage Statistics Vital Product Data Service [BACK] [UP] [DOWN] [ENTER] -------------------------------------------------------------------------- 3. Press UP and DOWN to highlight Settings. Press ENTER. The Settings menu displays, as follows: -------------------------------------------------------------------------- Settings Panel 0100 Configuration Cleaning Mode Display/Change SCSI IDs Add/Remove Control Paths Date/Time Sounds [BACK] [UP] [DOWN] [ENTER] -------------------------------------------------------------------------- 4. Press UP or DOWN to highlight Cleaning Mode. Press ENTER. The Cleaning Mode screen displays and indicates whether automatic cleaning is currently enabled or disabled. -------------------------------------------------------------------------- Cleaning Mode Panel 0110 Automatic Cleaning is ENABLED Disable Automatic Cleaning [BACK] [ENTER] -------------------------------------------------------------------------- 5. The ENTER key acts as a toggle switch for the two choices. Press ENTER until Disable Automatic Cleaning is highlighted. You should receive the following message: If you continue you will set the Automatic Cleaning Mode to DISABLED. If you disable automatic cleaning you should ensure that each logical library has at least one cleaning cartridge since host-initiated cleaning can not use a cleaning cartridge located in a different logical library. Do you want to continue? 6. Press YES to disable automatic cleaning. The Cleaning Mode screen redisplays with the new setting. 7. Press BACK until you return to the Activity screen from step 1. PARTITIONING If your IBM 3584 tape library contains 2 or more drives, it can be partitioned into 2 or more logical libraries. If you have partitioned this library, make sure that it is operating as you configured it prior to installing any Sun StorEdge SAM-FS or Sun SAM-QFS software. For more information on partitioning this library, see your IBM documentation. This subsection describes aspects of using the partitioning feature with the Sun StorEdge SAM-FS and Sun SAM-QFS software. When a cartridge is exported (as opposed to being placed in the drawer by a human), only the partition from which it was exported can access that drawer slot. If the cartridge is removed and re-inserted by a human, it is accessable to any/all partitions. The act of removal referred to in this subsection consists of the following steps: 1. Open door. 2. Remove cartridge(s). 3. Close door. 4. Wait for door to lock and then unlock. 5. Open door. 6. Replace cartridge(s). 7. Close door. NOTES Much of the text on this man page was derived from the IBM 3584 UltraScalable Tape Library Planning and Operator Guide, IBM publication GA32-0408-01, copyright IBM Corporation 2000. SEE ALSO IBM 3584 UltraScalable Tape Library Planning and Operator Guide, IBM publication GA32-0408-01. http://www.ibm.com/storage/hardsoft/tape/lto/3584 Sun Microsystems Last change: 03 Dec 2001 Device and Network Interfaces sam-remote(7) NAME sam-remote, sam-clientd, sam-serverd - Describes the Sun SAM-Remote interface and daemons SYNOPSIS /opt/SUNWsamfs/sbin/sam-serverd mshmid pshmid equip /opt/SUNWsamfs/sbin/sam-clientd mshmid pshmid equip AVAILABILITY SUNWsamfs DESCRIPTION The Sun SAM-Remote client and server software allows automated libraries to be shared among the Solaris systems in a Sun StorEdge SAM environment. Sun SAM-Remote allows you to configure multiple storage clients that archive and stage files from a centralized optical and/or tape library. This environment also allows you to make multiple archive copies on various media housed in multiple libraries. DAEMONS The Sun SAM-Remote daemons, sam-serverd and sam-clientd, control Sun SAM-Remote. The sam-robotsd daemon starts the sam-serverd and sam-clientd daemons. The identifiers associated with these daemons are as follows: mshmid The identifier of the master shared memory segment created by sam-amld. pshmid The identifier of the preview shared memory segment created by sam-amld. equip The equipment number of the device. For more information on the sam-robotsd or sam-amld daemons, see the sam-robotsd(1M) or sam-amld(1M) man pages. CONFIGURATION Configuring the Sun SAM-Remote client and server software involves adding lines to the mcf file on both the system to be used as the Sun SAM-Remote client and on the system to be used as the Sun SAM-Remote server. In addition, a client configuration file must be created on the Sun SAM-Remote client, and a server configuration file must be created on the Sun SAM-Remote server. Each entry in mcf file can configure up to ten clients per server. Use more mcf entries to configure more than ten clients. In the mcf file, the Equipment Type field contains sc to define a Sun SAM-Remote client or ss to define a Sun SAM- Remote server. The server configuration file defines the disk buffer characteristics and media to be used for each client. For a client named portland for example: portland media 100 at (000031|000032|000034|000035|000037|000038) endmedia The media definitions must be indented with white space or tab characters. The regex data must be enclosed by parentheses. For a complete description of the Sun SAM-Remote configuration process, see the Sun StorEdge SAM-FS Storage and Archive Managment Guide. FILES mcf The master configuration file for Sun StorEdge SAM, Sun StorEdge QFS, the Sun SAM-Remote client, and the Sun SAM-Remote server. /opt/SUNWsamfs/lib/librmtsam.so The Sun SAM-Remote shared object library. SEE ALSO sam-amld(1M), sam-robotsd(1M). mcf(4). Sun StorEdge SAM Storage and Archive Management Guide. Sun Microsystems Last change: 21 Feb 2003 Device and Network Interfaces samaio(7) NAME samaio - Pseudo Device Driver for AIO AVAILABILITY SUNWqfsr SUNWsamfsr DESCRIPTION The pseudo driver, samaio, allows you to attach a QFS file to a character device, which can then be accessed through that device. setfa -q attaches a QFS file to samaio. When you open a file with the -q attribute set, you use the char- acter device. Samaio translates access to the character device into I/O on the underlying QFS file. This is useful for aio because raw device I/O is faster than file system aio. Samaio is controlled through /dev/samaioctl - this is the only device exported during attach, and is minor number 0. QFS communicates with samaio through ioctls on this device. When a file is attached to samaio, character devices are exported in /dev/rsamaio. These devices are identified by their minor number. Minor devices are tracked with state structures handled with ddi_soft_state(9F). The command ls displays a character device for files with the -q attribute set, The command sls displays a regular file with its current length for files with the -q attribute set, ERRORS EACCES Permission denied. EBUSY The device was opened exclusively by another thread. EFAULT The argument was a bad address. EINVAL Invalid argument. EIO An I/O error occurred. ENOTTY This indicates that the device does not sup- port the requested ioctl function. ENXIO During opening, the device did not exist. FILES /dev/samaioctl Master control device /dev/rsamaio/n Character device for file n /kernel/drv/samaio 32-bit driver /kernel/drv/samaio.conf Driver configuration file. (Should not be altered.) /kernel/drv/sparcv9/samaio 64-bit driver SEE ALSO driver.conf(4), devfsadm(1M), setfa(1), sam_setfa(3) Sun Microsystems Last change: 30 Jun 2004 Device and Network Interfaces samst(7) NAME samst - Driver for SCSI media changers and optical drives SYNOPSIS samst@target,lun:a AVAILABILITY SUNWsamfs DESCRIPTION This driver handles embedded SCSI-2 and CCS-compatible SCSI media changers, optical drives, CD-ROM drives and non-motion I/O for tape drives The type of device is determined using the SCSI inquiry com- mand. The only I/O supported for optical devices is "raw". samst supports 512-, 1024-, 2048-, and 4096-byte sector sizes for optical media. The names of the raw files are found in /dev/samst. Special handling during open If O_NDELAY or O_NONBLOCK is specified on the open, then the device does not have to be in the ready state for the open to succeed. This allows the opening of a device for ini- tialization or to check the media type. ERRORS EACCES Permission denied. EBUSY The device was opened exclusively by another thread. EFAULT The argument was a bad address. EINVAL Invalid argument. EIO An I/O error occurred. ENOTTY This indicates that the device does not sup- port the requested ioctl function. ENXIO During opening, the device did not exist. FILES /kernel/drv/samst.conf driver configuration file /dev/samst/cntnun raw files where: cn controller n tn SCSI target id n (0-6) un SCSI LUN n (0-7) SEE ALSO samdev(1M). driver.conf(4). ANSI Small Computer System Interface-2 (SCSI-2) DIAGNOSTICS Error for command '' Error Level: Fatal Requested Block , Error Block: Sense Key: Vendor '': ASC = 0x (), ASCQ = 0x, FRU = 0x The command indicated by failed. The Requested Block is the block where the transfer started and the Error Block is the block that caused the error. Sense Key, ASC, and ASCQ information is returned by the target in response to a request sense command. Check Condition on REQUEST SENSE A REQUEST SENSE command completed with a check condi- tion. The original command will be retried a number of times. Not enough sense information The request sense data was less than expected. Request Sense couldn't get sense data The REQUEST SENSE command did not transfer any data. Reservation Conflict The drive was reserved by another initiator. SCSI transport failed: reason 'xxxx' : {retrying|giving up} The host adapter has failed to transport a command to the target for the reason stated. The driver will either retry the command or, ultimately, give up. Unhandled Sense Key The REQUEST SENSE data included an invalid sense key. Unit not Ready. Additional sense code 0x The drive is not ready. device busy too long The drive returned busy during a number of retries. incomplete read/write - retrying/giving up There was a residue after the command completed nor- mally. logical unit not ready The unit is not ready. NOTES This driver can accept removable media devices that identify themselves as "direct access" by setting the variable samst_direct to a nonzero value. You can do this using the set command in the /etc/system file (see system(4)). Whenever a new version of Sun StorEdge SAM-FS or Sun SAM-QFS is installed, the existing samst.conf file is copied to samst.conf.MMDDYY for reference and backup purposes. Sun Microsystems Last change: 05 Nov 2001 Device and Network Interfaces sony(7) NAME sony - Attaches a Sony network-attached tape library through the DZC-8000S interface AVAILABILITY SUNWsamfs DESCRIPTION The Sun StorEdge SAM-FS software package contains the Sun StorEdge SAM-FS and Sun SAM-QFS interface to a Sony network-attached library. This interface uses the DZC-8000S 3.01 interface supplied by Sony. For more information on DZC-8000S, see the Sony PetaSite Application Interface DZC- 8000S manual. This manual is supplied by Sony. CONFIGURATION It is assumed that the site has the PetaSite Controller (PSC) configured and operating with the Sony library. In the Execute Mode of the PSC configuration, the following must be set to on: o Thread With Load o Unthread with Fast Unload o Unthread with Eject o Wait for Drive Use The Equipment Identifier field in the Sun StorEdge SAM-FS or Sun SAM-QFS mcf file must be the full path name to a Sony parameters file. For more information on specifying a parameters file, see the mcf(4) man page. The parameters file consists of a list of keyword = value pairs. All keyword and value specifications are case-sensitive and must be entered as shown on this man page. The keyword and value specifications are as follows: userid = userid Identifies the user during initialization of the Sony library functions. The userid values can be specified in hexadecimal or decimal. The valid range is from 0 to PSCUSERIDMAX(0xfff), which is 0 <= userid <= 65535 (decimal) or 0 <= userid <= 0xffff (hexadecimal). This is a required parameter. server = serverid Specifies the host name of the server running the PSC server code. This is a required parameter. sonydrive binnum = path [ shared ] Specifies characteristics of the tape drive. There must be one sonydrive line for every drive assigned to Sun StorEdge SAM-FS or Sun SAM-QFS in the mcf file. This name must match the Equipment Identifier of an entry in the mcf file. The following arguments follow the sonydrive keyword: binnum Specifies the bin number assigned to the drive in the PSC configuration. The bin number can be identified using the PSC Monitoring and Maintenance terminal. This is a required argument. path Specifies the Solaris /dev/rmt/ path name to the device. The path must match the Equipment Identifier of an entry in the mcf file. This is a required argument. shared Specifies that this drive is shared with other processes. For example, this drive can be shared between multiple Sun StorEdge SAM-FS or SAM-QFS servers. This is an optional argument. EXAMPLE The following example shows the configuration files for a network-attached Sony library with Sony DTF tapes. Here are the sample entries in the mcf file. The catalog file is placed in the default directory, which is /var/opt/SUNWsamfs/catalog. The mcf file is as follows: # # This is the file: /etc/opt/SUNWsamfs/mcf # This file shows sample mcf entries for a Sony network-attached # robot with Sony DTF tapes. # /etc/opt/SUNWsamfs/sonyfile 50 pe sony50 on /var/opt/SUNWsamfs/sony50cat /dev/rmt/0cbn 51 so sony50 on /dev/rmt/1cbn 52 so sony50 on The parameters file for a Sony library supporting Sony DTF tapes is as follows: # # This is file: /etc/opt/SUNWsamfs/sonyfile # # The userid identifies the user during initialization of # the PetaSite library functions. Valid IDs are 0 to # PSCUSERIDMAX(0xfff). # userid = 65533 # # The server identifies the hostname for the server running # the DZC-8000S server code. # server = europa # # The sonydrive bin number 1001 is from the PSC configuration file # sonydrive 1001 = /dev/rmt/0cbn shared # a comment # # The sonydrive bin number 1002 is from the PSC configuration file # sonydrive 1002 = /dev/rmt/1cbn # a comment IMPORT/EXPORT The physical adding and removing of cartridges in a Sony network-attached library is accomplished using the PSC utilities. The import(1M) and export(1M) commands affect only the library catalog. Therefore, importing and exporting cartridges with the Sony network-attached library proceeds according to the following two-step process: 1. Physically import or export the cartridge using the PSC software. 2. Virtually update the library catalog using the Sun StorEdge SAM-FS or Sun SAM-QFS import/export utilities. The import(1M) command has an optional -v option that allows you to specify the VSN to be added. The samsony package verifies that PSC knows about the VSN before updating the catalog with the new entry. The export(1M) command removes the entry from the catalog. CATALOG There are several methods for building a catalog for a Sony network-attached library. You should use the method that best suits your system configuration, typically depending on the size of the catalog that is needed. Method 1: Create a catalog with existing VSN entries. You can build a catalog that contains entries for many tapes by using the build_cat(1M) command. As input to the build_cat(1M) command, you need to create a file that contains the slot number, VSN, bar code label, and media type. For example, the file input_vsns follows: 0 "SEG001" "SEG001" so 1 "SEG002" "SEG002" so 2 TEST1 TEST1 so 3 TEST2 TEST2 so The input_vsns file can be used as input to the build_cat(1M) command as follows: build_cat input_vsns /var/opt/SUNWsamfs/sony50cat Method 2: Create a null catalog and import VSN entries. You can create an empty catalog and populate it. To create a catalog that will accommodate 1000 slots, use the build_cat(1M) command as follows: build_cat -s 1000 /dev/null /var/opt/SUNWsamfs/catalog/sony50cat Use the import(1M) command to add VSNs to this catalog, as follows: import -v "SEG005" 50 Method 3: Use the default catalog and import VSN entries. If a catalog path name is not specified in the mcf file, a default catalog is created in /var/opt/SUNWsamfs/catalog/family_set_name when Sun StorEdge SAM-FS or Sun SAM-QFS is initialized. Following initialization, you must import VSN entries to this catalog by using the import command as follows: import -v "SEG005" 50 In the previous import(1M) command, 50 is the Equipment Ordinal of the library as specified in the mcf file. FILES mcf The configuration file for the Sun StorEdge SAM-FS and Sun SAM-QFS software. /opt/SUNWsamfs/lib/libpsc.so The PSC library supplied by Sony. SEE ALSO build_cat(1M), dump_cat(1M), export(1M), import(1M), sam- robotsd(1M). mcf(4). Sun Microsystems Last change: 02 Jun 2004 Device and Network Interfaces ssi.sh(7) NAME ssi.sh - The configuration file for the StorageTek (STK) Client System Interface CSI. AVAILABILITY SUNWsamfs DESCRIPTION ssi.sh is a script that allows users to select values for several dynamic environment variables used by the CSI. The STK API code defines default values for these variables if they are not defined dynamically. To allow the most flexi- bility in setting these variables, a shell script /etc/opt/SUNWsamfs/scripts/ssi.sh, is used by the sam- stkd(1M) daemon, to start the ssi_so. In general, most sites do not need to change the variables within this script. CONFIGURATION An example script can be found in /opt/SUNWsamfs/examples/ssi.sh. This script, or a user created script, must be copied to /etc/opt/SUNWsamfs/scripts/ssi.sh It is assumed that the site has the server daemons (CSI and ACSLM) configured and operating with the STK library. The following environment variables are defined in the shell script supplied in /opt/SUNWsamfs/examples/ssi.sh: CSI_TCP_RPCSERVICE This variable is used to define whether the CSI operates as a TCP RPC Server. This environmental variable must be set to TRUE for the firewall-secure CSC. The firewall-secure ACSLS applications packets are all sent using the TCP network transport. CSI_UDP_RPCSERVICE This variable is used to define whether the CSI operates as a UDP RPC server. This environmental variable must be set to FALSE for the firewall- secure CSC. The firewall-secure ACSLS applications packets are all sent using the TCP network tran- sport. The CSI can operate as a TCP and a UDP server simul- taneously. CSI_CONNECT_AGETIME This defines the value of the maximum age of pending requests in the CSI's request queue. This variable is accessed as a "C" character array datatype, expressed as an integer number of seconds. A value of 172800 indicates two days. Messages older than this value are removed from the queue and the CSI sends an entry to the Event Log when this happens. CSI_RETRY_TIMEOUT This defines the minimum amount of time, in seconds, that the CSI will wait between attempts to establish a network connection. CSI_RETRY_TRIES This variable defines the number of attempts the CSI will make to transmit a message. Pending messages are discarded if a connection cannot be established within the defined number of tries. The CSI_RETRY_TIMEOUT and CSI_RETRY_TRIES together determine the minimum total time the CSI will attempt to send a message. SEE ALSO sam-robotsd(1M). stk(7), ssi_so(7). Sun Microsystems Last change: 12 Jan 2004 Device and Network Interfaces ssi_so(7) NAME ssi_so - The StorageTek (STK) ACSAPI client daemon. AVAILABILITY SUNWsamfs DESCRIPTION ssi_so is a shared object version of the SSI daemon supplied by STK. This daemon is the interface that samfs uses (see stk(7)) to communicate with the ACSLM. The ssi needs a number of parameters set to communicate with the ACSLM. These parameters are set through shell environ- ment variables. To allow the most flexibility in setting these variables, a shell script (/etc/opt/SUNWsamfs/scripts/ssi.sh) is used by the stk dae- mon (see sam-stkd(1M)), to start a ssi_so daemon. In gen- eral, most sites should not need to change the variables within this script. SEE ALSO sam-robotsd(1M). stk(7). Sun Microsystems Last change: 12 Jan 2004 Device and Network Interfaces stk(7) NAME stk - The StorageTek interface through ACSAPI AVAILABILITY SUNWsamfs DESCRIPTION stk is the Sun StorEdge SAM-FS and Sun SAM-QFS interface to the StorageTek libraries. This interface utilizes the ACSAPI interface supplied by StorageTek. The Sun StorEdge SAM-FS software package installs the libraries and daemons for the client side of the API. For more information on ACSAPI and interfacing the StorageTek libraries, see the documentation supplied with the StorageTek hardware and server side daemons. CONFIGURATION It is assumed that the site has the server daemons (CSI and ACSLM) configured and operating with the StorageTek library. The Equipment Identifier field in the mcf file, (see mcf(4)), is the full path name to a parameters file used by stk. This file consists of keyword = value and path_name = value pairs. All keyword, path_name, and value entries are case-sensitive. The keywords are: access This is the user_id used by this client for access control. If this parameter is not supplied, the access control string will be a null string (no user_id). hostname This is the hostname for the server that is running ACSLS. If the hostname is not supplied, the default will be localhost. All sites should set this value. ssihost This is the name used for the Sun StorEdge SAM-FS server when a multihomed Sun StorEdge SAM-FS server is used. The ssihost would be the name of the Sun StorEdge SAM-FS server on the lan connecting to the ACSLS host. Only sites where a multihomed Sun StorEdge SAM-FS server is used need to supply an ssihost value. The default will be localhost. portnum This is the portnum for SSI services on the server that is running ACSLS. If the port number is not supplied, the default is 50004. Please note that if you are running co-hosted ACSLS 5.3 or higher, the default value does not work (try a higher port number, like 50014). If you are running multiple connections to ACSLS servers, then the port number for each stk configuration file needs to be unique (for example, 50014 in one, 50015 in the next, etc.). ssi_inet_port This is the fixed port number for incoming responses and specifies the port the SSI will use for incoming ACSLS responses in a firewall environment. Valid values are 1024 - 65535, and 0. Setting this environmental variable to a non-zero value makes the SSI use this port for incoming ACSLS responses. This means that the firewall needs to allow incoming requests on that port in order for the ACSLS responses to be received by the SSI. Setting this value to zero or leaving it unset indicates that the previous behavior of allowing the port to be dynami- cally allocated will remain in effect. csi_hostport This firewall environmental variable specifies the port to which the SSI will send its ACSLS requests on the ACSLS server. Setting this variable eliminate queries to the portmapper on the ACSLS server and instead, sends requests to this port on the ACSLS server. Valid values are 1024 - 65535, and 0. Set- ting this variable to zero or leaving it unset indi- cates that the previous behavior of querying the portmapper on the ACSLS server will continue to be used. capid This specifies the CAP (Cartridge Access Port) to be used for exporting of volumes when the -f option is used with export command. Following the capid is the description of this CAP in terms of the StorageTek library. This description starts with an open parenthesis followed by 3 keyword = value pairs followed by a close parenthesis. The keyword = value pairs between the parentheses may be separated by a comma (,), a colon (:) or by white space. acs is the ACS number for this CAP as configured in the StorageTek library. lsm is the LSM number for this CAP as configured in the StorageTek library. cap is the CAP number for this CAP as configured in the StorageTek library. capacity This is used to set the capacity of the media supported by the StorageTek. The parameter to capacity is a comma separated list of index = value pairs enclosed in parentheses. index is the index into the media_type file (supplied by StorageTek and located on the ACS system) and value is the capacity of that media type in units of 1024 bytes. You should only need to supply this entry if the ACS is not returning the correct media type or new media types have been added. Sun StorEdge SAM-FS and Sun SAM-QFS have defaults for index values that were current at the time of release. Gen- erally, it is necessary to supply an index only for new cartridge types. For the capacity of each cartridge type, see the Sun StorEdge SAM-FS Storage and Archive Management Guide. device_path_name There is one device_path_name entry for every drive attached to this client. The device_path_name is the path to the device on the client. This name must match the Equipment Identifier of an entry in the mcf file. Following the device_path_name is the description of this drive in terms of the StorageTek library. This description starts with an open parenthesis followed by 4 keyword = value pairs followed by a close parenthesis. The keyword = value pairs between the parentheses may be separated by a comma (,), a colon (:) or by white space. Following the close parenthesis is an optional keyword used by Sun StorEdge SAM-FS and Sun SAM-QFS software to designate when a drive is shared with other Sun StorEdge SAM-FS and Sun SAM-QFS servers. The keyword identifiers and their meanings are as follows: acs is the ACS number for this drive as configured in the StorageTek library. lsm is the LSM number for this drive as configured in the StorageTek library. panel is the PANEL number for this drive as configured in the StorageTek library. drive is the DRIVE number for this drive as configured in the StorageTek library. shared The shared keyword follows the close parenthesis. This keyword is optional and is used to indicate the drive is shared with other Sun StorEdge SAM-FS and Sun SAM-QFS servers. EXAMPLE Here is a sample parameters file and mcf entries for a StorageTek library: # # This is file: /etc/opt/SUNWsamfs/stk50 # hostname = acsls_server_name portnum = 50004 ssi_inet_port = 0 csi_hostport = 0 access = some_user # No white space allowed in the user_id field capid = (acs=0, lsm=1, cap=0) /dev/rmt/0cbn = (acs=0, lsm=1, panel=0, drive=1) #a comment /dev/rmt/1cbn = (acs=0, lsm=1, panel=0, drive=2) shared #a comment capacity = (0=215040, 1=819200, 5=10485760) The mcf file entries that reference this configuration file are: # # Sample mcf file entries for a StorageTek library # /etc/opt/SUNWsamfs/stk50 50 sk sk50 - /var/opt/SUNWsamfs/catalog/sk50 /dev/rmt/0cbn 51 st sk50 - /dev/rmt/1cbn 52 st sk50 - IMPORT/EXPORT Since the physical adding and removing of cartridges in the StorageTek library is done with ACSLM utilities, the import/export commands and GUI buttons will only affect the library catalog. The import command has optional parameters for supplying a single volume to be added or to add a number of volumes from a pool (see import(1M)). export (see export(1M)) will remove an entry from the catalog. CATALOG The Sun StorEdge SAM-FS and Sun SAM-QFS systems automati- cally build a library catalog for a StorageTek automated library. However, you must populate the library catalog. For information on populating the library catalog, see the Sun StorEdge SAM-FS Storage and Archive Management Guide. FILES mcf The configuration file for the Sun StorEdge SAM-FS and Sun SAM-QFS software. /etc/opt/SUNWsamfs/scripts/ssi.sh A shell script used to start ssi_so. /opt/SUNWsamfs/sbin/ssi_so A shared object version of the SSI daemon supplied by StorageTek. /opt/SUNWsamfs/lib/stk/* The libraries needed by the API interface supplied by StorageTek. /opt/SUNWsamfs/sbin/stk_helper A program to issue commands for the StorageTek ACSAPI SEE ALSO build_cat(1M), dump_cat(1M), export(1M), import(1M), sam- robotsd(1M). mcf(4). ssi_so(7). Sun StorEdge SAM-FS Storage and Archive Management Guide. Sun Microsystems Last change: 02 Jun 2004