In message 7F608EC0BDE6D111B53A00805FA7F7DA0200F6CA@TAHOE.netapp.com, "Bul fer, David" writes:

Check out http://now.netapp.com/misc/sw_release.shtml

David

So who tested cluster takeover/giveback during the "comprehensive development and release procedure"...? Can they tell me what I'm doing wrong? Was bug 14194 (Filer crashes during boot during partner giveback) discovered during this testing and 5.3 was released anyway? If so, I think you guys are carrying that MS partnership a bit too far...

Ok, maybe comparing you guys to MS was below the belt. I'll take that back. But I'm still curious how 5.3 made it as far as it did? I thought clustering was the hot new thing at NetApp.

Did somebody decide a boot during giveback was ok for now? It's not a problem until the partner s fixed or until your testing to see that you got what you paid for. If this was the case, a "known bugs list" would've been nice.

disappointed,

jason

-----Original Message----- From: Jason D. Kelleher [mailto:kelleher@susq.com] Sent: Monday, April 26, 1999 12:22 PM To: toasters@mathworks.com Subject: Early Access Releases

Anyone know what NetApp's "official" stance is on Early Access Releases? Are they beta tested in the field before becomming Early Access? Is anyone who installs an Early Access Release a beta tester? Does NetApp beta test?

Has anyone out there installed 5.3, 5.3D2 (fixes NDMP problems), or 5.3D7 (supposed to fix crash during giveback) on an F740 cluster and successfully done a takeover/giveback without at least one extra reboot (the system doing the giveback) and a core file? If so, were you using second level VIFs? If you were using second level VIFs, and it actually worked, did your messages file list network errors after takover that NetApp said were ok?

I've been working with tech support for over a week now on these issues and my managers just turned up the heat on me. I'm hoping someone has an "it all worked after I did..." story.

any help appreciated,

jason