This is an old revision of the document!
HPE iLO 4 Password Recovery via Local Linux Host OS
This guide outlines how to safely recover administrative access to an HPE iLO 4 management processor using a local Linux host operating system after a motherboard replacement or lost credentials.
Context & Problem
When an HPE system board is replaced, the default iLO login credentials printed on the server chassis' physical pull-out tag no longer match the replacement hardware.
- The Trap: Performing a standard iLO factory reset will only revert the system to the unknown default password printed on the replacement motherboard's internal sticker, locking you out permanently.
- The Solution: Because you have root/administrator privileges on the local host operating system, you can leverage the internal PCIe system bus to communicate directly with the iLO hardware via IPMI, bypassing remote authentication completely.
Prerequisites & Environment
This method works on virtually any modern Linux-based host operating system (Debian, Ubuntu, RHEL/CentOS, Proxmox, TrueNAS SCALE, etc.).
- Uncomplicated Environments (TrueNAS SCALE, Proxmox VE, etc.): Storage and hypervisor appliances typically come with the core utility
ipmitoolpre-installed in the base OS image, making this an immediate out-of-the-box solution. - Standard Linux Distros (Ubuntu/Debian/RHEL): You may need to install the package first via your standard package manager:
# For Debian / Ubuntu: sudo apt update && sudo apt install ipmitool # For RHEL / CentOS / Rocky Linux: sudo dnf install epel-release && sudo dnf install ipmitool
⚠️ CRITICAL: Password Length Limitations ⚠️
Before injecting a password, you must adhere to a strict character limit rule to avoid locking yourself out of the Web UI:
- The Rule: Passwords must be between 8 and 20 characters long, containing a mix of uppercase, lowercase, and numbers.
- The Danger: The IPMI protocol has a maximum limit of 20 characters. If you pass a password longer than 20 characters to
ipmitool, it will accept it with zero errors but will silently truncate the password to the first 20 characters. When logging into the iLO Web UI later, entering your full untruncated password will fail.
Step-by-Step Recovery
Step 1: Load the IPMI Kernel Modules
Many modern operating systems turn off host-to-hardware IPMI communication by default to reduce background overhead. Run these commands to manually load the required Linux kernel drivers:
sudo modprobe ipmi_si sudo modprobe ipmi_devintf
Step 2: Audit the Active iLO Accounts
iLO stores its credentials using numeric Index IDs rather than just text strings. Query the user map on channel 2 to check the existing configuration on the motherboard:
sudo ipmitool user list 2
Expected output will list the User IDs alongside their privilege levels. For a replacement board, you will likely see the official factory account plus leftover profiles from the board's previous deployment:
ID Name Callin Link Auth IPMI Msg Channel Priv Limit 1 Administrator true false true ADMINISTRATOR 2 admin true false true ADMINISTRATOR 3 (Empty User) true false false NO ACCESS
Step 3: Choose an Authentication Path
Depending on your security and administrative preferences, choose Option A to clean and overwrite the existing structure, or Option B to safely add a new user without touching existing accounts.
Option A: Reclaim & Secure (Recommended)
This approach targets the standard HPE account name while shutting down security loopholes left by previous owners or tests.
1. Reset the Default HPE Administrator Account (ID 1)
Overwrite the unknown password for the official HPE account name. Ensure your new password adheres to the 8-20 character rule.
sudo ipmitool user set password 1 "SecurePass123!"
2. Disable Leftover Legacy Accounts (ID 2)
Leaving a rogue administrator account active from a previous deployment poses a security risk. Disable the leftover admin account completely to close the loophole:
sudo ipmitool user disable 2
Option B: Create a Brand-New User Account (Conservative)
If you prefer a conservative approach that leaves existing accounts completely untouched to avoid breaking potential external monitoring tools or automated scripts, you can provision an entirely new user account in an empty slot (e.g., ID 3).
Unlike overwriting an existing profile, a brand-new user starts with zero permissions. You must run a full 4-step sequence to name, password-protect, enable, and privilege-elevate the slot:
1. Set the Custom Username
sudo ipmitool user set name 3 your_new_username
2. Set the Password
Ensure your new password adheres to the 8-20 character rule.
sudo ipmitool user set password 3 "SecurePass123!"
3. Enable the Account
sudo ipmitool user enable 3
4. Grant Full Administrator Privileges
The integer 4 tells iLO to grant this slot full administrative tokens. Without this step, you will log into the web UI but see a blank screen with no access rights.
sudo ipmitool user priv 3 4
Quick Reference Table
| Action | Target ID | Command |
|---|---|---|
| Option A: Reset Default | ID 1 | sudo ipmitool user set password 1 “NewPassword” |
| Option A: Disable Legacy | ID 2 | sudo ipmitool user disable 2 |
| Option B: Full New User Setup | ID 3 | sudo ipmitool user set name 3 <user>sudo ipmitool user set password 3 <pass>sudo ipmitool user enable 3sudo ipmitool user priv 3 4 |
Note: Changes take effect instantly with zero server reboots or downtime required. You can immediately navigate to the iLO web interface in your web browser and log in using the newly configured credentials.