We just resolved a problem with tape drive paths for library clients
dropping offline. We have been rolling over test systems to new servers
which use shared NPIV based HBA's (AIX lpars sharing VIO based hba's). We
were running v5.4.1 StorageAgents, which turns out don't support NPIV. The
StorageAgent was throwing a errors that it couldn't find the serial number
of the tape drive that the library manager selected for use. We upgraded
to v5.5.1 and the problem was resolved.
To help figure out the problem you're going to have to piece together a
full view of what's happening.
- rmt paths line up correctly between library manager and library client
- library manager: hdwr errors (errpt on AIX), TSM errors, Atape errors
(runnig Atape? in /var/adm/ras)
- library client: hdwr errors, TSM errors (TSm instance where
StorageAgent is sending msgs), Atape errors.
Someone somewhere is throwing an error and you need to find it.
Rick
From: Yuvaraja Shivarama <yuvaraja.deepti AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: 07/20/2011 02:42 PM
Subject: paths going offline from library manager (in this 3
library clients paths are going offline)
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Hi All,
Any body know what could be the problem if the paths are going
offline
very frequently from library manager.
aix-5.5
the paths which are going offline are library clients in that library
manager.
there is no much drives going offline.
no rmt mismatch found and no other issues from server end.
Thanks
Yuvaraja
-----------------------------------------
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.
|
