HP LTO 4 SAS Cleaning cartridge HP-configured or Universal, Non-HP Ultrium 1 cleaning cartridge

Page 47

Cleaning cartridge (HP-configured or Universal)

When a valid cleaning cartridge (one that has not expired) is loaded, behavior depends on the Clean Protect bit of the Set Drive Configuration command.

Clean Protect = 1 f the Clean Protect bit is set to 1, the drive will not thread the tape or clean the drive until an ACI Load command with the Clean bit set to 1 is sent to the drive. If the Load command is sent without the Clean bit set the drive will return a CHECK CONDITION. Also, if the “cleaning cartridge” is not in fact a cleaning cartridge, the Load command with the Clean bit set to 1 will produce a CHECK

CONDITION.

Clean Protect = 0 If the Clean Protect bit in the Set Drive Configuration command is set to 0, the drive will thread the tape and clean the drive when a cleaning tape is loaded.

When the cleaning cartridge is seated in the drive, the ‘cartridge type’ field in the Get Drive Status RDATA will be set to 06h (cleaning).

While the drive is cleaning, the Cleaning bit in the Get Drive Status RDATA will be set to 1 and the Tape Activity field will be set to Ah (cleaning).

When cleaning has finished, if Auto-Eject is disabled, the cartridge will be in the ready eject position with the Cartridge Present, Write Protect, Ready Eject, and Ready Load bits set to 1, Cartridge Type = ‘Cleaning’, and

Tape Activity = ‘Idle’. The cartridge can now be unloaded from the drive.

Expired cleaning cartridge (HP-configured or Universal)

If an expired cleaning cartridge is loaded into the drive, the cartridge will be placed in the ready eject position with the Cartridge Present, Write Protect, Ready Eject, Ready Load, Media Error, TapeAlert, and Clean Expired bits set to 1, Cartridge Type = ‘Cleaning’, and Tape Activity = ‘Idle’. TapeAlert flag 22h will be set.

Non-HP Ultrium 1 cleaning cartridge

If a non-HP Ultrium 1 cleaning cartridge is loaded into the drive, the cartridge will not be recognized as a supported cartridge. The cartridge will be placed in the ready eject position with the Cartridge Present, Write Protect, Ready Eject, Ready Load, Media Error, and TapeAlert bits set to 1, Cartridge Type = ‘Unknown’, and Tape Activity = ‘Idle’. TapeAlert flag 17h will be set.

Unreadable data cartridge

If a data cartridge is loaded that cannot be read, the cartridge will be placed at the ready-to-eject position with the Cartridge Present, Write Protect, Ready Eject, Ready Load, Media Error, and TapeAlert bits set to 1, Cartridge Type = ‘Unknown’, and Tape Activity = ‘Idle’. TapeAlert flag 05h will be set.

Ultrium 5 and later data cartridges

If an Ultrium 5 or later data cartridge is loaded into the drive, the drive will recognize the cartridge as a non-supported cartridge. The cartridge will be placed at the ready-to-eject position with the Cartridge Present, Write Protect, Ready Eject, Ready Load, Media Error, and TapeAlert bits set to 1, Cartridge Type = ‘Unknown’, and Tape Activity = ‘Idle’. TapeAlert flag 0Ch will be set.

HP LTO Ultrium 4 drives technical reference manual, volume 2: software integration 47 HP restricted

Page 46 Page 48
Image 47
Page 46 Page 48
Contents HP restricted volume 2 software integrationLTO 4 FC, SCSI and SAS drives HP LTO Ultrium tape drives technical reference manualLegal and notice information 3 Use of tapes Contents1 Designing backup applications 2 Configuration and initialization4 Factors affecting performance 5 Supporting Ultrium features7 Exception handling 6 Sense keys and codesHP restricted Drives-general Related documentsDocumentation map Documents specific to HP Ultrium drivesInterface Installation and configurationOperation CartridgesDealing with errors Maintenance and troubleshootingGeneral documents and standardization LTO Ultrium featuresLarge data transfer size 1 Designing backup applicationsNon-immediate commands Optimizing performanceMonitoring tape use Cleaning tape headsManaging the use of tapes Information in Cartridge MemoryDisplaying drive information Design goals for LTO backup applicationsDiagnostic logs TapeAlertInclude the capability to download firmware Operating system drivers 2 Configuration and initializationInquiry string recovery SCSI protocol, regardless of transport or interface type Example16 Configuration and initialization Supporting additional LUNs Support for additional LUNEnabling additional LUN support 18 Configuration and initialization LTO cartridge memory Using Cartridge Memory attributesUsing MODE SENSE 3 Use of tapesInterpreting Log Sense data Tape status and capacityFinding the remaining capacity CDB fields Using the SET CAPACITY commandCommand descriptor block New additional sense codes and TapeAlert flags Changes to SCSI commandsWORM media How WORM media worksRe-writing media labels Error Usage pageERASE commands rejected SET CAPACITY commandUnique media identifier Using CM to check tape integrityBehavior with a missing or inconsistent EOD value Barcode support Responding to Cartridge Memory dataLoad count Corrective action RWW retry countsEnsuring the recommended minimum transfer sizes 4 Factors affecting performanceWays of optimizing performance Detecting the drive’s speedMedia type identification Using Cartridge Memory instead of tape headersUsing the Performance Log page for diagnosing problems Time-out valuesHost-related factors Recommended support of log pagesFactors affecting performance makes sense to split heavily used FC cards across separate PCI busses ExampleRecommendation where possible or a reasonably sized RAID system. More disks meansDo not interleave write commands with other commands, such as READ Drive-related factorsFormat-related factors Page 34 Factors affecting performance Further information 5 Supporting Ultrium featuresCartridge Memory LTO-CM Automation interfaceAutomation/Device Interface ADI Slave to a library controller Automation Control Interface ACIModes of usage through ACI SCSI pass-through mode ACI command setACI commands that affect drive streaming performance Backward compatibility New features in ACISCSI command Encryption support 42 Supporting Ultrium features Further detailsSupporting the ACI protocol Recommended ACI time-out valuesTreatment of reserved fields Recommended power-up sequenceRecommended load-unload configuration Upgrading the drive firmware Firmware upgrade via tapeRecommended Get Drive Status polling frequency ACI protocol communications retryHandling irregular cartridges Firmware upgrade via the primary host interfaceFirmware upgrade via ACI Library firmware upgrade via tapeUnreadable data cartridge Cleaning cartridge HP-configured or UniversalExpired cleaning cartridge HP-configured or Universal Non-HP Ultrium 1 cleaning cartridgeCartridge cannot be loaded Valid firmware upgrade cartridgeData cartridge with unreadable CM Cartridge fails to seat or loadIs there separate firmware for drives intended to go into libraries? Frequently asked questionsCleaning Invalid firmware upgrade cartridgeResetting using the ACIRSTL line Backup softwareResetting drives Resetting via the ACI Reset commandBuffer size at EW-EOM Accessing Cartridge Memory without threading the tapeControlling data compression Other mode page information52 Supporting Ultrium features Rewind on resetWrite delay time Partition sizeConsole Message 6 Sense keys and codesSense keys-actions to take Actionerror to the calling application “3h-MEDIUM ERROR” on page 62 . Also see the Media AccessFor additional sense codes, see “3h-MEDIUM ERROR” on log the error, terminate I/O to the drive, and pass the appropriateConsole Message ActionConsole Message Actionpage reached, unable to fit Additional sense codes-actions to takePhysical End-of-Tape0h-NO SENSE 2h-NOT READY 1h-RECOVERED ERROR60 Sense keys and codes The software must issue a LOAD before media accessLUN not accessible, port in The command cannot be executed because the specifiedmechanism tests are being executed. When the tests are 62 Sense keys and codes 3h-MEDIUM ERRORA READ , SPACE , WRITE or WRITE FILEMARKS command and the drive. Based on this, ask the user to clean the Send a console message that an unrecovered error on64 Sense keys and codes Send a message to the console indicating that there is 66 Sense keys and codes The current command such as READ, SPACE, REWIND4h-HW ERROR 68 Sense keys and codes 5h-ILLEGAL REQUESTA MODE SELECT parameter list sent to the drive contains 32 initiators to register, using PERSISTENT RESERVE OUT 6h-UNIT ATTENTIONpersistent reservation using the PERSISTENT RESERVE OUT allowed to execute. In other words, some commands canAction A SET DEVICE IDENTIFIER command has been successful service action removed all reservations and the persistentA PERSISTENT RESERVE OUT command was executed WRITE BUFFER or MAINTENANCE OUT command7h-DATA PROTECTION Action 8h-BLANK CHECK related to a missing EOD data set. The most likely cause Bh-ABORTED COMMANDREAD BUFFER command 76 Sense keys and codes Dh-VOLUME OVERFLOWA WRITE or WRITE FILEMARKS command has encountered 4. Allow the user to reset devices Typical escalation procedure1. Retrieve fault information 3. Allow the user to try recoverySupporting TapeAlert Monitoring the condition of the drive and mediaType FlagsPage Page Page Page Page Page Page TapeAlert models Designing software to use the TapeAlert logTapeAlert informational exception usage model Reading the TapeAlert logTapeAlert polling usage model Supporting OBDR One-Button Disaster Recovery OBDRResponding to the ‘Clean’ LED Requirements for drivers and logical device managers Providing pass-through modeGlossary see ”read-while-write” Index Page Page HP restricted
Top Page Image Contents