The QUERY SAN server command might not
be displaying all the devices because of the SAN configuration.
You might have to refresh the SAN because the configuration
was changed (add/remove device) and the system configuration needs
to be updated.
- Update configuration on AIX®:
- For IBM devices:
- Issue the cfgmgr command to configure new devices
and view the new configuration. The special file name for IBM tape devices
(not the IBM® Tivoli® Storage Manager devices)
is /dev/rmtX for tape drives and /dev/smcX for medium changers.
Tip: Special file name: /dev/rmt0, /dev/smc0
- For the Tivoli Storage
Manager devices:
- To update the special files, use , then discover
devices supported by Tivoli Storage
Manager.
The special file name is /dev/mtX for tape drives and /dev/lbX for
medium changers.
Tip: Special file name: /dev/mt0,
/dev/lb0
Alternatively, you can reinstall the IBM device
driver. Tivoli Storage
Manager device
driver updates all the current special file name.
- Update configuration on Windows:
- With the plug and play, the Windows registry
is updated and the device name might change without the need to restart
the computer or have the device driver's involvement. The Tivoli Storage
Manager server detects
the change in a special file name and updates the new special file
name when it accesses the tape devices (during server initialization
or normal operation). The correct device name is updated in the Tivoli Storage
Manager database.
The special file name is /dev/mtA.B.C.D for both Tivoli Storage
Manager devices
and IBM devices,
and /dev/lbA.B.C.C for both Tivoli Storage
Manager devices
and IBM medium
changers. The special file name TapeX is only for IBM tape drives
and ChangerX is only for IBM medium
changes.
Tip: Special file name: mt0.1.0.0, lb0.0.1.0, Tape0,
and Changer0.
- Update configuration on Linux:
The host bus adapter (HBA) gets the most up-to-date configuration
information as a result of the RSCN. Sometimes, the computer must
be restarted to be able to pick up the configuration changes.
- For IBM devices:
- Issue the lin_taped command to reconfigure
devices. The device information can be retrieved from the /proc/scsi/IBMtape file
for tape devices and /proc/scsi/IBMchanger file
for medium changers. The special file name is /dev/IBMTapeX for tape
devices and /dev/IBMChangerX for medium changers.
Tip: Special
file name: /dev/IBMTape0, /dev/IBMChanger0
- For the Tivoli Storage
Manager devices:
- Users can issue autoconf, the Tivoli Storage
Manager device driver
auto configure script. This script resides in the /opt/tivoli/tsm/devices/bin directory
(or in the same directory as the tsmscsi file)
to be able to configure devices and get all the current special file
names and device information. The device special file name is /dev/mtX for
tape devices and /dev/lbX for medium changers.
Tip: Special file name: dev/tsmscsi/mt0, /dev/tsmscsi/lb0
Alternatively,
you can reinstall the IBM device
driver. Tivoli Storage
Manager device
driver updates all the current special file names.
With the Linux pass-thru
device driver for the
Tivoli Storage
Manager devices,
the HBA driver and the generic driver must be reloaded to get all
the current special file names. You have to run the autoconf script
so that the
Tivoli Storage
Manager device
driver can create configuration files (
/dev/tsmscsi/lbinfo and
/dev/tsmscsi/mtinfo).
These files are used by the
Tivoli Storage
Manager server to
create the special file names after each SAN discovery.
- 32 bits (Linux xSeries®)
- Ensure that the HBAAPI wrapper library libhbaapi32.so is in the
same directory as dsmserv or in the /opt/tivoli/tsm/server/bin directory.
- 64 bits (Linux pSeries)
- Ensure that the HBAAPI wrapper library libhbaapi64.so is
in the same directory as dsmserv or in the /opt/tivoli/tsm/server/bin directory.
- 64 bits (Linux zSeries®)
- Ensure that the pseudo-HBAAPI wrapper library libhbaapi64.so is
in the same directory as dsmserv or in the /opt/tivoli/tsm/server/bin directory.
The wrapper library, libhbaapi64.so, is a link
to the /usr/lib64/libzfcphbaapi.so file.
- Update the configuration on Oracle Solaris:
The HBA gets the most up-to-date configuration information
as result of the RSCN. Most of the time, the computer must be restarted
to pick up the configuration changes. Reinstall the IBM device
driver package or the Tivoli Storage
Manager device driver
package and run autoconf. Or issue the rem_drv and add_drv commands
to reconfigure devices and update the special file name:
- For IBM devices:
- The IBM device
driver has already completed configuring the devices after installing
the device driver package. The /opt/IBMtape/tapelist -l command
can show all IBM device
information on the system. The special file name is /dev/rmt/Xst for
tape devices and /dev/rmt/Xsmc for medium changers.
Tip: Special file name: /dev/rmt/0st, /dev/rmt/0smc
- For Tivoli Storage
Manager devices:
- Modify /usr/kernel/drv/mt.conf and /usr/kernel/drv/lb.conf and
ensure that name="mt" parent="pseudo" instance=16383; and
name="lb" parent="pseudo" instance=16383; are not commented
out in the mt.conf and lb.conf files.
Ensure that each entry for a device in /usr/kernel/drv/lb.conf and /usr/kernel/drv/mt.conf is
correct. After running autoconf, device information can be found in
the mtinfo and lbinfo files
in the /opt/tivoli/tsm/devices/bin directory
or the same directory as the autoconf script. The special file name
is /dev/rmt/Xmt for tape drives and /dev/rmt/Xlb for
medium changers.
Tip: Special file name: /dev/rmt/0mt, /dev/rmt/0lb
Important: Ensure that the two pseudo devices, /devices/pseudo/mt@16383:tsmmtctl and /devices/pseudo/lb@16383:tsmlbctl,
are in the /devices/pseudo directory.
Ensure
that the pseudo device special files, /dev/tsmmtctl and /dev/tsmlbctl are
linked to their corresponding pseudo devices in /devices/pseudo/mt@16383:tsmmtctl and /devices/pseudo/lb@16383:tsmlbctl.