External Chassis Fans Not Redundant
External Chassis Fans Not Redundant
Error Class : 0x0002 | Error Code: 0x0024
Symptom
External Chassis Fans Not Redundant (Chassis %1, Location %2).
Cause
One or more fans are not functioning or have been removed.
Action
Add a fan or replace the failed fan.
Be sure the fan configuration meets the functional requirements of the server.
- Be sure the fans are properly seated and working:
- Follow the procedures and warnings in the server documentation for removing the access panels and accessing and replacing fans.
- Unseat, and then reseat, each fan according to the proper procedures.
- Replace the access panels, and then attempt to restart the server.
- Be sure the fan configuration meets the functional requirements of the server.
- Be sure no ventilation issues exist. If the server is operated for an extended period of time with the access panel removed, airflow might be impeded, causing thermal damage to components.
- Be sure no POST error messages are displayed while booting the server that indicate temperature violation or fan failure information.
- Use iLO or an optional IML viewer to access the IML to see if any event list error messages relating to fans are listed.
- In the iLO web interface, navigate to the Information > System Information page and verify the following information:
- Click Fans, and then verify the fan status, fan speed, and airflow requirements.
- Click Temperatures, and then verify the temperature readings for each location on the Temperatures tab. If a hot spot is located, check the airflow path for blockage by cables and other material. A hot spot is not an absolute temperature but is relative to a component specification. Hot spot is defined as temperature on a sensor within 3°C of a Caution threshold listed on the Temperature tab.
- Replace any required non-functioning fans and restart the server.
- Be sure all fan slots have fans or blanks installed. For airflow requirements, see the server documentation.
- Verify the fan airflow path is not blocked by cables or other material.
For additional information, see the Troubleshooting Guide for HPE ProLiant Gen10 servers.
Hewlett Packard Enterprise has defined a set of rules that are used 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.
- Download the AHS log from the server.
- Log in to AHSV at http://www.hpe.com/servers/ahsv, and then enter your Passport account, which is required.
- Upload the AHS log to AHSV.
- Go to the AHSV dashboard page to confirm errors.
- Navigate to the Fault Detection Analytics page to identify additional error conditions and possible fixes.
After an AHS log is uploaded and if you still need support from Hewlett Packard Enterprise, you can use AHSV to create a support case.
- Go to the AHSV Dashboard and from the Navigation menu click Create a Support Case.
The Case Creation window is displayed.
- Fill out the contact information in the form.
- In the Issue section, enter:
- Problem Description
- Case Comments
- Click Submit. The support case is submitted to Hewlett Packard Enterprise Support for advanced diagnosis and troubleshooting. If you have missed any information, the block is displayed with a red border and a popup window stating what should be added.
- Hewlett Packard Enterprise Support will resolve the issue and report back to you.
See the Active Health System Viewer User Guide.
Support and Other Resources
For additional product information located in our user manuals, go to the Hewlett Packard Enterprise Library at http://www.hpe.com/info/enterprise/docs:
- User Guide
- Maintenance and Service Guide
- Troubleshooting
- Release Notes
Hewlett Packard Enterprise believes in being unconditionally inclusive. Efforts to replace noninclusive terms in our active products are ongoing.