How to configure email alert for HP Server

How to Configure Email Alerts for HP Servers: A Complete DevOps Guide

If you're running HP ProLiant servers in production, you need real-time alerts when hardware fails. The built-in HP Management Agents can send email notifications for critical events like disk failures, fan malfunctions, or power supply issues - but the configuration process isn't always intuitive. I've set this up across hundreds of HP servers in enterprise environments, and in this guide, I'll walk you through the exact steps I use, including the gotchas that most documentation misses.

We'll cover the full process: installing the required HP software, configuring SMTP settings, selecting which events to monitor, and verifying the alerts actually work. By the end, you'll have a robust monitoring system that pages your team when hardware starts failing - before it takes down your applications.

Prerequisites

Before we begin, ensure you have:

• A physical HP ProLiant server (Gen8 or newer recommended - older generations may have different software versions)
• Windows Server 2012 R2 or newer installed (this guide focuses on Windows; Linux steps differ slightly)
• Administrator access to the server
• Access to an SMTP server (either internal like Exchange or external like SendGrid/SMTP2GO)
• The HP Service Pack for ProLiant (SPP) ISO or executable - download the latest version from HPE's SPP page
• A valid email address for receiving alerts (preferably a distribution list or monitoring alias)

I recommend testing this in a non-production environment first, as some steps require reboots that could impact running services.

Step 1: Install HP Management Agents

The HP Management Agents are part of the HP Service Pack for ProLiant (SPP). This package includes all the drivers and utilities needed to monitor and manage HP hardware.

1.1 Download and Mount the SPP

Download the latest SPP ISO from HPE's website. For this guide, we'll assume you're using the executable version (setup.exe) rather than the ISO.

1.2 Run the Installer

Double click setup.exe under HP Support Packs

The installer will launch with a welcome screen. Click Next to begin.

1.3 System Component Check

The installer will scan your system for compatible hardware and existing HP software:

The tool starts checking the system components
Click OK

This step verifies that your server is a supported HP model and checks for any existing HP software that might need updating. If you see warnings about unsupported hardware, double-check that you're using the correct SPP version for your server generation.

1.4 Installation Options

On the installation options screen:

Keep default settings. Click Install

The default settings will install all necessary components, including:

• HP Insight Management Agents
• HP Insight Management WBEM Providers
• HP System Management Homepage
• HP Event Notifier (this is the component we need for email alerts)

If you're working in a secure environment, you might want to customize the installation to exclude components you don't need, but for most use cases, the defaults are fine.

1.5 Reboot the Server

After installation completes, you'll see:

Reboot the server now or schedule a different time to reboot the server (click Exit)

I recommend rebooting immediately to ensure all components initialize properly. The HP Management Agents won't function correctly until after a reboot.

Step 2: Configure Email Alerts

Now that the software is installed, we'll configure the Event Notifier to send email alerts when hardware issues occur.

2.1 Launch Event Notifier Configuration

Log back into the server and navigate to:

HP Management Agents - Event Notifier Config

You can find this in the Start Menu under "HP Management Agents" or by searching for "Event Notifier Config".

2.2 Welcome Screen

The configuration wizard will launch. Click Next on the welcome screen.

2.3 SMTP Server Configuration

On the SMTP Configuration screen, you'll need to enter your mail server details:

Type server name on from address. Mail server is smtp.bmogc.net. Click Next

Replace these values with your actual SMTP server details:

• From Address: The email address that will appear as the sender (e.g., "hp-alerts@yourcompany.com")
• Mail Server: Your SMTP server address (e.g., "smtp.yourcompany.com" or "smtp.sendgrid.net")
• Port: Typically 25, 587 (TLS), or 465 (SSL) depending on your SMTP server configuration
• Authentication: Check this if your SMTP server requires credentials

For production environments, I recommend using an internal SMTP relay with authentication to avoid being flagged as spam. If you're using a cloud SMTP service like SendGrid, you'll need to use their specific server address and port (usually 587 with TLS).

2.4 Add Recipients

Click Add to configure who should receive the alerts:

Click Add to add recipient

In the recipient dialog:

Type the display name and address. Click OK

Enter:

• Display Name: A friendly name like "IT Operations Team"
• Email Address: The actual email address (e.g., "it-ops@yourcompany.com")

I recommend using a distribution list or monitoring alias rather than individual email addresses. This makes it easier to manage who receives alerts as team members change.

2.5 Select Events to Monitor

This is the most critical part of the configuration. Click the Events button:

Click on Events button

You'll see a list of all possible events that can trigger alerts. The default selection includes many informational events that can generate noise. For production environments, I recommend:

Select events to send alert. Click Remove all and then select Errors/failures events only. After select events, click "set as default" button.

Here are the specific event categories I typically monitor:

Category	Events to Monitor
Storage	Disk failure, array accelerator battery failed, logical drive failed
Power	Power supply failed, redundant power supply lost
Cooling	Fan failed, fan degraded, thermal shutdown imminent
Memory	Uncorrectable memory error, memory module failed
Processor	Processor failed, processor degraded
Network	Network adapter failed
System	System overheating, system power fault

After selecting your events, click Set as Default to save these settings for future use.

2.6 Complete Configuration

Add any additional recipients if needed, then click Finish to save your configuration:

Add another recipient and click Finish

The Event Notifier service will restart to apply your changes. This typically takes 30-60 seconds.

Common Pitfalls and Troubleshooting

Over the years, I've encountered several issues that can prevent HP email alerts from working correctly. Here are the most common problems and how to fix them:

3.1 SMTP Server Connection Issues

Symptoms: No emails are received, and the Event Notifier logs show connection timeouts or authentication failures.

Solutions:

• Verify SMTP server address and port: Double-check that you're using the correct server address and port. Many organizations have different SMTP servers for internal vs. external use.
• Test SMTP connectivity: From the server, use telnet to test the connection:

  telnet smtp.yourcompany.com 25
  

  If the connection fails, check your firewall rules and network connectivity.
• Authentication issues: If your SMTP server requires authentication, ensure you've checked the authentication box in the Event Notifier configuration and entered valid credentials. Some SMTP servers require the full email address as the username.
• TLS/SSL requirements: If your SMTP server requires TLS or SSL, you may need to configure this in the Event Notifier settings. The HP Management Agents don't always support modern TLS versions, so you might need to use an internal SMTP relay that supports older protocols.

3.2 Event Notifier Service Not Running

Symptoms: The Event Notifier configuration wizard completes successfully, but no alerts are generated.

Solutions:

• Check service status: Open Services.msc and verify that the "HP Insight Event Notifier" service is running. If not, start it manually.
• Verify service account: The service should be running under the Local System account. If it's configured to run under a specific user account, ensure that account has the necessary permissions.
• Check dependencies: The Event Notifier service depends on the "HP Insight Foundation Agents" service. Ensure this service is also running.
• Review logs: Check the Event Notifier logs at C:\Program Files\HP\Insight Management Agents\logs\EventNotifier.log for errors.

3.3 Alerts Not Triggering for Specific Events

Symptoms: Some events trigger alerts while others don't, even though they're selected in the configuration.

Solutions:

• Verify event selection: Some events are nested under categories. For example, disk failure alerts might be under "Storage" → "Smart Array" → "Logical Drive". Expand all categories to ensure you've selected the specific events you want.
• Check event thresholds: Some events (like temperature warnings) have thresholds that can be adjusted. You might need to modify these in the HP System Management Homepage.
• Update firmware: Older firmware versions might not report certain events correctly. Check for firmware updates for your server's iLO and system ROM.
• Test with known events: To verify the alerting system is working, you can trigger a test event. For example, you can temporarily unplug a redundant power supply to generate a power-related event.

3.4 Emails Going to Spam

Symptoms: Alerts are being sent but ending up in spam folders.

Solutions:

• Configure SPF/DKIM: If you're using an external SMTP service, ensure your domain has proper SPF and DKIM records configured.
• Use a dedicated subdomain: Consider using a subdomain like "alerts.yourcompany.com" for monitoring emails to improve deliverability.
• Whitelist the sender: Add the "from" address you configured to your email system's whitelist.
• Use an internal SMTP relay: For the most reliable delivery, set up an internal SMTP relay that forwards emails to your primary mail server.

3.5 Performance Impact

Symptoms: The HP Management Agents are consuming excessive CPU or memory resources.

Solutions:

• Adjust polling intervals: In the HP System Management Homepage, you can adjust how frequently the agents poll for hardware status. The default is usually 60 seconds, which is fine for most environments.
• Limit monitored components: If you're monitoring many servers, consider reducing the number of components being monitored or increasing the polling interval.
• Update to latest version: Newer versions of the HP Management Agents are generally more efficient. Check for updates.
• Check for memory leaks: Some older versions had memory leak issues. If you notice the memory usage growing over time, schedule regular service restarts.

How to Verify Your Configuration

After completing the configuration, it's crucial to verify that the alerting system is working correctly. Here's how I test HP email alerts:

4.1 Test SMTP Configuration

First, verify that the SMTP settings are correct:

1. Open the Event Notifier Configuration tool again.
2. Navigate to the SMTP configuration screen.
3. Click the Test button (if available in your version).
4. If there's no test button, you can trigger a test alert by temporarily changing an event selection and then changing it back.

Check the recipient email address for the test message. If you don't receive it within 5 minutes, check the Event Notifier logs for errors.

4.2 Trigger a Test Event

The most reliable way to test is to trigger an actual hardware event. Here are some safe ways to do this:

• Unplug a redundant power supply: If your server has redundant power supplies, unplugging one will generate a power-related event without causing downtime.
• Remove a hot-swappable fan: On servers with redundant cooling, removing one fan will trigger a cooling event.
• Simulate a temperature event: In the HP System Management Homepage, you can sometimes adjust temperature thresholds to trigger a warning (be careful with this method).

After triggering the event, check:

1. That the event appears in the HP System Management Homepage under "System Status".
2. That an email is received at the configured address within 5 minutes.
3. That the email contains the correct event details.

4.3 Check Event Notifier Logs

Review the Event Notifier logs for any errors or warnings:

C:\Program Files\HP\Insight Management Agents\logs\EventNotifier.log

Look for entries like:

[INFO] Successfully sent email alert for event: Power Supply 1 Failure

If you see errors like "Failed to connect to SMTP server" or "Authentication failed", revisit your SMTP configuration.

4.4 Verify Service Health

Check that all required HP services are running:

sc query "HP Insight Event Notifier"
sc query "HP Insight Foundation Agents"

Both services should show a state of "RUNNING". If not, start them manually:

net start "HP Insight Event Notifier"
net start "HP Insight Foundation Agents"

Key Takeaways

• Use the latest HP Service Pack for ProLiant: Always download the most recent version from HPE's website to ensure compatibility with your server hardware and operating system.
• Be selective with event monitoring: Configure alerts only for critical errors to avoid alert fatigue. Focus on events that indicate actual hardware failures rather than informational messages.
• Test SMTP connectivity thoroughly: SMTP configuration is the most common point of failure. Verify connectivity, authentication, and email delivery before relying on the system for production alerts.
• Monitor the Event Notifier service: Set up monitoring for the HP Insight Event Notifier service to alert you if it stops running. A failed service means no alerts will be sent.
• Document your configuration: Keep records of which events are being monitored, SMTP server details, and recipient email addresses. This makes troubleshooting and maintenance much easier.

FAQ

Can I configure HP email alerts on Linux servers?

Yes, but the process is different. For Linux servers, you'll need to:

1. Install the HP Management Agents for Linux (available in the SPP ISO).
2. Configure the HP Event Notifier using the command-line tools (hpevntnotifier).
3. Edit the configuration file at /opt/hp/hp-snmp-agents/cma.conf to specify SMTP settings and event filters.
4. Restart the HP SNMP agents service.

The Linux version doesn't have a GUI configuration tool, so you'll need to work with configuration files and command-line utilities.

How do I configure HP email alerts for multiple servers?

For multiple servers, I recommend:

1. Standardize your configuration: Create a documented procedure for configuring alerts, including exact event selections and SMTP settings.
2. Use configuration management: Tools like Ansible, Puppet, or Chef can automate the installation and configuration of HP Management Agents across multiple servers.
3. Centralize monitoring: Consider using HP Systems Insight Manager (HP SIM) or a third-party monitoring tool like Nagios or Zabbix to centralize alert management.
4. Test each server: Even with automation, verify that alerts are working on each server, as hardware differences might require configuration adjustments.

For large environments, I've written PowerShell scripts that use the HP CLI tools to configure alerts consistently across hundreds of servers.

Why aren't my HP email alerts working after a server reboot?

This is usually caused by one of these issues:

1. Service not set to automatic: Check that the "HP Insight Event Notifier" service is set to start automatically:

   sc config "HP Insight Event Notifier" start= auto
   

2. Service dependencies not met: The Event Notifier service depends on the "HP Insight Foundation Agents" service. Ensure both are set to start automatically.
3. Network not ready: If your SMTP server is on the network, the Event Notifier service might start before network connectivity is established. You can set the service to "Automatic (Delayed Start)" to give the network time to initialize.
4. Configuration lost: In rare cases, the configuration might not persist after a reboot. Verify that your settings are still present in the Event Notifier Configuration tool after rebooting.

Can I integrate HP email alerts with my existing monitoring system?

Yes, there are several ways to integrate HP alerts with other monitoring systems:

1. SNMP traps: The HP Management Agents can send SNMP traps for hardware events. Configure your monitoring system to receive and process these traps.
2. Email parsing: Configure your monitoring system to parse the HP alert emails and generate alerts in your primary monitoring tool.
3. API integration: For advanced integration, use the HP iLO RESTful API to query hardware status and integrate with your monitoring system.
4. Syslog forwarding: Configure the HP Management Agents to forward events to a syslog server, which can then be processed by your monitoring system.

For most environments, I recommend using SNMP traps as they provide the most reliable and timely integration with monitoring systems like Nagios, Zabbix, or Prometheus.

🛒 Recommended gear on Amazon

Disclosure: some links above are affiliate links — if you buy through them I may earn a small commission at no extra cost to you. Thanks for supporting the channel!