StorageTek SL150 Modular Tape Library
 

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

In this Document

Goal

Solution

References

Applies to:

Goal

 SL150 - How To Avoid Library Serial Number Corruption?

Solution

How is the SL150 configuration stored and maintained?

1. There are 3 USB sticks containing serial numbers and configuration information inside the library, located at the following cards: KLM, KLC and KLO.

   
   The card descriptions are:
   KLM = The Mother board located in the base Chassis CRU.
   KLC = The Library Controller card located in the robotics CRU.
   KLO = Card located at the Op Panel CRU.
   
   This is a list of latest CRU part number at the moment, to hold the USB sticks:
   7093070 [C] Robot Module with Switch Lock

   7069157 [C] Base Chassis

   7309393 [C] Operator Panel
   

   Note: If you order purely the KLM card, which is a FRU, it will not come with a USB stick. The idea there is that you take it from the existing KLM, and this way there is no issue with serial number corruption when replacing the KLM card itself.
   

2. Each of these 3 USB sticks holds a copy of the library configuration and serial number. Two of them need to match each other, this information being copied over to the third USB stick which may be blank or hold mixed information compared to the other two. As long as at least two copies are in sync, there is no problem. When you replace just one of these 3 components listed above, you see the following message in the library logs. This sample is after replacing the chassis:
   
   "getCheckProductIDSN: KLM updated, didn't match KLO and KLC."
   

3. You will get an issue, if for some reason all of these 3 USB sticks hold different information. This is typically caused by replacing more than one of the above listed components without a successful reboot between times. A typical scenario is that you first replace the robot, and the library still fails to initialize, and then you replace the chassis, which then leads to the corruption scenario. This is because the library will not write to the new USB stick on the new robot KLC until it’s fully initialized, so just having the new robot in and a partial initialization will not be enough for the new robot's USB stick to get written with the new library serial number.
   
   

4. The only way to get past this corrupted situation is to engage L2 to arrange a Webex session with the customer, and re-program the serial number on the live system. Also depending on the library code level, you need to take a different approach on how to identify and handle the corrupted serial number.
   
   A) Library code 2.01 and below will fail the initialization with this misleading error, also described in this KB:
   
   SL150 - Error : "Magazines Not Latched" 9081, Library Will Not Initialize (Doc ID 1539657.1)
   
   You will have the ability to log in via BUI and collect the service bundle in this state. You can also fix the library serial number via Webex session in this state as it allows us to login.
   
   B) Library code 2.25 will fail the library with error code 9999, which you can only see from the library operator panel as the library will not let you in via BUI at this point. The library is basically not powering up at all in this scenario. In this situation we have to first get past the 9999 error so we can get the library to boot up enough for us to do the serial number correction via Webex.
   
   Refer to attachment on how it looks like from the Op panel:
   
   How to get past the 9999 error?
   
   The foolproof approach is to replace all 3 components listed in step 1. However, we have realized that just by replacing the Op panel, we can get past the 9999 situation, as it will have a blank USB stick when coming from the factory, and thus it handles the situation differently, allowing us to login and fix the serial number remotely. This is not always 100% certain so, in the worst case scenario order 3 new fresh parts, and replace them all at the same time without powering on the subsystem in the meantime.
   
   
   C) Library code 2.50 will fail the library with the new error code 9093, to notify the user about the SN mismatch. The new 2.50 code will allow you get a Service Bundle in this situation. It will allow access to the BUI and you should be able to collect a service bundle as well as resolving the serial number problem via Webex.
   
   

5. There might also be a situation where you already replaced and returned the robot CRU and you cannot still get the library up. Like with fault code: 9135. Then you realize you need to have the base chassis replaced to solve the original problem. Then your challenge is that, by replacing the base chassis in this condition, you will corrupt the library serial number. Here’s a document to tell you how to get the library base chassis replaced, so that you will take the original USB stick from the old chassis, and in this way prevent the serial number for corrupting. Keep in mind, that you need to ship an FE for this task as it should be treated as KLM replacement, and the KLM is a FRU not a CRU.
   
   SL150 - Steps to replace the base chassis CRU and use the existing USB stick from the original base chassis KLM card (Doc ID 2020327.1)

Note: Experienced an issue where library consistently failed to initialize and had to swap KLM from old chassis to new chassis. Please refer to SR 3-12140414995. (Updated 10-Feb-2016)

References

This solution has no attachment