ONTAP Hardware
ONTAP Hardware
Hi there,
We're running DOT 7-mode (v8.0.2) and just experienced a failover on our filer2. I've run the following commands from the sp on that filer and attached the output:
I did notice in the system logs this error preceded the failover:
PANIC: nested machine check exception detected on CPU 2, no coredump will be generated.
If someone could provide me with some insight into this error and how serious it is I would appreciate it, we would like to giveback but are unsure if that is wise.
Thanks,
~ Jon
Solved! See The Solution
Jon -
I ran the err message through the Data ONTAP Panic Message Analyzer on mysupport.netapp.com.
Response: 'The panic message could not be safely matched to a single bug.'
8.0.2 Is an older release - you might want to consider doing an upgrade soon.
Given no signs of hardware failure, you're probably OK to do the giveback...
I hope this response has been helpful to you.
At your service,
Eugene E. Kashpureff, Sr.
Independent NetApp Consultant http://www.linkedin.com/in/eugenekashpureff
Senior NetApp Instructor, IT Learning Solutions http://sg.itls.asia/netapp
(P.S. I appreciate 'kudos' on any helpful posts.)
Jon -
I ran the err message through the Data ONTAP Panic Message Analyzer on mysupport.netapp.com.
Response: 'The panic message could not be safely matched to a single bug.'
8.0.2 Is an older release - you might want to consider doing an upgrade soon.
Given no signs of hardware failure, you're probably OK to do the giveback...
I hope this response has been helpful to you.
At your service,
Eugene E. Kashpureff, Sr.
Independent NetApp Consultant http://www.linkedin.com/in/eugenekashpureff
Senior NetApp Instructor, IT Learning Solutions http://sg.itls.asia/netapp
(P.S. I appreciate 'kudos' on any helpful posts.)
What the others said, please do an uprade sooner rather than later. 8.0.2 is rather old and since it's an unpatched release contains a few annoying bugs... your NetApp partner should be able to tell you more about it and help you upgrade your system.
The hardware in question isn't, by chance, a FAS3140? We had similar problems with a few 3140's once which were only fixed by upgrading everything to a more recent version (OnTap, BIOS, disk/shelf firmware, etc.)
Thanks for the feedback, we did a giveback a few days ago, so far so good.
We're in the process of migrating to a new cDOT 8.3P1 cluster.