IBM System Storage TS3310, Информация по обслуживанию

Страница: 138 / 531

T080: Module SN Change
Description GUI Description: The library detected the removal of an expansion module
or a replacement of the control module.
Explanation: When the library powers ON and the robot initializes, the bar
code serial number (SN) labels in each module are scanned by the robot
beginning at the bottom of the library (closest to the y-axis home) and then
working up. The library uses the control module (CM) SN and any
expansion module SN to establish key operational properties and
characteristics of library storage slots and partitions. A change in the CM SN
or the removal of an EM (even if it is replaced with another EM) will
“break” any already established partition in such a way that it must be
deleted. This ticket was designed to notify the user that a condition exists
that requires the deletion of a partition(s) and allow the user to assess
whether perhaps human error is involved such as mixing the Library Control
Blade's compact flash memory between libraries.
Detection Scenario
At library boot up time, the robot attempts to scan all module SN's. When
SN's are discovered, they are compared to persisted data on the system
compact flash.
Root Causes
1. An LCB is improperly swapped into a different physical module and the
system reads the physical module label.
2. A CM chassis FRU is replaced in an already configured system
3. A previously detected and configured EM is removed completely from a
vertical stack of modules.
4. A previously detected and configured EM is removed completely from a
vertical stack of modules and replaced with another EM of similar OR
different size and location.
5.
Bar code reader is not scanning the labels correctly.
6.
Scratched or damaged label.
Possible FRU Replacement
v Picker Assembly
Resolution Perform “DR039: Resolve Logical Library Deletion” on page 6-75.
T081: Incorrect Module Brand
Description GUI Description: The library detected an incompatible module brand that
does not match the library configuration.
Explanation: The branding of a system is accomplished in two different
ways. The firmware uses information saved on the compact flash to
determine what brand the firmware and GUI's will present to the user. There
is also physical branding of the system in the form of different cosmetic
skins, badging, paint, external labels, etc. on each module. In addition, each
module has a machine readable bar code label that carries a module serial
number (SN) and branding information that should match the physical
branding of the module. The library manufacturing process should install a
machine readable bar code label that matches the external, user visible
branding of the module.
Because the library robot can read this bar code label, it can check the
branding of the physical modules against the branding of the firmware and
GUI's. This ticket is a defensive tool used to notify the user that there is a
mismatch in the branding mechanisms. The root cause of a mismatch can be
manufacturing defects, logistical errors (shipping the wrong spare part), or
user errors such as moving parts between systems.
6-36
TS3310 Tape Library Maintenance Information