The supported iLO 4 interfaces on an HPE ProLiant DL380 Gen9 do not provide an administrator command to stop one selected physical fan and later start it again. iLO and system firmware manage the redundant fan bank from temperature, configuration, and health data. Removing or failing one fan can make the remaining fans run faster and may reduce redundancy or trigger protective action.
Commands such as fan info or per-fan PWM controls found in community posts generally refer to modified firmware, private debug commands, or another iLO generation. COMMAND NOT RECOGNIZED on current supported iLO 4 firmware is not a syntax puzzle that should be solved by flashing an unofficial image.
What iLO 4 Supports
HPE’s official iLO 4 Scripting and Command Line Guide documents supported remote mechanisms including SSH/SMASH CLP, RIBCL XML, HPONCFG, IPMI, and RESTful tooling. These interfaces can report configuration and embedded-health information and perform documented administrative actions.
They do not expose a supported “fan 6 off” lifecycle for a DL380 Gen9. Fan speed is part of the server’s thermal-control system, not a normal per-device operator setting.
The iLO web interface is the clearest supported view. In the current iLO 4 user guide, review system information, fan status, temperature sensors, and the Integrated Management Log. Menu names can vary slightly with firmware and platform.
Why the Firmware Keeps Control
Server airflow is designed as a system. A particular fan may cool more than the component physically nearest to it, and the required speed changes with:
- processor and memory population;
- storage cages and controllers;
- PCIe cards and risers;
- inlet temperature and local sensor margins;
- missing blanks, baffles, or access panels;
- fan type, redundancy state, and firmware policy.
Stopping a fan for a “quiet test” changes pressure and airflow across the chassis. The controller may compensate by accelerating other fans, so the server becomes louder while operating with less redundancy.
Use SSH for Discovery, Not Unsupported Control
When connected to the iLO 4 SSH prompt, enter only commands—not the displayed prompt copied from a tutorial. Start with the built-in help and object discovery documented for the installed firmware:
help
show /
The available SMASH CLP targets and properties depend on platform, firmware, and privileges. Navigate only to targets returned by show; do not assume a path from another model exists. A health target may be readable without providing a writable per-fan property.
If fan info is rejected, that confirms it is not a supported command in that CLI environment. Do not downgrade or patch production management firmware to obtain it. iLO is a security boundary with access to power, console, firmware, and hardware health.
Read Fan Health Through Supported Channels
Use one or more of these methods:
- iLO web → Power & Thermal or System Information → Fans and Temperatures.
- Integrated Management Log for fan, sensor, power, and enclosure events.
- HPE’s documented embedded-health query through HPONCFG/RIBCL when collecting from the host OS.
- A supported monitoring platform using the iLO interface and schema appropriate to the firmware.
Record fan state, reported percentage or speed when available, inlet temperature, every sensor near caution, and the exact timestamp. A snapshot stating only “fan 6 is loud” cannot distinguish a worn bearing from firmware correctly reacting to another component.
Protect management data. Do not embed an iLO username or password directly in an XML file, command history, monitoring script, or article. Use the tool’s supported credential handling and restrict the management network.
Diagnose Fans Running at High Speed
HPE’s official cooling and fan troubleshooting guidance recommends checking fan and temperature tabs, IML events, firmware, airflow, baffles, component blanks, heatsinks, and correct fan types.
Follow this order:
1. Check health before noise
Look for a fan marked failed, degraded, or missing. Check whether another component is degraded. Redundancy loss can trigger higher speeds even when the remaining fans are healthy.
2. Check every temperature sensor
High speed can be a response to a sensor approaching its caution threshold. Do not look only at CPU temperature. Storage, memory, VRMs, chipset, PCIe area, and inlet sensors can drive cooling demand.
3. Restore the designed airflow path
Shut down according to the service guide before opening the chassis. Verify the access panel, air baffle, fan modules, risers, heatsinks, drive blanks, and PCIe slot blanks are present and seated correctly. Do not operate for an extended period with the panel removed; it can worsen airflow across components.
4. Review recent hardware changes
An unsupported PCIe card, storage controller, transceiver, or drive may lack thermal information expected by platform firmware. That does not justify overriding the fans. Confirm the component is supported, has current firmware, is in an approved slot, and receives the required airflow.
5. Update supported firmware deliberately
Review iLO, System ROM, Intelligent Provisioning, controller, and device firmware against HPE’s support matrix for the exact server. Take configuration backups and read release notes. Firmware updates are maintenance operations, not an emergency noise button.
6. Isolate mechanical noise
A fan that rattles or grinds at low speed may have a mechanical fault. HPE’s guidance is to check for loose objects and replace the fan. Use the server maintenance and service guide for safe hot-plug capability and replacement procedure; do not obstruct blades by hand.
Cooling Policies Are Not Per-Fan Switches
System ROM or platform settings may offer thermal configuration choices such as optimal cooling, increased cooling, or maximum cooling. Availability and names depend on the ROM and hardware. These policies affect the controller’s overall behaviour and do not grant safe manual control of one fan.
Before changing a policy, record the original setting and understand why a more aggressive policy was selected. Workload, ambient conditions, hardware population, or a vendor requirement may make it intentional.
Avoid Modified iLO Firmware for Fan Commands
Community firmware patches that expose hidden commands are outside HPE’s supported security and thermal model. Risks include management-controller compromise, loss of remote recovery, inability to apply security updates, corrupted flash, incorrect thermal response, and hardware damage.
A quieter lab server is not worth turning its out-of-band controller into an unverified firmware experiment. If acoustic limits are a primary requirement, use supported components and settings, relocate the server, improve room cooling, or choose hardware designed for the environment.
The supported answer is therefore intentionally narrow: read individual fan health, inspect the sensors and logs that explain speed, replace a failed or noisy module according to the service guide, and let firmware control the fan bank. Do not try to stop one DL380 Gen9 fan over iLO 4.
