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-1554285.1
Update Date:2018-04-10
Keywords:

Solution Type  Problem Resolution Sure

Solution  1554285.1 :   SL150 - Message "The Number of KLEs Seen by MCI Does Not Match Z's Range for Modules - GOING INOP" MSG 3203 Issued During Initialization  


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


During a new installation of a multi-module SL150 the customer sees  "The number of KLEs seen by MCI does not match Z's range for Modules - GOING INOP"  in the error logs

In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-7111922971>

Applies to:

StorageTek SL150 Modular Tape Library - Version All Versions and later
Information in this document applies to any platform.
New SL150 Installation
10 Module SL150 configuration.
1.82 Firmware

Symptoms

During initialization the following series of errors are seen in the error logs and the library does not go online (goes inop).

This is accompanied by multiple robot reach / put type errors. e.g. 5121, 3202 etc.

2013-05-13T19:08:02.138    0000    0.0.0.0.0    1228     "Director - initResponse() directorSelfInit; MCI Module Count is Greater than Z Range for Modules Calculation: MCI ModCnt=10, Z Sweep ModCnt=1; End of Text"             /usr/local/bin/Ifm     519                robot      error
       2013-05-13T19:08:02.143    0100    0.0.0.0.0    1228     "IfmInitThread:Failure to Initialize...reason==The number of KLEs seen by MCI does not match Z's range for Modules - GOING INOP"                                  3202                  ifm      error
       2013-05-13T19:08:03.160    3750    0.0.0.0.0    3755     "Process /usr/local/share/sbin/snmptrapd murdered by signal 11"                                  3750           processMgr      error


Changes

 The library was newly installed.

Cause

Misalignment of the modules caused robot movement sensor to be impeded resulting in the library not detecting the required number of modules during initial scan.  When the robot initializes, it moves to the bottom of the stack of modules and counts the number of modules present.  In this instance it detected 1 module when there should have been 10.  This misalignment also caused the robot movement to be impeded resulting in the attendant robot messages in the log.

Solution

Check for correct alignment of all modules. Refer to the SL150 Installation Manual E28647_05.

Remove all the magazines and inspect the Z-Home sensor for misplacement. (Refer to Doc ID 1532413.1)

 

References

<NOTE:1532413.1> - SL150 - Initialization Failure, Robot Z Home Sensor Init Error, Fault Code 9135
http://docs.oracle.com/cd/E35103_06/en/E28647/E28647_05.pdf

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