Big Thanks to all who helped me fix the problem
My Friend Bashar Hijjawi
Luke A. Ka
and all who sends me
The solution is just change the GBIC modules on both sides (A5000, E4000)
IB. then in stall the patches mentioned in the new A5x00 software/Firmware
comply with the sequence in patch instalation.
Original Question is .
please be patient to read this.
we have an E4000 system running solaris 2.6, 8 processors, 4GB memory and
A5000 array of 14 FC-AL disks (ST19171FC) configured to three volumes using
veritas volume manager.
the problem comes up while running a big process which takes more than one
week to finish and it always get interrupted after 3-5 days because the
the following is hung time error messages.. /var/adm/messages
Jun 14 00:10:20 ultra4k unix: sf0: Target 0x33 Reset Failed. Ret=105
Jun 14 00:10:22 ultra4k unix: sf0: sf:Target driver initiated lip
Jun 14 00:10:22 ultra4k unix: ID[SUNWssa.socal.link.5010] socal0: port 0:
Channel is OFFLINE
Jun 14 00:10:22 ultra4k unix: ID[SUNWssa.socal.link.6010] socal0: port 0:
Channel Loop is ONLINE
Jun 14 00:10:23 ultra4k unix: sf0: ELS 0x0 to target 0x3d retrying
Jun 14 00:11:37 ultra4k unix: WARNING:
Jun 14 00:11:37 ultra4k unix: SCSI transport failed: reason 'timeout':
Jun 14 00:20:09 ultra4k last message repeated 16 times
Jun 14 00:20:10 ultra4k unix: WARNING:
Jun 14 00:20:10 ultra4k unix: SCSI transport failed: reason 'timeout':
I searched sunsolve to find out a solution but nothing refer to exact
problem.. there is one patch (106129-03) for Seagate ST19171FC FC-AL disks
not applied .. is it the solution or just waste of time? because to apply
this patch we have to remove all our Veritas Filesystems and build it gain
after applying the patch.??
any body suspect that GBIC modules could be a problem???
I Shall sumarise..
Deya Eddin Atawneh.
Jeraisy UNIX account Supervisor.
TEL: 873-0333, Mobile: 055872795.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:23 CDT