This section describes how to set up the ETERNUS LT20/LT40/LT60 tape libraries.
Disabling the st driver
Note
To build a tape server in cluster, do not disable the st driver in this step; 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 27 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@17,4000/fibre-channel@4/st@1,0: ... |
Check the displayed device file to confirm that the st driver recognizes the LT20/LT40/LT60 device.
../../devices/pci@17,4000/fibre-channel@4/st@1,0:
1 2 31:"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 LT20/LT40/LT60 is controlled by the st driver 3:"1,0"= Hexadecimal display indicating "Target ID (LOOP ID),LUN" |
From these contents, the user can determine if the physical path is an HBA connected to the LT20/LT40/LT60, check whether or not the target ID (LOOP ID) and LUN information match the LT20/LT40/LT60 drive, and find out if the LT20/LT40/LT60 drive is controlled by the st driver.
Note
If the LT20/LT40/LT60 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 LT20/LT40/LT60 is controlled by the st driver, comment out the target definition that corresponds to the LT20/LT40/LT60 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 LT20/LT40/LT60 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 LT20/LT40/LT60 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 LT20/LT40/LT60 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 4 and the LUN number is 1.
#
# --------------------------------------------------------------
# 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=1; |
Note
In the /usr/kernel/drv/lb.conf file, the "name" value "lb" and the "class" value "scsi" are fixed values.
Register the lb driver.
# /opt/tivoli/tsm/devices/bin/autoconf |
Driver configuration of drive
Set the configuration file (mt.conf) of mt driver, which is one of the TSM device drivers.
Installing TSM device drivers stores the mt driver configuration file (mt.conf) at the following location:
/usr/kernel/drv/mt.conf |
Edit the mt.conf file by adding definitions that specify the drive device target ID and the LUN number.
In the following example, the Target ID is 6 and the LUN number 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 # -------------------------------------------------------------- # # -------------------------------------------------------------- # Tivoli Storage Manager SCSI Device Driver for Tape Drives # Configuration File # -------------------------------------------------------------- # ... name="mt" class="scsi" target=6 lun=0; |
Note
In the /usr/kernel/drv/mt.conf file, the "name" value "mt" and the "class" value "scsi" are fixed values.
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=
"CTRL:0x200100e0000e100c",
"DRV00:0x201000e0000e100d";
...
port=
"fjpfca0:nport",
"fjpfca1:nport";
...
fcp-bind-target=
"fjpfca0t4:CTRL",
"fjpfca1t6:DRV00";
|
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 27 Feb 15:07 /dev/rmt/0lb -> ../../devices/pci@16,2000/scsi@1/st@5,0: lrwxrwxrwx 1 root other 51 27 Feb 16:50 /dev/rmt/5lb -> ../../devices/pci@17,4000/fibre-channel@4/lb@4,1:lb # |
Check the displayed device file to see if the lb driver recognizes the LT20/LT40/LT60 robot.
../../devices/pci@17,4000/fibre-channel@4/lb@4,1:lb
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:"lb"= Indicates that the LT20/LT40/LT60 is controlled by the lb driver
3:"4,1"= 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 LT20/LT40/LT60, check whether or not the target ID (LOOP ID) and LUN information match the LT20/LT40/LT60 robot, and find out if the LT20/LT40/LT60 robot is controlled by the lb driver.
Execute the ls command to display the device file (mt).
# ls -l /dev/rmt/*mt lrwxrwxrwx 1 root sys 52 14 Jul 10:02 /dev/rmt/5mt ->../../devices/pci@17,4000/fibre-channel@2/mt@6,0:mt lrwxrwxrwx 1 root sys 42 14 Jul 10:02 /dev/rmt/6mt ->../../devices/pci@16,4000/scsi@2/mt@0,0:mt |
Check the displayed device file to see if the mt driver recognizes the LT20/LT40/LT60 drive.
../../devices/pci@17,4000/fibre-channel@2/mt@6,0:mt
1 2 3
1:"devices/pci@17,4000/fibre-channel@2" = This is the physical path name that indicates where the HBA is installed.
2:"mt"= Indicates that the LT20/LT40/LT60 is controlled by the mt driver
3:"6,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 LT20/LT40/LT60, check whether or not the target ID (LOOP ID) and LUN information match the LT20/LT40/LT60 drive, and find out if the LT20/LT40/LT60 drive is controlled by the mt 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 27 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 LT20/LT40/LT60 device.
../../devices/pci@1f,4000/FJSV,ulsa@3/st@1,0:
1 2 3
1:"devices/pci@1f,4000/FJSV,ulsa@3" = This is the physical path name that indicates where the HBA is installed.
2:"st"= Indicates that the LT20/LT40/LT60 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 LT20/LT40/LT60, check whether or not the target ID (LOOP ID) and LUN information match the LT20/LT40/LT60 drive, and find out if the LT20/LT40/LT60 drive is controlled by the st driver.
Note
If the LT20/LT40/LT60 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 LT20/LT40/LT60 is controlled by the st driver, comment out the target definition that corresponds to the LT20/LT40/LT60 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 LT20/LT40/LT60 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 LT20/LT40/LT60 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.
Checking SCSI ID and LUN number
Use the probe-scsi-all command to check the SCSI ID and the LUN number of the robot and the drive.
In the following coding example, the SCSI ID is 4, the LUN number of drive is 0, and the LUN number of robot is 1.
{0} ok probe-scsi-all
...
/pci@500/pci@0/pci@9/pci@0/FJSV,eulsa@8,1
/pci@500/pci@0/pci@9/pci@0/FJSV,eulsa@8
Target 4 SCSI ID
Unit 0 Removable Tape HP Ultrium 4-SCSI W51W
Unit 1 Removable Device type 8 HP 1x8 G2 AUTOLDR B.72
...
{0} ok |
Robot settings
Enter the Target ID of the LT20/LT40/LT60 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 4 and the LUN number is 1.
#
# --------------------------------------------------------------
# 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=1; |
Note
In the /usr/kernel/drv/lb.conf file, the "name" value "lb" and the "class" value "scsi" are fixed values.
Register the lb driver.
# /opt/tivoli/tsm/devices/bin/autoconf |
Driver configuration of drive
If a non-IBM drive device is used, set the configuration file (mt.conf) of the mt driver, which is one of the TSM device drivers.
Installing TSM device drivers stores the mt driver configuration file (mt.conf) at the following location:
/usr/kernel/drv/mt.conf |
Edit the mt.conf file by adding definitions that specify the drive device target ID and the LUN number.
In the following coding example, the Target ID is 4 and the LUN number 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 # -------------------------------------------------------------- # # -------------------------------------------------------------- # Tivoli Storage Manager SCSI Device Driver for Tape Drives # Configuration File # -------------------------------------------------------------- # ... name="mt" class="scsi" target=4 lun=0; |
Note
In the /usr/kernel/drv/mt.conf file, the "name" value "mt" and the "class" value "scsi" are fixed values.
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 27 Feb 15:07 /dev/rmt/0lb -> ../../devices/pci@16,2000/scsi@1/st@5,0: lrwxrwxrwx 1 root other 51 27 Feb 16:50 /dev/rmt/3lb -> ../../devices/pci@1f,4000/FJSV,ulsa@3/lb@4,1:lb # |
Check the displayed device file to see if the lb driver recognizes the LT20/LT40/LT60 robot.
../../devices/pci@1f,4000/FJSV,ulsa@3/lb@4,1:lb
1 2 3
1:"devices/pci@1f,4000/FJSV,ulsa@3" = This is the physical path name that indicates where the HBA is installed.
2:"lb"= Indicates that the LT20/LT40/LT60 is controlled by the lb driver
3:"4,1"= 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 LT20/LT40/LT60, check whether or not the target ID (LOOP ID) and LUN information match the LT20/LT40/LT60 robot, and find out if the LT20/LT40/LT60 robot is controlled by the lb driver.
Execute the ls command to display the device file (mt).
# ls -l /dev/rmt/*mt lrwxrwxrwx 1 root root 56 27 Feb 16:50 /dev/rmt/1mt -> ../../devices/pci@1f,4000/FJSV,ulsa@3/mt@4,0:mt |
Check the displayed device file to see if the mt driver recognizes the LT20/LT40/LT60 drive.
../../devices/pci@1f,4000/FJSV,ulsa@3/mt@4,0:mt
1 2 3
1:"devices/pci@1f,4000/FJSV,ulsa@3" = This is the physical path name that indicates where the HBA is installed.
2:"lb"= Indicates that the LT20/LT40/LT60 is controlled by the driver other than made by IBM.
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 LT20/LT40/LT60, check whether or not the target ID (LOOP ID) and LUN information match the LT20/LT40/LT60 drive, and find out if the LT20/LT40/LT60 drive is controlled by the mt driver.
