This section describes how to set up the ETERNUS LT230 (SCSI connection) 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 17 Feb 15:07 /dev/rmt/0 -> ../../devices/pci@16,2000/scsi@1/st@5,0: lrwxrwxrwx 1 root root 50 27 Feb 15:07 /dev/rmt/1 -> ../../devices/pci@1f,4000/FJSV,ulsa@3/st@1,0: ... |
Check the displayed device file to see if the st driver recognizes the LT230 device.
../../devices/pci@1f,4000/FJSV,ulsa@4/st@1,0:
1 2 3
1: "devices/pci@1f,4000/FJSV,ulsa@4" = This is the physical path name that indicates where the HBA is installed
2: "st" = Indicates that the LT230 is controlled by the st driver
3: "1,0" = Hexadecimal display indicating "Target ID (LOOP ID),LUN" |
From these contents, check whether the physical path is an HBA connected to the LT230, and whether the target ID (LOOP ID) and LUN information match the LT230 drive. Then determine whether or not the LT230 drive is controlled by the st driver.
Note
If the LT230 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 of those programs.
If the LT230 is controlled by the st driver, comment out the target definition that corresponds to the LT230 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 LT230 drive.
Note
Make sure that the definition is not commented out if there is a driver on the server.
Delete the device file of the LT230 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 LT230 robot in the /usr/kernel/drv/lb.conf file. Refer to the sample lb.conf file and enter the robot SCSI ID as the Target ID. In the following coding example, the Target ID is 2.
#
# --------------------------------------------------------------
# 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=2 lun=1; |
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
Check the definition of the LUN ID, and the Target ID of the drive in the /usr/kernel/drv/IBMtape.conf file.
However, as this is normally set up at the time of installation, change is not particularly required, only a check of 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
Set the robot and driver's alias name, port and fcp-bind-target in the /kernel/drv/fjpfca.conf file. For the Target ID of the robot, use 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=
"DRV00:0x201000e0000e100d",
"DRV01:0x201100e0000e100d";
...
port=
"fjpfca0:nport",
"fjpfca1:nport";
...
fcp-bind-target=
" fjpfca0t2:DRV00",
" fjpfca1t3:DRV01"; |
Creating a device file
Reboot the server.
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 |
After the server starts up, execute the ls command to display the device file (1b).
# 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@2,1:lb # |
Check the displayed device file to see if the 1b driver recognizes the LT230 robot.
../../devices/pci@17,4000/fibre-channel@4/lb@2,1:lb
1 2 3
1:"devices/pci@17,4000/fibre-channel@4"= Physical path name that indicates the location where HBA is mounted.
2:"lb"= Indicates that the LT230 is controlled by the lb driver
3:"2,1"= Hexadecimal display indicating "Target ID (LOOP ID),LUN" |
From these contents, check whether the physical path is an HBA connected to the LT230, and whether the target ID (LOOP ID) and LUN information match the LT230 robot. Then, determine whether or not the LT230 robot is being controlled by the 1b 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@2,0:st lrwxrwxrwx 1 root root 56 Feb 27 16:50 /dev/rmt/2st -> ../../devices/pci@17,4000/fibre-channel@4/IBMtape@3,0:st # |
Check the displayed device file to see if the IBMtape driver recognizes the LT230 driver.
../../devices/pci@17,4000/fibre-channel@4/IBMtape@2,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 LT230 is controlled by the st driver
3:"2,0"= Hexadecimal display indicating "Target ID (LOOP ID),LUN" |
From these contents, check whether the physical path is an HBA connected to the LT230, and whether the target ID (LOOP ID) and LUN information match the LT230 drive. Then, determine whether or not the LT230 drive is being controlled by the IBMtape driver.
Note
The SCSI-ID or LU for the robot or the drive of the ETERNUS LT library may differ depending on the model of the device or settings. For details, refer to the manual of the hardware or contact a Fujitsu Engineer (CE).
Disabling the st driver
Execute the ls command to display the device files.
# 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/scsi@3/st@0,0:
: |
Check the displayed device files to see if the st driver recognizes the LT230 device.
../../devices/pci@17,4000/scsi@3/st@0,0:
1 2 3
1:"devices/pci@1f,4000/scsi@3" = This is the physical path name that indicates where the HBA is installed.
2:"st" = Indicates that the LT230 is controlled by the st 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 LT230, check whether or not the target ID (LOOP ID) and LUN information match the LT230 drive, and find out if the LT230 drive is controlled by the st driver.
Note
If the LT230 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 LT230 is controlled by the st driver, comment out the target definition that corresponds to the LT230 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 LT230 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 LT230 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 LT230 robot in the /usr/kernel/drv/lb.conf file. Refer to the sample lb.conf file and enter the robot SCSI ID as the Target ID. In the following coding example, the SCSI ID is 0.
#
# --------------------------------------------------------------
# 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=0 lun=0; |
Note
In the /usr/kernel/drv/lb.conf file, the "name" value "lb", the "class" value "scsi". For the "lun", check the setting of LT230 and set it accordingly.
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;
|
Creating a device file
Re-boot the server.
# touch /reconfigure # /usr/sbin/shutdown -y -i6 -g0 |
After the server is activated, 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 root 51 Feb 27 16:50 /dev/rmt/1lb -> ../../devices/pci@17,4000/scsi@3/lb@0,0:lb # |
Check the displayed device file to see if the lb driver recognizes the LT230 robot.
../../devices/pci@17,4000/scsi@3/lb@0,0: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 LT230 is controlled by the lb 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 LT230, check whether or not the target ID (LOOP ID) and LUN information match the LT230 robot, and find out if the LT230 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/scsi@3/IBMtape@1,0:st lrwxrwxrwx 1 root root 56 2 month 27 day 16:50 /dev/rmt/2st -> ../../devices/pci@17,4000/scsi@3/IBMtape@2,0:st # |
Check the displayed device file to see if the IBM tape driver recognizes the LT230 drive.
../../devices/pci@17,4000/scsi@3/IBMtape@1,0:st
1 2 3
1: "devices/pci@17,4000/scsi@3" = This is the physical path name that indicates where the HBA is installed.
2: "IBMtape" = Indicates that the LT230 is controlled by the IBM tape 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 LT230, check whether or not the target ID (LOOP ID) and LUN information match the LT230 drive, and find out if the LT230 drive is controlled by the IBM tape driver.
