Recently installed an ADIC changer with LTO drives. ADIC professional services installed the ATDD device driver and the drives are seen by ioscan as tape type devices but the only special file that was created is /dev/rmt/chng. I think I need to create the normal 8 tape device files for Veritas Netbackup to see the drives. How do I do this?
The command /usr/sbin/insf -e will install the special files for the tape drives. The insf should work for most situations. If you need a customized special file for your tape drives you can use the command /usr/sbin/mksf. You can find more information on these commands in the manual "Configuring HP-UX For Peripherals" on pages 184 and 190, which can be downloaded from www.docs.hp.com.
insf -e does not install the special files and running mksf returns "Don't know how to handle driver "atdd"" It is my understanding that HP-UX 11.00 does not natively support LTO drives hence the atdd driver.
Sorry didn't notice that you were using LTO drives. Here is what I found.
From IBM's Ultrium Device Drivers Installation and User's Guide:
1. Modify the /stand/system file, adding a line if the form of:
driver 56/48.3.0 atdd
with the adapter/drive path for your device
2. Modify /etc/rc.config.d/atdd.cfg, adding the hardware path and instance:
ATDD_HWPATH[#]=56/48.3.0
where # denotes the next instance and the adapter/drive path for you device.
3. Build the kernel as root:
# mk_kernel -o /stand/vmunix -s /stand/system
4. Reboot the system:
# shutdown -r now
5. After the system is up, run /opt/OMNImag/bin/atdd_cfg to create the new special files for the device.
# atdd_mksf -ti
where instance is the number from the ioscan output for the newly installed device. This command echoes to console but does not create special files. To create special files pipe the command to 'sh'.
This re-created the /dev/rmt/chng special file but does not seem to create the #m, #mb, #mn, #mnb, #BEST, #BESTb, #BESTn, and #BESTnb that Veritas, and SAM, seem to be looking for to identify a tape drive
The machine is a L2000 dual 440MHz processor with 4GB of RAM. It is running HP-UX 11.00 64-bit with June 2001 patch bundles, (new install). The machine has a pair of Tachyon FC adapters (HP A5158A) which are hooked through a EMC DS-16M switch to a PathLight FC Bridge which connects to the ADIC Scalar 1000 with four LTO drives in it.
ioscan -kfnC tape shows the following:
tape 0 0/4/0/0.97.7.19.0.0.2 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/0chng tape 55 0/4/0/0.97.7.19.0.0.3 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/55chng tape 1 0/4/0/0.97.7.19.0.0.4 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/1chng tape 56 0/4/0/0.97.7.19.0.0.5 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/56chng tape 4 0/7/0/0.97.11.19.0.0.2 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/4chng tape 3 0/7/0/0.97.11.19.0.0.3 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/3chng tape 5 0/7/0/0.97.11.19.0.0.4 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/5chng tape 57 0/7/0/0.97.11.19.0.0.5 atdd CLAIMED DEVICE IBM ULTRIUM-TD1 /dev/rmt/57chng
The FC adapters are 0/4 and 0/7 so it appears that I am correctly seeing the two paths to each of the four tape drives which are assigned LUNs 2,3,4 and 5 respectively.
The robot is assigned LUN 1 and the ioscan -kfnC autoch shows the following:
For info the PathLight is LUN 0 and shows up as a ctl device as /dev/rscsi/c5t0d0 and /dev/rscsi/c7t0d0
Zones on the FC switch seem to be setup correctly and I can access the drives using the /dev/rmt/#chng special files to perform functions like rewinding or reading and writing a tar file to tape if I manually load a tape into one of the drives so I know that the data paths are valid.
This is our first time using either a SAN or a library with LTO drives so these are all new problems to me. I appreciate the help as ADIC doesn't seem to have any advice for me at all.
I have read through the IBM atdd documentation and the only thing that I can come up with is to double check your /etc/rc.config.d/atdd.cfg file and make sure that there is a HWPATH= entry for each tape drive. You can also try and run the atdd_mksf and not pipe it to sh and see what commands the script is trying execute to create the special files. I have attached the IBM documentation if you want to take a look at it.
I was able to create the special files I needed by editing the atdd_mksf shell script to remove all branches except the one I needed. I do not know why the command did not correctly enter the proper branch under normal execution but it works now.
