iLO watches the server hardware even when the OS is down. To hear about a failed drive, fan or power supply before users do, configure iLO to push alerts to you. iLO 5 (ProLiant Gen10/Gen10 Plus) and iLO 6 (Gen11) offer three channels: AlertMail (email), SNMP traps to your monitoring system, and remote syslog. All three are configured under Management in the iLO web interface.
Before you start
- An iLO account with the Configure iLO Settings privilege.
- iLO reachable on the management network, with DNS and a correct time source so alert timestamps make sense. See iLO first-time setup.
- For AlertMail: an SMTP server iLO can reach, and an account on it if authentication is required.
- For SNMP: the IP or FQDN of your SNMP manager, and a community string or SNMPv3 credentials.
- For remote syslog: a syslog server listening on UDP (and on TLS if you use iLO 6 with TLS).
Which channels need a licence
| Channel | Licence (per HPE iLO licensing guides) |
|---|---|
| AlertMail (email-based alerting) | iLO Advanced |
| Remote syslog | iLO Advanced |
| SNMP alerts | Not listed in the licensing table; the SNMP procedures in the user guides list only the Configure iLO Settings privilege, with no licence prerequisite. |
If you only have iLO Standard, SNMP traps are your option for push alerts.
Step 1 — Configure AlertMail
- Click Management in the navigation tree, then the Mail tab.
- Enable Enable iLO AlertMail.
- Fill in Recipient Email Address (several addresses separated by commas or semicolons, up to 260 characters), Sender Domain or Email Address, SMTP Port and SMTP Server.
- Leave Enable SMTP Secure Connection (SSL/TLS) on (it is the default) if your server supports STARTTLS; HPE recommends port 587 for secure connections. The default port is 25.
- If the SMTP server needs a login, enable Enable SMTP Authentication, enter the SMTP Username, tick Change SMTP Password and enter the password twice.
- Click Apply, then Send Test AlertMail.
- Check the iLO Event Log to confirm the test message was sent, and check the mailbox.
Note: iLO supports only explicit/opportunistic TLS (STARTTLS) SMTP servers. If you enter only a sender domain, iLO sends from <iLO Hostname>@<Sender Domain>, which your mail server must accept.
Step 2 — Configure SNMP alerts and destinations
Turn on traps
- Click Management. The SNMP Settings page opens.
- In SNMP Alerts, set Trap Source Identifier to iLO Hostname (the default, which stays with the system board) or OS Hostname.
- Enable SNMPv3 Trap (recommended) and/or SNMPv1 Trap. Optionally set Periodic HSA Trap Configuration so iLO repeats the health-status trap daily, weekly or monthly while a component stays failed or degraded.
- Click Apply.
Add an SNMPv3 user (for v3 traps)
- In SNMPv3 Users, click New.
- Enter Security Name, Authentication Protocol (MD5, SHA or SHA256; MD5 is not available in the FIPS or CNSA security states), Authentication Passphrase, Privacy Protocol and Privacy Passphrase (8 to 49 characters each).
iLO supports up to eight SNMPv3 users.
Add the destination
- In SNMP Alert Destinations, click New.
- Enter the manager's IP or FQDN in SNMP Alert Destination.
- Choose SNMP Protocol: SNMPv1 Trap (enter a Trap Community), SNMPv3 Trap or SNMPv3 Inform (select the SNMPv3 User).
- Click Add. iLO supports up to eight destinations.
- Back in SNMP Alerts, click Send Test Alert and confirm your manager received it.
The SNMP Settings section (System Location, System Contact, read communities) applies to the default Agentless Management and AMS configuration. If you also run an OS-based SNMP service with the System Management Assistant, configure matching settings on the host. To decode a trap, match its event class and code with the IML messages and troubleshooting guide listed in the user guide.
Step 3 — Configure remote syslog
Remote syslog forwards the Integrated Management Log (IML) and the iLO Event Log in RFC 5424 format. The screen differs between versions.
| iLO 5 user guide | iLO 6 user guide | |
|---|---|---|
| Where | Management > Remote Syslog tab | |
| Transport | UDP | UDP or TLS |
| Servers | One Remote Syslog Server box; separate several servers with semicolons; all share one port | Add one server at a time (IP address, protocol, port) |
| Default port | 514 | 514 (UDP), 6514 (TLS) |
iLO 5
- Click Management, then the Remote Syslog tab.
- Enable Enable iLO Remote Syslog, enter Remote Syslog Port and Remote Syslog Server, and click Apply.
- Click Send Test Syslog.
iLO 6
- Click Management, then the Remote Syslog tab, then Add.
- Enter the IP Address, select TLS or UDP, enter the Port, and click Add.
- For TLS, click Import under Certificate Information and paste the syslog server's Base64-encoded X.509 CA certificate.
- Click Send Test Syslog.
Testing and troubleshooting
- No test email: check the iLO Event Log for the send result, confirm the SMTP server accepts the sender address, and that port 25 or 587 is open from the iLO network.
- Send Test Alert is greyed out: both SNMPv1 Trap and SNMPv3 Trap are disabled.
- SNMPv3 Trap missing from the protocol list: enable SNMPv3 Trap and create at least one SNMPv3 user first.
- Cold Start traps arriving as broadcasts: iLO broadcasts the Cold Start Trap to the subnet when no destination is configured, SNMP is disabled, or destinations cannot be resolved. Fix the destination entries.
- TLS syslog fails on iLO 6: import the CA certificate of the syslog server.
Frequently asked questions
Can I get iLO email alerts with iLO Standard?
No. Email-based alerting and remote syslog are listed as iLO Advanced features in the HPE iLO licensing guides. Use SNMP traps, or install an iLO Advanced licence.
What does iLO send to remote syslog?
The IML and iLO Event Log entries, each starting with the iLO timestamp, iLO hostname and the subsystem that generated it.
Checklist
- Licence confirmed for AlertMail and remote syslog.
- AlertMail configured and a test email received.
- SNMPv3 user and alert destination added; test trap received by the manager.
- Remote syslog server added and a test message received.
- Know where to look next: the IML and the AHS log.
Skyline can supply, configure and maintain Dell, HPE and Huawei servers under an annual maintenance contract (AMC). Contact us.
Comments
0 total · 0 threads