Filter
Top Products
Chapter 6 HPSS Configuration
388 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
6.8.13.2.4 Vendor Information
1. 3584 UltraScalable Tape Library Planning and Operator Guide GA32-0408-01
2. IBM Ultrium Device Drivers Installation and User's Guide GA32-0430-00.1
3. IBM Ultrium Device Drivers Programming Reference WB1304-01
4. 3580 Ultrium Tape Drive Setup, Operator and Service Guide GA32-0415-00
5. 3584 UltraScalable Tape Library SCSI Reference WB1108-00
6.8.13.3 IBM 3494/3495 PVR Information
6.8.13.3.1 Vendor Software Requirements
HPSS is designed to work with IBM 3494/3495 robots attached to an HPSS server with either RS-
232, Ethernet, or Block Multiplexer (BMUX) control connections. Data paths to the drives will be
SCSI-2 with RS-232 and Ethernet control paths, or BMUX if BMUX control paths are used. The
HPSS PVR must run on a machine with the appropriate version of Library Manager Control Point
(LMCP) device drivers installed.
6.8.13.3.2 Configuration Requirements
When configuring an HPSS PVR to manage an IBM robot, the Drive Address configuration entries
correspond to the device number of the drive. Determine the device number by running the HPSS
tool GetESANumbers for each tape drive in the robot.
The HPSS PVR requires one or two LMCP device special files to access the robot. For AIX systems,
these files are usually named /dev/lmcpX and can be created using the System Management
Interface Tool (SMIT). For a BMUX connected robot, the files can be defined to be a Command Port
or an Asynchronous (Async) Port. The HPSS PVR requires both. By default, the PVR will expect the
Command and Async ports to be named /dev/lmcp0 and /dev/lmcp1 respectively. Control
connections must be made prior to configuration of the /dev/lmcpx devices or undefined errors
may result. For Solaris systems, the symbolic library name defined in /etc/ibmatl.conf (e.g., 3494a)
should be used.
For RS-232 and Ethernet connected robots, the device special files support both command and
async capabilities. If only one device special file is created, the environment variables or
configuration should be set so that both the command and async ports point to that one special file.
It is also possible to create two device special files and arbitrarily select one to be the command port
and the other to be the async port. The PVR can then be configured to recognize the ports as
described above in the BMUX case.
HPSS can share an IBM robot with other tape management systems. If a robot is shared, care must
be taken to make sure that a drive is not used by any other tape management system while that
drive is configured as unlocked in theHPSS PVL. This is important because HPSS periodicallypolls
all of its unlocked drives even if they are not currently mounted. The two LMCP device special files
(or possibly one file in the case of an RS-232 or Ethernet controlled robot) are not available to other
tape management programs. Additional device special files may be created for other programs.