ADSM-L

Re: Upgrading IBMTape and lmcpd drivers

2003-11-03 11:50:58
Subject: Re: Upgrading IBMTape and lmcpd drivers
From: Farren Minns <fminns AT WILEY.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 3 Nov 2003 16:34:37 +0000
Thanks for that info. However, you seem a lot more knowledgable than me on
this. I'm not an expert Solaris admin by any means.

When you say HBA, I'm assuming Host Bus Adapter? I know that we use theres
to connect a couple of our servers to a SAN, but our TSM server is just an
E250 attached to the 3590's (SCSI - We have a dual differential SCSI
adapter in the E250). Can I assume that your system uses fibre attached
drives?

Many thanks

Farren Minns
|+-------------------------------+----------------------------------------|
||   Luke Dahl                   |                                        |
||   <ldahl AT JPL.NASA DOT GOV>        |                                       
 |
||   Sent by: "ADSM: Dist Stor   |   To:        ADSM-L AT VM.MARIST DOT EDU     
 |
||   Manager"                    |           cc:                          |
||   <ADSM-L AT VM.MARIST DOT EDU>      |           Subject:        Re: 
Upgrading|
||                               |   IBMTape and lmcpd drivers            |
||   11/03/2003 04:24 PM         |                                        |
||   Please respond to "ADSM:    |                                        |
||   Dist Stor Manager"          |                                        |
||                               |                                        |
|+-------------------------------+----------------------------------------|








The upgrade is pretty straightforward for both IBMtape and lmcpd
drivers.  Be
very sure that you've got supported hba's in your servers - and you may
want to
check with IBM to see if you need to load additional drivers.  We are still
unable to connect to our updated H1A's because of driver issues.  We're
waiting
for the Emulex card to arrive so we can get them up and running.  There are
a
number of files you can modify and your CE should be familiar with this.
At the least you probably need to uncomment this line in the
/kernel/drv/st.conf file:
# This line adds support for Fibre Channel Tapes
#name="st" parent="fp" target=0;

Also, are you attaching directly to your server or are you going through a
switch?  Your CE needs to set hard or soft addressing on the drives
depending
on which one (I believe - my CE argued with me over that but that's what
the
manual says).  Hope this helps.

Luke Dahl
NASA-Jet Propulsion Laboratory
818-354-7117


Farren Minns wrote:

> Hi All TSMers
>
> Running TSM 5.1.6.2 on a Solaris 2.7 server.
>
> This coming week we are having our two 3590 tape drives (housed in an IBM
> 3494 library) upgraded from B1A to H1A format (SCSI attached). As such, I
> know that some sort of upgrade has to be performed on the lib  as well as
a
> full upgrade of the two drives (I'm sure the IBM engineer will be fine
with
> that part).
>
> However, I'm also going to upgrade the IBMTape and  lmcpd drivers to make
> sure I'm fully up to date. My question is, how easy are these upgrades.
> Once I have installed the latest version of these drivers, will there be
> some other configuration (either on the OS of within TSM itself)
necessary.
>
> If anyone out there has done this recently and has any info on this, then
> I'd be very grateful.
>
> Many thanks in advance
>
> Farren Minns - John Wiley & Sons


*****************************************************************************

This email transmission is confidential and intended for the person or
organisation it is addressed to. If you are not the intended recipient, you
must not copy, distribute, or disseminate the information, open any
attachment, or take any action in reliance of it. If you have received this
message in error please notify the sender.

Any views expressed in this message are those of the individual sender,
except where the sender specifically states otherwise.

Although this email has been scanned for viruses you should rely on your
own virus check, as the sender takes no responsibility for any damage
arising out of any bug or virus infection.
*****************************************************************************
<Prev in Thread] Current Thread [Next in Thread>