Here are some things to do . . .
Check that the tape drive is logged into the switch port, and you see the
wwn on the switch port.
Check the tape drive that it sees the san - usually a light indicating a
connection to the san by the cable port (3592's have this, not sure about
3590E's)
Check that the wwn on the switch port is the same as was there previously
(ie: the wwn didn't change)
Check that the zone is correct (you didn't change it . . .but . . .).
Check the wwn on the AIX RMT device matches what you see on the switch port
(lsattr -El rmtX)
(do this for all RMT paths to the tape drive)
Check what atape thinks about the paths (tapeutil -f /dev/rmtX path)
Check that the tsm tape device (wwm, s/n) matches the AIX rmt devices,
which matches the actual tape device.
Try the cable in a different drive that you know works.
Try the drive with a cable from a working drive.
Stick a tape in the drive and try and tar some data onto it (ie: bypass
TSM).
Try bypass cable straight from the tape drive direct to another server with
a open hba, and see if it drive comes in and is usable (tar stuff onto a
tape).
Rick
T
"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: Tape Drive SN issue
.EDU>
04/30/2009 10:40
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
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.
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
|
