This section describes how to set up the ETERNUS LT270 tape library.
Disabling the st driver
Note
To build a tape server in cluster, do not disable the st driver in this step, but the device should be recognized by the st driver as well.
Execute the ls command to display the device file.
# ls -l /dev/rmt/*[0-9] lrwxrwxrwx 1 root root 40 Feb 27 15:07 /dev/rmt/0 -> ../../devices/pci@16,2000/scsi@1/st@5,0: lrwxrwxrwx 1 root root 50 Feb 27 15:07 /dev/rmt/1 -> ../../devices/pci@17,4000/fibre-channel@4/st@1,0: ... |
Check the displayed device file to see if the st driver recognizes the LT270 device.
../../devices/pci@17,4000/fibre-channel@4/st@1,0:
1 2 3
1: "devices/pci@17,4000/fibre-channel@4 " = This is the physical path name that indicates where the HBA is installed.
2: "st" = Indicates that the LT270 is controlled by the st driver
3: "1,0" = Hexadecimal display indicating "Target ID (LOOP ID),LUN" |
From these contents, the user can find out if the physical path is an HBA connected to the LT270, check whether or not the target ID (LOOP ID) and LUN information match the LT270 drive, and find out if the LT270 drive is controlled by the st driver.
Note
If the LT270 is not included in the drives controlled by the st driver, steps 3 to 5 below are not required.
If there are programs that access the drive, stop all those programs.
If the LT270 is controlled by the st driver, comment out the target definition that corresponds to the LT270 drive in /kernel/drv/st.conf.
Point
To comment out the target definition, insert "#" at the start of the part that matches the target ID (LOOP ID) and LUN of the LT270 drive.
Note
If the server has in-built drives, ensure that you do not comment out the definitions for the in-built drives.
Delete the device file of the LT270 drive that is controlled by the st driver.
The following is an example of how to delete the device file confirmed in Step 1 and 2.
# rm -i /dev/rmt/*
rm: remove /dev/rmt/0 (yes/no)? n
rm: remove /dev/rmt/0b (yes/no)? n
:
rm: remove /dev/rmt/1 (yes/no)? y
rm: remove /dev/rmt/1b (yes/no)? y
: |
Note
When executing the rm command, be careful not to accidentally delete other files.
Robot settings
Enter the Target ID of the LT270 robot in the /usr/kernel/drv/lb.conf file. Refer to the sample lb.conf file and enter the Target ID. In the following coding example, the Target ID is 4.
#
# --------------------------------------------------------------
# IBM Tivoli Storage Manager for Sun Solaris Server
# Licensed Materials - Property of IBM
# 5765-303 (C) Copyright IBM Corporation 1999.
# All rights reserved.
# Refer to Copyright Instructions Form Number G120-2083
# --------------------------------------------------------------
:
:
name="lb" class="scsi"
target=4 lun=0; |
Note
In the /usr/kernel/drv/lb.conf file, the "name" value "lb", the "class" value "scsi", and the "lun" value of 0 are fixed values.
Register the lb driver.
#/opt/tivoli/tsm/devices/bin/autoconf |
IBM Tape Driver settings
Enter the Target ID and LUN ID of the drive in the /usr/kernel/drv/IBMtape.conf file. However, these values are normally set during installation and usually need not be changed. Simply check the contents.
###############################################################################
###############################################################################
## ##
## IBM SCSI Tape & Medium Changer Device Driver for Solaris 8, 9 and 10 ##
## (C) COPYRIGHT IBM Corporation, 1994 - ##
## ##
## IBMtape.conf - Configuration File ##
## Licensed Materials - Property of IBM ##
## All Rights Reserved ##
## ##
## US Government Users Restricted Rights - Use, duplication, or ##
## disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ##
## ##
###############################################################################
###############################################################################
# An example entry for high numbers of target and lun
# name="IBMtape" class="scsi" target=200 lun=3;
# An example entry for QLogic HBA running qla HBA driver
# name="IBMtape" parent="qla2100" target=0; # for qla2100 only
# name="IBMtape" parent="qla2200" target=0; # for qla2200 only
# name="IBMtape" parent="qla2300" target=0; # for qla2300 only
# An example entry for AMCC JNI HBA
# name="IBMtape" parent="jnic146x" target=0;
# An example entry for Emulex HBA
# name="IBMtape" parent="lpfc" target=0;
name="IBMtape" parent="pseudo" instance=16383;
name="IBMtape" class="scsi" target=0 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=0 lun=1 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
:
:
name="IBMtape" class="scsi" target=255 lun=0 block_size=0 buffering=1 immediate=0 trailer=0 sili=0;
name="IBMtape" class="scsi" target=255 lun=1 block_size=0 buffering=1 immediate=0 trailer=0 sili=0; |
HBA driver settings
The HBA driver setup method is shown below.
Set the robot, the alias name of the drive, the port and fcp-bind-target in the /kernel/drv/fjpfca.conf file. For the robot Target ID, enter the Target ID that was set in the /usr/kernel/drv/lb.conf file.
#
# All Rights Reserved, Copyright (c) FUJITSU LIMITED 2000
#
#ident "@(#)$Id: fjpfca.conf,v 3.1.1.1 2001/04/20 11:19:47 hiroki Exp $ FUJITSU"
:
alias=
"CTRL:0x200100e0000e100c",
"DRV00:0x201000e0000e100d",
"DRV01:0x201100e0000e100d",
"DRV02:0x201200e0000e100d",
"DRV03:0x201300e0000e100d";
:
port=
"fjpfca0:nport";
:
fcp-bind-target=
"fjpfca0t4:CTRL",
"fjpfca0t0:DRV00",
"fjpfca0t1:DRV01",
"fjpfca0t2:DRV02",
"fjpfca0t3:DRV03"; |
For details of the HBA driver settings, refer to the Fujitsu HBA driver settings under "Solaris OS settings" in the "ETERNUS LT270 Tape Library Setup Guide".
Note
These examples are for the Fujitsu HBA driver (FJSVpfca). Refer to the HBA manual of your product if another HBA driver, such as Emulex, NetMarks, is used. This setting is only required for fiber channel switch connection (FC-SW connection). Settings that include target ID set by the LT library are required for direct connection. Refer to "ETERNUS SF TSM ETERNUS LT Library Operator's Guide" for details.
Creating a device file
Reboot the server.
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 |
After the server is rebooted, execute the ls command to display the device file (lb).
# ls -l /dev/rmt/?lb lrwxrwxrwx 1 root root 40 Feb 27 15:07 /dev/rmt/0lb -> ../../devices/pci@16,2000/scsi@1/st@5,0: lrwxrwxrwx 1 root other 51 Feb 27 16:50 /dev/rmt/5lb-> ../../devices/pci@17,4000/fibre-channel@4/lb@4,0:lb # |
Check the displayed device file to see if the lb driver recognizes the LT270 robot.
../../devices/pci@17,4000/scsi@3/lb@0,4:lb
1 2 3
1: "devices/pci@17,4000/scsi@3" = This is the physical path name that indicates where the HBA is installed.
2: "lb" = Indicates that the LT270 is controlled by the lb driver
3: "4,0" = Hexadecimal display indicating "Target ID (LOOP ID),LUN" |
From these contents, the user can find out if the physical path is an HBA connected to the LT270, check whether or not the target ID (LOOP ID) and LUN information match the LT270 robot, and find out if the LT270 robot is controlled by the lb driver.
Execute the ls command to display the device file (st).
# ls -l /dev/rmt/?st lrwxrwxrwx 1 root root 56 Feb 27 16:50 /dev/rmt/1st-> ../../devices/pci@17,4000/fibre-channel@4/IBMtape@0,0:st lrwxrwxrwx 1 root root 56 Feb 27 16:50 /dev/rmt/2st-> ../../devices/pci@17,4000/fibre-channel@4/IBMtape@1,0:st lrwxrwxrwx 1 root root 56 Feb 27 16:50 /dev/rmt/3st-> ../../devices/pci@17,4000/fibre-channel@4/IBMtape@2,0:st lrwxrwxrwx 1 root root 56 Feb 27 16:50 /dev/rmt/4st-> ../../devices/pci@17,4000/fibre-channel@4/IBMtape@3,0:st # |
Check the displayed device file to see if the IBM tape driver recognizes the LT270 drive.
../../devices/pci@17,4000/fibre-channel@4/IBMtape@0,0:st
1 2 3
1: "devices/pci@17,4000/fibre-channel@4" = This is the physical path name that indicates where the HBA is installed.
2: "IBMtape" = Indicates that the LT270 is controlled by the IBM tape driver
3: "0,0" = Hexadecimal display indicating "Target ID (LOOP ID),LUN" |
From these contents, the user can find out if the physical path is an HBA connected to the LT270, check whether or not the target ID (LOOP ID) and LUN information match the LT270 drive, and find out if the LT270 drive is controlled by the IBM tape driver.
