Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2157438.1
Update Date:2017-08-16
Keywords:

Solution Type  Problem Resolution Sure

Solution  2157438.1 :   SL8500 - FSC 3215 - 'Robot initialization error' with Download File Write Failed  


Related Items
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-12963596539>

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

FSC 3215:Robot initialization error.

With the following result text:

"Download file write failed : retrying with DCI", Exception=scp command failed 10.0.3.13: SCP command gave bad exit value (): 1"

 

Changes

 A handbot was recently replaced and is undergoing first initialization in the library or the library firmware was upgraded.

Cause

This is a known condition. When a robot is replaced, during the initial handshake, it needs to reconcile its status with the library. One of the requirements is that the robot runs the same firmware as the library, so the library will push the associated robot firmware to the new unit, if it came with a lower or higher revision firmware than the one supported by the library.

Solution

The preferred method to push the firmware uses the SCP protocol. This is a relatively recent addition to the library functionality and if the robot was flashed with older firmware at the factory, it will not support transferring firmware with SCP.
In such a case, the library will post an error with FSC 3215 and may create an ASR.

Library functionality is not affected.  The library controller will fall back to DCI protocol, which works on all versions, but is no longer preferred as it is slower and may require retries.

References

<NOTE:1014752.1> - SL8500 - What Causes a Call Home Event on the SL8500?

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback