Using Hp Library & Tape Tools To Diagnose Problems - HP BL536A User's & Service Manual

Table 38 Informational events (continued)
Value Informational event
0x03 Drive clean
0x04 Mailslot open
0x05 Mailslot close
0x06 Magazine remove
0x07 Magazine reinsertion
0x08 Power on
0x09 Power off
0x0A User login
0x0B User logout
0x0C System test run
0x0D Wellness test run
0x0E Bus reset occurred
0x0F Device reset
0x10 Abort
0x1 1 Drive tape alert flag
0x12 Power on init done
0x13 Incorrect key server token PIN entered
0x14 Backup initiated on key server token
0x15 Backup off key server token finished
0x16 A new write key was automatically generated on
the key server token.
0x17 A new write key was manually generated on the
key server token.
0x18 More than 5 invalid key server token PIN attempts
0x19 Restore initiated on key server token
0x1A Restore off key server token finished
0x1B Key server token is over 90% full
0x1C Key server token contains keys that have not been
backed up.
Using HP Library & Tape Tools to diagnose problems
With HP Library & Tape Tools installed on the host server you can:
Identify all parallel SCSI devices connected to your system.
View detailed configuration, identification, inventory, and drive information for the device.
Easily update device and drive firmware.
Run advanced diagnostic tests, including connectivity, read/write, media validation, and
testing the functionality of the device.
128 Troubleshooting
Description
Drive cleaning process
Open mailslot command
Close mailslot
Magazine remove event
Magazine insertion event
Power on event
Power off event
User login at interface (RMU, OCP, SERIAL)
User logout at interface (RMU, OCP, SERIAL)
System test run
The wellness test was run
A bus reset occurred
Device reset command
SCSI task aborted
Drive reported informational tape alert flag
Power on init completed successful
Incorrect key server token PIN entered
Incorrect key server token PIN entered
The backup of the key server token has finished.
A new write key was automatically generated on the
key server token.
A new write key was manually generated on the key
server token.
More than five attempts were made to set the key
server token with invalid PINs.
A restore operation was initiated on the key server
token.
A restore operation was completed on the key server
token.
The key server token is over 90% full.
The key server token contains keys that have not been
backed up.