Sun StorageTek SL3000 Modular Library System
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
 

In this Document

Symptoms

Changes

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for Oracle Support personnel
Created from <SR 3-4877399572>

Applies to:

Symptoms

During initialization, get following messages in SL3000 logs:

Time : 2011-11-21T07:47:41.235
Device Address : 1.0.0.0.0
User : root
Requester : default
Activity : internal
Request Id : 0
Level : error
Result Code : 3215
Text : "Robot initialization error - Data: 2011-11-21T07:47:41.232
Parameters : 1.0.0.0.0, root, default, internal, 0, error, 3104, "subId=1 The frame labels do not support dual robots. Fix and reboot.", left=BDM01/ right=BDM01/"


Time : 2011-11-21T07:47:41.232
Device Address : 1.0.0.0.0
User : root
Requester : default
Activity : internal
Request Id : 0
Level : error
Result Code : 3104
Text : "subId=1 The frame labels do not support dual robots. Fix and reboot."
Parameters : left=BDM01/ right=BDM01/

Changes

Installing 1 x SL3000 base module,1 x CEM, 2 x AEM.
Library firmware is 3.0.

Cause

Need correct labels in library to configure properly.

Solution

Need to convert two CEM labels to AEM labels (Access expansion modules, one for each bot).

Frame Label Scan Tip -
You can watch the way the frame labels are scanned by the Tall-Bots to verify that a subsystem configuration check is occurring. If only the top label is scanned, the configuration will not be updated. If all 4 labels are scanned, a new configuration will be built from that boot. Remember the following tip that relates to the re-configuration process.

Must Use "config check" not Power Cycling -
When adding features or during initial installation of the SL3000 it may be necessary to force the machine to reconfigure all the walls. In the past with older code you needed to use the "power off, open door, close door, power on" sequence to force a reconfiguration. In FRS-2.35 code the CLI "config check" command with a reboot could be used to force the reconfiguration. In FRS-3.0 code the power cycle option no longer works and you must use the CLI "config check" command to cause a reconfiguration.

NOTE: Due to the way some data is kept in cache before it is written to non-volatile memory, do not power cycle the SL3000 after entering the "config check" command. Instead, use the CLI or the SLConsole to reboot the subsystem. If you try a reset with a power cycle, the reconfiguration may not occur as the config check that was entered may not have time to be written to the database.

This solution has no attachment