Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1910640.1
Update Date:2018-01-05
Keywords:

Solution Type  Problem Resolution Sure

Solution  1910640.1 :   SL150 - New Installation, Robot Initialization Failure Code 9109  


Related Items
  • StorageTek SL150 Modular Tape Library
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL150 Library
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: SL150 log is encrypted which can only see from SPLAT, customer can't see above error logs
Created from <SR 3-9267470631>

Applies to:

StorageTek SL150 Modular Tape Library - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Product: SL150 Library
Install Model: Base Module(2 Drives) + 1 * Expansion Module(No Drives)

Problem: Robot Initialization Failure Code 9109
FSC9109

Changes

New installation;
Replaced robot module, but problem symptom remains.

Cause

 From error log found KLE connection failure, see below...

2014-07-01T18:53:31.380,      0.0.0.0.0, 529,            robot, /usr/local/bin/Ifm,  error, 0000, 1220, "Director - initResponse() directorSelfInit; Module 2 KLE Not Connected; End of Text"
2014-07-01T18:53:31.393,      0.0.0.0.0, 3202,              ifm,                 ,  error, 0100, 1220, "IfmInitThread:Failure to Initialize...reason==Communication to a KLE failed during Module locate operations. KLE disconnected? - GOING INOP"
2014-07-01T18:53:53.413,      0.0.0.0.0, 000,         VMonitor,                 ,  error, 0000, 7027, "VMonitorDriveInit driveInfo::issueCommand(): Drive Get Info Response Bad Result Code = 6414 For Drive ID 1"
2014-07-01T18:54:15.447,      0.0.0.0.0, 000,         VMonitor,                 ,  error, 0000, 7027, "VMonitorDriveInit driveInfo::issueCommand(): Drive Get Info Response Bad Result Code = 6414 For Drive ID 2"

Above error caused by USB Type A expansion interconnect cable being faulty.

Solution

 Replacement of the USB Type A expansion interconnect cable fixed the problem.

References

<NOTE:1558425.1> - SL150 - Robot Fails To Initialize With a 9109 Fault Code Resulting SL150 Going INOP
<NOTE:1532098.1> - SL150 - New Install, Robot Fails with Error 9109, Robot Initialization Failure
<NOTE:1588711.1> - SL150.9109.robot.initialization.failure

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback