Run the support_infoscript, located in the/opt/OMImag/bindirectory for the static driver and in /opt/atdd/binfor the DLKM driver. This script gathers important system and configuration information. There are several sections with the keyword VERIFY, indicating information that should be verified for correctness.
Log in as userid ″root″on the system which experienced a problem. Then run the script and redirect the output to an end of a file:
Static:
/opt/OMImag/bin/support_info > support_info.out DLKM
/opt/atdd/bin/support_info > support_info.out
Tracing Facility
Running the ATDD_trace utility, located in the /opt/OMImag/binfor the static driver and in /opt/atdd/binfor the DLKM driver, displays debug information. The utility traces can be started at any time before an operation on a tape device. The default debug level is 0x00001003, which shows driver configuration and per instance drive attribute configuration and errors. You can increase the amount of debug information displayed by enabling more trace flags. Issuingatdd_trace -f 0x1fffffff turns on every trace.
Enter the following commands to start the trace:
1. First, determine which items need to be traced and set the trace flags using the atdd_trace command. For example, to trace everything:
For the Static driver:/opt/OMImag/bin/atdd_trace -f 0x1fffffff
For the DLKM driver:/opt/atdd/bin/atdd_trace -f 0x1fffffff
In HP-UX 11iv3, run thesam utility or# kctune atdd_trace_level=1command to set the trace level to 1. The default set is 3.
The set of trace flags is displayed in Table 13.
Table 13. Trace Flags
COMMAND VALUE
Configuration 0x00000001
General errors 0x00000002
Routine entry points 0x00000004
Returns 0x00000008
TRACE_DBG information 0x00000010
Open/Close routine 0x00000020
Trace motion commands 0x00000040
Read/Write 0x00000100
Strategy 0x00000200
Open/Close states 0x00000400
IOCTLs 0x00000800
Trace device config routines 0x00001000 Trace SCSI level stuff 0x00004000
Configuration 0x10000000
Entry point 0x01000000
General information 0x00400000
Memory 0x00200000
2. Clear the trace buffer:
For the Static driver:/opt/OMImag/bin/atdd_trace -c
For the DLKM driver:/opt/atdd/bin/atdd_trace -c
3. To have trace data displayed immediately in a readable format as it is collected: For the Static driver:/opt/OMImag/bin/atdd_trace -b
For the DLKM driver:/opt/atdd/bin/atdd_trace -b
4. Start the operations on a tape device.
5. To display collected trace data in a readable format at any time: For the Static driver:/opt/OMImag/bin/atdd_trace -d
For the DLKM driver:/opt/atdd/bin/atdd_trace -d
6. The atdd_trace output can be redirected to place the trace data in a readable format into a file, by entering:
For the PB driver:/opt/OMImag/bin/atdd_trace >trace.txt
For the PCI driver:/opt/atdd/bin/atdd_trace >trace.txt
7. In HP-UX 11i v3, the ATDD trace is logged into syslog of /var/adm/syslog/ syslog.log once the kernel tunable of atdd_direct_trace is enabled. To set a value (0 or 1) to atdd_direct_trace, run# kctune atdd_direct_trace=value.
Atdd_d Log Daemon
The device driver provides a log daemon (atdd_d) facility for the Enterprise Tape System 359x to automatically store drive dumps, to retrieve and store SIM/MIM (Service and Media Information Messages) data, and to log error messages into the /var/adm/atdddirectory. Theatdd_dlog daemon is not automatically started in 11.0, 11i v1 and v2 but not in 11i v3, when the driver is installed.
The following steps document how to start and configure the daemon:
1. Start the daemon by running: For the Static driver:
#/opt/OMImag/bin/atdd_d For the DLKM driver: #/opt/atdd/bin/atdd_d
2. Check whether the daemon is running by entering: #ps -ef | grep atdd_d
3. To view and/or modify the settings for the daemon, enter: For the Static driver:
# /opt/OMImag/bin/atdd_d -h usage: atdd_d [options] For the DLKM driver: # /opt/atdd/bin/atdd_d -h usage: atdd_d [options]
[-d <log directory>] default is /var/adm/atdd
[-n <maximum number of dumps>] default is 10 [-z <maximum size of a dump>] default is 1048576 [-s <maximum size of a log>] default is 100000
For example, to decrease the number of drive dumps to store from 10 to 6 and change the log directory to/tmp/drive_dump, do the following:
For the Static driver:
#/opt/OMImag/bin/atdd_d -n 6 -d/tmp/drive_dump For the DLKM driver:
#/opt/atdd/bin/atdd_d -n 6 -d/tmp/drive_dump
4. View theatdd_d.log, which provides information about the daemon start time, message type (1 for the drive dump, 2 for SIM/MIM data, and 3 for Error message), time stamp, H/W path, and size. Refer to an example in Figure 10 on page 89.
Note: No entry is made in the log file when the daemon stops. Run #ps -ef | grepatdd_dto check if the daemon is stopped.
5. Stop the daemon by using the following commands: Get the daemon process id: #ps -ef | grep atdd_d kill the daemon process: #kill -9 process_id
Problems and Solutions
Table 14 describes problems and possible solutions for errors you may encounter with the DLKM driver.
Table 14. Problems, Reasons, and Solutions
Problem Reason and Solution
The system hangs running rmsf -H on HP-UX 11i. DLKM Infrastructure does not set the correct flag in the device switch table entry for a DLKM driver that uses. Install HP patch PHKL_29818
ATDD DLKM modules are not loaded in the running kernel.
A message in the file/var/adm/syslog/syslog.log
″vmunix: WARNING: modpath: DLKM is not initialized″
The current kernel is not matching the symbol table (DLKM) in/stand/dlkm
Need to rebuild the kernel by running the following commands: #cd /stand/build #/usr/lbin/sysadm/system_prep -s /stand/build/system #/usr/sbin/mk_kernel -s /stand/build/system #mv /stand/system /stand/system.prev #mv /stand/build/system /stand/system #kmupdate /stand/build/vmunix_test #shutdown -ry now
A message in the file/var/adm/syslog/syslog.log
″modld: Attempt to load unregistered module″
ATDD DLKM Module’s component files are not copied to certain subdirectories of/usr/confand/stand
Remove ATDD and try to install it again.
Table 14. Problems, Reasons, and Solutions (continued)
Problem Reason and Solution
# kmtune | grep atdd
kmtune: Cannot open file -- /stand/.kmsystune_lock
The file .kmsystune_lock was removed manually. Use the following command to create the .kmsystune_lock file again:
# touch /stand/.kmsystune_lock
IBM tape devices not claimed in ioscan -fnk display As″root″, verify the drivers loaded in the running kernel using`kmadmin -s`
If status is″LOADED″
then run'atdd_claim -b' to claim all IBM devices, then run 'atdd_claim -t'to claim the tape drives, then run'atdd_claim -c'to claim the changers. If status is″UNLOADED″
then run'kmadmin -L atdd'to load the ATDD, then run 'kmadmin -L acdd'to load the ACDD, then run'atdd_claim'to claim the tape devices.
If status is still″UNLOADED″, then check the entries of the files ’atdd’ and/or ’acdd’ in/etc/loadmods
If no atdd and/or acdd file entries exist, the driver may be statically bound to the kernel or the ATDD package may not be installed. Check the installation running the following command:
# swlist atdd
No special files found in/dev/rmt Execute the atdd_mksf and acdd (if you have changers managed by the acdd driver) scripts found in
/opt/atdd/bin
atdd_mksf and acdd_mksf
Note: The script prints out the commands that are necessary to create the special files. To create the files you must″pipe″the output to shell (sh), using the following commands:
atdd_mksf | sh acdd_mksf | sh
The special files for a device are duplicates. Remove all of the special files for the device in/dev/rmt Create the special files again by running the commands
atdd_mksforacdd_mksf
No special files are created by HP Stape and Schgr after installing ATDD
Create the special files by running the command:
# insf -e
Cannot open Special File and the system log has the following message:
Invalid SCSI request in data at bit 7 of byte 4
Wrong DENSITY setting. Check the current value by running the command:
atdd_cfg -g DENSITY
Try setting value to 0 (zero) by running the command:
atdd_cfg -s DENSITY 0
An attempt to read data times out and returns an error and the system log has the following messages: A SCSI command timed out and was aborted.
Make sure the SILI configuration parameter is″1″. This can be checked by running the command:
atdd_cfg -g SILI
If the value of SILI = 0, try setting the value to 1, by running the following command: atdd_cfg -s SILI 1
Table 15 on page 91 describes problems and possible solutions for errors you may encounter with the static driver.
Table 15. Troubleshooting (Problems and Solutions)
Problem Solution
No special files found in/dev/rmt Issue the following commands:
cd /opt/OMImag/bin atdd_mksf | sh
If you are using the PB drivers or are not using the standard device driver defaults with PCI drivers:
Verify that the hardware path for the device is listed in the configuration file:
/etc/rc.config.d/atdd.cfg
If the hardware path is missing or incorrect, the driver was not installed properly.
Claimed by HP Stape driver Run the command:# lsdevto check that the atdd is in the current kernel:
1. If the atdd is not in the output, rebuild the kernel or reinstall atdd;
2. If the atdd is in the output:
a. Rebuild the system I/O configuration:
1) Remove/stand/ioconfigand/etc/ioconfigafter to backup the files;
2) Reboot the system;
3) On System Console, enter the command:# /sbin/ioinit -cwhile the autobooting is
halted;
4) Run the command:# /sbin/insf -e 5) Enter the command:# ^Dto exit the I/O
configuration
b. Consider reinstalling the HP-UX operating system if the system is new or this is a new update. Cannot open Special File. The system log has the
following message:
Invalid SCSI request in data at bit 7 of byte 4
Wrong DENSITY setting. Check the current value by:
atdd_cfg -g DENSITY <atdd_inst>
Try setting it to 0 (zero):
atdd_cfg -s DENSITY 0 <atdd_inst>
An attempt to read data times out and returns an error. The system log has the following messages:
A SCSI command timed out and was aborted.
LLIO: Detected PowerFail (probably caused by SCSI bus or device reset).
Check that the SILI configuration parameter is 1 by executing:
atdd_cfg -g SILI <atdd_inst>
If the SILI parameter is zero, try setting it to 1:
atdd_cfg -s SILI 1 <atdd_inst>
An attempt to read data times out and returns an error. The system log has the following messages:
A SCSI command timed out and was aborted. scsi3: ....date code...
scsi3: ....timestamp...
Check that the FORCE_NARROW parameter is valid for this device by executing:
atdd_cfg -g FORCE_NARROW <atdd_inst>
If FORCE_NARROW is 1, try setting it to 0:
Purpose . . . 93 Data Flow . . . 93 Product Requirements . . . 94
Hardware Requirements for Intel and AMD
Opteron Processors . . . 94 Hardware Requirements for IBM System p
Models . . . 95 Hardware Requirements for IBM System z
Models . . . 95 Software Requirements for Intel and AMD
Opteron Processors . . . 96 Software Requirements for IBM System p Models 96 Software Requirements for IBM System z Models 96 Installation and Configuration Instructions . . . . 96 Conventions Used . . . 96 Components Created During Installation . . . 97 Installation Procedure . . . 97 Updating Procedure . . . 98 Querying the Installed Package . . . 98 Verifying Installation and Updating . . . 99 Configuring Tape and Medium Changer Devices on Intel-Compatible Systems . . . 99 Configuring Tape and Medium Changer Devices on IBM System p Models . . . 100 Configuring Tape and Medium Changer Devices on IBM System z Models . . . 100 Uninstall Procedure . . . 102 Tape Drive, Media, and Device Driver Parameters 102 Configuration Parameters . . . 102 Nonchangeable Parameters . . . 103 Changeable Parameters . . . 104
Special Files . . . 107 Special Files for the Tape Device . . . 107 Special Files for the Medium Changer Device 107 Control Path Failover Support for Tape Libraries 108
Configuring and Unconfiguring Path Failover Support . . . 108 Primary and Alternate Paths . . . 108 Querying Primary and Alternate Path
Configuration . . . 109 Disable and Enable Primary and Alternate Paths 109 Data Path Failover and Load Balancing Support for Tape Drives . . . 110
Primary and Alternate Paths . . . 111 Querying Primary and Alternate Path
Configuration . . . 111 Disable and Enable Primary and Alternate Paths 111 Open Source Device Driver - lin_tape . . . 112 IBMtape and lin_tape Comparison . . . 112 Installation . . . 112 Driver parameters and special device files . . . 112 Path Failover Support . . . 113 lin_taped Daemon . . . 113 System-Managed Encryption . . . 113 Device Driver Configuration . . . 113 Querying Tape Drive Configuration . . . 114 Testing Data Encryption Configuration and
Connectivity . . . 115 Problem Determination . . . 116 Configure and Run lin_taped Daemon . . . . 116 Reservation Conflict Logging . . . 120 Tape Drive Service Aids . . . 121 This chapter describes the IBM Linux Tape and Medium Changer Device Driver (lin_tape).
For tape diagnostic and utility functions refer to Chapter 10, “IBM Tape Diagnostic Tool (ITDT),” on page 259 or “Linux System - Tape Utility Program (IBMtapeutil)” on page 385.
Purpose
The lin_tape and medium changer device driver is designed specifically to take advantage of the features provided by the IBM tape drives and medium changer devices. The goal is to give applications access to the functions required for basic tape operations (such as backup and restore) and medium changer operations (such as mount and demount the cartridges), as well as to the advanced functions needed by full tape management systems. Whenever possible, the driver is designed to take advantage of the device features transparent to the application.
Data Flow
The software described in this chapter covers the Linux Device Driver (lin_tape device driver) and the interface between the application and the tape device.
Figure 11 illustrates a typical data flow process.
Product Requirements
More current information on supported hardware and software configurations for lin_tape is in the README files. The most current information is found in the README files on the IBM Device DriversFTP site, which is located at:
ftp://ftp.software.ibm.com/storage/devdrvr/Linux
Information specific to certain distributions are in the README files in the distribution-specific directories under the Linux directory.
Information there includes:
v Specifics on Linux distributions and kernel levels
v Supported Host Bus Adapter cards and required firmware and HBA device driver levels
v Other important information that is not included in this manual