HPE Integrated Lights-Out (iLO) provides an out-of-band management interface that allows administrators to manage servers remotely without relying on the operating system. The iLO Command Line Interface (CLI) is a powerful management interface that allows administrators to configure hardware settings, control server power, monitor system health, and perform maintenance tasks using commands.
Using HP iLO CLI commands, administrators can manage servers from anywhere over the network. This is especially useful when the operating system is down or the server cannot be accessed using standard remote tools such as SSH or RDP.
The CLI interface is commonly used in automated environments, troubleshooting scenarios, and remote data center management.
Accessing HPE iLO Command Line Interface
Connect to iLO using SSH
The easiest way to access the iLO command line interface is through SSH.
Example:
ssh Administrator@ILO-IP
Example:
ssh Administrator@10.10.10.100
After successful authentication you will see the iLO CLI prompt:
</>hpiLO->
You can now run various iLO CLI commands to manage the server hardware.
Connect to iLO from Onboard Administrator (OA)
If you are using HPE BladeSystem, you can connect to the server iLO from the enclosure’s Onboard Administrator.
First login to the OA using SSH:
ssh Administrator@OA-IP
Once logged in, connect to the desired blade server:
CONNECT SERVER 1
Example output:
Connecting to bay 1 ...
User:OAtmp-HPadmin logged-in to server1 (192.168.1.100)
iLO 4 Advanced for BladeSystem
Server Name: server1
Server Power: On
</>hpiLO->
You are now connected to the iLO CLI of the blade server.
Understanding the iLO CLI prompt
After connecting to the iLO interface, you will see the following prompt:
</>hpiLO->
This prompt indicates that you are inside the HPE iLO command line environment. From here you can execute different commands to configure or monitor the server.
The prompt may change slightly depending on firmware versions such as iLO4 or iLO5, but the command structure generally remains the same.
Navigating the iLO CLI command hierarchy
The iLO CLI follows a hierarchical object-based structure, where commands operate on different system paths.
For example:
show /map1/accounts1
This command displays all configured iLO user accounts.
Another example:
show /system1/cpu1
This command shows CPU information for the server.
Common CLI paths include:
| Path | Description |
|---|---|
/map1 |
Management processor configuration |
/system1 |
Server hardware information |
/system1/cpu1 |
CPU information |
/system1/bootconfig1 |
Boot configuration |
/system1/oemhp_power1 |
Power monitoring |
/map1/accounts1 |
iLO user accounts |
Understanding this hierarchy makes it easier to explore and execute HP iLO CLI commands efficiently.
HPE iLO CLI Quick Reference Table
The following table contains some of the most commonly used HPE iLO CLI commands for server management.
| Command | Description |
|---|---|
show /map1/accounts1 |
List iLO user accounts |
create /map1/accounts1 username=user password=pass |
Create new iLO user |
set /map1/accounts1/user password=newpass |
Change user password |
show /map1/firmware1 |
Show iLO firmware version |
show /map1/enetport1/lanendpt1/ipendpt1 |
Show network configuration |
set /map1/dhcpendpt1 EnabledState=yes |
Enable DHCP |
show /system1 |
Display system information |
show /system1/cpu1 |
Display CPU details |
show /system1/bootconfig1 |
Show boot configuration |
set /system1/bootconfig1/bootsource2 bootorder=1 |
Change boot order |
show /system1/oemhp_power1 |
Show power usage |
start /system1/led1 |
Enable server UID LED |
stop /system1/led1 |
Disable server UID LED |
show /map1/oemhp_vm1/cddr1 |
View virtual media status |
set /map1/oemhp_vm1/cddr1 oemhp_boot=connect |
Mount ISO image |
User and Account Management Commands
Create a new iLO user
You can create a new user account in iLO using the create command.
Example:
create /map1/accounts1 username=adminuser password=StrongPassword123
If the command completes successfully, iLO will return a status message indicating the user was created.
This command is commonly used when provisioning new servers or granting remote management access to administrators.
List all iLO users
To display all configured user accounts on the iLO interface, use the following command:
show /map1/accounts1
Example output:
/map1/accounts1
Targets
Administrator
adminuser
emergency
This command helps administrators verify which users currently have access to the iLO interface.
Change password for an existing user
If you need to reset or change a user password, use the set command.
Example:
set /map1/accounts1/adminuser password=NewSecurePassword
Password updates take effect immediately, allowing administrators to quickly recover or secure compromised accounts.
Delete an iLO user account
If a user no longer requires access to iLO, the account can be removed using the delete command.
Example:
delete /map1/accounts1/adminuser
After executing this command, the user will no longer be able to log in to the iLO interface.
Removing unused accounts improves security and reduces the risk of unauthorized access.
Modify user privileges and access rights
You can modify user privileges such as administrator access or operator permissions.
Example:
set /map1/accounts1/adminuser oemhp_privilege=Administrator
Privilege levels determine what actions the user can perform within the iLO interface, such as managing power operations or configuring network settings.
Network Configuration Commands
Show current iLO network configuration
To view the currently assigned IP address and network configuration:
show /map1/enetport1/lanendpt1/ipendpt1
Example output:
IPv4Address=10.10.10.100
SubnetMask=255.255.255.0
AddressOrigin=Static
This command is often used to confirm the configured IP address of the iLO interface.
Configure static IP address
To assign a static IP address to the iLO management interface:
set /map1/enetport1/lanendpt1/ipendpt1 IPv4Address=10.10.10.100 SubnetMask=255.255.255.0
After executing this command, the iLO controller will reset to apply the new network configuration.
Configure subnet mask and gateway
To configure the default gateway used by iLO:
set /map1/gateway1 AccessInfo=10.10.10.254
The gateway is required if administrators need to access the iLO interface from a different network.
Enable or disable DHCP
To check the current DHCP configuration:
show /map1/dhcpendpt1
Example output:
EnabledState=no
To enable DHCP:
set /map1/dhcpendpt1 EnabledState=yes
To disable DHCP and use static configuration:
set /map1/dhcpendpt1 EnabledState=no
Configure DNS servers
You can configure DNS servers to allow hostname resolution.
Example:
set /map1/dnsserver1 AccessInfo=8.8.8.8
You can configure multiple DNS servers if required.
Reset network configuration
If network settings are incorrect or unreachable, resetting the iLO controller may restore connectivity.
Example command:
reset /map1
After the reset completes, the iLO controller will restart and apply the new configuration.
Server Power Management Commands
Check server power status
To display the current server power state:
show /system1
Example output:
Server Power: On
This command helps administrators verify whether a server is currently powered on or powered off.
Power on the server remotely
To power on a server using iLO CLI:
start /system1
This command is useful when a server has been shut down or when powering systems during maintenance windows.
Gracefully power off the server
To initiate a graceful shutdown of the operating system:
stop /system1
This command sends a shutdown request to the operating system if it is supported.
Graceful shutdown prevents data loss and allows services to terminate properly.
Force power off the server
If the operating system becomes unresponsive, a forced shutdown may be required.
Example:
stop /system1 force
This command immediately powers off the server.
Administrators should use this command carefully because unsaved data may be lost.
Reset the server remotely
To perform a remote reboot of the server:
reset /system1
This command is commonly used during troubleshooting or after firmware updates.
It allows administrators to restart the server without physical access to the machine.
Boot Configuration Commands
Boot configuration commands allow administrators to control how the server starts and which device is used during boot. These HP iLO CLI commands are especially useful when performing remote OS installations or troubleshooting boot issues.
Show current boot order
To display the current boot configuration of the server, use the following command:
show /system1/bootconfig1
Example output:
/system1/bootconfig1
Targets
bootsource1
bootsource2
bootsource3
bootsource4
bootsource5
This command shows all configured boot sources available to the server.
Change boot order using CLI
To modify the boot order, change the bootorder value for a specific boot source.
Example:
set /system1/bootconfig1/bootsource2 bootorder=1
Example output:
bootsource2=BootFmDisk bootorder=1
bootsource1=BootFmCd bootorder=2
bootsource3=BootFmUSBKey bootorder=3
This command sets the disk as the first boot device.
Set boot device for next reboot
Sometimes administrators only want to change the boot device temporarily for the next reboot.
Example:
set /system1/bootconfig1/bootsource4 bootorder=1
This allows the server to boot from the network for tasks such as PXE boot installation.
Configure persistent boot order
To view the boot configuration of all devices, run:
show -all /system1/bootconfig1
Example output may include:
bootdevice=BootFmDisk
bootdevice=BootFmCd
bootdevice=BootFmUSBKey
bootdevice=BootFmNetwork
Administrators can adjust the boot order for each device to create a persistent boot sequence.
Switch boot mode between legacy and UEFI
To view the current boot mode:
show /system1/bootconfig1
Example output:
oemhp_bootmode=Legacy
Depending on firmware support, the boot mode may be switched to UEFI using:
set /system1/bootconfig1 oemhp_pendingbootmode=UEFI
Changing boot mode usually requires a server reboot to take effect.
Firmware Management Commands
Check installed iLO firmware version
To display the currently installed iLO firmware version:
show /map1/firmware1
Example output:
/map1/firmware1
version=2.55
name=iLO 4
date=Aug 16 2017
This command is often used during troubleshooting or when verifying firmware upgrades.
Display firmware details
To display detailed firmware information:
show /map1/firmware1
This output includes information such as firmware version, release date, and firmware name.
Administrators often check this information before performing upgrades or compatibility testing.
Load or upgrade iLO firmware
The iLO CLI provides the ability to load firmware packages if supported by the system.
Example:
load /map1/firmware1
Firmware upgrades are typically performed through the iLO web interface or through management tools, but the CLI can also initiate firmware loading when supported.
Administrators should always ensure firmware compatibility before applying upgrades.
Hardware Monitoring Commands
View CPU information
To display CPU details:
show /system1/cpu1
Example output:
name=Intel(R) Xeon(R) CPU E5-2640 v3
number_cores=8
threads=16
speed=2600MHz
status=OK
If the server has multiple processors, additional CPU entries may be available.
Example:
show /system1/cpu2
This command displays information about the second processor installed in the system.
Check system health status
To display the overall system health:
show /system1
Example output:
sys_health=OK
The system health status helps administrators quickly determine whether any hardware components are reporting errors.
View memory information
Memory information can be displayed using system monitoring commands.
Example:
show /system1
This command provides a summary of system hardware including installed memory and system status.
In many servers, memory health and configuration details are reported through system hardware objects.
Display hardware sensors and status
To view detailed hardware information:
show /system1
This command provides status information about several hardware components including:
| Component | Description |
|---|---|
| CPU | Processor status and configuration |
| Memory | Installed memory and health |
| Power | Power usage and status |
| System | Overall hardware health |
Hardware monitoring commands are commonly used during remote diagnostics and preventive maintenance.
Power Monitoring Commands
Power monitoring commands allow administrators to monitor server power usage and configure power-related settings using HPE iLO CLI commands. These commands help in tracking energy consumption and managing power behavior during server startup.
View average power consumption
To display the average power usage of the server:
show /system1/oemhp_power1 oemhp_AvgPower
Example output:
/system1/oemhp_power1
oemhp_AvgPower=82 Watts
This command provides the average power consumption calculated over a recent time window.
Administrators often use this information when monitoring data center power utilization.
View real-time power usage
To display the current power consumption:
show /system1/oemhp_power1
Example output:
oemhp_PresentPower=90 Watts
This command allows administrators to monitor real-time power usage of the server.
Power monitoring is particularly useful when diagnosing hardware issues or optimizing energy usage in data centers.
Configure automatic power-on delay
Automatic power-on delay helps prevent power surges when multiple servers start simultaneously.
To configure power-on delay:
set /system1/oemhp_power1 oemhp_auto_pwr=15
Example output:
status=0
status_tag=COMMAND COMPLETED
The value specifies the delay (in seconds) before the server powers on after power restoration.
Virtual Media Commands
Mount ISO image remotely
To mount an ISO image located on a remote HTTP server:
set /map1/oemhp_vm1/cddr1 oemhp_image=http://10.43.22.100/os-image.iso
After setting the image location, connect the virtual media:
set /map1/oemhp_vm1/cddr1 oemhp_boot=connect
Example output:
oemhp_connect=Yes
oemhp_boot=Always
This mounts the ISO image so the server can access it as a virtual CD/DVD.
Boot server from mounted ISO
To boot the server using the mounted ISO image:
set /map1/oemhp_vm1/cddr1 oemhp_boot=connect
Then reboot the server to start the installation or recovery process.
This is commonly used for remote OS installations.
Disconnect virtual media
After completing the installation or maintenance task, disconnect the ISO image:
set /map1/oemhp_vm1/cddr1 oemhp_boot=disconnect
Example output:
oemhp_connect=No
Disconnecting unused virtual media helps prevent accidental booting from external images.
Set one-time boot from virtual media
To configure the server to boot from virtual media only for the next reboot:
set /map1/oemhp_vm1/cddr1 oemhp_boot=once
This ensures that the server returns to the normal boot device after the installation process.
LED and Hardware Indicator Commands
View UID LED status
To check whether the UID LED is currently enabled:
show /system1/led1
Example output:
enabledstate=disabled
This command helps determine whether the identification LED is currently active.
Enable server UID LED
To enable the UID LED:
start /system1/led1
Example output:
status=0
status_tag=COMMAND COMPLETED
When enabled, the LED will illuminate on the physical server, making it easier to locate in the rack.
Disable server UID LED
To turn off the UID LED:
stop /system1/led1
Example output:
enabledstate=disabled
Disabling the LED after locating the server helps prevent confusion during maintenance operations.
Blade and Enclosure Information Commands
View blade slot and enclosure details
To display blade information:
show /map1/blade1
Example output:
bay_number=2
ip_address=192.168.1.10
mac_address=94:18:82:72:25:4b
This command shows the bay location of the blade inside the enclosure.
Check blade health status
The same command also displays health information:
show /map1/blade1
Example output:
sys_health=OK
If any hardware issues occur, the health status will indicate warnings or errors.
Retrieve enclosure IP information
The enclosure IP address is also displayed when checking blade details:
show /map1/blade1
Example output:
ip_address=192.168.1.10
This IP address typically refers to the Onboard Administrator managing the blade enclosure.
Administrators can use this information to access enclosure management and connect to other blade servers.
Useful iLO CLI Troubleshooting Commands
When managing servers remotely, administrators often rely on HPE iLO CLI troubleshooting commands to diagnose hardware issues, inspect configuration details, or recover from management interface failures.
These commands allow administrators to inspect system status and resolve issues without accessing the operating system.
Show full system configuration
To display complete system information, including hardware and configuration details:
show /system1
Example output may include:
name=ProLiant Server
status=OK
power=On
sys_health=OK
This command provides a quick overview of the server hardware and health status.
Administrators commonly use this command when performing remote diagnostics.
View event logs
iLO maintains internal event logs that record hardware and management events.
To view log entries:
show /system1/log1
Example output may include events such as:
System power restored
Temperature sensor warning
Fan speed adjustment
Reviewing event logs helps administrators detect hardware failures and identify system warnings.
Reset iLO controller
If the iLO interface becomes unresponsive or network connectivity issues occur, resetting the controller may restore normal operation.
Example command:
reset /map1
Example output:
Resetting iLO controller...
CLI session stopped
After executing this command, the iLO management processor will restart.
Restore iLO configuration to default
If the configuration becomes corrupted or inaccessible, administrators may restore the iLO settings to default values.
Example:
reset /map1 factory
This resets the iLO controller to factory defaults.
After the reset completes, administrators must reconfigure network settings and user accounts.
Security Related iLO Commands
Security configuration is an important part of managing servers through iLO. Administrators can configure access methods, monitoring settings, and alerting mechanisms using HP iLO CLI commands.
Enable or disable SSH access
To verify SSH access configuration:
show /map1/ssh
Example output:
EnabledState=yes
To disable SSH access:
set /map1/ssh EnabledState=no
To enable SSH access again:
set /map1/ssh EnabledState=yes
SSH access allows administrators to securely connect to the iLO command line interface.
Configure SNMP settings
SNMP monitoring enables external monitoring tools to collect server information.
To display current SNMP configuration:
show /map1/snmp1
Example output:
accessinfo1=0
readcom1=""
trapcom1=""
To configure an SNMP monitoring host:
set /map1/snmp1 accessinfo1=192.168.1.50
This allows monitoring systems to receive alerts from the server.
Configure alerting and monitoring
iLO can send alerts to monitoring platforms when hardware issues occur.
Example command:
set /map1/snmp1 oemhp_iloalert=yes
Example output:
SNMP settings modified.
This enables alert notifications for system events.
Set system contact and location
Administrators can configure system contact and location information for inventory management.
Set system location:
set /map1/snmp1 oemhp_systemlocation="Datacenter Rack A1"
Set system contact:
set /map1/snmp1 oemhp_systemcontact="Server Admin Team"
These settings are commonly used in monitoring dashboards and asset tracking systems.
Differences Between iLO4 and iLO5 CLI
Although iLO4 and iLO5 share a similar command structure, there are several differences in features, security capabilities, and management functionality.
Command compatibility
Most HPE iLO CLI commands follow the same object hierarchy across versions.
Common command paths such as:
/system1
/map1
/system1/cpu1
/system1/bootconfig1
remain consistent across both versions.
This ensures that administrators familiar with iLO4 CLI can easily adapt to iLO5 environments.
New features in iLO5 CLI
iLO5 introduces several enhancements compared to earlier versions.
Some improvements include:
| Feature | Description |
|---|---|
| Improved security | Stronger encryption and authentication mechanisms |
| HTML5 remote console | Modern browser-based console support |
| Enhanced monitoring | Better hardware telemetry and logging |
| REST API support | Integration with automation and orchestration tools |
These improvements make iLO5 more suitable for modern data center automation.
Common limitations in iLO4
While iLO4 remains widely used, it has several limitations compared to newer versions.
Examples include:
| Limitation | Description |
|---|---|
| Older encryption standards | Less advanced security options |
| Limited automation integration | Fewer API capabilities |
| Legacy remote console support | Older Java-based console options |
Administrators managing older servers should ensure firmware updates are applied regularly to maintain stability and security.
Frequently Asked Questions
1. How do I access the HPE iLO CLI?
You can access the iLO command line interface using SSH with the command ssh Administrator@ILO-IP or by connecting through the HPE BladeSystem Onboard Administrator using CONNECT SERVER.2. What is the iLO CLI prompt?
After logging in to iLO using SSH or OA, the command line prompt appears as </>hpiLO-> where you can run management commands.3. What can you do with HPE iLO CLI commands?
Using iLO CLI commands you can create users, configure network settings, manage firmware, control server power, mount ISO images, monitor hardware status, and configure boot options.4. Are iLO CLI commands the same for iLO4 and iLO5?
Most iLO CLI commands are similar between iLO4 and iLO5 because both follow the same command structure such as /system1 and /map1 paths, although some parameters may vary depending on firmware version.5. How do I connect to iLO from Onboard Administrator?
After logging into the enclosure OA CLI, run CONNECT SERVERSummary
HPE Integrated Lights-Out (iLO) provides powerful out-of-band server management capabilities that allow administrators to monitor and control servers remotely without relying on the operating system. Using the HPE iLO CLI, administrators can perform many important tasks such as managing user accounts, configuring network settings, controlling server power, mounting virtual media, monitoring hardware health, and adjusting boot configurations.
In this guide, we explored a wide range of HPE iLO 4 and iLO 5 CLI commands, including commands for user management, network configuration, firmware inspection, hardware monitoring, power management, and troubleshooting. These commands help administrators efficiently manage servers in data centers and remote environments.
Understanding the iLO command hierarchy, such as /system1 and /map1, makes it easier to navigate the CLI and discover additional commands available for server management.
By mastering these HP iLO CLI commands, administrators can quickly diagnose hardware issues, perform remote installations, manage server resources, and maintain reliable infrastructure operations.
