HPE iLO 5 and iLO 6 Complete Configuration Guide

3 Nov 2026, 17:4317 min readby ITYantra Admin

Complete guide to configuring HPE iLO 5 and iLO 6 management including network setup, user accounts, security, virtual media, and automation.

# HPE iLO 5 and iLO 6 Complete Configuration Guide

Introduction

HPE Integrated Lights-Out (iLO) is the embedded management processor in ProLiant servers. iLO provides out-of-band management, allowing administrators to monitor, configure, and control servers independently of the host operating system. This guide covers complete iLO 5 and iLO 6 configuration, from initial network setup to advanced security and automation.

You will learn:

iLO 5 vs iLO 6 feature differences
Initial network configuration
User account and authentication setup
Security hardening (certificates, SSH, SNMP)
Virtual media and remote console
Firmware management and updates
Automation via Redfish API and PowerShell
Monitoring and alerting configuration

Technical Background

iLO Architecture

iLO is a dedicated ARM-based management processor with its own:

Processor and memory
Network interface (dedicated or shared)
Firmware storage
Connection to the host server via internal bus

**Key Capabilities:**

Operates independently of host OS (works when server is off)
Out-of-band access on separate network
Hardware health monitoring
Remote power control (on/off/reset)
Virtual media (ISO, USB over network)
Remote console (KVM over IP)
Event logging and alerting

iLO 5 vs iLO 6

| Feature | iLO 5 | iLO 6 | |---------|-------|-------| | Introduced | Gen10 (2017) | Gen11 (2022) | | Processor | ARM-based | ARM-based (enhanced) | | Web Interface | HTML5 | HTML5 (modernized) | | Redfish API | v1.x | v1.x (enhanced) | | Security | Silicon Root of Trust | Enhanced SRoT | | Two-Factor Auth | Optional | Standard | | SSH Access | Yes | Yes | | SNMP | v1, v2c, v3 | v1, v2c, v3 (enhanced) | | Virtual Media | Yes | Yes (enhanced) | | iLO Federation | Yes | Yes | | HPE OneView Integration | Yes | Yes |

Authentication Methods

1. **Local Users:** Username/password stored in iLO 2. **Directory Authentication:** Active Directory, LDAP, RADIUS 3. **Two-Factor Authentication:** TOTP or hardware token (iLO 6 standard, iLO 5 advanced) 4. **Certificate-Based:** Client certificate authentication

iLO Licensing

| License | Features | |---------|----------| | iLO Standard | Basic remote management, power control, health monitoring | | iLO Advanced | Virtual media, remote console, iLO Federation, advanced security | | iLO 6 includes Advanced features by default on Gen11 |

Prerequisites

Hardware Requirements

HPE ProLiant server (Gen10+ for iLO 5, Gen11 for iLO 6)
iLO network port (dedicated or shared with LOM)
iLO license (Standard or Advanced)

Software Requirements

Web browser (Chrome, Firefox, Edge) for web interface
iLO Amplifier Pack or HPE OneView (optional, for bulk management)
HPE iLO PowerShell cmdlets (optional, for automation)
curl or Postman (for Redfish API testing)

Network Requirements

Dedicated management network VLAN
IP address for iLO (static or DHCP)
DNS server configuration
SMTP server for email alerts
Firewall rules for iLO ports (HTTPS 443, SSH 22)

Step-by-Step Implementation

Step 1: Initial iLO Network Configuration

**Purpose:** Configure iLO network access for remote management.

**Via iLO Web Interface (first time):** 1. Connect iLO management port to network 2. Find iLO IP via DHCP server or iLO discovery utility 3. Access `https://<ilo-ip>` in browser 4. Accept security warning (self-signed certificate) 5. Log in with default credentials (on iLO security label pull tab) 6. Change default password immediately 7. Configure network settings (static IP recommended)

**Via hponcfg Utility (Linux/Windows):**

# Create XML configuration
cat > ilo-network.xml << 'EOF'
<RIBCL VERSION="2.2">
  <LOGIN USER_LOGIN="Admin" PASSWORD="password">
    <RIB_INFO MODE="write">
      <MOD_NETWORK_SETTINGS>
        <DNS_DOMAIN_NAME VALUE="ityantra.co.in"/>
        <DHCP_ENABLE VALUE="N"/>
        <MOD_NIC_SETTINGS>
          <NET_SETTINGS VALUE="Y">
            <IP_ADDRESS VALUE="10.0.1.50"/>
            <NETMASK VALUE="255.255.255.0"/>
            <GATEWAY_IP_ADDRESS VALUE="10.0.1.1"/>
            <ENABLE_100 VALUE="N"/>
            <ENABLE_10 VALUE="N"/>
          </NET_SETTINGS>
        </MOD_NIC_SETTINGS>
        <MOD_DNS_SETTINGS>
          <DNS_SERVER_1 VALUE="10.0.1.10"/>
          <DNS_SERVER_2 VALUE="10.0.1.11"/>
          <DHCP_DNS_UPDATE VALUE="Y"/>
        </MOD_DNS_SETTINGS>
      </MOD_NETWORK_SETTINGS>
    </RIB_INFO>
  </LOGIN>
</RIBCL>

# Apply configuration
hponcfg -f ilo-network.xml -l ilo-network.log

**Via Redfish API:**

# Configure iLO network via Redfish
curl -k -u admin:password -X PATCH \
  -H "Content-Type: application/json" \
  -d '{
    "EthernetInterfaces": [{
      "Ipv4": {
        "AddressOrigin": "Static",
        "Address": "10.0.1.50",
        "SubnetMask": "255.255.255.0",
        "Gateway": "10.0.1.1"
      }
    }]
  }' \
  https://<ilo-ip>/redfish/v1/Managers/1/EthernetInterfaces/1

**Verification:** iLO accessible at configured IP address.

Step 2: Change Default Password and Configure Users

**Purpose:** Secure iLO access with strong credentials.

**Via Web Interface:** 1. Navigate to Administration → User Administration 2. Change default Administrator password 3. Create additional user accounts:

4. Assign appropriate privileges to each user

Read-only users for monitoring
Operator users for power control
Administrator users for full access

**User Privileges:**

**Administrator:** Full access to all iLO features
**Operator:** Power control, virtual media, remote console
**User:** View-only access to health and event logs
**Console:** Remote console access only

**Via ssacli/hponcfg:**

# Create user via hponcfg XML
cat > ilo-users.xml << 'EOF'
<RIBCL VERSION="2.2">
  <LOGIN USER_LOGIN="Admin" PASSWORD="password">
    <USER_INFO MODE="write">
      <ADD_USER
        USER_NAME="monitor"
        USER_PASSWORD="ChangeMe123!"
        LOGIN_PRIV="Y"
        REMOTE_CONS_PRIV="N"
        VIRTUAL_MEDIA_PRIV="N"
        VIRTUAL_POWER_PRIV="N"
        CONFIG_ILO_PRIV="N"
      />
    </USER_INFO>
  </LOGIN>
</RIBCL>
EOF

hponcfg -f ilo-users.xml -l ilo-users.log

**Verification:** Can log in with new user accounts at appropriate privilege levels.

Step 3: Configure Directory Authentication

**Purpose:** Centralize authentication via Active Directory or LDAP.

**Via Web Interface:** 1. Navigate to Administration → Directory Authentication 2. Enable directory authentication 3. Configure:

Directory server type (Active Directory, LDAP, RADIUS)
Server address and port
Bind account credentials
Base DN for user search
Group mapping to iLO roles

**Example Active Directory Configuration:**

Server: `dc01.ityantra.co.in`
Port: `389` (LDAP) or `636` (LDAPS)
Bind DN: `CN=ilo-bind,OU=Service Accounts,DC=ityantra,DC=co,DC=in`
Base DN: `DC=ityantra,DC=co,DC=in`
Group mapping: `CN=iLO-Admins,OU=Groups` → Administrator role

**Verification:** Can log in with Active Directory credentials.

Step 4: Security Hardening

**Purpose:** Secure iLO against unauthorized access.

**Certificate Configuration:**

# Generate CSR via iLO web interface
# Administration → Security → Certificate → Generate CSR
# Submit to CA, install signed certificate

# Or via Redfish
curl -k -u admin:password -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "Certificate": {
      "CertificateType": "PEM",
      "CertificateString": "-----BEGIN CERTIFICATE-----..."
    }
  }' \
  https://<ilo-ip>/redfish/v1/Managers/1/Security/1/Certificate

**SSH Configuration:** 1. Navigate to Administration → Security → SSH 2. Enable SSH access 3. Configure SSH port (default 22, change if desired) 4. Upload SSH public keys for key-based authentication 5. Disable password authentication for SSH (optional)

**SNMP Configuration:** 1. Navigate to Administration → Management → SNMP 2. Enable SNMP v3 (recommended) or v2c 3. Configure community strings (v2c) or users (v3) 4. Configure trap destinations for alerting

**Two-Factor Authentication (iLO 6 / iLO 5 Advanced):** 1. Navigate to Administration → Security → Two-Factor Authentication 2. Enable TOTP 3. Configure TOTP issuer name 4. Users enroll via authenticator app (Google Authenticator, Authy)

**Verification:** Security scan shows no vulnerabilities, all authentication methods working.

Step 5: Configure Email Alerts

**Purpose:** Receive notifications for hardware events.

**Via Web Interface:** 1. Navigate to Administration → Management → Email Alerts 2. Enable email alerts 3. Configure:

SMTP server address and port
SMTP authentication (if required)
Sender email address
Recipient email addresses
Alert severity levels (Critical, Warning, Informational)
Specific events to alert on

**Test Alert:** 1. Click "Send Test Email" 2. Verify receipt in inbox 3. Adjust severity levels as needed

**Verification:** Test email received successfully.

Step 6: Configure Virtual Media and Remote Console

**Purpose:** Enable remote installation and console access.

**Requirements:** iLO Advanced license

**Virtual Media (ISO mounting):** 1. Navigate to Remote Console & Media → Virtual Media 2. Click "Insert Media" 3. Select ISO file from local computer 4. Select drive type (CD/DVD or USB) 5. Click "Insert" 6. In server BIOS, set boot order to boot from virtual media

**Remote Console:** 1. Navigate to Remote Console & Media → Remote Console 2. Click "Launch Remote Console" 3. Download and run iLO Remote Console plugin 4. Connect to server console 5. Use for OS installation, BIOS configuration, troubleshooting

**Verification:** Can mount ISO and access remote console successfully.

Step 7: Configure Power Management

**Purpose:** Control server power remotely.

**Power Operations:** 1. Navigate to Server → Power 2. Available actions:

Power On
Power Off
Power Cycle (reset)
Reset (warm boot)
NMI (Non-Maskable Interrupt, for crash dump)
UID (Unit Identification, blink chassis light)

**Power Schedule:** 1. Navigate to Administration → Management → Power Schedule 2. Configure scheduled power on/off times 3. Useful for non-production servers to save power

**Verification:** Can remotely power cycle server successfully.

Step 8: Firmware Management

**Purpose:** Keep iLO and server firmware up to date.

**Via iLO Web Interface:** 1. Navigate to Administration → Firmware & OS → Firmware Update 2. Check for available updates 3. Upload SPP (Service Pack for ProLiant) ISO via virtual media 4. Or use HPE OneView for bulk firmware updates

**Via ssacli:**

# Check iLO firmware version
ssacli ctrl slot=0 show | grep -i ilo

# Or via web interface
# iLO version shown on dashboard

**Firmware Update Best Practices:** 1. Update iLO first, then system ROM, then other components 2. Schedule during maintenance window 3. Have backup power (UPS) during firmware update 4. Test in non-production first

**Verification:** All firmware at current SPP version.

Step 9: Automation via Redfish API

**Purpose:** Programmatic iLO management.

**Get iLO Information:**

curl -k -u admin:password \
  https://<ilo-ip>/redfish/v1/Managers/1/ | jq '.'

**Get Server Health:**

curl -k -u admin:password \
  https://<ilo-ip>/redfish/v1/Chassis/1/ | jq '.Status, .PowerState'

**Power Control:**

# Power off
curl -k -u admin:password -X POST \
  -H "Content-Type: application/json" \
  -d '{"ResetType": "PowerOff"}' \
  https://<ilo-ip>/redfish/v1/Managers/1/Actions/Manager.Reset

# Power cycle
curl -k -u admin:password -X POST \
  -H "Content-Type: application/json" \
  -d '{"ResetType": "PowerCycle"}' \
  https://<ilo-ip>/redfish/v1/Managers/1/Actions/Manager.Reset

**Virtual Media via Redfish:**

# Insert virtual media
curl -k -u admin:password -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "Image": "http://<web-server>/ubuntu.iso",
    "Inserted": true,
    "WriteProtected": false
  }' \
  https://<ilo-ip>/redfish/v1/Managers/1/VirtualMedia/1/Actions/VirtualMedia.InsertMedia

**Verification:** API calls return expected JSON responses.

Configuration Examples

Complete iLO Security Hardening Script

#!/bin/bash
# iLO security hardening
ILO_IP="10.0.1.50"
ILO_USER="Admin"
ILO_PASS="ChangeMe123!"

# 1. Change default password
echo "Changing iLO password..."
curl -k -u "$ILO_USER:$ILO_PASS" -X PATCH \
  -H "Content-Type: application/json" \
  -d '{"Password": "NewSecurePassword123!"}' \
  https://$ILO_IP/redfish/v1/Managers/1/Accounts/1

# 2. Enable SSH key authentication
# (Upload via web interface or Redfish)

# 3. Configure SNMP v3
echo "Configuring SNMP..."
curl -k -u "$ILO_USER:$ILO_PASS" -X PATCH \
  -H "Content-Type: application/json" \
  -d '{
    "SNMP": {
      "AuthenticationProtocol": "HMAC_SHA256",
      "PrivacyProtocol": "AES_CBC_128"
    }
  }' \
  https://$ILO_IP/redfish/v1/Managers/1/ManagerNetworkProtocol/1

# 4. Enable email alerts
echo "Configuring email alerts..."
curl -k -u "$ILO_USER:$ILO_PASS" -X PATCH \
  -H "Content-Type: application/json" \
  -d '{
    "Email": {
      "SMTPServer": "smtp.ityantra.co.in",
      "FromAddress": "ilo@ityantra.co.in",
      "Enable": true
    }
  }' \
  https://$ILO_IP/redfish/v1/Managers/1/ManagerNetworkProtocol/1

PowerShell iLO Automation

# Install HPE iLO cmdlets
Install-Module -Name HPE.iLO.Cmdlets

# Connect to iLO
$iloSession = Connect-ILORest -IpAddress 10.0.1.50 -User Admin -Password "Password"

# Get server health
Get-ILORest -Uri "/redfish/v1/Chassis/1/" | Select-Object Status, PowerState

# Power cycle server
Invoke-ILORest -Uri "/redfish/v1/Managers/1/Actions/Manager.Reset" -Method Post -Body @{ResetType="PowerCycle"}

# Create user
Invoke-ILORest -Uri "/redfish/v1/Managers/1/Accounts/" -Method Post -Body @{
    UserName = "monitor"
    Password = "ChangeMe123!"
    RoleId = "ReadOnly"
}

Disconnect-ILORest -Session $iloSession

Verification

iLO Connectivity Verification

# Ping iLO
ping -c 4 10.0.1.50

# HTTPS access
curl -k -I https://10.0.1.50/

# SSH access
ssh admin@10.0.1.50

# Redfish API
curl -k -u admin:password https://10.0.1.50/redfish/v1/

**Expected:** All commands succeed, HTTPS certificate valid (or trusted), SSH key or password authentication works.

User Access Verification

# Test read-only user
curl -k -u monitor:password https://10.0.1.50/redfish/v1/Chassis/1/

# Test administrator user
curl -k -u admin:password https://10.0.1.50/redfish/v1/Managers/1/

# Verify privileges match expectations

Alert Verification

1. Trigger a test event (remove drive cable, change BIOS setting) 2. Verify email alert received 3. Verify event logged in iLO event log

Troubleshooting

| Scenario | Symptom | Possible Cause | Diagnostic | Corrective Action | Verification | |----------|---------|----------------|------------|-------------------|--------------| | Cannot access iLO web interface | Connection timeout | Network issue, iLO service stopped, wrong IP | `ping <ilo-ip>`, check iLO physical LED | Check network, reset iLO (hold ID button 5+ seconds) | iLO web interface loads | | Default password doesn't work | Login failed | Password already changed, wrong account | Check iLO security label, contact previous admin | Password reset via physical access (jumper on system board) | Can log in with new password | | Certificate warning | Browser shows security warning | Self-signed certificate | Browser certificate details | Install CA-signed certificate or add exception | No certificate warning | | Cannot mount virtual media | ISO won't mount | iLO Standard license (no virtual media), browser issue | Check license status, try different browser | Upgrade to iLO Advanced, use different browser | ISO mounted successfully | | Email alerts not received | No emails arriving | SMTP misconfiguration, firewall blocking port 25 | Test SMTP connection, check iLO event log | Fix SMTP settings, open firewall port | Test email received | | Redfish API returns 401 | Authentication failed | Wrong credentials, account locked | Verify credentials, check iLO user status | Reset password, unlock account | API calls succeed | | Slow iLO web interface | Pages load slowly | Network latency, iLO under load, browser issue | Check network, restart iLO service | Optimize network, reduce concurrent sessions | Web interface responsive | | iLO firmware update fails | Update interrupted | Power loss during update, incompatible SPP | iLO event log, SPP version check | Recover iLO firmware, reapply update | Firmware at correct version | | SNMP traps not received | No traps in monitoring system | Wrong community string, trap destination | SNMP walk test, check firewall | Fix SNMP configuration, open UDP 162 | Traps received | | Two-factor auth not working | TOTP codes rejected | Time sync issue, wrong secret | Check iLO time, regenerate secret | Sync iLO time with NTP, re-enroll TOTP | TOTP authentication works |

Best Practices

1. **Change default password immediately** — Default credentials are publicly documented and a major security risk.

2. **Use dedicated management network** — Isolate iLO traffic from production traffic.

3. **Enable SNMP v3** — SNMP v1/v2c sends community strings in cleartext.

4. **Configure email alerts** — Critical hardware events should generate immediate notifications.

5. **Use directory authentication** — Centralized user management with AD/LDAP.

6. **Keep iLO firmware updated** — Security vulnerabilities are patched in firmware updates.

7. **Restrict iLO access** — Firewall management network, only allow admin subnets.

8. **Install CA-signed certificates** — Avoid browser warnings and man-in-the-middle risks.

9. **Document iLO IP addresses** — Include in asset tracking and runbooks.

10. **Test recovery procedures** — Practice iLO password reset and firmware recovery in lab.

Conclusion

HPE iLO 5 and iLO 6 provide comprehensive out-of-band management for ProLiant servers. Proper configuration of network, authentication, security, and alerting is essential for reliable server operations. The Redfish API enables automation at scale, while iLO Advanced features (virtual media, remote console) simplify OS installation and troubleshooting.

Key security considerations include changing default passwords, using directory authentication, enabling two-factor authentication, and restricting network access. Regular firmware updates and monitoring ensure iLO remains a trustworthy management path.

References

HPE iLO 5 User Guide: https://www.hpe.com/info/ilo5-docs
HPE iLO 6 User Guide: https://www.hpe.com/info/ilo6-docs
HPE Redfish API Documentation: https://developer.hpe.com/
HPE iLO PowerShell Cmdlets: https://www.hpe.com/info/ilo-powershell
HPE iLO Security Best Practices: https://www.hpe.com/info/ilo-security
Redfish Specification: https://www.dmtf.org/standards/redfish

#hpe#ilo#ilo-5#ilo-6#server-management#remote-management#infrastructure