ONTAP Discussions
ONTAP Discussions
Hi
Can anybody share a documentation about Netapp FIFO string decoding?
There is a topic in NCSE exam "Describe how to decode FIFO strings", I can find NO information about it.
Any information is appriciated.
Thank you
Nick
I am aware of a single internal KB article that mentions it. May be some information is contained in service partner training, but those materials I have do not have anything.
I got feeling that exam is heavily oriented towards internal stuff, not partners.
Thanks for a quick reply Andrei.
I struggled with FIFO during NAHSE certification, and I picked tiny pieces of information in bug reports.
Can you share anything you have? If you can't do that, can you share KB internal id/URL, I can ask Netapp staff to send it to me?
NCSE-Specialist and NCSE certifications are mandatory for FY19 ONTAP Support Specialist, which is (was) required for partner ASP status.
Looks like I've found information:
https://kb.netapp.com/app/answers/answer_view/a_id/1071055
The following FIFO string is reported when running the sp status -d
command:
ONTAP Shutdown BBSP:C=00 L=2F FIFO: F0 F1 F3 F2 5 B2 0 0 10 84 20 E F E0 C0 C2 D E F 10 12 13 14 14 15 15 13 12 16 17 19 19 1A 1A 17 16 1B 1B 1C 1C 10 F 1E 1E 1F 1F E D D E F 10 12 13 14 14 15 15 13 12 16 17 19 F2 F1 F0 F3
Break down the FIFO string into the individual components:
<F2 F1 F3 F2> # all 4 cores enter machine check handler
<5 B2 0 0 10 84 20 E F> # machine check bank 5 records the error, status
<E0> # core 0 is handling the machine check error
<C0> # enter chipset error handler
<C2> # enter PCI error handler
<D E F 10 12 13 14 14 15 15 13 12 16 17 19 19 1A 1A 17 16 1B 1B 1C 1C 10 F 1E 1E 1F 1F E D> # PCI bus has been probed once, no hangs
@Nick4704, which FIFO string should NOT be used to determine root cause?
A) before NMI BBSP: C=00 L=00
B) BIOS exit BBSP:C=2F L=00
C) ONTAP shutdown BBSP:C=00 L=2F
D) before reset BBSP: C=00 L=00
before NMI BBSP: C=00 L=00
FIFO F0 F1 F3 F> # all 4 cores enter machine check handler