You're right guys : LTO Library's are supported since earlier versions, but
I couldn't get
our new IBM Ultrium Tape Library completely working without doing the
upgrade from 4.1.0 to
4.1.3 (which adds the lto devtype).
I could find this in the README File (and wrongly assumed LTO wasn't
supported before, but it is,
through the generictape devtype): Sorry about that !
Nonetheless maybe it can still help some people :
Part of the readme file of the 4.1.3 update.
$$1 o Support for IBM LTO Ultrium (358x) devices
**********************************************************************
TSM supports the IBM 3580, 3581, 3583 and 3584 LTO Ultrium products on the
AIX, NT 4.0 and NT 5.0 platforms.
- The IBM 3580 is a stand-alone drive.
- The IBM 3581, 3583 and 3584 are automated libraries.
Users must use the SSD RMSS device drivers on these platforms to recognize
and configure the IBM 3580, 3581, 3583 and 3584.
To obtain the correct level of the device driver, review the README files
in the ftp.software.ibm.com/storage/devdrvr.
To define the device class, users should use the following:
DEFINE DEVCLASS device_class_name DEVTYPE=LTO
FORMAT=[DRIVE or ULTRIUM or ULTRIUMC]
LIBRARY=library_name
NOTE: For RSM, the DEVTYPE is LTO instead of GENERICTAPE. All other
devices will continue to be defined with DEVTYPE=GENERICTAPE.
On the AIX and NT 4.0 platforms, users should define the IBM 3581, 3583
and 3584 automated libraries as follows:
DEFINE DRIVE library_name drive_name DEVICE=<device_special_file>
ELEMENT=<element_number>
On Windows 2000 platform, users should define the IBM 3581, 3583 and 3584
automated libraries as follows:
DEFINE LIBRARY library_name LIBTYPE=RSM MEDIATYPE="LTO Ultrium"
Note that the quotes around "LTO Ultrium" are required.
Users should use standard RSM configuration techniques.
Examples:
On AIX, assuming AIX recognized and configured the medium
changer as /dev/smc0 and the drive as /dev/rmt0:
DEFINE LIBRARY 3584LIB LIBTYPE=SCSI DEVICE=/dev/smc0
DEFINE DRIVE 3584lib rmt0 DEVICE=/dev/rmt0 ELEMENT=104
and so on ....
-----Oorspronkelijk bericht-----
Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Maurice
van 't Loo
Verzonden: donderdag 16 augustus 2001 20:27
Aan: [EMAIL PROTECTED]
Onderwerp: Re: Defining devicetype of LTO
I worked with NSM's with TSM 4.1.0.0 and LTO library's, no problem.....
----- Original Message -----
From: "wouter-v" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 16, 2001 3:32 PM
Subject: Re: Defining devicetype of LTO
> You need at least TSM V 4.1.3 to have support for LTO devices !!
>
> When your are sure about this you can use the command (for example) :
> def devclass tape_class devtype=lto format=drive library=ltolib
>
> Wouter Verschaeve
>
>
> >===== Original Message From "ADSM: Dist Stor Manager"
<[EMAIL PROTECTED]>
> =====
> >>Thanks but I've tried it from the command line too and still get the
> >>following:
> >>
> >>define devc lto library=lto3583 estcap=100g devt=lto format=drive
> >>ANR2020E DEFINE DEVCLASS: Invalid parameter - LTO.
> >
> >Doing 'HELP DEFINE DEVCLASS' should show what devices your current
> >software is capable of supporting, as the embedded help info is
> >supposed to exactly match the software level.
> >
> > Richard Sims, BU
>
