Readme

IBM TotalStorage Tape Diagnostic Tool Standard Edition README
=============================================================
-------------------------------------------------------------------------------
Table of contents
=================
1.0 Prerequisites
1.1 Supported Products
1.2 Supported Operating Systems and Platforms
1.3 Screen Size
2.0 Installation & Initial Startup
2.1 Microsoft Windows
2.2 Sun Solaris
2.3 i5/OS
2.4 All other supported Operating Systems
3.0 General Program Navigation
4.0 Scan
5.0 Test Device
6.0 Firmware Dump
7.0 Microcode Download
8.0 Full Write
9.0 Encryption Test
10.0 Tape Usage
11.0 Manual Inspection
12.0 Known Issues/Limitations
12.1 All operating systems
12.1.1 User Interface issues
12.1.2 Command Timeout
12.1.3 3583 Microcode Update
12.1.4 3581-2U
12.1.5 3581
12.1.6 3582
12.1.7 3576/TS3310
12.1.8 3592/TS1120
12.2 Windows
12.3 AIX
12.4 Linux
12.4.1 Linux on pSeries
12.4.2 Linux on zSeries
12.5 Solaris
12.6 HP-UX
12.6.1 PA-Risc
12.6.2 Itanium/IA-64
12.7 i5/OS
-------------------------------------------------------------------------------
1.0 Prerequisites
=================
1.1 Supported Products
----------------------
IBM TotalStorage Tape Diagnostic Tool Standard Edition (ITDT-SE) will support
diagnostics for the following products:
IBM Ultrium 3580 Tape Drive (Generation 1, 2, 3 and 4)
IBM Ultrium Tape Drives T200/F, T400/F, T800/F, T800V, T1600/F
IBM System Storage 3588/TS1030 model F3A and F3B Tape Drive
IBM System Storage 3588/TS1040 model F4A Tape Drive
IBM System Storage 3580 Half Height/TS2230 Tape Drive Express
IBM System Storage TS2340 Tape Drive Express
IBM 3592/TS1120 Enterprise Tape System
IBM 3581 Ultrium Tape Autoloader
IBM 3581-2U Ultrium Tape Autoloader
IBM 3582 and 3583 Ultrium Scalable Tape Library
IBM System Storage 3573/TS3100 and TS3200 Tape Library Express
IBM System Storage 3576/TS3310 Tape Library
On i5/OS see Section 12.7 "i5/OS" for product support limitations.
1.2 Supported Operating Systems and Platforms
---------------------------------------------
Microsoft Windows Server 2000 with SP4 (32-bit IX86)
Microsoft Windows Server 2003 (32-bit IX86)
AIX 5L 5.2 and 5.3 (64-bit pSeries)
Linux systems with Kernel 2.4 and 2.6, glibc 2.2.5 and later (32-bit IX86)
Linux systems with Kernel 2.4 and 2.6, glibc 2.2.5 and later (64-bit pSeries)
Linux systems with Kernel 2.6, glibc 2.3.3 and later (64-bit zSeries)
Solaris Version 9 and 10 (64-bit SPARC)
HP-UX Version 11.xx (PA-Risc and Itanium)
i5/OS V5R3 and V5R4 (iSeries)
1.3 Screen Size

---------------
80x24 (VT 100) screen resolution is ideal, higher resolutions will also work.
2.0 Installation & Initial Startup

===================================
2.1 Microsoft Windows
---------------------
NOTE: ITDT-SE can only be used by a user with Administrator rights.
1. Download itdtinst<version>Windows.exe to a directory of your choice.
2. Execute itdtinst<version>Windows.exe.
3. Start itdt.exe.
At first program startup, the license text will be displayed and the input and
output directories will be created.
ITDT-SE does not create any registry entries or make changes outside the
installation directory.
2.2 Sun Solaris
---------------
NOTE: ITDT-SE can only be used by a user with root access rights.
1. Download itdtinst<version>Solaris to a directory of your choice.
2. Make itdtinst executable with "chmod 700 itdtinst<version>Solaris".
3. Execute itdtinst<version>Solaris.
4. Configure the sgen driver
ITDT-SE requires that the sgen device driver is configured so that the
devices you want to work with can be found. A script
"sgen_solaris_conf.sh" is included in the ITDT-SE package which allows the
user to configure the sgen generic scsi driver that is shipped with
Solaris.
NOTE: For system security reasons, please always re-set the sgen device
driver settings after you finished working with ITDT-SE, using the
sgen_solaris_conf.sh script.
Start this script with root access:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SGEN driver configuration utility version 0.3
All rights reserved by IBM (C)
1) Check Driver 4) Stop sgen driver
2) List driver settings 5) Start sgen driver
3) New driver configuration 6) Exit program
Select an action:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Select the following items:
1) Check driver -> checks if the driver /kernel/drv/sgen is available
2) List driver settings -> shows the current activated devices
3) New driver configuration -> displays following screen to create a new
driver configuration:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SGEN driver configuration utility version 0.3
All rights reserved by IBM (C)
1) List targets 5) Add target(s) range
2) Define device types 6) Remove target(s) range
3) Add a target 7) Save configuration
4) Remove a target 8) Back to Main Menu
Select an action:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From the New Configuration screen select:
1) List targets -> shows the targets in current configuration
2) Define device types -> defines drive and changer types
3) or 5) Add target(s) -> adds targets to the list
4) or 6) Remove target(s) -> removes targets from the list
7) Save configuration -> saves your modifications
8) Back to Main Menu -> go back to main menu and continue with following
steps
4) Stop sgen driver -> stops the driver (e.g. rem_drv sgen)
5) Start sgen driver -> stops and starts the sgen driver
New devices will be found using the definitions
done in 3) New driver configuration
6) Exit program -> close the shell script
5. Start itdt.
ITDT-SE does not make changes outside the installation directory.
2.3 i5/OS
---------
NOTE: ITDT-SE on i5/OS requires that the QShell is installed.
ITDT-SE can only be used by a user with QSECOFR rights.
To install ITDT-SE:
1. Unzip itdtinst<version>I5OS.zip (The zipped save file is over 15 Mb.)
2. Create a save file ITDTI5OS on the target iSeries:
CRTSAVF FILE(QGPL/ITDTI5OS)
3. FTP the save file(ITDTI5OS.FILE), in binary mode, into the save
file created in the above step.
4. Restore ITDT library: RSTLIB SAVLIB(ITDT) DEV(*SAVF) SAVF(QGPL/ITDTI5OS)
Four objects should be restored.
5. Call the install program: CALL ITDT/INSTALL
6. Launch the iSeries Q-Shell environment QSH
7. Enable QShell support for multi-threaded programs:
export QIBM_MULTI_THREADED=Y
8. Change to the folder /home/itdt
9. Start itdt
2.4 All other supported operating systems

-----------------------------------------
NOTE: ITDT-SE can only be used by a user with root access rights.
1. Download itdtinst<version><OS> to a directory of your choice.
itdtinst<version>Aix is for AIX, itdtinst<version>LinuxX86 is for Linux on
Intel hardware, itdtinst<version>LinuxPPC is for Linux on pSeries,
itdtinst<version>LinuxS390X is for Linux on zSeries,
itdtinst<version>Hpux is for HP-UX.
2. Make itdtinst<version><OS> executable with "chmod 700 itdtinst<version><OS>".
3. Execute itdtinst<version><OS>.
4. Start itdt.
3.0 General Program Navigation

==============================
To execute a command, enter the shortkey displayed in brackets followed by
the Enter key.
Use the online help - press H followed by the Enter from any screen to
bring up the online help for that screen.
4.0 Scan
========
The scan functionality is used to discover all supported tape and library
devices that are attached to the computer system so that they can be selected
for the subsequent ITDT-SE operations.
It also serves as a connection test that can be used to verify proper attachment
of the devices.
After starting ITDT-SE, press the S key followed by the Enter key to activate
the scan functionality:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
IBM TotalStorage Tape Diagnostic Tool SE V1.2
Entry Menu
[S] Scan for tape drives
[H] Help
[Q] Quit program
Notes:
- During a test, user data on the cartridge will be erased!
- Make sure no other program is accessing the devices used by ITDT!
- A device scan may take several minutes in some cases!
- Q + Enter will always close this program.
- H + Enter will display a Help page.
<[H] Help | [Q] Quit | Command > s

Depending on the operating system and the number of attached drives, the scan
can take several minutes - for more details, please refer to section 12.
During the scan operation, a bar in the lower left edge of the screen will
show that the scan operation is still in progress.
Once the scan is finished, you will see a screen similar to the following:
IBM TotalStorage Tape Diagnostic Tool - Device List
Host Bus ID LUN Model Serial Ucode Changer [#]
+----+----+----+----+----+--------------+------------+------+------------+-+
| 0 | 1 | 0 | 4 | 0 | ULT3580-TD1 | 6811003728 | 36UG | IBM7801127 | |
| 1 | 1 | 0 | 5 | 0 | ULT3580-TD1 | 6811003629 | 36UG | IBM7801127 | |
| 2 | 1 | 0 | 6 | 0 | ULT3583-TL | IBM7801127 | 2.86 | | |
| 3 | | | | | | | | | |
| 4 | | | | | | | | | |
| 5 | | | | | | | | | |
| 6 | | | | | | | | | |
| 7 | | | | | | | | | |
| 8 | | | | | | | | | |
| 9 | | | | | | | | | |
| 10 | | | | | | | | | |
| 11 | | | | | | | | | |
+----+----+----+----+----+--------------+------------+------+------------+-+
[S] Scan [T] Test Device [W] Full Write [E] Encryption Test
[D] Firmware Dump [M] Microcode DL [I] Manual Inspect[U] Tape Usage
<[H] Help | [Q] Quit | Line # | Command >
The device list shows all detected devices with their connection information
(host adapter number, bus number, SCSI/FCP ID and LUN) along with product data
(Model name, Unit Serial number, Microcode revision).
For drives that are attached to a library, the Changer column will show the
serial number of the changer the drive is attached to.
To scroll down in the list to access non-displayed entries, type + and press
Enter. For fast down scrolling type + followed by a space and the number of
lines to scroll down then press Enter.
To scroll back, use - instead of +.
If no devices appear in the list, make sure that
- You are running ITDT-SE with administrator/root rights
- The devices are properly attached and powered on
5.0 Test Device

===============
WARNING: The test device functionality erases user data on the cartridge that
is used for the test!
The test can take from 15 minutes up to 2 hours.
The test runs only on tape drives not on autoloaders or libraries.
We recommend to use a new or rarely used cartridge to run the test. Scaled
(capacity-reduced) cartridges should not be used to test the device.
The test will check if the tape device is defective and output a pass/fail
result.
To test tape drives within a library, the library must be in online mode.
After starting ITDT-SE, press S followed by the Enter key to activate the device
scan. After the scan is finished, you should see a screen like the following:
+----+----+----+----+----+--------------+------------+------+------------+-+
| 0 | 1 | 0 | 4 | 0 | ULT3580-TD1 | 6811003728 | 36UG | IBM7801127 | |
| 1 | 1 | 0 | 5 | 0 | ULT3580-TD1 | 6811003629 | 36UG | IBM7801127 | |
| 2 | 1 | 0 | 6 | 0 | ULT3583-TL | IBM7801127 | 2.86 | | |
| 3 | | | | | | | | | |
| 4 | | | | | | | | | |
| 5 | | | | | | | | | |
| 6 | | | | | | | | | |
| 7 | | | | | | | | | |
| 8 | | | | | | | | | |
| 9 | | | | | | | | | |
| 10 | | | | | | | | | |
| 11 | | | | | | | | | |
+----+----+----+----+----+--------------+------------+------+------------+-+
<[H] Help | [Q] Quit | Line # | Command > 1
To test a tape drive, you have to select the line number from the leftmost
column in the table that corresponds to the device that you want to test. In the
example above, the tape drive #1 shall be selected, so 1 followed by Enter will
select that device:
+----+----+----+----+----+--------------+------------+------+------------+-+
| 0 | 1 | 0 | 4 | 0 | ULT3580-TD1 | 6811003728 | 36UG | IBM7801127 | |
| 1 | 1 | 0 | 5 | 0 | ULT3580-TD1 | 6811003629 | 36UG | IBM7801127 |X|
| 2 | 1 | 0 | 6 | 0 | ULT3583-TL | IBM7801127 | 2.86 | | |
| 3 | | | | | | | | | |
| 4 | | | | | | | | | |
| 5 | | | | | | | | | |
| 6 | | | | | | | | | |
| 7 | | | | | | | | | |
| 8 | | | | | | | | | |
| 9 | | | | | | | | | |
| 10 | | | | | | | | | |
| 11 | | | | | | | | | |
+----+----+----+----+----+--------------+------------+------+------------+-+
<[H] Help | [Q] Quit | Line # | Command >
The selected device is marked with an X in the rightmost column.
Type T and press Enter to start the test.
ITDT-SE will then switch to the device test screen. If no cartridge is inserted,
ITDT-SE will prompt to insert a cartridge. Either insert a cartridge and press
the Enter key or abort the test by entering C followed by the Enter key.
If ITDT-SE detects data on the cartridge, it will show the following screen:
IBM TotalStorage Tape Diagnostic Tool - Device Test
+--------------------+ +---------------+
Model: | ULT3580-TD1 | Serial No: | 6811003629 |
+---------+---------------------------+ +---------------+
| |
+-----+ | Cartridge not empty! | +---------------+
Host: | 1 | | Overwrite data? | | 36UG |
+-----+ | | +---------------+
Bus: | 0 | | ALL DATA ON CARTRIDGE | | IBM7801127 |
+-----+ | WILL BE DELETED! | +---------------+
| |
+---------| [Y] Yes [N] No | +--------------------+
Progress: |#########| | | MOUNT TAPE |
+---------| | +--------------------+
+---------------------------+
[A] Abort
< [Y] Yes | [N] No

Type Y followed by Enter to continue the test if you are absolutely sure that
data on the cartridge can be overwritten. If you are unsure, press N followed by
Enter to abort the test.
During the test, the program will show a progress indicator in form of a bar of
hash marks (#) that shows the progress of a single sub-test as well as a
description of that sub-test. In the following screenshot, the LOAD/WRITE/UNLOAD
test is running and it is currently 25% completed:
+--------------------+ +---------------+
+--------------------+ +---------------+
+-----+ +-----+ +---------------+
Host: | 1 | ID: | 5 | Microcode: | 36UG |
+-----+ +-----+ +---------------+
Bus: | 0 | LUN: | 0 | Changer: | IBM7801127 |
+-----+ +-----+ +---------------+
+--------------------+ +--------------------+
Progress: |##### | Status: | LOAD WRITE UNLOAD |
+--------------------+ +--------------------+
[A] Abort
<[Q] Quit | Command >
Note that you can abort the test by pressing the A key followed by enter at any
time except during the POST tests that are not interruptible. Also note that it
may take some time until the test actually aborts.
If all sub-tests are finished, ITDT-SE will show a screen similar to the
following:
+--------------------+ +---------------+
+--------------------+ +---------------+
+-----+ +-----+ +---------------+
+-----+ +-----+ +---------------+
+-----+ +-----+ +---------------+
+--------------------+ +---------------------------+
Result: | PASSED | Code:| OK |
+--------------------+ +---------------------------+
Dumps:
+---------------------------+---------------------------+
Bin Log: | 6811003629.021.blz | |
+---------------------------+ |
Text Log: | 6811003629.006.txt | |
+---------------------------+---------------------------+
[R] Return to device list
<[H] Help | [Q] Quit | Command >
It shows attachment and device information as in the device list together with
the test Result and failure information in the Code field.
In the example above, the test passed, so the drive is tested good.
The screen also shows the output files that were generated during the test run.
The files may be requested by the IBM Support Center.
If you want to use other ITDT-SE functions, press R followed by Enter to return
to the device list, otherwise you may press Q followed by Enter to exit the
program.
6.0 Firmware Dump

=================
Start ITDT-SE, then type S and press Enter to scan for the devices.
Select the device you want to retrieve a firmware dump from by entering its
number and press Enter.
Type D and press Enter to start the firmware dump for the selected device. You
will see the ongoing dump process (it takes less than 1 min). When the process
is finished a screen like the following will be shown:
IBM TotalStorage Tape Diagnostic Tool - Firmware Dump
+--------------------+ +---------------+
+--------------------+ +---------------+
+-----+ +-----+ +---------------+
+-----+ +-----+ +---------------+
+-----+ +-----+ +---------------+
+---------------------------+ Two dump files were generated:
Files: | 6811003629.001.a.gz | .a.gz - before "Force Dump"
| 6811003629.001.b.gz | .b.gz - after "Force Dump"
+---------------------------+
+---------------------------+ +--------------------+
Log: | 6811003629.022.blz | Status: | PASSED |
+---------------------------+ +--------------------+
[R] Return to Device List
Run on a tape drive the "Firmware Dump" function stores 2 dump files in the
output folder of the program (*.a.gz and *.b.gz). Both files start with the
serial number of the device. Run on a tape library or autoloader the "Firmware
Dump" function stores one Log file in the output folder of the program (*.blz).
program.
7.0 Microcode Download

======================
The Microcode Download allows to upgrade the firmware of tape drives and tape
libraries indicated in Section 1.1 "Supported Products" except the 3576/TS3310
Tape Library.
See Section 12.1.7 "3576/TS3310" to get more information on how to update the
firmware on a 3576/TS3310 Tape Library.
See Section 12.1.3 "3583 Microcode Update" to get more information on how to run
a firmware upgrade on a 3583 Ultrium Scalable Tape Library.
On Linux, also see the firmware update restriction described in Section 12.4
"Linux".
Determine the latest firmware files available from the Web site:
http://www.ibm.com/storage/lto
Download the files to the ITDT-SE input subdirectory that was created during the
installation.
Example input directory (Windows): c:\itdt\input
Example input directory (Unix): /home/user/itdt/input
Select the device you want to update by entering its number and press Enter.
Type M and press Enter to display the Firmware Update screen:
IBM TotalStorage Tape Diagnostic Tool - Firmware Update
+--------------------+ +---------------+
Model: | ULT3583-TL | Serial No: | IBM7801127 |
+--------------------+ +---------------+
+-------------------------------------------------------------+
FW Dir: | /home/balazard/test/input/ |
+-------------------------------------------------------------+
[#]
+---+-------------------------------------+-+ +------+
Content: | 0 | V3_10_04.lif |X| Dir OK: | true |
| 1 | v2_86_02.lif | | +------+
| 2 | | |
| 3 | | |
| 4 | | |
| 5 | | | [F] FW Directory
| 6 | | | [D] Dir Refresh
| 7 | | | [R] Return
| 8 | | |
| 9 | | | [C] Continue
+---+-------------------------------------+-+
7.1 Select the firmware file

----------------------------
If the firmware file you downloaded is listed in the Content field, type the
corresponding line number and press Enter.
If the firmware file is stored in an other directory than the one displayed in
FW Dir, type F followed by a space and the fully qualified path to the directory
containing the firmware file, then press Enter.
Example for changing the firmware directory (Windows): f c:\firmware
Example for changing the firmware directory (Unix): f /home/user/firmware
If no files are displayed in the Content field, check the Dir OK field on the
right side of the screen, it indicates true if the directory exists, false
otherwise.
If the content of the displayed FW Dir has changed, type D and press Enter to
refresh the directory content.
NOTE: The selected filename is reset to the first item (#0) after using the
Refresh function.
If the displayed directory contains more files than those shown, type + and
press Enter to scroll down the list. For fast down scrolling type + followed by
a space and the number of lines to scroll down then press Enter.
To scroll back, use - instead of +.
After selecting the firmware file, enter C and press Enter to continue.
7.2 Start firmware update
-------------------------
Make sure the file displayed in the FW File field is the appropriate one.
Type S and press Enter to start the firmware update, or type C and press Enter
to change the selected firmware file and proceed like described in Section
7.1 "Select the firmware file".
NOTE: The selected filename is reset to the first item when returning to that
dialog from the "Start Update" dialog.
The firmware update ususally takes 3-5 minutes, but it can take up to 45 minutes
for libraries. If you decide not to run the firmware update, type R and press
Enter to return to the Device List.
Warning! Once started, do not interrupt the firmware update.
During the firmware update the following screen will be displayed, indicating
the progress:
IBM TotalStorage Tape Diagnostic Tool - Firmware Update
+--------------------+ +---------------+
Model: | ULT3583-TL | Serial No: | IBM7801127 |
+--------------------+ +---------------+
+-----+ +-----+ +---------------+
Host: | 1 | ID: | 6 | Microcode: | 2.86 |
+-----+ +-----+ +---------------+
Bus: | 0 | LUN: | 0 | Changer: | |
+-----+ +-----+ +---------------+
+-------------------------------------------------------+
FW Dir: | /home/balazard/test/input/ |
+-------------------------------------------------------+
FW File: | V3_10_04.lif |
+-------------------------------------------------------+
+----------+ +--------------------+
Progress: |## | Status: | UPDATE FIRMWARE |
+----------+ +--------------------+
After completion the Status field on the bottom right side indicates PASSED if
the firmware was updated successfully and FAILED otherwise.
Type R and press Enter to return to the Device List.
8.0 Full Write

==============
WARNING: The full write functionality erases user data on the cartridge that
is used for the test!
The full write will take approximately 2 hours.
The full write runs only on tape drives not on autoloaders or libraries.
The full write will write the entire cartridge with varying block sizes either
with compressible or incompressible data and output performance data.
The full write test can be used to
- demonstrate that the drive is capable of writing the full amount of data on a
cartridge.
- reveal system performance bottlenecks. Run the test with incompressible data
first, then with compressible data. If you don't see a difference in overall
performance, you most probably have a bandwith limitation caused by the
system/cabling/HBA.
- identify system issues with compression. Compression will always be switched
on during the full write. When run with compressible data, the output will
show the compression rate. If that is higher than 1.0 but your system seems
not to compress data on the cartridge, check your device driver and software
settings to see if they disable compression.
To perform a full write on tape drives within a library, the library must be in
online mode.
scan.
Select the device you want to write to by entering its number and press Enter.
Type W and press Enter to start the full write.
ITDT-SE will then switch to the full write screen. If no cartridge is inserted,
If ITDT-SE detects data on the cartridge, it will show the following screen:
IBM TotalStorage Tape Diagnostic Tool - Full Write
Block Size Data Size Elapsed Data Rate
Serial No: (KB) (MB) Time (s) (MB/s)
+---------------+ +-----------+-----------+-----------+-----------+
| 1100000547 | | +---------------------------+ | |
+---------------+ | | | | |
+-+ | | Cartridge not empty! | | |
Comp./Incomp.:| | | | Overwrite data? | | |
+-+ | | | | |
| | ALL DATA ON CARTRIDGE | | |
| | WILL BE DELETED! | | |
Curr. block size: | | | | |
+----------+ | | [Y] Yes [N] No | | |
| |(KB) | +---------------------------+ | |
+----------+ +-----------+-----------+-----------+-----------+
Remaining (KB): Progress: Status:
+---------------+ +--------------------+ +-------------+
| | |############ | | MOUNT TAPE | [A] Abort
+---------------+ +--------------------+ +-------------+
< [Y] Yes | [N] No
Type Y followed by Enter to continue the test if you are absolutely sure that
data on the cartridge can be overwritten. If you are unsure, press N followed by
Enter to abort the full write.
Next select the type of data to write:
+---------------+ +-----------+-----------+-----------+-----------+
| 1100000547 +----------------------------------------+ |
+--------------| | |
+| | |
Comp./Incomp.:|| What type of data do you want | |
+| to write? | |
| | |
| [C] Compressible [I] Incompressible | |
Curr. block siz| | |
+----------+ +----------------------------------------+ |
| |(KB) | | | | |
+----------+ +-----------+-----------+-----------+-----------+
+---------------+ +--------------------+ +-------------+
| | |# | | FULL WRITE | [A] Abort
+---------------+ +--------------------+ +-------------+
<[C] Compressible | [I] Incompressible>
During the full write, the program will show a progress indicator in form of a
bar of hash marks (#) that shows the progress of a single sub-test as well as
information about that sub-test:
+---------------+ +-----------+-----------+-----------+-----------+
| 1100000547 | | 512 | 20980 | 192.625 | 108.919 |
+---------------+ | 256 | 20980 | 195.588 | 107.269 |
+-+ | 128 | 20980 | 194.464 | 107.89 |
Comp./Incomp.:|C| | 64 | 20980 | 194.418 | 107.915 |
+-+ | 32 | | | |
| 16 | | | |
| 8 | | | |
Curr. block size: | 4 | | | |
+----------+ | 2 | | | |
| 32 |(KB) | 1 | | | |
+----------+ +-----------+-----------+-----------+-----------+
+---------------+ +--------------------+ +-------------+
| 5215061 | |############### | | FULL WRITE | [A] Abort
+---------------+ +--------------------+ +-------------+
Note that you can abort the full write by pressing the A key followed by enter
at any time. Also note that it may take some time until the full write actually
aborts.
If all write operations are finished, ITDT-SE will show a screen similar to the
following:
+---------------+ +----------+----------+----------+---------+
| 1100000547 | | 512 | 20980 | 192.625 | 108.919 |
+---------------+ | 256 | 20980 | 195.588 | 107.269 |
| 128 | 20980 | 194.464 | 107.89 |
C/I: Total KB: Comp.Ratio | 64 | 20980 | 194.418 | 107.915 |
+--+----------+---------+ | 32 | 20980 | 248.693 | 84.3639 |
| C| 214842077| 85.79 | | 16 | 20980 | 375.806 | 55.8286 |
+--+----------+---------+ | 8 | 20980 | 610.141 | 34.3867 |
| 4 | 20980 | 1065.05 | 19.6994 |
+---------------+ | 2 | 20980 | 1941.42 | 10.8069 |
Result: | PASSED | | 1 | 20980 | 3733.66 | 5.61935 |
+---------------+ +----------+----------+----------+---------+
Code: Bin Log: Text Log:
+------------------+ +--------------------++--------------------+
| OK | | 1100000547.009.blz || 1100000547.007.txt |
+------------------+ +--------------------++--------------------+
It shows the performance statistics for every block size written on the
cartridge. If an error occured during the full write, data will be only written
partially.
program.
9.0 Encryption Test

===================
The encryption test is only supported on encryption enabled drives.
This test shall be used to verify if data on the cartridge was
actually written encrypted. It will read both decrypted and raw data from the
cartridge into two separate files on disk. The user can then verify that the
data differs to ensure that encryption worked.
scan.
Select the device you want to test by entering its number and press Enter.
Type E and press Enter to start the encryption test.
ITDT-SE will then switch to the following screen. You are prompted to enter the
number of the start record and amount of data (in kB) to be read:
+--------------------+ +---------------+
Model: |+---------------------------------------------+365056 |
+| |--------+
| ITDT - Encryption Verification |
+| |--------+
Host: || +-----------+ | |
+| [S] Start Record: | 0 | |--------+
Bus: || +-----------+ | |
+| |--------+
| +-----------+ |
+| [L] Data Length(kB) | 10000 | |-------------+
Progress: || +-----------+ | |
+| |-------------+
| |
+---------------------------------------------+
[A] Abort
< [Enter] OK |[S] Start Record |[L] Length |[C] Cancel >
Press S followed by a blank and the start record number, then press the Enter
key to enter the start record number. Press L followed by a blank and the data
length, then press the Enter key to enter the data length. If you entered the
values correctly, press the Enter key to start the test.
During the encryption test, the program will show a progress indicator in form
of a bar of hash marks (#) that shows the progress of a single sub-test as well
as information about that sub-test:
+--------------------+ +---------------+
Model: | 03592E05 | Serial No: | 000001365056 |
+--------------------+ +---------------+
+-----+ +-----+ +---------------+
Host: | 1 | ID: | ## | Microcode: | 1A1A |
+-----+ +-----+ +---------------+
Bus: | 0 | LUN: | ## | Changer: | |
+-----+ +-----+ +---------------+
+--------------------+ +--------------------+
Progress: |##### | Status: | ENCRYPTION VERIF. |
+--------------------+ +--------------------+
[A] Abort

Note that you can abort the encryption test by pressing the A key followed by
enter at any time. Also note that it may take some time until the encryption
test actually aborts.
If all operations are finished, ITDT-SE will show a screen similar to the
following:
+--------------------+ +---------------+
Model: | 03592E05 | Serial No: | 000001365056 |
+--------------------+ +---------------+
+-----+ +-----+ +---------------+
Host: | 1 | ID: | ## | Microcode: | 1A1A |
+-----+ +-----+ +---------------+
Bus: | 0 | LUN: | ## | Changer: | |
+-----+ +-----+ +---------------+
+--------------------+ +---------------------------+
Result: | PASSED | Code:| OK |
+--------------------+ +---------------------------+
Dumps:
+---------------------------+---------------------------+
Bin Log: | 000001365056.blz | 000001365056.ENC |
+---------------------------+ 000001365056.DEC |
Text Log: | | |
+---------------------------+---------------------------+
After completion the Status field on the bottom left side indicates PASSED if
the encrypted test completed successfully and ABORTED otherwise.
Type R and press Enter to return to the Device List.
10.0 Tape Usage
===============
The tape usage function retrieves statistical data and error counters from a
cartridge.
scan.
Select the device you want to test by entering its number and press Enter.
Type U followed by the Enter key to start the tape usage log retrieval.
ITDT-SE will then switch to the tape usage screen. If no cartridge is inserted,
During the get logs operation, the program will show a progress indicator in
form of a bar of hash marks (#) that shows the progress of a single
sub-operation as well as a description of that operation.
If all sub-operations are finished, ITDT-SE will show a screen similar to the
following:
IBM TotalStorage Tape Diagnostic Tool - Tape Usage

+--------------------+ +----------------+
+--------------------+ +----------------+
Tape Usage:
+-------------------------+-------+------------------------+-------+
| Thread Count: | 687 | Data Sets Read: | 725758|
| Data Sets Written: | 186875| Read Retries: | 6 |
| Write Retries: | 34 | Unrecovered Read Err.: | 0 |
| Unrecovered Write Err.: | 0 | Suspended Reads: | 0 |
| Suspended Writes: | 139 | Fatal Suspend Reads: | 0 |
| Fatal Suspended Writes: | 0 | | |
| | | | |
+-------------------------+-------+------------------------+-------+
+---------------+ +----------------+
Code: | OK | Result: | PASSED |
+---------------+ +----------------+
After completion the Status field on the bottom right side indicates PASSED if
the log retrieval completed successfully and ABORTED otherwise.
11.0 Manual Inspection

======================
A manual inspection record can be generated if the device does not appear in the
device list. This is intented for devices that can not be recognized or have a
technical problem which can not be determined by ITDT-SE.
To open the Manual Inspection screen, type I and press Enter.
In the next screen, type M followed by a space and the model name and press
Enter.
Example: M ULT3580-TD1
will produce the following output:
IBM TotalStorage Tape Diagnostic Tool - Manual Inspection
Please execute the SCSI or Fibre Wrap test for your drive
as described in the Service and Operator Guide for the product
and enter the result below:
+--------------------+ +---------------+
[M] Model: | ULT3580-TD1 | [N] Serial Number: | |
+--------------------+ +---------------+
+-+
[C] Single Char Display Code: | |
+-+
+-----------------------------------+
[T] Message Display Text: | |
+-----------------------------------+
[A] Additional Inspection Information:
+----------------------------------------------------------------------+
| |
+----------------------------------------------------------------------+
[S] Save Manual Inspection Results

Type N followed by a space and the serial number and press Enter.
Type C followed by a space and the code from the single character display and
press Enter.
Type T followed by a space and the content of the Message Display and press
Enter.
You can optionally type A followed by a space and an additional information text
and press Enter.
After all information has been entered, type S and press Enter to save the
data. By doing that, the information will be stored in a binary file, which can
be used for further analysis and a human readable text file. Both files will be
stored in the ITDT-SE output folder.
to
the device list, otherwise you may press Q followed by Enter to exit the
program.
12.0 Known Issues/Limitations

=============================
12.1 All operating systems

--------------------------
12.1.1 User Interface issues

If you press the arrow keys on most Unix consoles, the input will be ignored
after pressing Enter.
When the tabulator key is pressed as an input string for field data, the user
interface will be corrupted.
Make sure that field input does not start with a number followed by space and
additional text as this will be interpreted as an entry to a specific row in
the field. To avoid this, use an underscore _ instead of the space character.
12.1.2 Command Timeout

There is no instant operation termination upon SCSI command timeout, for example
when the SCSI cable is unplugged after starting POST A.
12.1.3 3583 Microcode Update

Important: When upgrading your library code from 2.6x.xxxx to 2.86.xxxx, it may
be necessary to download the firmware via serial port or RMU. Please refer to
the applicable firmware upgrade instructions.
Attention: When updating library firmware, do not power-off the 3583 library for
at least 5 minutes after the update is complete or the library may become
unusable.
12.1.4 3581-2U
Instructions for getting a scratch tape into position 1 in the 3581 2U.
The following instructions apply to the 3581 models L28/L38/L3H/F28/F38/F3H:
When using ITDT-SE to run diagnostics on IBM 3581 models
L28/L38/L3H/F28/F38/F3H, you must export any cartridge that is currently in
slot 1 and then import a scratch (empty) cartridge into slot 1. The diagnostics
will overwrite any data that is on the cartridge so be sure to use a cartridge
that does not contain data.
To export a cartridge from slot 1 using the OCP:
Press any button (Cancel, Previous, Next, or Enter) on the OCP to display
the Information Menu screen.
Press Next to display the Commands Menu screen.
Press Enter then Next or Previous, as necessary, until EXPORT is displayed.
Press Enter to display the EXPORT FROM: screen.
Use the Next and Previous buttons as necessary to select slot 1. Note: if
slot 1 is not available for selection then it is already empty - only slots
containing cartridges are available for selection.
Press Enter to initiate the export.
When the I/O Door opens, remove the cartridge.
Press Enter.
Press Cancel to return to the EXPORT screen.
Press Cancel. The library will re-inventory all cartridges and then return
to the Home Screen.
To import a cartridge to slot 1 using the OCP:
Press any button (Cancel, Previous, Next, or Enter) on the OCP to display the
Information Menu screen.
Press Next to display the Commands Menu screen.
Press Enter then Next to access IMPORT.
Press Enter to display the IMPORT TO: screen.
Use the Next and Previous buttons as necessary to select slot 1. Note: if
slot 1 is not available for selection then it already has a cartridge
loaded - only slots that are empty are available for selection.
Press Enter to initiate the import.
When the I/O Door opens, insert the scratch (empty) cartridge. The Autoloader
will import the cartridge, close the I/O Door, and insert the cartridge into
the selected slot.
When the cartridge has been inserted into its slot, press Cancel to return to
the IMPORT screen.
Press Cancel. The library will re-inventory all cartridges and then return to
the Home Screen.
12.1.5 3581
The 3581 may cause a SCSI command timeout when a (second) microcode update is
performed on the same machine.
12.1.6 3582
The 3582 incorrectly reports ready state directly after a tape is inserted while
CM is still being read, so that an immediately following medium movement may
fail. To avoid this, press "OK" in the Insert Tape dialog only after waiting
some additional seconds.
When testing a tape drive inside a 3582 library, ITDT-SE asks to put a cartridge
in the topmost I/O station. Please insert the cartridge into the I/O station on
the right side.
12.1.7 3576/TS3310
Library Microcode download using ITDT-SE is not supported with the 3576/TS3310.
Please update the Firmware using the 3576/TS3310 Web User Interface.
12.1.8 3592/TS1120
For drives in a 3494 or STK silo library, the [T] option will not work as in
these environments the library will not unmount the cartridge when it is
unloaded by the drive.
12.2 Windows
------------
After a firmware update, devices may disappear from the bus. This is a known
Windows problem. (Article # Q812024,
http://support.microsoft.com/default.aspx?scid=kb;en-us;812024).
Repeated Scan operations may help to rediscover the device.
When switching applications on Windows while ITDT-SE is running, an extra ESC
character may appear on the input line and the input will be ignored after you
press the Enter key.
12.3 AIX
--------
Rescan may take very long (6-10 minutes), depending on the number of host
adapters and devices attached.
Scan limitations:
- 20 host adapters
- SCSI ID: 0-15, LUN: 0 and 1
- FCP ID: only devices that have the device state "available"
- 256 devices overall
For FC devices, the ID and LUN will not be displayed as they are too long for
display (can be up to 20 characters).
When logged in via telnet, backspace may not be working - will insert an escape
sequence instead and the input will be ignored after Enter is pressed.
12.4 Linux
----------
ITDT-SE on Linux requires glibc 2.2.5 or later.
When using an Emulex FC-AL host adapter, Microcode update may not work due to
an issue with the transfer size. In this case, use other tools to perform a
microcode update under Linux / Emulex.
Scan limitations:
- 2 channels per host adapter. Devices attached on more than 2 channels will
be detected if they were already attached at boot time.
- SCSI/FCP: ID 0-255, LUN: no restriction, but active device detection only
for LUN 0 and 1
- 256 devices overall
12.4.1 Linux on pSeries

When using an IBM branded Emulex FC-AL host adapter, Microcode update may not
work due to an issue with the transfer size. In this case, use other tools to
perform a microcode update under Linux / Emulex.
12.4.2 Linux on zSeries

SUSE SLES9 requires that the kernel update SUSE-SA:2007:035 is installed.
12.5 Solaris
------------
Rescan may take very long (6-8 minutes), depending on the numbers of host
adapters and devices attached.
Scan limitations:
- SCSI ID 0-255, LUN 0-10
The SUN X6768 FC-AL host adapter is not supported with this release.
Devices attached to this host adapter will not be recognized by ITDT-SE.
12.6 HP-UX
----------
Please verify that you have the following patches installed before you are going
to start ITDT-SE.
12.6.1 PA-Risc
--------------
ITDT-SE on HP-UX PA-Risc requires at least these two operating system patches:
- ld and linker tools cumulative patch
- libc cumulative patch
12.6.2 Itanium/IA-64
--------------------
ITDT-SE on HP-UX Itanium requires all regular patches and the following patches:
PHCO_33742 1.0 or later VxVM 3.5~IA.014 Command Patch 03
PHKL_33743 1.0 or later VxVM 3.5~IA.014 Kernel Cumulative Patch 03
PHSS_32502 1.0 or later Aries cumulative patch
PHSS_33349 1.0 or later linker + fdp cumulative patch
Note: ITDT-SE is emulated by Aries (a binary emulator that transparently
emulates 32-bit and 64-bit HP-UX PA-RISC applications on HP-UX IA-64 machines).
12.7 i5/OS
----------
ITDT-SE on i5/OS supports only tape drives, no autoloaders and no libraries.
Media changers and media changer operations are not supported with this ITDT-SE
release. To test a tape drive inside a library, the cartridge must be imported
manually before starting the Device Test.
ITDT-SE on i5/OS V5R4 requires the following PTF to be installed:
PTF Release Abstract
SI25023 540 OSP-MEDIA-TAPE-THREADS-MSGCEE0200-T/QTAHRMGR QTARDCAP FAILS

Readme

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Readme

Hochgeladen von

Copyright:

Verfügbare Formate

IBM TotalStorage Tape Diagnostic Tool Standard Edition README

1.3 Screen Size

2.0 Installation & Initial Startup

2.4 All other supported operating systems

3.0 General Program Navigation

<[H] Help | [Q] Quit | Command > s

5.0 Test Device

< [Y] Yes | [N] No

6.0 Firmware Dump

7.0 Microcode Download

7.1 Select the firmware file

8.0 Full Write

9.0 Encryption Test

<[Q] Quit | Command >

IBM TotalStorage Tape Diagnostic Tool - Tape Usage

11.0 Manual Inspection

<[H] Help | [Q] Quit | Command >

12.0 Known Issues/Limitations

12.1 All operating systems

12.1.1 User Interface issues

12.1.2 Command Timeout

12.1.3 3583 Microcode Update

12.4.1 Linux on pSeries

12.4.2 Linux on zSeries

Das könnte Ihnen auch gefallen