Detection Scenario During the Installation & Verification Test run, any library error occurs that
is not already handled by an existing RAS ticket.
Root Causes Any function that is executed by the Installation & Verification Test that does
not complete successfully.
Resolution Perform “DR021: Contact IBM Service” on page 6-68.
T096: Module Communication Error
Description GUI Description: An error occurred while trying to communicate with a
module.
Explanation: The system is having a problem finding and/or communicating
with all the modules in the library.
Detection Scenario At boot up, the library cannot determine the status of all modules.
Root Causes
v Bent pin on a terminator or a module-to-module cable.
v I/O station sensor error.
v I2C bus error.
Possible CRU Replacements
v LCB
v Module-to-module cable
v CAN Bus terminator
Possible FRU Replacement
v CM or EM module
v I/O Station assembly
v I/O Lock assembly
Resolution Perform “DR056: Resolve Module Communication” on page 6-80.
T108: Incompatible Drive Brand
Description GUI Description: An incompatible drive sled installation has been detected.
Explanation: Different library configurations support different drives. The
drive sleds will contain certain configuration information that the library will
use to validate that the drive is indeed configured properly. If a drive's
configuration data does not match what the library expects, the drive will
not be usable and this ticket will be generated.
Detection Scenario When drive is installed, the configuration data does not match what is
expected.
Root Causes
v User installed a drive from a different brand library.
v User did not purchase the drive from an official TS3310 sales channel.
v Drive sled does not have the correct configuration information
programmed.
Possible FRU Replacement Drive sled
Resolution Perform “DR068: Resolve Incompatible Tape Drive” on page 6-81.
Chapter 6. Service Action Tickets (Txxx) and Diagnostic Resolutions (DRxxx) 6-45
To Next Page
Loading...
Need help?
General
