IBM System Storage TS3310, Maintenance Information

Page: 143 / 531

T087: Invalid Library SN Label Warning
Description GUI Description: The library's serial number barcode label cannot be read by
the robot but the library is able to initialize and continue operation.
Explanation: The library logic learns the serial number of the system by
reading an internal serial number label. The service tag is located on the
same label as the serial number. This is done at first bootup from a "clear to
ship" condition in order to establish the serial number. It is also done on
subsequent bootups to confirm that the compact flash memory card is in the
proper library. The library will report this operator intervention message
when it cannot read the library serial number but it has confirmed
functionality of the barcode reading system by successfully reading some
other barcode label in the library and it has the library serial number stored
in memory from a previous successful read. When this operator intervention
message is posted, the user can be confident that at least one other barcode
label has been read.
For example, barcodes that can be used the check functionality are:
v
WWN or SN (in control modules)
v
OID (in expansion modules)
Different tickets will be posted if there are motion-related problems, scanner
communication problems, and so on.
Detection Scenario Any power-up. System memory already has a valid SN established for the
LCB.
Root Causes
v Label is damaged.
v Label is missing.
v
Label is physically obstructed.
v
Label is readable but does not meet minimum criteria to be considered a
library SN label.
v Scanner cannot read the serial number label.
Possible CRU Replacements
v
LCB Flash Memory
v
LCB
Possible FRU Replacement
v Module (EM or CM) - only dispatch this FRU if the label is missing or
damaged.
v
Picker Assembly
v
Y- carriage Assembly
Resolution
1.
Perform “DR051: Resolve Library SN Label Detection” on page 6-79.
2.
Inspect the label inside the unit for damage.
3.
Clear the RAS ticket.
4.
Upgrade the library firmware to 400G or later and run the IVT - Picker
test using the Library Tests option accessed through the Operator Panel.
If the test passes, the issue is most likely not the picker.
Note: IVT is optimized for firmware to firmware versions 520G and
above and libraries built after July 1, 2008 (serial numbers with last four
digits 8609 and above).
v If your library was built on or before July 1, 2008, and you are
running firmware version 520G or above, you will not be able to run
IVT test, even though the selection is available.
v If your library was built on or before July 1, 2008, and you are running
firmware version 500G or below, you can run the test, but it is not
recommended because it may produce erroneous results.
Chapter 6. Service Action Tickets (Txxx) and Diagnostic Resolutions (DRxxx)
6-41