![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 1004384.1 : SL8500 - Code Activation Time Out
PreviouslyPublishedAs 206060 Oracle Confidential (PARTNER). Do not distribute to customers Reason: Confidential information provided to Oracle and Partner Service Personnel
Applies to:Sun StorageTek SL8500 Modular Library SystemAll Platforms SymptomsCode Activation Time Out.Several sites have reported issues down leveling code during HandBot replacements. Code Mismatch. ChangesTypically seen while replacing a failed HandBot, example; the new HandBot from stock is at 3.08 and the LC code is at 3.02b or below.CauseAfter the new HandBot is initialized the device status indicates "Code Mismatch" and the SLC icon is Yellow.SolutionAs previously recommended, re-activation of the current level of LC is executed from SLC.Steps to Follow SL8500 Code Activation Time Out: Several sites have reported issues down leveling code during HandBot replacements. Typically seen while replacing a failed HandBot, example; the new HandBot from stock is at 3.08 and the LC code is at 3.02b or below. After the new HandBot is initialized the device status indicates "Code Mismatch" and the SLC icon is Yellow. As previously recommended, re-activation of the current level of LC is executed from SLC. During the activation process a message is posted on the console: "FAILED TO GET AN INTERMEDIATE RESPONSE FOR THE USER TASK. IT MIGHT STILL BE RUNNING ON THE LIBRARY." During the activation process SLC is running a response handler in the background which can time out after 12 minutes if a completion status is not received for the associated code module. Up to 5 code modules can be downloaded and transferred to flash memory on the HandBot's HBB card. The number of modules transferred is dependent on the difference in the code levels between the new HandBot and the active code on the LC. The libs.cramfs file is the largest module and the one most likely to timeout. Even though the SLC response handler times out the current file transfer will continue and probably succeed. It should be obvious when the transfer is complete via the wait LED?s on the front key panel. When the wait LED?s stop flashing; the file download and HBB flash update is complete for the associated file. If the difference in the LC and HandBot is great enough there may be other modules that also require updates such as the robot.cramfs file. Example would be the LC at 2.52 and the new HandBot is at 3.08.
Note: Due to these issues, it is recommended to attempt to perform code changes remotely. If one does attempt a code change remotely, wait 10 minutes after receiving the console error message before rebooting the Handbot. @ SL8500 Modular Library System, SL8500 Code Activation Time Out, Modular Library System, Code Activation, Time Out, CRCM Previously Published As 90895 Attachments This solution has no attachment |
||||||||||||
|