![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1384090.1 : SL3000 - ACSLS Not Able to Detect New Slot Count
In this Document
Applies to:Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version: 8.0Sun StorageTek SL3000 Modular Library System - Version: Not Applicable and later [Release: N/A and later] Information in this document applies to any platform. SymptomsACSLS not able to detect new slot countACSLS is not able to detect the new slot count after adding a third drive bay with 8 drives to the BDM. Deleted and reassigned the partition on SL3000 (1 partition) and followed by config acs acs_id. All the new drives are discovered but the slot count remain the same as before. ChangesAdded an expansion module to the SL3000Added or modified drive bays, frames, CAPs or anything that affects slot capacity. CauseThe new slots are not know to ACSLS unless ACSLS is re-configured.The library reports the potential cell locations that are not accessible to ACSLS when ACSLS audits it. Inaccessible cell locations include: ■locations where CAPs, drives, and operator panels are installed. ■cell locations that the robots cannot access. ■cell locations that are not activated . ■cell locations that are not in this partition You must audit an SL3000 after it is configured or re-configured to ACSLS SolutionYou must audit an SL3000 after it is configured or re-configured to ACSLS. The library reports the potential cell locations that are not accessible to ACSLS when ACSLS audits it.Inaccessible cell locations include: - Locations where CAPs, drives, and operator panels are installed. - Cell locations that the robots cannot access. - Cell locations that are not activated . - Cell locations that are not in this partition. Note: Refer to the ACSLS Administrator Guide for additional information. Run the get_diags utility and keep it for later use. Run the following command: free_cells.sh -a and keep the result for later use. Start an HLI trace on the ACSLS box, by executing the following command: start_logging.sh acslh then start an AUDIT of the full ACS from a "cmd_proc -l" (not a cmd_proc, but a "cmd_proc -l" !) ... and keep a copy of the output. See if AUDIT works. Perform the following command to check if number of slots known by ACSLS is correct: free_cells.sh -a If number of slots still incorrect, check in the $ACS_HOME/log/acsss_config.log file for the last config and note all available panels (the ones which are not marked "SL3000 Panel Not Installed"), those will include "SL3000 Drive Panel" and "SL3000 Cell Panel". Now that you have the list of all effective panel, try to perform an AUDIT of PANEL, in the form: AUDIT acs,lsm,6 PANEL acs,lsm,1stpanel acs,lsm,2ndpanel acs,lsm,3rd panel ... acs,lsm,Nthpanel (all the panels in a same AUDIT command) Check again with a: free_cells.sh -a This normally is the trick ! Stop the HLI trace by running the following command: stop_logging.sh acslh Run a new get_diag utility (do not delete the previous one !) Should this process not resolve the issue, open a Collaboration SR to Library Software Support and attach all get_diags output, cmd_proc output from AUDIT and the acslh.log. Provided by Rich Kent and Boon Pink Chew Attachments This solution has no attachment |
||||||||||||
|