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-2373018.1
Update Date:2018-03-15
Keywords:

Solution Type  Problem Resolution Sure

Solution  2373018.1 :   SL8500 - Tape library Robot Showing Failure to Communicate  


Related Items
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
  •  




In this Document
Symptoms
Cause
Solution


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for service personnel
Created from <SR 3-17034710991>

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Tape library Robot at 1,1,0,20 shown failed to communicate.

1.1.0.2.0                   HBB   74034391      HBB   74034391      Error          robot               false          false                  INVESTIGATE Error Status

2018-03-08 18:12:11 Rail 1
--------------------------------------------------
Bot(1.1.0.2.0)
1301 - (17X)
Device response time-out, request=  healthCheck  internalActivity   183  
Device response time-out, request=  healthCheck  internalActivity   197  
Device response time-out, request=  healthCheck  internalActivity   212  
Device response time-out, request=  healthCheck  internalActivity   198  
(Errors Started - 2018-03-08 17:56:11 Errors Stopped - 2018-03-08 18:12:11)

45911 2018-03-08T17:56:11.400 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605063"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>183</watchdogTimeout></parms></request>
45916 2018-03-08T17:57:11.479 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605075"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45921 2018-03-08T17:58:11.635 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605087"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45926 2018-03-08T17:59:11.649 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605099"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45931 2018-03-08T18:00:11.639 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605111"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45936 2018-03-08T18:01:11.719 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605132"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>212</watchdogTimeout></parms></request>
45941 2018-03-08T18:02:11.549 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605144"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45946 2018-03-08T18:03:11.739 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605156"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45951 2018-03-08T18:04:11.671 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605168"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45956 2018-03-08T18:05:11.759 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605180"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45961 2018-03-08T18:06:11.629 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605201"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45966 2018-03-08T18:07:11.659 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605213"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45971 2018-03-08T18:08:11.699 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605225"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45976 2018-03-08T18:09:11.779 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605237"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45981 2018-03-08T18:10:11.819 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605249"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>
45986 2018-03-08T18:11:11.929 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605270"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>198</watchdogTimeout></parms></request>
45991 2018-03-08T18:12:11.799 1.1.0.2.0 root default internal 0 error 1301 "Device response time-out", request=<request sequence="605282"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>197</watchdogTimeout></parms></request>

Cause

 Robot is defective, possible motor issue.

Solution

Replace the robot.


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