What we finally wound up doing was using the HP Win2K driver. Still, the drive reports as TSM Device Type Unknown, but it seems to work just fine.
Wow, that damn thing is very fast: ~10 GB in 15 minutes. I'll do more comprehensive testing tomorrow and Monday and report what I learn. I'll do the same thing on SDLT. Thanks, Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Tab Trepagnier Sent: Thursday, November 08, 2001 5:24 PM To: [EMAIL PROTECTED] Subject: Re: HP LTO Drives and TSM Kelly, I'm not sure about Ultrium specifically, but your question, "...the only thing I can think is that the drive firmware is sufficiently different from what was tested but that seems pretty farfetched. Perhaps a Tivoli person can fill us in, at least generically, how device support is determined..." is very possible. That is exactly what happened to us with our new HP 4/40 DLT library. The HP library arrived with firmware version 1.25.0. The TSM device driver did not work at all - even lbtest failed. After calling Tivoli and HP it was determined that the driver (we were at 4.1.2.0 at the time) was developed using firmware version 1.13.0. The newer firmware version was returning more data than expected in response to certain queries and overrunning the driver's receive buffer. There was an APAR on that and it had been closed. Tivoli reopened it. HP published their SCSI command set implementation as a PDF on their web site and I sent that PDF to Tivoli development for reference. With the release of TSM 4.1.4.0 the new driver was included and that worked AOK with the new firmware. In fact, right now we are using firmware 1.30.0 and TSM is working fine. But that doesn't mean that situation couldn't happen again. Good luck. Tab Trepagnier TSM Administrator Laitram Corporation
