T10000C/T10000D - Media Validation operations with STA

Asset ID:	1-72-1943461.1
Update Date:	2017-05-19
Keywords:

Solution Type Problem Resolution Sure

Solution 1943461.1 : T10000C/T10000D - Media Validation operations with STA

Applies to:

StorageTek T10000C Tape Drive - Version All Versions and later
StorageTek T10000D Tape Drive - Version All Versions and later
StorageTek Tape Analytics - Version 2.0 and later
Information in this document applies to any platform.

STA 2.0.0.83, STA 2.0.1.4, T10KC 3.62.108, and T10KD_4.09.10x

Summary:
A new code release for T10KC at 3.62.108 is scheduled to release 11/11/2014. The TTI specification was upgraded to 5.50 for this release to support the new 18 character serial number for the updated drive trays. This will impact Media Validation for STA 2.0.0 and STA 2.0.1 if the drive code level is updated to the code levels that support TTI_5.50. To ensure customers can still perform Media Validation operations with STA, until they upgrade to a future STA release, the actions identified below, will need to be performed.

STA = StorageTek Analytics

Symptoms

Behavior of STA if the Actions are NOT taken:

If a customer does not follow the designated actions and does upgrade their T10000C/D drives to the new code level, then the customer will experience the following behavior:

STA will not initiate or recognize drives for Media Validation operations with 3.62.108/TTI 5.50.
STA will still process the exchanges for both Standard and MV exchanges on drives with 3.62.108 or greater code using the same calculations as previously done with the lower TTI levels. STA will process the longer drive tray serial numbers and will still have the drives show up in the STA UI screens.

Cause

Firmware issue.

Solution

Actions Required by Customers or Service:

STA 2.0.0.83, STA 2.0.1.4

Customers will need to follow the actions listed below in order to support Media Validation with this and all future releases of T10KC drive codes and all future T10KD drive codes with TTI version 5.50<noted in the code string>:

The steps below are to be performed on the STA server.

The STA Application and STA Database must both be up and running to start the procedure.

From a Linux command shell:

1. mysql -uroot -p stadb

2. INSERT INTO `stadb`.`lkup_drive_fw_mapping` (`in_fw`, `mapped_fw`) VALUES ('3.62.109-5.50', '1.59.301-5.40');

3. quit

4. STA stop all

5. STA start all

6. Note: it will take 10 -> 20 minutes for the MV drives to be scanned and recognized.

Note:

In this example the coded string '3.62.109-5.50' in step #2 must match what the drive is reporting on the “STA Drives - Overview” screen. View the column named “Drive Firmware Version” to obtain the same. You may have to add that column to the screen if it is not already showing via the View -> Columns option on that same screen.

It is possible the coded string can vary in the same code release; example 3.62.109-5.50 and RC362109-5.50. It may be necessary to insert both strings, not just one. Hence do step #2 twice, one for each version if necessary.

INSERT INTO `stadb`.`lkup_drive_fw_mapping` (`in_fw`, `mapped_fw`) VALUES ('3.62.109-5.50', '1.59.301-5.40');
INSERT INTO `stadb`.`lkup_drive_fw_mapping` (`in_fw`, `mapped_fw`) VALUES ('RC362109-5.50', '1.59.301-5.40');

T10000D:

The next T10000D release 4.09.10x is also expected to support TTI 5.50 and will impact STA 2.0.0 and STA 2.0.1 in the same manner. This release is tentatively scheduled for Q1_2015.

Resolution

Upgrade to STA at 2.1.0 or greater; STA_2.1.0 released Q1_2015.

Attachments

This solution has no attachment