Page 16
Product ID, first 8 bytes
“Ultrium ” This will be the same for all HP Ultrium products, regardless of generation or model.
Product ID, last 8 bytes
1st byte: | Generation identifier: |
| “4” | LTO 4 (1600 GB at 2:1 compression) |
2nd byte | “–” Hyphen separator (ASCII 2Dh) |
3rd–6th bytes | “SCSI” | SCSI protocol, regardless of transport or interface type |
Product Revision Level | | |
1st byte | Product codename ID: |
| “A” | LTO 4 SAS full-height drive |
| “B” | LTO 4 SCSI full-height drive |
| “H” | LTO 4 FC full-height drive |
2nd byte | Release type: | |
| “0”, “1” | Development |
| “2” | Formal release |
| “3”, ... | Post-release |
3rd byte | Minor release level: “0”–“9”, then “A” –”Z” |
4th byte | Firmware variant: |
| “D” | Standard distribution firmware |
| “W” | Standard HP automation firmware |
Example
If new drive families or variants support features that are not available in previous generation products, you can detect the existence of these features through the SCSI MODE SENSE and LOG SENSE commands. Exact details will become available as new products are defined. There is no need to limit driver or application connectivity to a single HP Ultrium product type.
To determine the drive technology family:
Examine only the first eight bytes of the Product ID field (the text “Ultrium ”).
To determine the Ultrium format generation:
Use one of the following two methods, of which the second is preferred:
•Examine the character in byte 9. A “4” indicates format LTO 4 (1600 GB capacity at 2:1 compression) and so on.
•Preferred method: Use the SCSI REPORT DENSITY SUPPORT command.
For an LTO 4 product with LTO Ultrium 4 media, the following will be returned:
Primary Density Code: | 46h | |
Assigning Organization: | LTO-CVE | Linear Tape Open Compliance and Verification Entity |
Density Name: | U-416 | 16 track |
16 Configuration and initialization
HP restricted
Contents
volume 2 software integration
LTO 4 FC, SCSI and SAS drives
HP LTO Ultrium tape drives technical reference manual
HP restricted
Legal and notice information
Contents
1 Designing backup applications
2 Configuration and initialization
3 Use of tapes
5 Supporting Ultrium features
4 Factors affecting performance
6 Sense keys and codes
7 Exception handling
HP restricted
Related documents
Documentation map
Documents specific to HP Ultrium drives
Drives-general
Installation and configuration
Operation
Cartridges
Interface
Maintenance and troubleshooting
Dealing with errors
LTO Ultrium features
General documents and standardization
1 Designing backup applications
Non-immediate commands
Optimizing performance
Large data transfer size
Cleaning tape heads
Managing the use of tapes
Information in Cartridge Memory
Monitoring tape use
Design goals for LTO backup applications
Diagnostic logs
TapeAlert
Displaying drive information
Include the capability to download firmware
Inquiry string recovery
2 Configuration and initialization
Operating system drivers
16 Configuration and initialization
Example
SCSI protocol, regardless of transport or interface type
Enabling additional LUN support
Support for additional LUN
Supporting additional LUNs
18 Configuration and initialization
Using Cartridge Memory attributes
Using MODE SENSE
3 Use of tapes
LTO cartridge memory
Finding the remaining capacity
Tape status and capacity
Interpreting Log Sense data
Command descriptor block
Using the SET CAPACITY command
CDB fields
Changes to SCSI commands
WORM media
How WORM media works
New additional sense codes and TapeAlert flags
Error Usage page
ERASE commands rejected
SET CAPACITY command
Re-writing media labels
Behavior with a missing or inconsistent EOD value
Using CM to check tape integrity
Unique media identifier
Load count
Responding to Cartridge Memory data
Barcode support
RWW retry counts
Corrective action
4 Factors affecting performance
Ways of optimizing performance
Detecting the drive’s speed
Ensuring the recommended minimum transfer sizes
Using Cartridge Memory instead of tape headers
Using the Performance Log page for diagnosing problems
Time-out values
Media type identification
Factors affecting performance
Recommended support of log pages
Host-related factors
Example
Recommendation
where possible or a reasonably sized RAID system. More disks means
makes sense to split heavily used FC cards across separate PCI busses
Drive-related factors
Do not interleave write commands with other commands, such as READ
Format-related factors
Page
34 Factors affecting performance
5 Supporting Ultrium features
Cartridge Memory LTO-CM
Automation interface
Further information
Automation/Device Interface ADI
Modes of usage through ACI
Automation Control Interface ACI
Slave to a library controller
ACI commands that affect drive streaming performance
ACI command set
SCSI pass-through mode
New features in ACI
Backward compatibility
SCSI command
Encryption support
Further details
Supporting the ACI protocol
Recommended ACI time-out values
42 Supporting Ultrium features
Recommended power-up sequence
Treatment of reserved fields
Recommended load-unload configuration
Firmware upgrade via tape
Recommended Get Drive Status polling frequency
ACI protocol communications retry
Upgrading the drive firmware
Firmware upgrade via the primary host interface
Firmware upgrade via ACI
Library firmware upgrade via tape
Handling irregular cartridges
Cleaning cartridge HP-configured or Universal
Expired cleaning cartridge HP-configured or Universal
Non-HP Ultrium 1 cleaning cartridge
Unreadable data cartridge
Valid firmware upgrade cartridge
Data cartridge with unreadable CM
Cartridge fails to seat or load
Cartridge cannot be loaded
Frequently asked questions
Cleaning
Invalid firmware upgrade cartridge
Is there separate firmware for drives intended to go into libraries?
Backup software
Resetting drives
Resetting via the ACI Reset command
Resetting using the ACIRSTL line
Accessing Cartridge Memory without threading the tape
Controlling data compression
Other mode page information
Buffer size at EW-EOM
Rewind on reset
Write delay time
Partition size
52 Supporting Ultrium features
6 Sense keys and codes
Sense keys-actions to take
Action
Console Message
“3h-MEDIUM ERROR” on page 62 . Also see the Media Access
For additional sense codes, see “3h-MEDIUM ERROR” on
log the error, terminate I/O to the drive, and pass the appropriate
error to the calling application
Action
Console Message
Action
Console Message
page
Additional sense codes-actions to take
Physical
End-of-Tape
reached, unable to fit
0h-NO SENSE
1h-RECOVERED ERROR
2h-NOT READY
The software must issue a LOAD before media access
LUN not accessible, port in
The command cannot be executed because the specified
60 Sense keys and codes
mechanism tests are being executed. When the tests are
A READ , SPACE , WRITE or WRITE FILEMARKS command
3h-MEDIUM ERROR
62 Sense keys and codes
Send a console message that an unrecovered error on
and the drive. Based on this, ask the user to clean the
64 Sense keys and codes
Send a message to the console indicating that there is
The current command such as READ, SPACE, REWIND
66 Sense keys and codes
4h-HW ERROR
A MODE SELECT parameter list sent to the drive contains
5h-ILLEGAL REQUEST
68 Sense keys and codes
6h-UNIT ATTENTION
persistent reservation using the PERSISTENT RESERVE OUT
allowed to execute. In other words, some commands can
32 initiators to register, using PERSISTENT RESERVE OUT
Action
service action removed all reservations and the persistent
A PERSISTENT RESERVE OUT command was executed
WRITE BUFFER or MAINTENANCE OUT command
A SET DEVICE IDENTIFIER command has been successful
7h-DATA PROTECTION
Code
8h-BLANK CHECK
READ BUFFER command
Bh-ABORTED COMMAND
related to a missing EOD data set. The most likely cause
A WRITE or WRITE FILEMARKS command has encountered
Dh-VOLUME OVERFLOW
76 Sense keys and codes
Typical escalation procedure
1. Retrieve fault information
3. Allow the user to try recovery
4. Allow the user to reset devices
Monitoring the condition of the drive and media
Supporting TapeAlert
Flags
Type
Page
Page
Page
Page
Page
Page
Page
Designing software to use the TapeAlert log
TapeAlert models
TapeAlert polling usage model
Reading the TapeAlert log
TapeAlert informational exception usage model
Responding to the ‘Clean’ LED
One-Button Disaster Recovery OBDR
Supporting OBDR
Providing pass-through mode
Requirements for drivers and logical device managers
Glossary
see ”read-while-write”
Index
Page
Page
HP restricted