Some comments in no particular order . . .
If you think it's a bad hba, and you are sharing the hba with disk+tape,
then it would effect both.
Are you seeing any errors in the AIX error log? (errpt cmd)
You have a EMC SAN with Navi. . . . are you using PowerPath? If yes, does
it show any errors? (powermt display)
Check the SAN switch ports for errors both on the hba->switch legs,
switch->tapedrive legs, any ISL legs.
The errors you list are all from a Audit cmd run. Do you get any errors
when the tapes are written?
Do the tape drives need cleaning?
If you can get TSM to run an Audit of a tape on different tape drives, do
you get errors from both tape drive for the same tape?
How new/old are the tapes? A long time ago when we had LTO1 tapes, new
tapes would cause all kinds of errors until they were completely used once.
"Prather, Wanda"
<wprat...@icfi.co
M> To
Sent by: "ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor cc
Manager"
<ads...@vm.marist Subject
.EDU> Re: ANR8311E errors
03/23/2010 09:40
AM
Please respond to
"ADSM: Dist Stor
Manager"
<ads...@vm.marist
.EDU>
You may be one of the folks that can't get away with having disk and tape
I/O on the same HBA.
If you can, replace that HBA card with a 2-port HBA card, and separate the
tape from the disk I/O.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Adrian Compton
Sent: Tuesday, March 23, 2010 1:53 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] ANR8311E errors
It is different tapes and different drives.
I am starting to think it could be the HBA FC card in the physical blade
that connets to the backplane of the Blade Chassis.
The tapes are ok, and it will happen on a new tape as well. All drive tests
come out as ok with now errors.
Regards
Adrian Compton
Group IT Infrastructure
Aspen Pharmacare Port Elizabeth
tel: +2741 4072855
Fax: +2741 453 7452
Cell: +27828617745
Email: acomp...@aspenpharma.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Prather, Wanda
Sent: 19 March 2010 17:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] ANR8311E errors
When you say "sporadically", do you mean this tape is really OK and the
errors are transient?
If you run AUDIT on this tape on the same drive, at another time, does the
tape read OK?
Or does the same tape always fail?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Adrian Compton
Sent: Friday, March 19, 2010 2:05 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] ANR8311E errors
Hi all
We are using a JS12 Blade in a IBM Blade Centre running AIX 5300-10,
Atape.driver 12.0.4.0, EMC SAN using NAVIAGENT and NAVICLIENT 6.28.21.0.
Tape and SAN traffic running through the Blade FC Card, and the other FC is
configured as failover. We are using this config in Mauritius and do not
have any errors at all.
The Tape Library is a TS3310 with a 9U expansion unit, and all licensing is
configured.
We have 4 x LTO3 FC 4GB Drives.
The Library is running firmware as below:
3576-MTL Firmware Version
570G.GS025
Robot Firmware Version
102Q.GR004
Imager Firmware Version
000
BSP Level
6.73
Last Update
10/14/2009 9:34
The drives firmware is as below:
Drives:
93G0
TSM Server Enterprise Edition is running at version 5.5.2, with a 2TB disk
storage pool on the SAN, that is used for OS/NT level backups.
All DB/Large/streaming structure backups go to Tapepools.
Current errors from the TSM actlog are as follows, and these same errors
are experienced sporadically as well during other operations such as
migration/reclaim etc, so not only limited to reads:
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for RDBLKID operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVXMB01_EXCH, Type Backup
(Active), Filespace ABOVXMB01\Second Storage Group, fsId 2, File Name \data
\0000\Mailbox Database 2\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVXMB01_EXCH, Type Backup
(Active), Filespace ABOVXMB01\Second Storage Group, fsId 2, File Name \logs
\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVSAPP01_DB, Type Backup
(Active), Filespace /APR, fsId 1, File Name \NODE0000\
DB_INCR_BACKUP.20100314230307.1.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVSAPP01_DB, Type Backup
(Active), Filespace /APR, fsId 1, File Name \NODE0000\
DB_INCR_BACKUP.20100314230307.2.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVSAPD01_DB, Type Backup
(Active), Filespace /ADV, fsId 1, File Name \NODE0000\
DB_INCR_BACKUP.20100315000307.1.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVSAPD01_DB, Type Backup
(Active), Filespace /ADV, fsId 1, File Name \NODE0000\
DB_INCR_BACKUP.20100315000307.2.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\data\0001, fsId 2, File Name \citrix\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\meta\0000, fsId 1, File Name \citrix\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\data\0001, fsId 2, File Name \master\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\meta\0000, fsId 1, File Name \master\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\data\0001, fsId 2, File Name \model\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\meta\0000, fsId 1, File Name \model\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\data\0001, fsId 2, File Name \msdb\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVLIC01_SQL, Type Backup
(Inactive), Filespace ABOVLIC01\meta\0000, fsId 1, File Name \msdb\ full.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVSAPS01_DB, Type Backup
(Active), Filespace /ASM, fsId 1, File Name \NODE0000\
DB_INCR_BACKUP.20100315013308.1.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for LOCATE operation, errno = 79.
3/18/2010 8:28:23 AM ANR2335W Audit Volume has encountered an I/O error for
volume ABO015L3 while attempting to read: Node ABOVSAPS01_DB, Type Backup
(Active), Filespace /ASM, fsId 1, File Name \NODE0000\
DB_INCR_BACKUP.20100315013308.2.
3/18/2010 8:28:23 AM ANR8311E An I/O error occurred while accessing drive
LTO3DR2 (/dev/rmt0) for OFFL operation, errno = 79.
I really appreciate your input and assistance. I am pulling my hair out now
and IBM is confused as well.
Regards
Adrian Compton
Group IT Infrastructure
Pharmacare Limited trading as Aspen Pharmacare P O Box 4002 Korsten Port
Elizabeth
6014
-----------------------------------------
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.
