Chapter 12. IBM Tivoli System Automation for Multiplatforms setup 611
12.6 Persistent binding of tape devices
Device configuration on SAN-attached devices is made simpler with the Tivoli
Storage Manager SAN Device Mapping function (SDM). SDM uses the SNIA
(Storage Networking Industry Association) Host Bus Adapter (HBA) API to
perform SAN discovery. The device serial number, manufacturer, and worldwide
name are initially recorded for each storage device. When the device
configuration changes, Tivoli Storage Manager can automatically update the
device path information without the need for device persistent binding.
In our lab environment we use a IBM TotalStorage 3582 Tape Library with two
LTO2 tape drives, each of them with one FC port. The first tape drives also acts
as medium changer device. As we depend on the path to the first tape drive
anyway, we do not activate the SDM function.
You can find a list of supported HBA driver versions for SDM at:
12.7 Installation of Tivoli System Automation
Before we start the installation and configuration of Tivoli System Automation for
Multiplatforms, we must set the management scope for RSCT for all users of
Tivoli System Automation for Multiplatforms on all nodes. We set the variable
permanently by setting it in the profile.
We downloaded the Tivoli System Automation for Multiplatforms tar file from the
Internet, so we extract the file, using the following command:
tar -xvf <tar file>
Now we change to the appropriate directory for our platform:
We install the product with the installSAM script as shown in Example 12-11.
Example 12-11 Installation of Tivoli System Automation for Multiplatforms
[root@diomede i386]# ./installSAM
installSAM: A general License Agreement and License Information specifically
for System Automation will be shown. Scroll down using the Enter key (line by
line) or Space bar (page by page). At the end you will be asked to accept the
terms to be allowed to install the product. Select Enter to continue.