Hello Vladimir,
A long time ago, we had a problem with timeouts and IBM gave us a sample
st.conf file with different timeout values for the lto tape drives. It was a
long time ago, so I do not know if the error messages match. But you might want
to look at the st.conf file entries for IBM lto-2's. If you are not using sun
hba cards you might also look at the firmware for the hba cards.
len
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Vladimir
Taleiko
Sent: Friday, September 14, 2007 9:22 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] scsi_pkt.us_reason = 3
Hi, all
I have Solaris 9 server with latest microcode/patches installed
NetBackup 6.0 MP4
L180 (IBM LTO2 - 5AT0)
Brocade 3800 (v3.2.1b, dual fabric)
c4 fc-fabric connected configured
unknown
c4::500104f0006e4931,0 med-changer connected configured
unknown
c4::5005076300615978,0 tape connected configured
unknown
c4::500507630061605e,0 tape connected configured
unknown
c5 fc-fabric connected configured
unknown
c5::5005076300615b41,0 tape connected configured
unknown
c5::5005076300615d9b,0 tape connected configured
unknown
c8 fc-fabric connected configured
unknown
c8::500507630061556a,0 tape connected configured
unknown
c8::5005076300615aaa,0 tape connected configured
unknown
c9 fc-fabric connected configured
unknown
c9::5005076300615937,0 tape connected configured
unknown
c9::5005076300615ba3,0 tape connected configured
unknown
and the following errors:
Jul 28 03:13:04 ni5nrp2 bptm[26639]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 28 07:11:25 ni5nrp2 bptm[27999]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 28 07:13:32 ni5nrp2 bptm[27983]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 28 08:42:36 ni5nrp2 bptm[15693]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 29 09:21:34 ni5nrp2 bptm[18406]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 29 10:51:12 ni5nrp2 bptm[5955]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 30 00:42:07 ni5nrp2 bptm[27613]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 30 00:52:03 ni5nrp2 bptm[27614]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
Jul 30 01:11:55 ni5nrp2 bptm[27620]: [ID 832037 daemon.error] scsi
command failed, may be timeout, scsi_pkt.us_reason = 3
bptm logs doesn't show any issues.
I've opened two cases in Sun and Symantec.
Sun guys said "There is no errors from scsi layer, call Symantec"
Symantec support said "these errors are being received by the bptm
process, and not being generated by it, please involve SUN"
I'm slightly confused. What is the cause of this errors?
--
Vladimir
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
