SL8500 - Synchronizing Code Between the Library Controller and the Library Sub-systems

Asset ID:	1-71-1014118.1
Update Date:	2011-03-16
Keywords:

Solution Type Technical Instruction Sure

Solution 1014118.1 : SL8500 - Synchronizing Code Between the Library Controller and the Library Sub-systems

Applies to:

Sun StorageTek SL8500 Modular Library System
All Platforms
Checked for relevance on 16-Mar-2011.

Goal

Synchronizing Code Between the Library Controller and the Library Sub-systems.

Solution

Steps to Follow
Use the following instructions for code synchronization:
- Code synchronization occurs on subsystem parts automatically if they are lower versioned than the main controller.
- When replacing FRU's such as robots, HBT, or HBZ, care should be taken to keep the doors closed and power on as an auto update occurs.
- Opening the doors or shutting down power while auto update is occurring can render the part useless. Auto code updates only occur to uplevel code versions different than the controller, NOT higher to lower.
- When installing a FRU, care should be taken to identify the code version on that part and remedy a mismatch if needed. FRU's not matching the controller with a higher code version will be marked yellow from SL Console.
- Those FRU's will need to have code activated to the correct version. FRU's with lower level microcode will fix themselves as the controller will update them automatically.
- Make sure you allow this to occur.

Follow instructions below to synchronize code versions between the library controller and the library sub-systems such as the hand bots (Robotics), CAP, etc...
1. Vary the ACS (all LSMs) offline from the host server.
2. Go into SL Console program. (see example screen below).
3. From the tools pull down tab select `Diagnostics'.
4. If you have already downloaded the code, select `Activate Code' tab from the diagnostics screen and go to step 7.
5. Otherwise, select `Load Code' tab from the diagnostics screen.
6. The library will prompt you for filename and location. Enter filename and hit `load' tab on the top right hand corner. After code download and unpack completes, select `Activate Code' tab.
7. In the `Choose a Target' pull down tab, select `SL8500 Code'.
8. The main window will show two code versions. Select FRS_1.42a ( for example) and hit start.

** This will start the code activate process.
1. The library controller will check each subsystem code module for current version level. If it finds the code module to be at a higher level, it will push the current code module to the subsystem. The main window on the console will show this activity. If the controller finds the code module to be at the correct level, it will skip that module and move on to the next module. This can be observed on the SLConsole main window with "skipping" message displayed next to the module. This process may take up to 70 minutes.
2. Upon successful completion of the code activate process, the controller will prompt the user to reboot the library.
3. At this time, reboot the library and wait for the library to complete its initialization process.
4. The code activate process may be repeated multiple times, till "skipping" messages are displayed for all modules. Reboot should be performed between each activation. 5. The first time activation completes and asks for reboot, go ahead and reboot the library, however, after the library completes initialization, activate code again. If all modules were skipped, activations are complete. No reboot is required.
6. If it finds a module that was not activated during previous activation, allow the module to be pushed to the subsystem and, when the library asks for a reboot, answer 'yes' to reboot the library.
7. The bottom line is, reboot the library if an activation of a module took place. In case of no module activation (skipped everything), skip reboot.

The use of 1.42a code is for example only - explaining how to go from FRS_2.00 to 1.42a for example, the procedure is good for all code activation levels. (note- this example was done with the older 2.16 version of SL Console and a new example is pending).

SL Console, SL8500, Re-synchronize code versions between the library controller and the library sub-systems, Synchronize code versions, How to synchronize code in library, Upgrade code versions, Code, Downgrade versions
Previously Published As STKKB70061

Attachments

This solution has no attachment