As a followup for this question, can anybody tell me where I would get the drivers for this? It is a HP E-series 712e tape library with LTO4 drives. We are upgrading from RedHat 5.2 to 5.4.
I went out to HP's web site, and the only thing they offered is called LTT, Library and Tape Tools. But it doesn't look like it includes a driver, just diagnostic tools, which won't solve my problems, since people have been telling me I need the driver. If HP doesn't supply one for their own product, where am I supposed to get one? Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 / Toll Free: (866) 796-9226 Cell: (314) 750-8721 -------- Original Message -------- Subject: [ADSM-L] SV: RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers From: Christian Svensson <christian.svens...@cristie.se> Date: Thu, May 13, 2010 3:44 am To: ADSM-L@VM.MARIST.EDU Hi John, When you upgrading RHEL from 5.2 to 5.4. Then does RHEL upgrade the kernel also. That mean you need to download the HP Tape Source Code Drivers again and re-compile them. The TSM Drivers you may have installed, they are only creating links to the correct SG devices that HP drivers are creating. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms ________________________________________ Från: John D. Schneider [john.schnei...@computercoachingcommunity.com] Skickat: den 13 maj 2010 06:42 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Len, The IBMTape drivers are intended only for the IBM tape drives. For all others (such as the HP in my case), the TSM drivers are what TSM wants us to use. So I believe that we are using the right sort of driver, and it has been working for some months; the problem only arose when we upgraded RedHat from 5.2 to 5.4. Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 / Toll Free: (866) 796-9226 Cell: (314) 750-8721 -------- Original Message -------- Subject: Re: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers From: Len Boyle <len.bo...@sas.com> Date: Wed, May 12, 2010 11:29 pm To: ADSM-L@VM.MARIST.EDU Hello John, I have not used tsm on Linux, but I have used ibm tape drives on linux. I used the ibm lintape driver. These tape drives were fc based. I am not sure if your tape drives are fc based. I am also not sure if the lintape driver supports scsi tape drives. I do have a tsm server running on windows and they recommended that we use the ibm tape drivers and not the tsm drivers for the newer tape drives. So I am doing a bit of guessing here. Since the tape driver is the piece between the os and the hardware I would expect that be the first part that needs looking at. It might be a change in the o/s api used by the tape driver. With the lintape driver you can test out the tape drive without tsm running. Do you have another box that you can test out the different tape drivers and tape drives? I just looked at the lintape readme and it appears that it only is supported with IBM devices. Does HP supply drivers for use with their tape drives and Linux? You might want to call IBM service for tsm and see what they might suggest. --------------------------------------------------------------------------------------------------------- I remember seeing this note on a past adsm-l mailing list entry. "Re: Library unavailable Michael Green Mon, 06 Jul 2009 23:23:45 -0700 I don't know about 3583, but with 3584 one shouldn't use the TSM supplied drivers. IBM provides a so called 'lintape' (ex IBMtape) driver on their FTP." ------------------------------------------------------------------------------------------------------ len -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 11:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Len, Thanks for your reply. No, we did not upgrade any of the TSM software, including the tape drivers. We were running the TIVsm-tsmscsi-6.1.3-1.x86_64 version both before and after the RedHat 5.2 to 5.4 upgrade. I have since found out that there is a 6.1.3-3 version of the driver. Since they are running the 6.1.3.3 version of TSM, they probably should be running that version of the driver, too. I don't know why or why not, since that is before they became my customer. The previous TSM admins that set all this up are no longer working for this company. But I hesitate to recommend upgrading the drivers as a course of action unless I can point to a concrete reason why. I went through the Release Notes and Readmes and could not find any hint of a driver problem being addressed. None of the tape driver APARs described since 6.1.3 in this Technote sound like they have anything to do with our problem: http://www-01.ibm.com/support/docview.wss?uid=swg21320763 Any insight would be appreciated. Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 / Toll Free: (866) 796-9226 Cell: (314) 750-8721 -------- Original Message -------- Subject: Re: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers From: Len Boyle <len.bo...@sas.com> Date: Wed, May 12, 2010 8:53 pm To: ADSM-L@VM.MARIST.EDU Did you upgrade the tape drivers? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of John D. Schneider Sent: Wednesday, May 12, 2010 5:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] RedHat 5.2 to 5.4 upgrade causes problems for TSMscsi tape drivers Greetings, I have a customer running TSM 6.1.3.3 under RedHat Linux 5.2. The Library Master instance on this server has a HP ESL722 tape library with LTO4 tape drives, and a HP VTL emulating a ESL tape library with LTO3 drives. They are running the TSMscsi drivers to talk to the drives, version TIVsm-tsmscsi-6.1.3-1.x86_64. Any time they reboot the server, they execute: cd /opt/tivoli/tsm/devices/bin ./autoconf -a which loads the tsmscsi driver and configures the drives. This has been working fine for months now. The output is: ****************************************** * IBM TIVOLI STORAGE MANAGER * * Autoconf Utility Program for Linux * ****************************************** Licensed Materials - Property of IBM (C) Copyright IBM Corporation 2009. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Added the read and write permissions for all users to /dev/sg35. Added the read and write permissions for all users to /dev/sg36. Added the read and write permissions for all users to /dev/sg37. Added the read and write permissions for all users to /dev/sg38. Added the read and write permissions for all users to /dev/sg39. Added the read and write permissions for all users to /dev/sg40. Added the read and write permissions for all users to /dev/sg41. Added the read and write permissions for all users to /dev/sg42. Added the read and write permissions for all users to /dev/sg43. Added the read and write permissions for all users to /dev/sg44. Added the read and write permissions for all users to /dev/sg45. Added the read and write permissions for all users to /dev/sg46. Added the read and write permissions for all users to /dev/sg47. Added the read and write permissions for all users to /dev/sg48. Added the read and write permissions for all users to /dev/sg49. Added the read and write permissions for all users to /dev/sg50. Added the read and write permissions for all users to /dev/sg51. Added the read and write permissions for all users to /dev/sg52. Added the read and write permissions for all users to /dev/sg53. Added the read and write permissions for all users to /dev/sg54. Added the read and write permissions for all users to /dev/sg55. Added the read and write permissions for all users to /dev/sg56. Added the read and write permissions for all users to /dev/sg57. Added the read and write permissions for all users to /dev/sg58. Added the read and write permissions for all users to /dev/sg59. Added the read and write permissions for all users to /dev/sg60. Added the read and write permissions for all users to /dev/sg61. Added the read and write permissions for all users to /dev/sg62. Added the read and write permissions for all users to /dev/sg63. Added the read and write permissions for all users to /dev/sg64. Added the read and write permissions for all users to /dev/sg65. Added the read and write permissions for all users to /dev/sg66. Tivoli Tape Drives: =================== Index Minor Host CHN ID LUN Type Vendor_ID Device_Serial_Number Product_ID Rev. 000 035 001 000 000 000 001 HP MXP09210N5 Ultrium 4-SCSI H36W 001 036 001 000 001 000 001 HP HU18282JH5 Ultrium 4-SCSI H36W 002 037 001 000 002 000 001 HP HU17340A0J Ultrium 4-SCSI H36W 003 038 001 000 003 000 001 HP MXP09210MC Ultrium 4-SCSI H36W 004 040 003 000 001 000 001 HP HU18494CGF Ultrium 4-SCSI H36W 005 041 003 000 002 000 001 HP MXP09190H5 Ultrium 4-SCSI H36W 006 042 003 000 003 000 001 HP HU19024M8Y Ultrium 4-SCSI H36W 007 044 004 000 000 001 001 HP 025qFkNO01 Ultrium 3-SCSI R210 008 045 004 000 000 002 001 HP 025qFkNO02 Ultrium 3-SCSI R210 009 046 004 000 000 003 001 HP 025qFkNO03 Ultrium 3-SCSI R210 010 047 004 000 000 004 001 HP 025qFkNO04 Ultrium 3-SCSI R210 011 048 004 000 000 005 001 HP 025qFkNO05 Ultrium 3-SCSI R210 012 049 004 000 000 006 001 HP 025qFkNO06 Ultrium 3-SCSI R210 013 050 004 000 000 007 001 HP 025qFkNO07 Ultrium 3-SCSI R210 014 051 005 000 000 000 001 HP HU17430JKJ Ultrium 4-SCSI H36W 015 052 005 000 001 000 001 HP MXP09190H4 Ultrium 4-SCSI H36W 016 053 005 000 002 000 001 HP HU18413JBJ Ultrium 4-SCSI H36W 017 054 005 000 003 000 001 HP MXP09170DG Ultrium 4-SCSI H36W 018 055 006 000 000 000 001 HP 025qFkNO08 Ultrium 3-SCSI R210 019 056 006 000 000 001 001 HP 025qFkNO09 Ultrium 3-SCSI R210 020 057 006 000 000 002 001 HP 025qFkNO0a Ultrium 3-SCSI R210 021 058 006 000 000 003 001 HP 025qFkNO0b Ultrium 3-SCSI R210 022 059 006 000 000 004 001 HP 025qFkNO0c Ultrium 3-SCSI R210 023 060 006 000 000 005 001 HP 025qFkNO0d Ultrium 3-SCSI R210 024 061 006 000 000 006 001 HP 025qFkNO0e Ultrium 3-SCSI R210 025 062 006 000 000 007 001 HP 025qFkNO0f Ultrium 3-SCSI R210 026 063 007 000 000 000 001 HP HU19044R76 Ultrium 4-SCSI H36W 027 064 007 000 001 000 001 HP HU18383947 Ultrium 4-SCSI H36W 028 065 007 000 002 000 001 HP MXP09210N8 Ultrium 4-SCSI H36W 029 066 007 000 003 000 001 HP HU181720AU Ultrium 4-SCSI H36W Tivoli Medium Changer Devices: ============================== Index Minor Host CHN ID LUN Type Vendor_ID Device_Serial_Number Product_ID Rev. 000 039 003 000 000 000 008 HP 2U10630005 ESL E-Series 6.23 001 043 004 000 000 000 008 HP 025qFkNO00 ESL E-Series 2.00 Yesterday they tried to upgrade from RedHat 5.2 to 5.4. We didn't change anything on the TSM software. The upgrade went fine, and after the reboot onto the new kernel, they went through the same routine of running "autoconf -a". This time when the TSM Library Master came up, it got I/O errors on each of the drives, and was not able to mount anything. It said it initialized the Library OK, but I have no way to know if that was really true. We were not able to figure out the why RedHat 5.4 caused TSM to have a problem. so eventually had to reboot on the old RedHat 5.2 kernel. They we ran "autoconf -a", brought up the TSM Library master, and everything worked fine. So the problem is definitely between RedHat 5.2 and 5.4. Has anyone seen a problem like this, and can give us some insight? Best Regards, John D. Schneider The Computer Coaching Community, LLC Office: (314) 635-5424 / Toll Free: (866) 796-9226 Cell: (314) 750-8721
