What are savecore and nosavecore AFF, ASA and FAS platforms?
Applies to
- AFF Systems
- ASA Systems
- FAS Systems
- ONTAP 9
Answer
- When a node panics, a core dump occurs.
- The system creates a core dump file that technical support can use to troubleshoot the problem.
- The architectural method by which the core dump file is saved depends on the NetApp AFF, ASA or FAS storage system model:
- SaveCore (also known as "savecore" or "save core")
- NoSaveCore (also known as "nosavecore" or "no save core").
- The following table outlines the differences between these two architectures for saving core dumps:
SaveCore Platform Attributes | NoSaveCore Platform Attributes |
Node root aggregate and node root volume are a larger size in order to store core dump files. | Node root aggregate and node root volume are smaller, since core dump files are not saved to the node's root volume. |
Cores are dumped to a spare disk (or sprayed across multiple spare disks) at the time of the panic. | Cores are dumped to a partition on the boot device (or a dedicated core dump device). |
After a node reboots, the core file is saved to the root volume. | The core dump in the boot device is considered "saved" when it is dumped. |
- The following table shows each platform model's architecture for core dump saving:
SaveCore Platforms | NoSaveCore Platforms |
AFF A200 | AFF A220, AFF C190, AFF A150, ASA A150 |
AFF A300 | AFF A250, AFF C250, ASA A250, AFF C250 |
AFF A700 (without the X9170A core dump device installed at system setup) | AFF A320, AFF A400, AFF C400, ASA A400, ASA C400 |
AFF A700s | AFF A700 (with the X9170A core dump device installed at system setup) |
FAS2620, FAS2650 | AFF A800, AFF C800, ASA A800, ASA C800 |
FAS8200 | AFF A900, ASA A900 |
FAS9000 | AFF A1K, AFF A90, AFF A70 |
FAS2720, FAS2750, FAS2820, FAS500f | |
FAS8300, FAS8700, FAS9500 |
Additional Information