Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 0d 19h 45m 15s Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

NetApp Exam NS0-093 Topic 4 Question 12 Discussion

Actual exam question for NetApp's NS0-093 exam
Question #: 12
Topic #: 4
[All NS0-093 Questions]

In which two sections of AutoSupport can you find information to analyze the following panic? (Choose two.)

Panic_Message: PCI Error NMI from device(s):ErrSrcID(CorrSrc(0xf00),UCorrSrc(0x18)), RPT(0,3,0):Qlogic FC 16G adapter in slot 1 on Controller

Show Suggested Answer Hide Answer
Suggested Answer: A, C

To analyze the provided panic error, the two sections of AutoSupport that are essential for investigation are:

1. HA-RASTRACE.TGZ

What it is: HA-RASTRACE.TGZ contains HA (High Availability) system trace logs. It records hardware diagnostics, error traces, and the HA system's response to hardware events. These logs are critical when analyzing hardware-related panics, including those caused by PCI errors.

Why it's relevant to the panic: In the given panic message, the NMI (Non-Maskable Interrupt) error originates from a Qlogic FC 16G adapter. HA-RASTRACE.TGZ will provide detailed diagnostics, including the error reporting from the HA interconnect and other hardware diagnostics. Specifically, it may include information about how the system detected the PCI fault and any actions taken to protect the system state.

How to analyze:

Extract the HA-RASTRACE.TGZ file from the AutoSupport bundle.

Review hardware-related trace messages for entries associated with the PCI bus or the Qlogic FC adapter.

Look for specific error codes or keywords like PCI Error, NMI, or Qlogic.


NetApp's 'AutoSupport Logs and Diagnostics Guide' highlights HA-RASTRACE.TGZ as a primary resource for debugging hardware faults.

The 'Panic Troubleshooting Guide' for ONTAP systems specifies HA-RASTRACE as a key source for identifying NMI-related errors.

2. SSRAM-LOG

What it is: SSRAM-LOG records low-level hardware error details, including PCI device register states and uncorrectable memory errors. It is particularly useful for analyzing errors originating in peripheral hardware like network or storage adapters connected via PCI.

Why it's relevant to the panic: The panic message explicitly references a PCI Error NMI caused by a Qlogic FC adapter. SSRAM-LOG captures detailed state information for PCI devices, which can help identify whether the fault originated in the adapter hardware, the PCI bus, or another related component.

How to analyze:

Extract the SSRAM-LOG from the AutoSupport bundle.

Search for PCI-related errors, including the specific error source IDs (e.g., ErrSrcID(CorrSrc(0xf00),UCorrSrc(0x18))).

Review the log entries to confirm the root cause of the NMI.

The 'Hardware Diagnostics and Troubleshooting Guide for ONTAP' lists SSRAM-LOG as a key file for debugging PCI errors.

NetApp's documentation on PCI diagnostics emphasizes the use of SSRAM-LOG for validating hardware-level faults.

Contribute your Thoughts:

Ty
1 months ago
I'm gonna have to go with B and D on this one. The ALL-COREDUMP.XML file could have some juicy core dump info, and the PCI-HIERARCHY.XML will show me the PCI layout. Gotta love those comprehensive log files!
upvoted 0 times
Johnson
14 days ago
B) ALL-COREDUMP.XML sounds like a good place to start.
upvoted 0 times
...
...
Lang
1 months ago
This panic message sounds like a real head-scratcher. Time to put on my detective hat and dig through those log files! *adjusts imaginary hat*
upvoted 0 times
Hubert
3 days ago
Let's start by checking ALL-COREDUMP.XML first, it might have some clues.
upvoted 0 times
...
Theodora
8 days ago
B) ALL-COREDUMP.XML
upvoted 0 times
...
Olene
12 days ago
A) HA-RASTRACE.TGZ
upvoted 0 times
...
Hubert
19 days ago
Yes, those are the two sections where you can analyze the panic message.
upvoted 0 times
...
Hubert
1 months ago
I think you can find information in ALL-COREDUMP.XML and PCI-HIERARCHY.XML.
upvoted 0 times
...
...
Oretha
2 months ago
I'm going to go with options A and D. The PCI-HIERARCHY.XML file should have the details on the PCI adapter, and the HA-RASTRACE.TGZ might have some additional logs that could be helpful.
upvoted 0 times
Novella
16 days ago
Let's check out A and D first, they seem like the most relevant sections to look into.
upvoted 0 times
...
Layla
18 days ago
I agree, those two sections should provide the necessary information to troubleshoot.
upvoted 0 times
...
Nobuko
23 days ago
I think you're right, A and D seem like the best options to analyze the panic.
upvoted 0 times
...
...
Annett
2 months ago
I'm not sure, but I think PCI-HIERARCHY.XML could also have some useful information.
upvoted 0 times
...
Casie
2 months ago
I agree with Lenna, those two sections seem relevant for analyzing the panic message.
upvoted 0 times
...
Lenna
2 months ago
I think the information can be found in HA-RASTRACE.TGZ and ALL-COREDUMP.XML.
upvoted 0 times
...
Rex
2 months ago
Hmm, the HA-RASTRACE.TGZ and ALL-COREDUMP.XML files also seem like they could have relevant information. Better check those too just to be sure.
upvoted 0 times
Glory
2 months ago
User 2: Yeah, and we should also look into the ALL-COREDUMP.XML file for more information.
upvoted 0 times
...
Hildegarde
2 months ago
User 1: I think we should check the HA-RASTRACE.TGZ file.
upvoted 0 times
...
...
Leatha
2 months ago
The PCI Error NMI information would definitely be in the PCI-HIERARCHY.XML file. That's where I'd look first for any PCI-related errors.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77
a