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-79-1665855.1
Update Date:2018-03-06
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1665855.1 :   STA 2.0 - Minimum Firmware Level of Code and Hardware Requirements for Tape Libraries and Tape Drives  


Related Items
  • StorageTek Tape Analytics
  •  
  • Sun StorageTek T10000A Tape Drive
  •  
  • Sun StorageTek T10000B Tape Drive
  •  
  • Sun StorageTek SL3000 Modular Library System
  •  
  • Sun StorageTek 9840D Tape Drive
  •  
  • HP LTO6 Tape Drive
  •  
  • StorageTek SL150 Modular Tape Library
  •  
  • Sun StorageTek SL8500 Modular Library System
  •  
  • Sun StorageTek SL500 Modular Library System
  •  
  • StorageTek T10000D Tape Drive
  •  
  • HP LTO5 Tape Drive
  •  
  • HP LTO4 Tape Drive
  •  
  • IBM LTO5 Tape Drive
  •  
  • IBM LTO3 Tape Drive
  •  
  • StorageTek T10000C Tape Drive
  •  
  • StorageTek Tape Analytics
  •  
  • IBM LTO6 Tape Drive
  •  
  • IBM LTO4 Tape Drive
  •  
  • HP LTO3 Tape Drive
  •  
  • Sun StorageTek 9840C Tape Drive
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: Tape Library Control Software
  •  




In this Document
Purpose
Scope
Details
References


Applies to:

StorageTek SL150 Modular Tape Library - Version All Versions and later
Sun StorageTek SL8500 Modular Library System - Version All Versions and later
IBM LTO6 Tape Drive - Version All Versions and later
Sun StorageTek T10000B Tape Drive - Version All Versions and later
HP LTO5 Tape Drive - Version All Versions and later
Information in this document applies to any platform.

Purpose

 This document lists the MINIMUM FIRMWARE requirements for Tape Libraries and Tape Drives TO BE SUPPORTED with StorageTek Tape Analytics (STA), Release 2.0

 For the best functionality and user experience, upgrade to the recommended or latest available firmware.

 Also a few needed hardware requirements are noted in this document, please have a read.

 Thank you

Scope

 To upgrade to the latest STA 2.x-supported firmware, open a service ticket with Oracle Support.
 Firmware versions are subject to change.

Details

1 Library Requirements

 

1.1 Library Firmware Requirements

Table 1  Library Firmware Requirements
FIRMWARE
SL150SL500SL3000SL8500
Minimum 1.82 1485
1493*
3.61

8.01
8.31*

Recommended** 2.01 1501 4.40 8.36

 

 

 

 

 

 

*     With IBM LTO 4 (with encryption), IBM LTO 5, and IBM LTO 6
**   At time of release. Newer firmware may be available
*** Includes Media Validation (MV) and richer component health data.

CAUTION SL8500 running firmware 8.31/8.35 and Redunant Electronic RE:
- 8.31/8.35 is not recommended for RE due to unexpected controller switches

Fix for this issue will be available on firmware 8.36 to be released october 2014

 

 

1.2 Library Hardware Requirements

Table 2  Library Hardware Requirements
Library Hardware Requirements
 
 
 
SL3000


SL8500
 
Component: HBT CARD
High-memory drive controller (HBT) card:
Required for Media Validation support (SL8500 only) and reporting of richer
drive data.
For libraries with LTO drives, a high-memory HBT card is required to enable
ADI mode.
To determine your HBT card's level of memory,
see "Verify the Drive Controller Card Version (SL3000 and SL8500 Only)"
in the STA Installation and Configuration Guide
Note:
All SL3000 libraries ship with the high-memory card.
Since 2006, all SL8500 libraries ship with the high-memory card.
 All other sl-series  
ETHERNET CONNECTION
Separate connection from STA to each library:
each library must have an assigned IP address and be reachable by the STA server.

Note:
Each library in an SL8500 complex has its own SNMP agent.
Therefore, STA must be able to connect to each library separately

 

 

1.3 Complex ID Requirements (SL8500 Only)

For STA to roll up library complex data correctly, each library complex at your site must have a unique complex ID.
On SL8500 libraries, complex IDs are set manually.
Table 3 lists valid SL8500 complex ID assignments.

 

■Each standalone SL8500 is considered to be a separate complex
and therefore must have a unique complex ID.

■Valid complex ID values are 1-127.

■Each multi-library complex must have a unique complex ID, and all libraries
within the complex must share the same ID
Caution
The Oracle Service Delivery Platform (SDP) also uses unique complex IDs for tracking library data.
If your site uses SDP, contact Oracle Service before changing any complex ID.
Changing the complex ID could cause SDP to fail.
In most cases, complex IDs are set correctly when SDP is connected.

 Ensuring the correct library complex ID is a configuration task in the STA Installation and Configuration Guide

 

Table 3 Example complex ID Assignments
Complex Type LibrariesAssigned Complex ID
Multi-library complex
SL8500-1

SL8500-2

SL8500-3
1

1

1

Standalone libraries

SL8500-4

SL8500-5

2

3

 

1.4 Volume Label Formatting Requirements (SL500 and SL150 Only)

Setting the proper volume label format is a configuration step in the STA Installation and Configuration Guide.
Volume serial numbers (volsers) in SNMP data must be formatted properly for STA to correctly process library exchange data.
The media volser includes a two-character suffix that indicates the media type.
For example, if a cartridge volser is ABC123L4, "L4" indicates the media type is LTO4.
For proper STA reporting, the volser suffix must be excluded.

Caution:
If these parameters are not set properly, volsers will be formatted incorrectly, causing exchanges processing to be blocked, superfluous attempts to get the latest media data, and irreversible,
eight-character volser records to appear on the Media - Overview screen whenever the "Show Removed Media" preference is set.

 

■ For all SL500 libraries monitored by STA, the label orientation for the host must be set to "left6" and "STA mode" must be set to "on".
("STA mode" affects only the format of the volser sent to the STA server through SNMP, not the format used on the SL500 library itself.)

■ For all SL150 libraries monitored by STA, "Volume Label Format" must be set to "Trim last two characters".

 

1.5 SL500 Fastload

The FastLoad option should be disabled on SL500 libraries, as cartridge mount traps
are not properly sent to STA when FastLoad is enabled.
FastLoad is disabled by default.
If you are unsure of the status of this option, contact Oracle Support

 

__________________________________________________________________________

 

2 Tape Drive Requirements

 

 

2.1 StorageTek Drive Firmware Requirements

 

Table 4  StorageTek Tape Drive Firmware - Minimum Versions for STA
StorageTek
Drive
TTI 5.10TTI 5.20TTI 5.30TTI 5.40

TTI 5.40

Media Validation Support*

T10000A 1.44.108 1.46.109 1.48.112 NA NA
T10000B 1.44.208 1.46.209 1.48.212 NA NA
T10000C NA 1.51.320 1.53.316 1.57.308 1.59.302
T10000D NA NA NA
4.07.104
(FC/FCoE)
4.07.106 (FICON)
4.07.106 (FC/FCoE)
4.07.106
(FICON)
9840C 1.44.510 1.45.503 NA NA NA
9840D 1.44.710 1.45.703 NA NA NA

 *In a FICON environment, Complete Verify Plus StorageTek Data Integrity Validation is not supported

 

 

2.2 HP LTO Drive Firmware Requirements

 

Table 5  HP LTO Tape Drive Firmware - Minimum Versions for STA
HP LTO DriveSupported
Firmware
SL8500SL3000SL500SL150
LTO3 LVD SCSI
G69S     YES  
LTO3 FC 2Gb
L6HS YES YES YES  
LTO3 FC 4Gb M6BS YES YES YES  
LTO4 LVD SCSI B57S     YES  
LTO4 FC 4Gb H58S YES YES YES  
LTO 5 Full-height FC 8Gb
I3CS YES YES YES  
LTO 5 Full-height SAS 6Gb
X3AS     YES*  
LTO 5 Half-height FC 8Gb
Y5BS       YES
LTO 5 Half-heigh SAS 6Gb Z55S       YES
LTO 6 Full-height FC 8Gb J2DS YES YES YES  
LTO 6 Half-height FC 8Gb 22GS       YES
LTO 6 Half-heigh SAS 6Gb 32DS       YES

 *Requires SL500 Bridged Base Unit

 

 

2.3 IBM LTO Drive Firmware Requirements

 

Table 6  IBM LTO Tape Drive Firmware - Minimum Versions for STA
IBM LTO
Drive
Supported
Firmware
SL8500SL3000SL500SL150
LTO3 FC 2Gb 93G0 YES YES YES  
LTO4 FC 2/4Gb 94D7 YES YES YES  
LTO4 FC 2/4Gb
w/ Encryption*
C7QH YES** YES YES**  
LTO5 FC 8Gb* D2AC YES** YES YES**  
LTO6 FC 8Gb* D8E4 YES** YES    
LTO7 FC 8Gb FA14 YES YES    

*If the customer is running our OKM encryption solution they must have Belisarius cards installed in the drive tray. If a customer running OKM encryption with Belisarius cards wants to enable ADI mode for STA then they must have the correct firmware installed on the Belisarius cards and the Belisarius cards must be forced into ADI mode. For the IBM LTO4, LTO5, and LTO6 drives the Belisarius card must be running a minimum code level of 4.17.18.36. For IBM LTO7 drives the Belisarius card must be running a minimum code level of 4.20.20.40.

** See Table 1 for minimum required library firmware version.


References

<NOTE:1912563.1> - SL8500 - 8.35 Firmware RE Recommendation, A heartbeat Can Be Missed and Cause the Library to Unintentionally Switch
http://docs.oracle.com/cd/E39018_01/en/E52310/E52310_01.pdf

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