An installation script (InstallAtdd)is provided to automate driver installation and perform some checking functions. It copies the latest version of the driver to the software depot and installs the latest driver version.
To install ATDD with the script, download the install script from the ftp site, then run the install script.
When the installation script runs, the customer is prompted with the question,
″Would you like to activate the Medium Changer support by ATDD (Y/N)?″. Enter
″Y″to allow the ATDD to configure all attached IBM Medium Changer devices, or answer ″N″to allow the HP native changer driver to configure these Medium Changer devices.
Notes:
1. If a previous version of ATDD is installed on your system, uninstall it before attempting to install the latest version. Refer to “Uninstalling the software” on page 66.
2. The system reboot is required to install ATDD in HP-UX 11i v3. To install ATDD manually, follow the steps in “Install Drivers Manually.”
Install Drivers Manually
Installing the drivers manually requires the steps detailed in the following sections.
1. “Copy the Software to the Software Depot” on page 62.
2. “Install the ATDD Software” on page 62.
3. If a previous version of ATDD is installed on your system, uninstall it before attempting to install the latest version. Refer to “Uninstalling the software” on page 66.
Copy the Software to the Software Depot:
Attention: If you do not copy the ATDD software into a depot, you will not be able to uninstall the product readily.
Copy the appropriate driver to the Software Depot. For example:
# swcopy -p -s /driver_location/atdd.x.x.x.x atdd (preview option)
# swcopy -s /driver_location/atdd.x.x.x.x atdd
Use swlistto verify that the ATDD software is in the depot:
# swlist -d atdd
Install the ATDD Software: When the software is in the depot and only the appropriate drives are powered on, the ATDD software can be installed to the root file system using the HP-UXswinstallcommand. If the target root file system is the primary, the ATDD software is configured automatically upon installation.
If the target is an alternate root file system, then the ATDD software is not configured automatically.
Note: If an earlier version of the product is already installed on the target root file system, the existing version is replaced. This is true even if the version already installed is more recent than the version being installed. The following commands install ATDD from the depot to the default root file system by issuing theswinstallcommand with theaskoptions set as follows:
# swinstall -p -x ask=true atdd (preview option)
# swinstall -x ask=true atdd in HP-UX 11.0, 11i v1, and v2
# swinstall -x autoreboot=true -x ask=true atdd in HP-UX 11i v3
Running theswinstallcommand with theaskoption set to TRUE prompts the customer,″Would you like to activate the Medium Changer support by ATDD (Y/N)?″. Enter″Y″to allow the ATDD to configure all attached IBM Medium Changer devices, or answer ″N″to allow the HP native changer driver to configure these Medium Changer devices.
You can use swlistto list the software installed on the default root file system as follows:
# swlist atdd
You can verify correct installation to the default root file system with theswverify command as follows:
# swverify atdd
After the installation is completed, run theioscancommand to list the tape drives found:
# ioscan -fknC tape
Class I H/W Path Driver S/W State H/W Type Description ============================================================================================ tape 0 0/3/0/0.5.0 atdd CLAIMED DEVICE IBM 03590E11
/dev/rmt/0m /dev/rmt/0mn /dev/rmt/c4t5d0BEST /dev/rmt/c4t5d0BESTn /dev/rmt/0mb /dev/rmt/0mnb /dev/rmt/c4t5d0BESTb /dev/rmt/c4t5d0BESTnb
tape 1 0/3/0/0.6.0 atdd CLAIMED DEVICE IBM 03590B11 /dev/rmt/1m /dev/rmt/1mn /dev/rmt/c4t6d0BEST /dev/rmt/c4t6d0BESTn
/dev/rmt/1mb /dev/rmt/1mnb /dev/rmt/c4t6d0BESTb /dev/rmt/c4t6d0BESTnb
tape 4 0/5/0/0.1.23.232.0.0.2 atdd CLAIMED DEVICE IBM ULT3580-TD1 /dev/rmt/4m /dev/rmt/4mn /dev/rmt/c6t0d2BEST /dev/rmt/c6t0d2BESTn
/dev/rmt/4mb /dev/rmt/4mnb /dev/rmt/c6t0d2BESTb /dev/rmt/c6t0d2BES
If you have enabled ACDD, run the following ioscancommand to view the medium changers found:
# ioscan -fnkC autoch
Class I H/W Path Driver S/W State H/W Type Description ======================================================================= autoch 0 0/3/0/0.5.1 acdd CLAIMED DEVICE IBM 03590E11
/dev/rmt/0chng
autoch 2 0/6/0/0.1.17.255.5.10.1 acdd CLAIMED DEVICE IBM 03590E11 /dev/rmt/2chng
autoch 4 0/5/0/0.1.23.232.0.0.1 acdd CLAIMED DEVICE IBM ULT3583-TL /dev/rmt/4chng
In HP-UX 11i v3, run # ioscan -funNC tape orautoch to display the tape devices configured with ATDD and ACDD drivers. Run #ioscan -funC tapeor autochto show the tape devices bound with the legacy atdd_leg and acdd_leg drivers.
Configure all IBM Tape Drives/Media Changers with ATDD/ACDD: By default, ATDD automatically configures all supported IBM tape drives that are attached and powered on when the ATDD package is installed. The ACDD driver does not configure IBM Medium Changer devices by default. To configure all IBM Medium Changer devices on the system during the install of ATDD package, run the
swinstallcommand with the-x ask=truecommand option and answer″Yes″to allow the ACDD to claim these devices.
To configure all IBM Medium Changer devices on the system after the install of the ATDD package:
v In HP-UX 11.0, 11i v1 and v2, run the command: # /opt/atdd/bin/atdd_claim -c
v In HP-UX 11i v3, do the following:
1. Bind each changer device with the ACDD driver: # ioscan -b -M acdd -H hw_path
2. Reboot the system to configure the changer devices: # shutdown -ry now
To remove the claim with ACDD after the next reboot: v In HP-UX 11.0, 11i v1 and v2, run the command:
# /opt/atdd/bin/atdd_claim -u v In HP-UX 11i v3, do the following:
1. Bind each changer device with a changer driver: # ioscan -b -M acdd -H hw_path
2. Reboot the system to unconfigure the changer devices: # shutdown -ry now
Configure Selected IBM Tape Devices with ATDD/ACDD in HP-UX 11.0, 11i v1 and v2:
Attaching Selected IBM Tape Devices to ATDD/ACDD During Auto Booting: To claim a specific tape device with atdd/acdd during reboot, edit the″Claiming Device″ section in the file of /sbin/init.d/atdd.
For example, to attach IBM 3590E11 medium changer with acdd driver:
1. To determine the HW path: # ioscan -fnk|grep IBM
autoch 0 0/3/0/0.5.1 schgr CLAIMED DEVICE IBM 03590E11
2. Comment out the command line(s) in the init script of /sbin/init.d/atdd: v For tape drives:
/opt/atdd/bin/atdd_claim -t v For medium changers:
/opt/atdd/bin/atdd_claim -c
3. Add a command line in the″Configuring Device″ section in /sbin/init.d/atdd: /opt/atdd/bin/atdd_claim -H 0/3/0/0.5.1
Attaching Selected IBM Tape Devices to ATDD/ACDD Dynamically: To dynamically attach selected IBM tape device after the ATDD installation, run the following commands.
# ioscan -fnk|grep IBM
autoch 0 0/3/0/0.5.1 schgr CLAIMED DEVICE IBM 03590E11
2. To claim the device with ATDD/ACDD: # /opt/atdd/bin/atdd_claim -H 0/3/0/0.5.1
Note: The dynamic attachment may be lost after the system reboots.
Attaching Selected IBM Tape Device with a Particular Driver: Use the systemioscan and rmsfcommands to force a non-atdd/acdd driver to bind an IBM tape device. For example, force bind the IBM 3590E media changer with the HP native changer driver schgr with these steps:
1. Determine the HW path of the device: # ioscan -fnk |grep IBM
tape 0 0/3/0/0.5.0 atdd CLAIMED DEVICE IBM 03590E11
autoch 0 0/3/0/0.5.1 acdd CLAIMED DEVICE IBM 03590E11
2. Remove the I/O configuration from the system: # rmsf -H 0/3/0/0.5.1
3. Force binding:
# ioscan -M schgr -H 0/3/0/0.5.1
4. Create the device special files: # insf -H 0/3/0/0.5.1
5. Verify the force binding: # ioscan -fnk |grep IBM
tape 0 0/3/0/0.5.0 atdd CLAIMED DEVICE IBM 03590E11
autoch 0 0/3/0/0.5.1 schgr CLAIMED DEVICE IBM 03590E11
Note: The force binding is lost after the system reboots. To keep the binding to a selected device with a particular driver after a reboot, add these command-lines in steps 2–4 in″Claiming Device″section in /sbin/init.d/atdd file. For example,
# Configuring Device Section:
# add specific device claim here, for example # /opt/atdd/bin/atdd_claim -H 0/3/0/0.5.1
# /opt/atdd/bin/atdd_claim -H 0/6/0/0.1.30.255.0.0.1 rmsf -H 0/3/0/0.5.1
ioscan -M schgr -H 0/3/0/0.5.1 insf -H 0/3/0/0.5.1
Configure Selected IBM Tape Devices with ATDD/ACDD in HP-UX 11i v3: By default, atdd driver automatically configures all supported IBM tape drives that are attached and powered on when the ATDD package is installed. The acdd driver does not configure IBM medium changer devices by default. All of IBM medium changers are claimed if you use acdd and acdd_leg as the changer drivers during ATDD are installed. To attach a selected IBM tape device with a particular driver, run the system ioscan command to force a non-ATDD/ACDD driver to bind an IBM tape device, and then reboot the system. For example, to force bind the IBM 3592E05 tape drive with the HP native tape driver estape, perform these steps:
1. Determine the HW path of the device: # ioscan -fNk | grep IBM
tape 1 64000/0xfa00/0x7 atdd CLAIMED DEVICE IBM 03592E05
2. Force the binding:
# ioscan -b -M estape -H 64000/0xfa00/0x7
# shutdown -ry now
4. Create the device special files if it does not exist after the system bootup: # insf -H 64000/0xfa00/0x7
5. Verify the force binding: # ioscan -fNk | grep IBM
tape 1 64000/0xfa00/0x7 estape CLAIMED DEVICE IBM 03592E05 Uninstalling the software:
Attention: Do not try to uninstall the ATDD software by simply deleting the files that make up the ATDD fileset. This causes a number of inconsistencies on the system. It is best to use theswremovecommand.
To uninstall ATDD (from the root file system): # swremove atdd in HP-UX 11.0, 11i v1 and v2 # swremove -x autoreboot=true atdd in HP-UX 11i v3
Other Administrative Tasks: To determine whether the current version of ATDD is installed or configured on the default root file system:
# swlist -a state atdd
To determine the versions of ATDD stored in the default depot: # swlist -d atdd
To remove ATDD from the depot: # swremove -d atdd
If more than one level of ATDD exists in the depot, explicitly specify the level to remove it. For example:
# swremove -d atdd,r=3.5.0.0
To view the fileset of ATDD installed on the system: # swlist -l file atdd
To display and manage ATDD kernel modules and kernel-tunable parameters, run kmadmin, kmsystem, kmtute and kmadmin commands in HP-UX 11.0 and 11i v1 and kcmodule, kctune commands in HP-UX 11i v2 and v3, or go to the “Kernel Configuration” in sam utility. Refer to the system manual for more detail.
For an example, print out the ATDD driver module status entering the command: # kcmodule -d atdd
Module State Cause Description
atdd static explicit Advanced Tape Device Driver