5. Reset iLO.
Resetting iLO is required because some Active Health System data is recorded to the log only during
iLO startup. Performing this step ensures that a complete set of data is available in the log.
6. Reboot the server.
Rebooting the server is required because some information, such as the operating system name and
version, is logged at server startup. Performing this step ensures that a complete set of data is
available in the log.
More information
Using AHSV to troubleshoot or open a support case on page 92
Intelligent Provisioning diagnostic tools on page 87
Downloading the AHS log through IP
For more information, see the Intelligent Provisioning user guide at
http://www.hpe.com/info/
intelligentprovisioning/docs.
Procedure
1. Open Intelligent Provisioning [F10] at boot-up.
2. Click Perform Maintenance.
3. Click Active Health System download.
4. Leave the range as the default or as instructed by the Hewlett Packard Enterprise technician.
5. Click Download.
More information
Using AHSV to troubleshoot or open a support case on page 92
Intelligent Provisioning diagnostic tools on page 87
Using AHSV to troubleshoot or open a support case
Hewlett Packard Enterprise has defined a set of rules to assist you with troubleshooting when you upload
an AHS log to Active Health System Viewer (AHSV), an online tool used to read, diagnose, and resolve
server issues.
For information on using the Active Health System Viewer, see the Active Health System Viewer User
Guide on the Hewlett Packard Enterprise website (http://www.hpe.com/support/ahsv-ug-en).
Procedure
1. Download the AHS log from the server.
For more information, see "Downloading the AHS log" in the Active Health System Viewer User Guide.
2. Log in to AHSV (http://www.hpe.com/servers/ahsv) with your HPE Passport credentials, and upload
the AHS log to AHSV.
3. Go to the AHSV dashboard to review errors.
4. Navigate to the Fault Detection Analytics page to identify additional error conditions and possible fixes.
Follow any recommended actions to clear the error.
5. If the issue persists, open a support case from the AHSV Dashboard.
92 Reports and logs