ACSLS - Configuration Utility Fails When the SL500 Base Module CAP is Configured for Storage

Asset ID:	1-71-1020177.1
Update Date:	2011-11-29
Keywords:

Solution Type Technical Instruction Sure

Solution 1020177.1 : ACSLS - Configuration Utility Fails When the SL500 Base Module CAP is Configured for Storage

Applies to:

Sun StorageTek SL500 Modular Library System
Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version: 7.3 and later [Release: 7.0 and later]
All Platforms
Checked for relevance on 29- Nov-2011.

Goal

Description
The ACSLS configuration utility will fail with a timeout error if the SL500 base module CAP is configured for use as storage cells.

The SL500 base module CAP should always be configured for use as I/O cells to enable Enter and Eject operations. SL500 expansion modules may be configured for use as storage or I/O cells.

There may also be errors in the postgres logs relating to the size of the cap, for example:

LOG: statement: insert into captable (acs, lsm, cap, cap_status, cap_state, cap_mode, cap_priority, cap_size, cap_condition, cap_availability, cap_desired_state) values (4, 0, 0, 10, 7, 1, 0, 0, 3, 2, 7)

ERROR: new row for relation "captable" violates check constraint "captable_cap_size_check"

To confirm cap size values the following command can be issued:

$ psql -d acsdb
Welcome to psql 8.1.11, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

acsdb=> \d captable
Table "acsss.captable"
Column | Type | Modifiers
-------------------+---------+--------------------
acs | integer | not null default 0
lsm | integer | not null default 0
cap | integer | not null default 0
cap_status | integer | not null default 0
cap_priority | integer | not null default 0
cap_state | integer | not null default 0
cap_mode | integer | not null default 0
cap_size | integer | not null default 0
cap_condition | integer | not null default 0
cap_availability | integer | not null default 0
cap_desired_state | integer | not null default 7
Indexes:
"captable_pkey" PRIMARY KEY, btree (acs, lsm, cap)
Check constraints:
"captable_acs_check" CHECK (acs >= 0 AND acs <= 31)
"captable_cap_availability_check" CHECK (cap_availability > -1 AND cap_availability < 5)
"captable_cap_check" CHECK (cap >= 0 AND cap <= 11)
"captable_cap_condition_check" CHECK (cap_condition > 0 AND cap_condition < 4)
"captable_cap_desired_state_check" CHECK (cap_desired_state = 7 OR cap_desired_state = 5 OR cap_desired_state = 2)
"captable_cap_mode_check" CHECK (cap_mode = 1 OR cap_mode = 2)
"captable_cap_priority_check" CHECK (cap_priority >= 0 AND cap_priority <= 16)
"captable_cap_size_check" CHECK (cap_size > 0)
"captable_cap_state_check" CHECK (cap_state = 7 OR cap_state = 5 OR cap_state = 6 OR cap_state = 8 OR cap_state = 2)
"captable_cap_status_check" CHECK (cap_status = 7 OR cap_status = 10 OR cap_status = 34 OR cap_status = 35 OR cap_status = 151)
"captable_lsm_check" CHECK (lsm >= 0 AND lsm <= 126)

Solution

Steps to Follow
This problem only affects the SL500 base module.

1. Verify that the acsss_config utility fails with these error messages:

     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): y

     /export/home/ACSSS/config/in_lib_conf: Time-out awaiting library handler response
     /export/home/ACSSS/config/in_lib_conf: Cannot get LH data
   /export/home/ACSSS/config/in_lib_conf: Failed to configure LSMs

     2008-11-07 12:36:50
     791 N in_tbl_dest.c 1 120
     The following tables have been removed:
     acstable,audittable, captable,celltable,csitable,drivetable,lockidtable,
     lsmtable,paneltable,pooltable,portable,vactable,scr_distr_table,volumetable,
     clienttable,ptptable,handtable,lmutable,displaycommand,displayoptions,
     displayfields,displayoptval,displaysubfields
     lib_config.sh 1612: Error: Configuration command in_lib_conf failed.
     Exiting.

2. Verify from the Sun Field Engineer how the CAP of the SL500 base module is configured

     If the CAP is configured for use as I/O, there could be other problems causing the acsss_config to fail.
     Refer to Document: 1020074.1 ACSLS - Troubleshooting 'acsss_config' Problems During Library
          Communications Configuration

    If the CAP is configured for use as storage, ask the Sun Field Engineer to change the CAP to be used for I/O. This is usually done using the SL500 CLI utility and not through ACSLS. Run the acsss_config utility again after making the CAP attribute change.

Attachments

This solution has no attachment