StorageTek T10000C Tape Drive
 
Sun StorageTek 9840A Tape Drive
 
Sun StorageTek T10000A Tape Drive
 
Sun StorageTek 9840D Tape Drive
 
Sun StorageTek Crypto Key Management System
 
Sun StorageTek 9940A Tape Drive
 
StorageTek T10000D Tape Drive
 
Oracle Key Manager
 
Sun StorageTek 9840 Tape Drive
 
Sun StorageTek T10000B Tape Drive
 
Sun StorageTek 9940B Tape Drive
 
Sun StorageTek 9840B Tape Drive
 
Sun StorageTek 9840C Tape Drive
 
Sun StorageTek 9940 Tape Drive
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
 

Applies to:

Goal

How to Collect Error logs and Drive dumps from T9840, T9940, and T10000 Tape Drives.

Solution

DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED:
Familiar with 9840, 9940 and T10000 tape drives.

- TIME ESTIMATE: 60 minutes

- TASK COMPLEXITY: 0

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
- PROBLEM OVERVIEW:
Undetermined problem with the tape drive. Need to acquire logs to determine what is causing drive failure.

- WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?:
Drives can be left online to collect all existing log files. The exception is if support has specific instructions to force a new drive dump, which requires drive to be offline to software application and OS.

- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:
Support files and drive dumps from the T9840, T9940, and T10000 tape drives can be gathered for analysis using the VOP or Multi-Drive VOP programs.

Application requirements & restrictions:
- MDVOP 1.2.14 or VOP 1.0.17 (or higher) is required to gather dumps and logs from T9840A/B/C or T9940A/B tape drives.
- MDVOP 1.3 or VOP 1.0.18 (or higher) is required to gather dumps and longs from T10000A/B drives running code version 1.48.x05 (or higher) and T10000C drives running 1.53.311 (or higher).
- Customers using the appropriate MDVOP application have the ability to gather the logs from the tape drives themselves.

Note: (Apr 2016) "Consider SDP2 installation as an easy way to automatically send logs etc."
Review to the following KB to SDP2 Introduction article https://support.oracle.com/epmos/faces/DocumentDisplay?id=1942540.1

Files to gather:
- Drive Event Logs
- Drive Perm Error Logs
- Drive ID files
- Drive Dumps*

*The process of gathering these files (including already existing drive dumps) is non-disruptive. However, forcing a new drive dump is not. If support has requested a new drive dump, please make sure the drive is not in use and is offline prior to forcing new dumps. If a dump already exists on the drive, the button in VOP labeled Dump will be illuminated orange.

To force a dump using VOP:
Note: This step can be skipped if support has not requested new a new drive dump.
- Make sure all traffic to the drive has been stopped.
- Bring up VOP and connect to the drive.
- Select > Drive Operations > Force Dump
- Watch the display on VOP. It should reconnect o the drive after the drive IPLs but it may not. If it does not reconnect to the drive, open a new session to the drive.

To gather the logs (and any existing dumps):
Simplest instruction to retrieve the logs per drive is:
Collect drive support logs using single drive VOP CSE version.
(VOP--File--Collect Support Logs)
This will pull ID, perms, event log, and a dump if such is available. You then only need to guide separately how to force/retrieve the dump for different purposes.

To gather the logs (and any dumps): (Out Dated Process Here. Dec 2015)
- Bring up VOP and connect to the drive.
- Select: Retrieve > Dumps to File   (Navigate to the desired location and save the file.)
- Select: Retrieve > Logs to File      (Navigate to the desired location and save the file.) 
- Select: Retrieve > Perms to File    (Navigate to the desired location and save the file.)
- Select: Retrieve > ID Files to File  (Navigate to the desired location and save the file.)

Zip and upload these files as attachments to the SR. (Note: Please do not use spaces in any of the file names.)

MDVOP (Multi-Drive Virtual Op Panel):
These files can be gathered from multiple drives at once if using MDVOP.
- Multiple drives can be selected by holding <CTRL> and clicking on the desired drives on either the Drive State View, Encryption View, or Drive Health View tabs.
- Once the desired drives are properly selected, select - Retrieve: All Logs in This Library.

Reference:
Alternate method to force a dump 9840A/B/C/D and 9940A/B only using the operator panel:

Note: Make sure there is no I/O activity at the drive:
- Hold in the Menu and Unload buttons for one second to dump current drive status from memory to EEPROM.
- Dump saving to the EEPROM begins when CHK FFFF displays and the power indicator begins to flash.
- When the dump is saved, the service indicator flashes.
- The drive automatically performs an IPL and returns to Online.
- The display will alternate between * (asterisk) and FFFF:Dmpyy

(yy = total number of all uncollected dump logs) until any normal drive activity is started.

OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
Bring drive back online to Operating System and Software Application.

PARTS NOTE:
StorageTek Virtual Op Panel Customer User's Guide
http://download.oracle.com/docs/cd/E19202-01/en/E20750/E20750_01.pdf

This solution has no attachment