ADSM-L

Re: [ADSM-L] Tape Drive SN issue

2009-04-30 11:40:30
Subject: Re: [ADSM-L] Tape Drive SN issue
From: Jo Lay <jolay AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 30 Apr 2009 08:39:14 -0700
Andy,

Do you have TSM SAN Discovery turned on?
If you do, you can perform "q SAN" and look for the drive serial number in
the output of "q san".  If you have ran cfgmgr after you changed GBIC,
TSM SAN Discovery function should be able to get the new path for these
drives using  serial number to match the new san map.

If you have TSM SAN Discovery turned on AND you have used cfgmgr AND you
still have the ANR8963E,  you should report this problem.
We can get a TSM server trace when TSM tries to mount the tape to see what
is going on.

The trace for TSM:

trace enable PVR MMS NA




Regards,

Jo Lay
Tivoli Storage Products, IBM Software Group
jolay AT us.ibm DOT com
Phone: 408-997-7999




                                                                       
             "Huebner,Andy,FOR                                         
             T WORTH,IT"                                               
             <Andy.Huebner@ALC                                          To
             ONLABS.COM>               ADSM-L AT VM.MARIST DOT EDU            
             Sent by: "ADSM:                                            cc
             Dist Stor                                                 
             Manager"                                              Subject
             <[email protected]         Re: [ADSM-L] Tape Drive SN issue
             .EDU>                                                     
                                                                       
                                                                       
             04/30/2009 08:21                                          
             AM                                                        
                                                                       
                                                                       
             Please respond to                                         
             "ADSM: Dist Stor                                          
                 Manager"                                              
             <[email protected]                                         
                   .EDU>                                               
                                                                       
                                                                       




The drives were verified in AIX after GBic change.  Since there was not a
port change there was no effect on AIX.
The library is aware of all of the drives.  I think I mentioned earlier
that the AS/400s that share the library have reported no problems with
these drives.
Thanks for the suggestions, we have looked at so many things it is hard to
recall them all, but we may have missed something simple.

Andy Huebner

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dwight Cook
Sent: Thursday, April 30, 2009 9:54 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Tape Drive SN issue

You are aware that under AIX if any WWN in the path of a drive changes,
then
that constitutes an entirely new device as seen by AIX.  If you replaced
GBics, it possibly could have caused the tape drive to take on a new rmt as
seen under AIX unless you performed a "rmdev -dl rmt_" on the existing
device found down that GBic and then ran cfgmgr afterwards so it would in
fact come back as the same device.

I take it that you have run cfgmgr and checked to see that there are no
new/unexpected rmt's present...  if not, please do that and run "lscfg -vpl
rmt__" against any new rmt's you see to determine if they are the drives
that you are having issues with (SR# cross ck)

Also from a library point of view... from your AIX host system you
performed
an "mtlib -l/dev/lmcp__ -qD"  to ck that the library does in fact still see
the drives.

Dwight


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Huebner,Andy,FORT WORTH,IT
Sent: Thursday, April 30, 2009 9:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Tape Drive SN issue

Update:
We turned on TapeAlertMSG - no new messages
We have changed the GBics on the switches - No change
We had IBM do a health check on the drives - Last abnormal error was months
earlier on one drive.  The other two were clean.
We have updated the firmware to the same version as a drive not having the
issue.  The troubled drives were slightly lower version - No change
We updated the drives to the current firmware - No change
We swapped cables with one of the working drives - No change
We verified the cabling on all drives - It was done right
We have opened a case - Waiting for call back.
We have considered kicking it - Might dent it.
We have run out of ideas - Heads are being scratched.

The question is what did we miss?


Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Huebner,Andy,FORT WORTH,IT
Sent: Monday, March 30, 2009 11:18 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Tape Drive SN issue

The error occurs when TSM attempts to mount a tape.  We have had no
problems
deleting and defining these paths, which I should have included in the
first
message.

Andy Huebner

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kelly Lipp
Sent: Monday, March 30, 2009 10:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Tape Drive SN issue

I assume these message occur when you try to define the path?

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Huebner,Andy,FORT WORTH,IT
Sent: Monday, March 30, 2009 9:50 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Tape Drive SN issue

We have a three drives that generate these messages and we are unable to
use
the drives because the path will not stay on-line.  We have not been able
to
find a solution to this problem.

03/30/2009 04:30:41  ANR8963E Unable to find path to match the serial
number
                      defined for drive L1R3DR1 in library IBM3494A .
(SESSION:
                      139365)
03/30/2009 04:30:41  ANR8873E The path from source TSMSERVER1 to
destination
                      L1R3DR1 (/dev/rmt13) is taken offline. (SESSION:
139365)

These are 3590-E drives; the other 21 do not have this problem.

The 24 drives are in one 3494 library, the library is shared by 2 TSM
servers, 1 TSM server is the library manager.  There are also 8 AS/400
LPARs
that use the library.  There have not been any problems reported by the
AS/400.
The problem started a few months ago with no known changes.
The AIX error logs do not show any problems, the fiber switch also does not
show any errors.  IBM has checked the drives and they do not show any
errors.
These drives are on different HBA's and different FC switches, both of
which
have working drives.
AIX has been restarted, due to other reasons, and that did not fix the
problem.  The drives have been reset and power cycled.
We are running AIX 5.3 & TSM 5.4.2.0.

What have we missed, what could be looked at next?  Does ANR8963E have a
hidden meaning?


Andy Huebner


This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using,
copying or distributing the information in this e-mail or its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and any
attachments.
Thank you.


This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using,
copying or distributing the information in this e-mail or its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and any
attachments.
Thank you.


This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using,
copying or distributing the information in this e-mail or its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and any
attachments.
Thank you.


This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using,
copying or distributing the information in this e-mail or its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and any
attachments.
Thank you.

<Prev in Thread] Current Thread [Next in Thread>