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-1533738.1
Update Date:2017-05-18
Keywords:

Solution Type  Problem Resolution Sure

Solution  1533738.1 :   SL150 - Fibre Channel Library Can Not Be Recognized by Server After Reboot  


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




In this Document
Symptoms
Cause
Solution


Created from <SR 3-6831438541>

Applies to:

StorageTek SL150 Modular Tape Library - Version All Versions and later
HP LTO4 Tape Drive - Version Not Applicable and later
HP LTO5 Tape Drive - Version Not Applicable and later
HP LTO6 Tape Drive - Version All Versions and later
Information in this document applies to any platform.

Symptoms

SL150 - Fibre Channel Library Can Not Be Recognized by Server After Reboot 

Media server
===========
Application_log
---------------
Error    26.02.2013 01:46:14    NetBackup TLD Control Daemon    5133    None    TLD(1) [5848] Could not get serial number for robot \\.\Scsi4: (SCSI coordinates {4,0,0,1})
Information    26.02.2013 01:46:14    NetBackup TLD Control Daemon    5122    None    DeviceIoControl() error on bus 0, target 0, lun 1 (2:The system cannot find the file specified. )
Error    26.02.2013 01:46:13    NetBackup TLD Daemon    5705    None    TLD(1) going to DOWN state, status: Unable to open robotic path
Error    26.02.2013 01:46:12    NetBackup TLD Control Daemon    5133    None    TLD(1) [9528] Could not get serial number for robot \\.\Scsi4: (SCSI coordinates {4,0,0,1})
Information    26.02.2013 01:46:12    NetBackup TLD Control Daemon    5122    None    DeviceIoControl() error on bus 0, target 0, lun 1 (2:The system cannot find the file specified. )
Information    26.02.2013 01:46:12    NetBackup TLD Control Daemon    0    None    starting tldcd
Error    26.02.2013 01:46:12    NetBackup TLD Daemon    5705    None    TLD(1) going to DOWN state, status: Unable to open robotic path
Error    26.02.2013 01:46:12    NetBackup TLD Control Daemon    5133    None    TLD(1) [5848] Could not get serial number for robot \\.\Scsi4: (SCSI coordinates {4,0,0,1})
Information    26.02.2013 01:46:12    NetBackup TLD Control Daemon    5122    None    DeviceIoControl() error on bus 0, target 0, lun 1 (2:The system cannot find the file specified. )
Error    26.02.2013 01:46:11    NetBackup    2670    None    Request for media ID KB5068 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Error    26.02.2013 01:46:11    NetBackup    2670    None    Request for media ID KB5055 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Error    26.02.2013 01:46:11    NetBackup    2670    None    Request for media ID KB5044 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
Error    26.02.2013 01:46:10    NetBackup TLD Daemon    5705    None    TLD(1) going to DOWN state, status: Unable to open robotic path
Error    26.02.2013 01:46:10    NetBackup TLD Control Daemon    5133    None    TLD(1) [2984] Could not get serial number for robot \\.\Scsi4: (SCSI coordinates {4,0,0,1})
Information    26.02.2013 01:46:10    NetBackup TLD Control Daemon    5122    None    DeviceIoControl() error on bus 0, target 0, lun 1 (2:The system cannot find the file specified. )
Error    26.02.2013 01:46:10    NetBackup TLD Control Daemon    5133    None    TLD(1) [8948] Could not get serial number for robot \\.\Scsi4: (SCSI coordinates {4,0,0,1})
Information    26.02.2013 01:46:10    NetBackup TLD Control Daemon    5122    None    DeviceIoControl() error on bus 0, target 0, lun 1 (2:The system cannot find the file specified. )
Information    26.02.2013 01:45:40    NetBackup TLD Control Daemon    0    None    starting tldcd

 

1. This issue was observed on all platform, HPUX, AIX, Linux, and Windows.
2. This issue is observed solid(always).
3. Host reboot or FC cable reinsertion is required to recover the status.

 

Cause

 This is a known issue with Brocade FC switches.  Minimum f/w levels are:  

6.4.2a, 7.0.0a and 6.3.2c depending on the model of the Brocade switch attached.

Solution

 Upgrade the Brocade Switch Firmware.

Bug 16265096 - SL150 FC can't be recognized by server after reboot(1017-1)

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