Chapter 4. Basic Administration

This chapter describes the ACSLS directory structure and tells how to perform the following basic ACSLS administrator tasks:

• Auditing the library

• Maintaining the ACSLS database

• Reconfiguring ACSLS

---

ACSLS Directory Structure

Table 6. ACSLS Directory Structure
Directory		Contents
/export/backup/		Database backups (for single disk systems).
/etc/		Miscellaneous UNIX files.
/etc/hosts		List of machines on the network and their addresses.
/etc/passwd		Basic information for each authorized user on the network.
/etc/networks		Information describing the TCP/IP network.
/etc/netmasks		Network masks used to implement IP standard subnetting.
/etc/rc		Command script; includes instructions to start up ACSLS automatically on system reboot.
/export/home/ACSSS/		ACSLS home directory. (By default, the ACS_HOME environment variable points to this directory.)
/export/home/ACSSS/.acsss_env		Defines the ACSLS environment variables.
/export/home/ACSSS/.login		Defines the ACSLS working environment; used by the C shell.
/export/home/ACSSS/.profile		Defines the ACSLS working environment; used by the k or Bourne shell.
/export/home/ACSSS/kill.acsss		ACSLS shutdown script.
/export/home/ACSSS/rc.acsss		ACSLS startup script.
/export/home/ACSSS/bin/		Contains executable shell scripts and programs.
/export/home/ACSSS/bin/ acsss_config		ACSLS configuration program.
/export/home/ACSSS/bin/back up.sh		Automatic database backup script.
/export/home/ACSSS/bin/ bdb.acsss		Manual database backup script.
/export/home/ACSSS/bin/ db_command		Database startup/shutdown script.
/export/home/ACSSS/bin/ db_export.sh		Database export script.
/export/home/ACSSS/bin/ db_import.sh		Database import script.
/export/home/ACSSS/bin/ rdb.acsss		Database recovery script.
/export/home/ACSSS/bin/ volrpt.exe		Executable to run volume report script.
/export/home/ACSSS/config/		Contains ACSLS configuration files.
/export/home/ACSSS/data/externa l/		Contains customized files used in access control, mixed media, and volume reporting.
/export/home/ACSSS/data/externa l/access_control/		Contains access control sample and customized files.
/export/home/ACSSS/data/ex ternal/access_con trol/ adi.names		Lists ADI names and user IDs of all hosts (OSLAN protocol).
/export/home/ACSSS/data/ex ternal/access_con trol/ adi.names.SAMPLE		Sample adi.names file; not actually used for controlling access.
/export/home/ACSSS/data/ex ternal/access_control/ com mand.ALL.allow		Lists users allowed to use all commands.
/export/home/ACSSS/data/ex ternal/access_control/ com mand.command.allow		Lists users allowed to use this command.
/export/home/ACSSS/data/ex ternal/access_control/ com mand.command.disallow		Lists users not allowed to use this command.
/export/home/ACSSS/data/ex ternal/access_control/ com mand.SAMPLE.allow		Sample command allow file; not actually used for controlling access.
/export/home/ACSSS/data/ex ternal/access_control/ com mand.SAMPLE.disallow		Sample command disallow file; not actually used for controlling access.
/export/home/ACSSS/data/ex ternal/access_control/ in ternet.addresses		Lists Internet addresses and user IDs of all hosts (TCP/IP protocol).
/export/home/ACSSS/data/ex ternal/access_control/ in ternet.addresses.SAMPLE		Sample internet.addresses file; not actually used for controlling access.
/export/home/ACSSS/data/ex ternal/access_control/ ow nership.assignments		Information about assigning ownership to volumes.
/export/home/ACSSS/data/ex ternal/access_control/ us ers.ALL.allow		Lists users allowed to access owned volumes with all commands.
/export/home/ACSSS/data/ex ternal/access_control/ us ers.ALL.disallow		Lists users not allowed to access owned volumes with any command.
/export/home/ACSSS/data/ex ternal/access_control/ us ers.command.allow		Lists users allowed to access owned volumes with this command.
/export/home/ACSSS/data/ex ternal/access_control/ us ers.command.disallow		Lists users not allowed to access owned volumes with this command.
/export/home/ACSSS/data/ex ternal/access_control/ us ers.SAMPLE.allow		Sample volume allow file; not actually used for controlling access.
/export/home/ACSSS/data/ex ternal/access_control/ us ers.SAMPLE.disallow		Sample volume disallow file; not actually used for controlling access.
/export/home/ACSSS/data/externa l/fixed_volume		Contains Extended Store Feature sample and customized files.
/export/home/ACSSS/data/ex ternal/fixed_vol ume lsm_fixed_volume		Extended Store Feature Control file; must be modified to enable this feature.
/export/home/ACSSS/data/externa l/mixed_media/		Contains mixed media sample and customized files.
/export/home/ACSSS/data/ex ternal/mixed_media/ scratch_preferences.dat		Lists transport types and a (user-defined) prioritized list of media types to use when selecting scratch volumes.
/export/home/ACSSS/data/ex ternal/mixed_media/ scratch_preferences.SAMPLE		Sample scratch preferences file; not actually used for controlling media.
/export/home/ACSSS/data/externa l/volrpt/		Contains volume report sample and customized scripts.
/export/home/ACSSS/data/ex ternal/volrpt/ own er_id.volrpt		Sample custom volume report input file.
/export/home/ACSSS/data/interna l/mixed_media/		Contains ACSLS internal mixed media files. Do not modify these files.
/export/home/ACSSS/data/in ternal/mixed_media/ drive_types.dat		Lists supported transport types.
/export/home/ACSSS/data/in ternal/mixed_media/ me dia_cleaning.dat		Lists transport types and compatible cleaning cartridge types.
/export/home/ACSSS/data/in ternal/mixed_media/ me dia_compatibility.dat		Lists transport types and compatible media types.
/export/home/ACSSS/data/in ternal/mixed_media/ me dia_types.dat		Lists supported media types.
/export/home/ACSSS/diag/		Contains diagnostic files and shell scripts.
/export/home/ACSSS/ diag/ bin/pinglmu.sh		Post-configuration tool to check connections between ACSLS server and serial libraries.
/export/home/ACSSS/ diag/ bin/probe-scsi.sh		Post-configuration tool to check connections between ACSLS server and SCSI libraries.
/export/home/ACSSS/ diag/ bin/README.txt		Describes the utilities in /export/home/ACSSS/diag/bin .
/export/home/ACSSS/ diag/ data/ivp.dat		Data file used to drive the IVP mount/dismount activities.
/export/home/ACSSS/ diag/ ivp/ivp.sh		Initial Verification Program (IVP) used for testing the mount/dismount commands.
/export/home/ACSSS/ diag/ ivp/README.ivp		Explanation of the IVP process.
/export/home/ACSSS/install/		Contains ACSLS installation scripts.
/export/home/ACSSS/install/ full_disk.sh		Oracle automatic checkpoint backup script.
/export/home/ACSSS/install/ sd_mgr.sh		Second disk installation script.
/export/home/ACSSS/lib/		Contains ACSLS installed shared libraries required at runtime.
/export/home/ACSSS/log/		Contains ACSLS event log and utility event log files.
/export/home/ACSSS/log/ acsss_config.log		Report of the library hardware configured by the acsss_config program.
/export/home/ACSSS/ log/ acsss_config_event.log		Logs events for the acsss_config program.
/export/home/ACSSS/log/ acsss_event.log		ACSLS event log.
/export/home/ACSSS/log/ bdb_event.log		Logs events for the bdb_acsss script.
/export/home/ACSSS/log/ cron_event.log		Logs events for the cron job that calls the full_disk.sh script.
/export/home/ACSSS/log/ex port_event.log		Logs events for the db_export.sh script.
/export/home/ACSSS/log/ full_disk.sh.log		Logs events for the full_disk.sh script.
/export/home/ACSSS/log/im port_event.log		Logs events for the db_import.sh script.
/export/home/ACSSS/log/ install.log		Logs events for the install.sh script.
/export/home/ACSSS/log/ rdb_event.log		Logs events for the rdb.acsss script.
/export/home/ACSSS/log/ scsilh.log		Logs events for SCSI LSM activity while in diagnostic mode.
/export/home/ACSSS/log/ sd_event.log		Logs events for the sd_mgr.sh script.
/export/home/ACSSS/log/ volrpt.log		Logs events for the volume report script.
/export/home/oracle/		Oracle database home directory.
/second_disk/		Second disk files (if using second-disk journaling).
/second_disk/ backup/		Database backups (if using second-disk journaling).
/tmp/		Temporary files.
/tmp/ acsss.pid		ACSLS process ID file; used in ACSLS startup and shutdown.

---

Auditing the Library

When to Run an Audit

• Create volume information in the database if you do not enter volumes through the CAP. For example, run an audit if you add an LSM to your library, open the LSM door, and manually add volumes to the LSM.

• Resolve discrepancies between the library and the database. For example, run an audit if you open an LSM door and manually remove volumes instead of ejecting them through the CAP. The audit deletes information for the removed volumes from the database.

• View the contents of cells specified by the audit (you must have a display monitor connected to the LSM robot's vision system).

• An external label that duplicates one already scanned.

• A missing or unreadable external label and no virtual label.

• An invalid media type.

Caution: Caution: Auditing the library deletes any database information about scratch pools, virtual volumes, volume types (data, scratch, clean), and access control.

Audit Intervals

Table 7. How the Scope of an Audit Affects the Audit Interval
This audit takes less time than...		This audit
A diagnostic ACS/LSM		An online ACS/LSM
An ACS/LSM dedicated to the audit		An ACS/LSM processing other requests
A full panel		A (partially or completely) empty panel
A drive panel		A standard panel
An inside panel		An outside panel

In addition, consider the LSM type for the component you audit, as shown in Table 8.

Table 8. Average Audit Times for Supported LSMs
LSM Type	Component	Average Audit Time
4410	LSM Panel Single cell	8.5 hours 25 minutes 15 seconds
9310	LSM	45 minutes
9360	LSM	5 minutes
97xx	LSM	1 minute
Note: These times assume no other active processes.

---

Maintaining the ACSLS Database

Table 9. ACSLS Database Information
Type of data	Examples	Loaded by
library configuration	ACS IDs LSM IDs transport IDs CAP IDs	acsss_config
volume data	vol_id (equivalent to the cartridge's external label) volume type (data, scratch, clean) media type (for example, 3480 cartridge) current location in the library (either a cell location or a library drive) State (in use, reserved by a process, or available) usage (how often used, date and time of last use) owner	audit, enter, eject

See Also

• Standard volume report

• Custom volume report

• query commands

Automatic Database Backup

Table 10. Checkpoint and Redo Log Files
File type		Definition and Use
checkpoint file		Provides a point-in-time snapshot copy of the entire database.
redo log files		Transaction records of database changes made since the last checkpoint. During database recovery using rdb.acsss, these files are applied sequentially to the checkpoint to re-create the database including all transactions since the checkpoint.

If you need to recover the database, the rdb.acsss utility uses the most current checkpoint on disk plus any redo log files that exist to restore the database to its current state. The redo log files, however, can consume considerable disk space. Therefore, the automatic checkpoint backup process makes the backup, then deletes the redo log files to free up space.

ACSLS also automatically creates a checkpoint backup file if less than six days have elapsed since the last backup but the free space available in the filesystem that contains the database drops to below a pre-determined safe zone (currently set to 50000 Kbytes). In this case, ACSLS also makes a check point backup, then deletes the redo log files to free up space.

Hint: For ACSLS 5.2 and above, StorageTek requires a two disk (primary and secondary) configuration for the ACSLS server. A two-disk configuration optimizes the database's ability to create checkpoint and redo log files and to recover from failures using these files. On a single-disk server, the database, automatic checkpoint backup, and the redo log files reside on different partitions of the single disk. On a two-disk server, the database resides on the primary disk and the automatic checkpoint backup and the redo log files reside on the second disk. If the primary disk fails on a two-disk server, you can recover the database (including transactions from the redo log files) from the backup and redo log files on the second disk. If the hardware configuration includes a second disk for database support and the second disk fails, you must deinstall the second disk using sd_mgr.sh. No data is lost, but running bdb.acsss more frequently is advised. When the second disk is replaced, rerun sd_mgr.sh to reinstall second disk support. If the disk fails on a single-disk server, you must recover the database (which does not include transactions from the redo log files) from a tape backup or from a file backup on a remote disk. For more information, see the second disk installation section in ACSLS Installation and Configuration Guide for your platform.

Doing Manual Backups to Tape

How often you back up the database depends on the amount of library activity. In general, you should back up the database often for frequent changes to library contents or configuration.

StorageTek recommends that you use bdb.acsss to manually back up the database to tape after:

• Running acsss_config.
• Importing the database. After you upgrade to a new version of ACSLS, do not use database backups or exports created with previous versions. Make sure, however, to create a new backup as soon as you have upgraded.
• A significant number of enters, ejects, scratch mounts, or volume state changes, such as from scratch to data or from locked to unlocked.
• Any database recovery.

The following sections describe how to back up the database and miscellaneous library resource files to the following:

• The default tape device attached and configured to the ACSLS server.

• A specified tape device attached and configured to the ACSLS server.

• To a UNIX file.

See Also

• bdb.acsss utility

• rdb.acsss utility.

• Restoring the database.

To back up the ACSLS database to the default tape device attached to the ACSLS server, do the following:

1. Login as acsss.

2. Insert a blank tape into the tape device.

3. Enter the following command:

   bdb.acsss
   

4. Wait for the following message to appear:

   ACSLS database backup successfully completed.
   

See Also

• Backing up to a Specified Tape Device Attached to the ACSLS Server.

• Backing up to UNIX files.

To back up the ACSLS database to a specified tape device attached to the ACSLS server, do the following:

1. Login as acsss.

2. Insert a blank tape into the tape device.

3. Enter the following command:

   bdb.acsss -f tape_device
   

   Where tape_device specifies a tape device attached to the ACSLS server.

4. Wait for the following message to appear:

   ACSLS database backup successfully completed.
   

bdb.acsss -f /dev/rmt/2

See Also

• Backing up to the Default Tape Device Attached to the ACSLS Server.

• Backing Up to a UNIX File.

Hint: StorageTek does not recommend that you back up to a UNIX file unless the file is on a remote disk.

To back up the ACSLS database to a UNIX file, do the following:

1. Login as acsss.

2. Enter the following command:

   bdb.acsss -f db_file 
   

   Where db_file specifies a UNIX file to contain the ACSLS database. You must have write permissions to the file.

3. Wait for the following message to appear:

   ACSLS database backup successfully completed.
   

See Also

• Backing up to the Default Tape Device Attached to the ACSLS Server.

• Backing up to a Specified Tape Device Attached to the ACSLS Server.

Restarting the Database

To restart the database, do the following:

1. Log in as acsss and open a UNIX command tool.

2. Enter the following command:

   db_command start
   

See Also

• Stopping ACSLS.

---

Reconfiguring ACSLS

Library Configuration Data

ACS data

The number of ACSs in the library, their identifiers, and the number of communication lines (ports) to each ACS. All ACSs in a library share the same database.

LSM data

The number of LSMs in each ACS and their identifiers; the location of each library drive, CAP, and PTP attached to each LSM; and the location and identifiers of adjacent LSMs.

Device states

The state and activity of each hardware component.

Cell map

A map of all storage cells in the library and their contents.

When You Must Reconfigure ACSLS

Examples of configuration changes requiring an update to the database include:

• Adding or removing an ACS, LSM (including a SCSI-driven LSM such as the 9710), Pass-Thru Port (PTP), transport, or standby LMU

• Changing the "master/slave" relationship between two LSMs

• Adding or removing a port connection between the server system and the LMU

Adding a SCSI-Driven Library to ACSLS

To add a SCSI-driven LSM to ACSLS, do the following:

1. Login as acsss.

2. Change to the install directory:

   cd /ACSSS/install
   

3. Login as root.

   su root
   

4. Enter the following command:

   . /install_scsi_platform.sh
   

   Where platform is sol for Solaris.

5. Respond to the prompts to install the SCSI device driver.

Reconfiguring ACSLS to Change System Options

To display the current value of an option, use these commands:

dv_print

displays values of dynamic options.

dv_config -s

displays values of static options.

dv_config -d

displays values of dynamic and static options.

Planning ACSLS Configuration Options

Table 11. ACSLS Configuration Options

Configuration Choice Group	Option Prompt	Option Description	Type	Valid Selections	Your Site's Selection
1. Set CSI tuning variables	Maximum age in seconds of pending requests in CSI request queue [172800]	Maximum timeout interval for pending requests in CSI request queue	Dynamic	172800 seconds 600 to 315360000 seconds
1. Set CSI tuning variables	Number of seconds between successive retries [4]	Minimum timeout interval between CSI attempts to establish a network connection	Dynamic	4
1. Set CSI tuning variables	Number of retries for the CSI before a timeout condition occurs [5]	Maximum times the CSI will retransmit a message	Dynamic	5
1. Set CSI tuning variables	Changes to alter the use of the TCP protocol will not take effect until the product is restarted. CSI support for RPC using the TCP protocol is enabled [TRUE]:	CSI acts as a TCP RPC server (TRUE) or not (FALSE)	Static	TRUE FALSE
1. Set CSI tuning variables	Changes to alter the use of the UDP protocol will not take effect until the product is restarted. CSI support for RPC using the UDP protocol is enabled [TRUE]:	CSI acts as a UDP RPC server (TRUE) or not (FALSE)	Static	TRUE FALSE
2. Set event logging variables	Number of event log files to retain [9]:	Number of rollover event log files; see "Specifying Options for Event and Statistic Logs"	Dynamic	9 0-9
2. Set event logging variables	Changes to the logging directory will not take effect until the product is restarted. What directory should logging information be in [$ACS_HOME/ log]:	Pathname for directory containing the event log	Static	$ACS_HOME/ log
2. Set event logging variables	Maximum library server event log size in Kbytes (=1000 bytes) [500]:	Maximum event log size (Kb); see "Specifying Options for Event and Statistic Logs"	Dynamic	500 32 or more
2. Set event logging variables	Date/time format for all logs [%Y-%m-%d %H:%M:%S]:	Date and time format for all ACSLS logs and command and utility output	Dynamic	The %Y variable can specify 4-digit year for mats, which is the default
3. Set general product behavior variables	Enable Library Volume Statistics Gathering (ON/ OFF) [OFF]:	Specifies if volume statistics are logged. Logging these statistics can take considerable disk space; see "Specifying Options for Event and Statistic Logs"	Dynamic	OFF ON
3. Set general product behavior variables	Number of acsss_stats log files to retain [9]:	Number of rollover statistics log files; see "Specifying Options for Event and Statistic Logs"	Dynamic	9 0-9
3. Set general product behavior variables	Maximum library server acsss_stats log size in Kbytes (=1000 bytes) [500]:	Maximum statistics log size (Kb); see "Specifying Options for Event and Statistic Logs"	Dynamic	500 32K or more
3. Set general product behavior variables	Select cleaning cartridge ordering method [VOLID_SORT]	Cleaning cartridge ordering for selection and query clean display: VOLID_SORT order by vol_id LEAST_USED order from least to most used MOST_ CAPACITY order from most to least available cleaning cycles	Dynamic	VOLID_SORT LEAST_USED MOST_ CAPACITY
3. Set general product behavior variables	Enable Transport Auto Clean Option (TRUE/FALSE) [TRUE]:	When option is TRUE and transport indicates cleaning is required, ACSLS will automatically clean the transport before next mount (TRUE) or not (FALSE) Note: You cannot use the acsss_config configuration program to enable auto-cleaning for drives attached to 97xx LSMs. Using ACSLS, you can only clean these drives by manually mounting a cleaning cartridge. The LSM hardware, however, lets you enable auto-cleaning via the LSM control panel. For more information, see your 97xx documen- tation.	Dynamic	TRUE FALSE
3. Set general product behavior variables	Library Server startup state (RUN/IDLE) [RUN]:	Initialize ACSLS in RUN or IDLE state	Static	RUN IDLE
3. Set general product behavior variables	Changes to the number of mount processes ACSLS supports will not take effect until the product is restarted. Number of mount processes [2]:	Number of ACSLS persistent mount processes; see "Specifying Options for ACSLS Processes"	Static	2 1-10
3. Set general product behavior variables	Enable QUERY persistent processes (TRUE/FALSE) [TRUE]:	TRUE specifies that ACSLS executes queries as one or more persistent processes. Use the following option to specify the number of query persistent processes; see "Specifying Options for ACSLS Processes"	Static	TRUE FALSE
3. Set general product behavior variables	Changes to the number of query processes that ACSLS supports will not take effect until the product is restarted. Number of query persistent processes [2]:	Number of ACSLS query persistent processes; see "Specifying Options for ACSLS Processes"	Static	2 1-10
3. Set general product behavior variables	Changes to the maximum number of ACSLS processes will not take effect until the product is restarted. Maximum number of ACSLS processes [40]:	Maximum ACSLS transient processes; see "Specifying Options for ACSLS Processes"	Static	40 32 and above
3. Set general product behavior variables	Enable automatic enter tracing facility (TRUE/FALSE ) [FALSE]:	Log automatic mode enters in the event log (TRUE) or not (FALSE)	Dynamic	FALSE TRUE
3. Set general product behavior variables	Enable volume tracing facility (TRUE/FALSE ) [FALSE]:	Log database volume additions and deletions in the event log (TRUE) or not (FALSE)	Dynamic	FALSE TRUE
4. Set access control variables	Changes to command access control will not take effect until the product is restarted. Access control is active for commands (TRUE/FALSE) [FALSE]:	Enable command access control (TRUE) or not (FALSE)	Static	FALSE TRUE
4. Set access control variables	Default access for commands (ACCESS/ NOACCESS) [ACCESS]:	If no access control files, enable default command access (ACCESS) or not (NOACCESS)	Dynamic	ACCESS NOACCESS
4. Set access control variables	Changes to volume access control will not take effect until the product is restarted. Access control is active for volumes (TRUE/FALSE) [FALSE]:	Enable volume access control (TRUE) or (FALSE)	Static	FALSE TRUE
4. Set access control variables	Default access for volumes (ACCESS/ NOACCESS) [NOACCESS]:	If no access control files, enable default volume access (ACCESS) or (NOACCESS)	Dynamic	NOACCESS ACCESS
4. Set access control variables	Messages will be logged when access to commands or volumes is denied (TRUE/FALSE) [FALSE]:	Log command and volume Access Denied messages in event log (TRUE) or (FALSE)	Dynamic	FALSE TRUE

Specifying Options for Event and Statistics Logs

• You can specify the number of rollover log files to "journal" entries when the base log file reaches maximum size. If you specify 0, ACSLS creates only one base log file with no rollover files. You must manually manage this base log file, which has no maximum size. If you specify 0 rollover log files and also specify a maximum size for the volume statistics log, ACSLS logs warning messages in the event log if the log file exceeds the specified maximum size.

Alternatively, you can specify 1 to 9 rollover log files. Rollover log files provide a history to ensure that you capture all log entries and can more easily locate specific log entries. For example, if you specify 2 rollover files for volume statistics logging, when the acsss_stats.log (base) file reaches maximum size, ACSLS renames it to the first rollover file (volstats0.log), then starts a new acsss_stats.log file. When the acsss_stats.log file again reaches maximum size, ACSLS renames the volstats0.log file to volstats1.log, renames acsss_stats.log to volstats0.log, and starts a new acsss_stats.log file. When all rollover files contain data and another rollover occurs, the highest numbered rollover file will be discarded.

• You can specify the maximum log file size; this maximum applies to both the base log and rollover log files. If you specify rollover log files, you can typically specify a smaller maximum file size (that applies to both base log and rollover files) than the maximum file size you would specify for a base log only, which must be large enough to contain enough meaningful entries.

Specifying Options for ACSLS Processes

• ACSLS system persistent

• CSI (1)

• ACSLS transient (specified via acsss_config)

• ACSLS query persistent (specified via acsss_config)

• ACSLS mount persistent (specified via acsss_config)

Warning: With a minimum configuration system, higher than 10 query persistent processes could use up system resources and not allow ACSLS to start up.

If the total number of all the processes listed above exceeds the Solaris system limit on processes per user, ACSLS may fail to start. If this happens, either increase the system limit on processes per user or lower one or more of the values for the ACSLS process options that you can specify via acsss_config.

Planning Library Configuration Options

Table 12. Library Configuration Options(Solaris)
Option Prompt	Option Description	Valid Selections	Your Site's Selection
Number of ACSs to be supported:	Specifies the number of ACSs in the library configuration.	A number between 1 and 127
Number of connections to ACS #nnn:	Number of connections to each ACS. This prompt appears for each configured ACS. You must specify at least one connection per ACS.	A number between 1 and 16, typically 1 or 2 (1 for SCSI devices)
Device name - ACS #nnn device #dd:	Full path name of the device attached to a port. This option appears for each port in the library.	Recommended path names: Solaris platform: /dev/ttya /dev/ttyb /dev/mchanger2

Table 13. Library Configurations Options (AIX)
Option Prompt	Option Description	Valid Selections	Your Site's Selection
Number of ACSs to be supported:	Specifies the number of ACSs in the library configuration.	A number between 1 and 127
Number of connections to ACS #nnn:	Number of connections to each ACS. This prompt appears for each configured ACS. You must specify at least one connection per ACS.	A number between 1 and 16. Non dual LMU configurations: typically 1 or 2 (1 for SCSI devices) Dual LMU configurations: typically 2 or 4
Device name - ACS #nnn device #dd:	Full path name of the device attached to a port. This option appears for each port in the library.	Recommended path names: AIX platform: /dev/tty0 /dev/tty1 /dev/mchanger0

How To Do a Reconfiguration

Use the Build/Verify Library Configuration routine to update the database with all configuration changes except adding or removing port connections. Use the Configure Library Communications routine to reconfigure ports. Use both routines if you have added or removed an ACS. Both of these routines warn you that existing configuration data will be overwritten.

In most cases, you should perform an audit after using the Build/Verify Library Configuration routine to reconfigure the library. See "Auditing the Library" for details on the specific types of configuration changes that require an audit.

If you are changing only one variable within a group, press <ENTER> to accept the new value, then press <CTRL> + D. To accept the defaults for the remaining items, complete the group, and return to the main menu.

See Also

• Auditing the Library.

• Displaying Dynamic and Static Variables.

Reconfiguring ACSLS on Solaris

To reconfigure ACSLS on Solaris:

1. Exit out of the CDE until you reach the CDE login.

2. Login as acsss.

3. At the password prompt, press <ENTER>.

4. Shutdown ACSLS.

   kill.acsss
   

   Note: If subsequent system messages indicate that the PID file does not exist, this means that ACSLS was not running.

5. To run the configuration script, enter

   acsss_config
   

   The ACSLS feature configuration screen appears.

   Note: The configuration script, acsss_config, will fail unless all LMUs, LSMs, and transports are fully configured, powered on, and ready.

6. Do you want to custom configure ACSLS?

1. Select 6 to exit the menu and continue the configuration process.

   The script displays progress messages during database creation. This takes about five minutes.

2. Enter y at the following prompt:

   Configure library communications? (y/n):
   

3. Have you previously configured the system?

Steps 10 and 12 refer to Table 12. "Library Configuration Options" (Solaris).

1. Enter the number of ACSs that will be supported at your site.

   Number of ACSs to be supported:
   

   You must answer at least 1 to this prompt. Hardware must be installed to support one or more ACSs.

2. Enter the number of connections to your ACS.

   Number of connections to ACS #n:
   

3. Enter the device name for each connection.

   Device name - ACS#n, device #n:
   

   Example device names for 4400 or 9300 libraries

   Device Name - ACS #0, device #0: /dev/ttya
   Device Name - ACS #0, device #1: /dev/ttyb
   
   

   
   

   Example device name for 97xx library

   Device Name - ACS #1, device #0: /dev/mchanger2
   
   

   
   

   Note: The device name is assigned during ACSLS installation when the SCSI device number is entered.

4. Enter y at the following prompt to build/verify the library configuration.

   This step builds a database image of your 
   complete library hardware configuration.  
   Before proceeding, make sure that your 
   library is completely configured, that all 
   subsystems are functional and powered on. 
   Build/Verify library configuration?
   
   (y or n):
   

5. Have you previously configured the system?

1. Respond (y or n) when the system asks whether to configure client system interfaces.

   Configure client system interfaces? 
   
   (y or n):
   

   YES	The following message displays: CSI SELECTION TABLE 1) OSLAN CSI Not Selected 2) ONC/RPC CSI Always Selected Do you want to change the CSI selection table (n): If y, the following message appears:Select OSLAN CSI (n): ONC/RPC is always selected.
   NO	Continue with Step 16.

2. Are you backing up the database to tape?

   Hint: At this point in the reconfiguration, StorageTek recommends that you back up the database to a tape that can be stored offsite and used, if needed, for disaster recovery of the database.

   YES

   Insert a blank tape when the following message displays: Prepare for database backup... Insert database backup tape Press RETURN to continue.The database backup procedure bdb.acsss automatically executes and captures the configuration data to enable database journaling. When the database backup is completed, the following message displays:Database backup successfully completed. Continue with Step 17.

   NO

   Press <.CTRL>. + C and see "Backing Up to a UNIX File" to back up the database to disk file. After making the backup, go to Step 18.

   Caution: The tape drive may appear idle during the backup. It may not make any sounds or flash any lights during this time. DO NOT remove the tape from the drive until you see the following success message indicating the backup is complete:

   Database backup successfully completed.
   

   Warning: Interrupting the backup process before completion will result in corruption of the database.

3. Remove the tape and store it in a safe place.

4. Run rc.acsss to start the server.

   If the automatic startup on reboot option was enabled during ACSLS installation, ACSLS is initiated automatically when the server system is rebooted.

Reconfiguring ACSLS on Solaris (Dynamic Variables Only)

To reconfigure ACSLS on Solaris to change dynamic variables only:

1. Exit out of the CDE until you reach the CDE login.

2. Login as acsss.

3. At the password prompt, press <ENTER>.

4. To run the configuration script, enter

   acsss_config
   

   The ACSLS feature configuration screen appears.

   Note: The configuration script, acsss_config, will fail unless all LMUs, LSMs, and transports are fully configured, powered on, and ready.

5. Do you want to custom configure ACSLS?

1. Select 6 to exit the menu and complete the configuration process.

   The configuration program updated the options you specified in Step 5. If you changed any options that affect dynamic variables, the new values are now in effect.

Reconfiguring ACSLS on AIX

To reconfigure ACSLS on AIX:

1. Login as acsss.

2. At the password prompt, press <ENTER>.

3. Shutdown ACSLS

   kill.acsss
   

   Note: If a subsequent system message indicates that the library server is not terminated, this means that ACSLS was not running.

4. To run the configuration script, enter

   acsss_config
   

   The ACSLS feature configuration screen appears.

   Hint: Make sure that all LMUs, LSMs, and transports are configured, powered on, and ready. The configuration script, acsss_config, will fail unless all LMUs, LSMs, and transports are configured, powered on, and ready.

5. Do you want to custom configure ACSLS?

1. Select 6 to exit the menu and continue the configuration process.

   The script displays progress messages during database creation. This takes about five minutes.

2. Enter y at the following prompt:

   Configure library communications? (y/n):
   

3. Have you previously configured the system?

   YES	Enter y at the following prompt:Library server database exists and will be overwritten, continue? (y or n):
   NO	Continue with Step 10.

   Steps 10 and 12 refer to Table 13. "Library Configuration Options (AIX)."

   1. Enter the number of ACSs that will be supported at your site.

      Number of ACSs to be supported:
      

      You must answer at least 1 to this prompt. Hardware must be installed to support one or more ACSs.

   2. Enter the number of connections to your ACS.

      Number of connections to ACS #n:
      

   3. Enter the device name for each connection.

      Device name - ACS#n, device #n:
      

      Example device names for 4400 or 9300 libraries

      Device Name - ACS #0, device #0: /dev/tty0
      Device Name - ACS #0, device #1: /dev/tty1
      
      

      Example device name for 97xx library

      Device Name - ACS #1, device #0: /dev/mchanger2
      
      

      Note: The device name is assigned during ACSLS installation when the SCSI device number is entered.

      In the following steps, refer to Table 13. for library configuration options.

   4. Enter y at the following prompt to build/verify the library configuration.

      This step builds a database image of your 
      complete library hardware configuration.  
      Before proceeding, make sure that your 
      library is completely configured, that all 
      subsystems are functional and powered on.  
      Build/Verify library configuration?
      
      (y or n):
      

   5. Have you previously configured the system?

      YES	Enter y at the following prompt:Library server database exists and will be overwritten, continue? (y or n): As the script builds the library configuration, it displays the following message for each panel in each LSM.ACS # n, LSM # nn, PANEL # nn, createdThe script also generates a library configuration report and appends it to the following file:/export/home/ACSSS/log/acsss_config.log
      NO	Continue with Step 15.

   6. Respond (y or n) when the system asks whether to configure client system interfaces.

      Configure client system interfaces? 
      
      (y or n):
      

      YES	The following message displays: CSI SELECTION TABLE 1) OSLAN CSI Not Selected 2) ONC/RPC CSI Always Selected Do you want to change the CSI selection table (n): If y, the following message appears:Select OSLAN CSI (n): ONC/RPC is always selected.
      NO	Go to Step 15.

   7. Are you backing up the database to tape?

      Hint: At this point in the reconfiguration, StorageTek recommends that you back up the database to a tape that can be stored offsite and used, if needed, for disaster recovery of the database.

      YES

      Insert a blank tape when the following message displays:Prepare for database backup... Insert database backup tape Press RETURN to continue. The database backup procedure bdb.acsss automatically executes and captures the configuration data to enable database journaling. When the database backup is completed, the following message displays:Database backup successfully completed. Continue with Step 16.

      NO

      Press <.CTRL>.+ C and see "Backing Up to a UNIX File" to back up the database to disk file. After making the backup, go to Step 17.

      Caution: The tape drive may appear idle during the backup. It may not make any sounds or flash any lights during this time. DO NOT remove the tape from the drive until you see the following success message indicating the backup is complete:

      Database backup successfully completed.
      

      Warning: Interrupting the backup process before completion will cause a corrupted backup file or tape.

   8. Remove the tape and store it in a safe place.

   9. Run rc.acsss to start the server.

      If the automatic startup on reboot option was enabled during ACSLS installation, ACSLS is initiated automatically when the server system is rebooted.

   ACSLS is now ready for library operations. If you want to enter ACSLS commands, log in as acssa.

   
   
   

   Reconfiguring ACSLS on AIX (Dynamic Variables Only)

   
   
   

   To reconfigure ACSLS on AIX to change dynamic variables only:

   1. Login as acsss.

   2. At the password prompt, press <ENTER>.

   3. To run the configuration script, enter

      acsss_config
      

      The ACSLS feature configuration screen appears.

      Note: The configuration script, acsss_config, will fail unless all LMU's and LSM's are fully configured, powered on, and ready.

   4. Do you want to custom configure ACSLS?

   YES	Go through each item of the menu, selecting op tions 1 through 5, and enter the variable informa tion referring to Table 11.
   NO	Press <ENTER> to accept the default settings.

   1. Select 6 to exit the menu and complete the configuration process.

      The configuration program updated the options you specified in Step 5. If you changed any options that affect dynamic variables, the new values are now in effect.