From: Geoff Lane (zzassgl@zoe.mcc.ac.uk)
Date: Wed May 05 2004 - 09:55:22 EDT
After some investigation and swapping of components, Sun have decided that
there may be a problem with the controller hardware and are sending an
engineer to conduct some tests.
Thanks,
On Thu, Apr 29, 2004 at 11:56:13AM +0100, Geoff Lane wrote:
> I'm having problems with a 3510 RAID box connected by fibre to a V480 server
> running Solaris 9 (with current recommended patches) via a JNI card. The
> 3510 and it's disks have the current recommended firmware, the management
> software is all at the current recommended release and patch level. (The
> s/w levels are all as recommended by Info Doc ID75203.)
>
> About once a day the following message appears and the RAID filesystems on
> the 3510 are corrupted...
>
> SUNWscsdMonitor[2173]: [ID 921123 daemon.error]
> [SUNWscsd 0x01060801:0x00000000 Critical] <rctrl3040> Unable to inquire Raid
> Controller. Chassis FRU Item: 370-5535-02 Serial No: 07BB9D HW Revision: 02
> Description: SE3510 FC Chassis/backplane Vendor JEDEC ID: 0x0301 Date: Thu
> Jan 8 13:41:16 2004 {Unique ID#: 07bb9d}
>
> Sometimes communication is re-established automatically. In this particular
> case I forced it by unplugging/plugging the fibre.
>
> jfca: [ID 275905 kern.info] jfca0: Link Down
> jfca: [ID 551951 kern.info] jfca0: Auto-Configured as Private Loop port
> jfca: [ID 118468 kern.info] jfca0: Link Up: 2Gig Loop SUNWscsdMonitor[2173]: [ID 298698 daemon.error]
> [SUNWscsd 0x03060803:0x00000000 Informational] <rctrl3040> Communication is
> reestablished with controller. {Unique ID#: 07bb9d}
>
> Everything checks out on the 3510 and it's disks. Everything I can look at
> via sccli looks OK. The JNI card only generates the normal boot time
> messages
>
> jfca: [ID 549544 kern.info] jfca0: Hba: SUNW,jfca Model: FCX-6562-L
> jfca: [ID 874998 kern.info] jfca0: FCode: Version 1.0 [F16]
> jfca: [ID 843335 kern.info] jfca0: IRQ: 1 Channel: 0
> jfca: [ID 601529 kern.info] jfca0: SubVend: 1242 Sub: 656c Rev: b200 Vend: 1242 Dev: 1560
> jfca: [ID 500909 kern.info] jfca0: WWNN: 1000000173012DB4 WWPN: 2000000173012DB4
> jfca: [ID 204285 kern.info] jfca0: Auto-negotiating link speed
> jfca: [ID 550636 kern.info] jfca0: Topology configuration is set to Auto-Negotiate
> jfca: [ID 861892 kern.notice] jfca0: SunFC JNI FCA v20040307-1.24
> jfca: [ID 333312 kern.notice] jfca0: Copyright(c) 1995-2003 JNI Corp, All Rights Reserved.
> jfca: [ID 551951 kern.info] jfca0: Auto-Configured as Private Loop port
> pcisch: [ID 370704 kern.info] PCI-device: SUNW,jfca@1, jfca0
> genunix: [ID 936769 kern.info] jfca0 is /pci@8,600000/SUNW,jfca@1
> genunix: [ID 936769 kern.info] fp1 is /pci@8,600000/SUNW,jfca@1/fp@0,0
> jfca: [ID 275905 kern.info] jfca0: Link Down
> jfca: [ID 551951 kern.info] jfca0: Auto-Configured as Private Loop port
> jfca: [ID 118468 kern.info] jfca0: Link Up: 2Gig Loop
>
>
> This is our first 3510/JNI configuration so I'm now stumped.
>
> Is there a way to check out the JNI card operation short of replacing it?
>
> Could there be a problem with the Fibre cable itself?
>
> Thanks, summary will follow,
>
> --
> | Geoff. Lane | Manchester Computing | Manchester | M13 9PL | England |
>
> "Bother", said Pooh, as he failed the dope test.
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
-- | Geoff. Lane | Manchester Computing | Manchester | M13 9PL | England | An efficient government is a cruel government _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:28:36 EDT