search

Installing a Tape Library on an HP S800 Running HP-UX 10.x

Use ioscan -f to probe your system for attached peripherals. Sample output follows:

Class    I  H/W Path  Driver  S/W State H/W Type  Description

=================================================================

bc       0            root    CLAIMED   BUS_NEXUS

ext_bus  2  8         scsi1   CLAIMED   INTERFACE HP 28655A - SC 

target   0  8.3       target  CLAIMED   DEVICE

spt      0  8.3.0spt     CLAIMED   DEVICE    HP      C1718T 

target   1  8.4       target  CLAIMED   DEVICE

spt      1  8.4.0spt     CLAIMED   DEVICE    HP      C1716T 

  1. You can also use the command $ /usr/sbin/lsdev -d spt to check whether the SCSI pass-through driver is installed.

    • If the driver is installed, output similar to the following appears:

      ------------------------------------------------

 Character Block Driver Class

    136 -1 spt spt

------------------------------------------------

      In this sample the major number of the spt driver is 136. If the driver is installed, proceed directly to step 16.

    • If the driver is not installed, the second line of the output will be blank. If the driver is not installed, proceed to the next step.

  2. Issue the command uname –a to check the revision of 10.x installed on your server:

    -------------------------------

    HP-UX abc B.10.00 A 9000

-------------------------------

    • If the operating system is revision 10.00, install patch PHKL_5406 or its succeeding patch. The following files are included in the patch PHKL_5406.

      Filename Protections Full path

======== =========== =========

libspt.a -r--r--r-- /usr/conf/lib/libspt.a

scsi\_io.c -r--r--r-- /usr/contrib/src/scsi\_io.c

scsi\_pt.7 -r--r--r-- /usr/share/man/man7.Z/scsi\_pt.7

spt -r--r--r-- /usr/conf/master.d/spt

    • If revision 10.01 is installed, the patch is unnecessary.

  3. If it was necessary to patch the kernel, you must configure the NIO SCSI pass-through driver. This driver does not auto-configure.

  4. Go to the build area and create a system file from your existing kernel:

    cd /stand/build /usr/lbin/sysadm/system_prep -s system

circle-info

Note. See the man page for “scsi_pt” for the most recent and accurate information on this procedure.

  1. Use grep spt system to check if the SCSI pass-through driver is configured into the current kernel. If no spt line is printed, add a line beginning with spt to the SCSI drivers area of the system file; e.g /stand/build/system.

  2. A driver statement is needed to override the standard driver that is automatically configured for any device. One statement is required for each desired NIO SCSI pass-through device (be it a SCSI target, or a SCSI LUN). Append the driver line(s) to the system file as follows:

cat >> system driver path spt

.......... # add more drivers if you want

^D # control “D” to exit the cat command

where:

path

The complete hardware path of the media changer from the ioscan command. In the example in step 1, the path is 8.3.0 for HP C1718T and 8.4.0 for HP C1716T. This means that the device connected to HP C1718T has a SCSI ID of 3 and LUN of 0. The device connected to HP C1716T has a SCSI ID of 4 and LUN of 0.

  1. Create the conf.c and config.mk files by issuing

    /usr/sbin/config -s system.

  2. Use make -f config.mk to build a new kernel.

  3. Use what ./vmunix_test |grep scsi_pt to verify that the pass-through driver has been built into the new kernel.

    An entry showing the revision information appears.

  4. Save the old system file by using

    mv /stand/system /stand/system.prev

  5. Move the new system file to be the current one by using

    mv ./system /stand/system.

  6. Save the old kernel by using

    mv /stand/vmunix /stand/vmunix.prev

  7. Move the new kernel to be the current one by using

    mv ./vmunix_test /stand/vmunix

  8. Reboot the system from the new kernel by using exec reboot.

  9. On your controller node, run detect -i at the command prompt. detect -i generates the device file for the media changer and places it in the dev directory.

    Example: /dev/c0t5d0_sa.

    It also creates all necessary mappings for the media changer device.

The installation of the tape library media changer device file is complete. To test the installation, proceed to Chapter 36: Tape Library Verification. Use the media changer device file name (for example, /dev/c0t5d0_sa) as the argument for the tape library interface test program (JItest).

Last updated