User's Manual

In these file names, YYYYMMDDhhmmss is the date and time OK was clicked. After a reboot there
also will be two files in the specified location:
• tapeapfousbf_YYYYMMDDhhmmss.bin.NNN
• tapeapfompic_YYYYMMDDhhmmss.bin.NNN
In addition to the date and time, in these file names NNNN will be a number from 1 - 16. The
File Size Limit value constrains the size of the log files and if the size limit is reached, the oldest
log entries are replaced with the new log entries. If 0 is specified as the file size, the log files can
become quite large and potentially fill up a hard drive. When Restart is selected and OK is clicked,
any existing log files are closed and new files are created with updated date and time. Each of
the files created after a restart or reboot can grow to the specified size. Before sending the log
files to HP, run the application, open the enable logging dialog, deselect Enable or select Restart
and then click OK to ensure the files have been completely written to disk.
Diagnostic dumps
There are two different diagnostic dump logs which can be saved and sent to HP for analysis. The
first is the standard Windows kernel dump which can be saved when a bug check (“blue screen”)
occurs. The other is a Driver Debug Log generated by a debug version of the advanced path
failover drivers. The debug version of the advanced path failover drivers is designated by a ‘d’ at
the end of the driver name (e.g., hpadvfox64d.exe) and will be provided by HP support if drive
debug logs are required. Debug logs can provide information on failover operations and whether
or not a bug check has occurred.
Memory dump setup
To configure Windows to produce a memory dump, see http://support.microsoft.com/kb/254649.
The configuration process includes specifying the name and location for the dump file, as well as
the type of the dump. The type should be a kernel memory dump, although the larger complete
memory dump is acceptable. Do not select the small memory dump. If a bug check occurs, then
after a reboot the file can be retrieved and sent for diagnosis.
Driver debug dump setup
Generating a driver debug dump log file requires installing checked drivers and the DebugView
application. This is an advanced technique. For instructions, see “Windows driver debug dump
setup” (page 66).
Bug checks
Following a bug check, restart the system and retrieve the kernel dump for transmission to HP. If
driver debug dumps were enabled, then retrieve the driver debug log file for transmission to HP.
Hangs
If the system hangs, the system can be configured to allow forcing a system crash from the keyboard.
This is explained in http://msdn.microsoft.com/en-us/library/ff545499(v=VS.85).aspx.
If the system hangs after configuring, force the crash and reboot. Then retrieve the kernel dump
for transmission to HP.
Linux logs and troubleshooting tools
Report cached reservation information
The Linux advanced path failover driver tracks reservation information for tape libraries to enable
rebuilding the reservations if a failure requires changing the drive that is hosting the library control
path. These commands dump the reservation information cache buffers to the /var/log/messages
file and the console.
Linux logs and troubleshooting tools 61