HPE ProLiant DL380 Gen10, User Manual

Page: 188 / 201

Troubleshooting
NMI functionality
An NMI crash dump enables administrators to create crash dump files when a system is hung and not responding to traditional
debugging methods.
An analysis of the crash dump log is an essential part of diagnosing reliability problems, such as hanging operating systems,
device drivers, and applications. Many crashes freeze a system, and the only available action for administrators is to cycle the
system power. Resetting the system erases any information that could support problem analysis, but the NMI feature
preserves that information by performing a memory dump before a hard reset.
To force the OS to initiate the NMI handler and generate a crash dump log, the administrator can use the iLO Generate NMI
feature.
Troubleshooting resources
Troubleshooting resources are available for HPE Gen10 and Gen10 Plus server products in the following documents:
• Troubleshooting Guide for HPE ProLiant Gen10 and Gen10 Plus servers provides procedures for resolving common
problems and comprehensive courses of action for fault isolation and identification, issue resolution, and software
maintenance.
• Error Message Guide for HPE ProLiant Gen10 servers and HPE Synergy provides a list of error messages and information
to assist with interpreting and resolving error messages.
• Error Message Guide for HPE ProLiant Gen10 Plus servers and HPE Synergy provides a list of error messages and
information to assist with interpreting and resolving error messages.
• Integrated Management Log Messages and Troubleshooting Guide for HPE ProLiant Gen10 and Gen10 Plus servers and
HPE Synergy provides IML messages and associated troubleshooting information to resolve critical and cautionary IML
events.
To access troubleshooting resources for your product, see the Hewlett Packard Enterprise Information Library:
• For Gen10 servers, see
https://www.hpe.com/info/gen10-troubleshooting.
• For Gen10 Plus servers, see https://www.hpe.com/info/gen10plus-troubleshooting.
Troubleshooting
188