We had similar problems on our F630s. Turns out this was due to the system backplane stack height. The backplane standoffs were about 3mm too short!

Since we have always been running 5.x.x of some flavor I'm not sure if it's OS related or not.

Check to see if the card edges are fully seated in the backplane. The watchdog resets were a problem only after I had reseated all cards and the system was up for a couple of days/weeks (it did vary that much). Flex in the chassis was enough to dislodge the environment card that has the stupid watchdog cable on it. One system was bad enough the CPU board had "intermittent" connection to the rest of the system.

The frustrating part was that Adaptec was the only site in this area to have this problem :( And it took me about 5 weeks to find it wasn't bad hardware.

I went to a local hardware store and picked up some washers to pick up the backplane. A real pain to install but fixed the problems.

After NetApp had found out about this manufacturing problem, all our F630 chassis were replaced with newer rev units that fix the stack height.

Good luck!

____________________________________________________ Steve D'Aurora ESN - Engineering Systems and Network Administrator Adaptec Milpitas, CA, USA

phone: 408 957 2351 fax: 408 957 4895 mailto: nevets@eng.adaptec.com

____________________________________________________

Date: Fri, 05 Feb 1999 09:12:59 -0600 From: John Tatar tatar@dis.anl.gov X-Accept-Language: en MIME-Version: 1.0 To: toasters@mathworks.com Subject: watchdog resets Content-Transfer-Encoding: 7bit

We have had a particularly annoying problem with our 540 filer over the last several months. We keep getting watchdog resets. As a matter of fact we just got another as I was composing this message. We get an average of one every other day.

We have checked the cables, reseated cards, replaced cards, replaced the head. I am going to start replacing the power supplies on the shelves tonight. If that doesn't work, we'll replace the SCSI cables between the shelves and the head.

This problem started after we upgraded the firmware and OS to 1.11a and 5.0.2R3 respectively. Has anyone else experienced this problem? How was the problem resolved?

TIA

--

John J. Tatar Systems & Network Engineering Section Advanced Computer Applications Group Decision & Information Sciences Division Argonne National Laboratory

mailto:tatar@dis.anl.gov or john@tatar.com Office: 630-252-3242 Fax: 630-252-5128 Pager: 630-266-1063 ===================================================================