T10000/9840 - Process For RTD Drives That Are Put Into Maintenance Mode

Asset ID:	1-72-1278426.1
Update Date:	2011-11-03
Keywords:

Solution Type Problem Resolution Sure

Solution 1278426.1 : T10000/9840 - Process For RTD Drives That Are Put Into Maintenance Mode

Applies to:

Sun StorageTek T10000B Tape Drive - Version: Not Applicable and later   [Release: N/A and later ]
Sun StorageTek T10000A Tape Drive - Version: Not Applicable and later    [Release: N/A and later]
Sun StorageTek 9840D Tape Drive - Version: Not Applicable and later    [Release: N/A and later]
Information in this document applies to any platform.
VSM RTDs in Maintenance Mode
o REQUIREMENT: Do not vary the drive back on-line.
o CSE should perform a "force dump" on the drive.
o After the "force dump", CSE should obtain:
+ ID files (get id)
+ drive dump file
+ event logs
+ any perm logs
o CSE should send all above files to Technical Support Rep assiged to the SR.
o Note: Some accounts have put automation in place to inform the operator to open a Service Ticket and tell Oracle that a drive is down waiting for a dump to be triggered.

--

Symptoms

RTD is in Maintenance Mode.

(Real Tape Drive as opposed to Virtual Tape Drive)

Cause

Many things can cause VTCS to put a drive in maintenance mode. This can VTSS, drive hardware, drive firmware VTSS firmware. A forced drive dump is needed to determine root cause.

Solution

Force a drive dump and sent it to the Tape Support Rep assigned to the SR for analysis. Do not just replace the drive as the drive may not be the problem.

How to force a drive dump for T10000 and 9840:

Dump collection is best done using either VOP or Multi Drive VOP. For 9x40A/B/C products you can use either STDS or VOP/MD VOP to retrieve the dump and associated log files.

STDS can be used to force and retrieve a dump from 9840A/B/C and 9940A/B drives.

VOP at version, 1.0.17 (or higher) can handle forcing and retrieval of a dump from all 9x40 and T10000 drive types.

Preferred method to Force a drive dump on all T10000 and 9x40 products:

Note: Forcing a drive dump is disruptive and requires that the drive first be taken offline by the host.

* Bring up VOP and connect to the drive. (or use MD VOP)
* Select >Drive Operations>Force Dump Note this can be done with the drive either offline or online.
* Watch the display on VOP. It may reconnect o the drive after the drive IPLs and it may not. If it does not reconnect to the drive then exit the VOP session and open a new session to the drive.

Preferred method to Retrieve a drive dump on all T10000 and 9x40 products:

Note: Retrieval of all logs including a dump can be done non-disruptively. (e.g. with the drive online and running jobs.)

* Bring up VOP and connect to the drive. (or use MD VOP)
* Select >Retrieve>Dumps to File Navigate to the path for the file.
* Select >Retrieve>Logs to File Navigate to the path for the file.
* Select >Retrieve>Perms to File Navigate to the path for the file.
* Select >Retrieve>IF Files to File Navigate to the path for the file
* Upload these files as attachments to the SR. Note: Please do not use spaces in any of the file names.

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

Note: Make sure there is not I/O activity at the drive:

- In open systems, ask the operator to make sure the drive is unavailable to the host.

- In the enterprise environment, ask the operator vary the drive offline.

A: Hold in the Menu and Unload switches 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.

Alternate method to retrieve a Forced dump for 9x40 or T10000. The dump tape method should only be used if you plan to pull the dump off the tape using SCSI/FC ToolBox. Technical Support will need a dump file rather then the dump tape.

B. If a dump tape is desired, collect (download) the EEPROM dump logs to tape using the following procedure.

The operation does not overwrite dump logs already on a dump tape. Newly collected dump logs append to dump logs already on the dump tape.

Use the following procedure to collect dump logs in the EEPROM to a tape:

1. Make sure the drive does not have I/O to/from the host.

2. Load a dump tape in the drive.

Notes: The following sequence occurs:

- Dump logs are automatically downloaded (written to the tape) from the drive's EEPROM.

- When the process is done, the dump tape ejects.

- If CHKxxxx displays, an error has occurred, and the drive was unable to write dump logs to tape.

- Make sure tape cartridge is formatted as a dump tape.

- Try a different dump tape.

Attachments

This solution has no attachment