PowerEdge: How to configure Email alerts and SNMP trap forwarding in the IDRAC console.

Purpose of Alerts 

• Real-Time Alerting 

• One to many management 

• Emails, Ticket Creating software, Secure Connect Gateway. 

Event Filters 

• Definitions for how the iDRAC treats different types of alerts.

• Configurable in Web Interface: Configuration - System Settings - Alerts

• Configurable using racadm racadm eventfilters 

• Configurable using Server Configuration Profile clone 

Testing Events 

• Under Configuration, System Settings and Test Event. 

• Corresponds with the Event Messages of the LC Log. 

• IDRAC acts as if an event happens and logs a second event saying it was a test. 

Alerts Option 1: SNMP 

• This is a commonly used protocol. 

• It uses UDP on port 162.

• Uses the SNMPv1 and v2 community string 

• It can use the SNMPv3 iDRAC user account.

• Required for Secure Connect Gateway.

• Only Alert type accepted by Open Manage Enterprise. 

Configuration in the user interface under Configuration - System Settings: 

• Enable Alerts and Event Filters. 

• Configure the SNMP destination and community string and iDRAC user account. 

• Set a customized port as needed.

Alerts Option 2: Remote Syslog 

• UDP Port 514 

• This is commonly used with third-party software like Splunk. 

Configuration in the user interface under Configuration > System Settings: 

• Enable Alerts and Event Filters 

• Remote Syslog Server Destination 

• Customize Port 

Alerts Option 3: Email 

• Use in scenarios where there are few servers 

• Covered in its own modules 

Alerts Option 4: Redfish Event and WS Event 

• Designed around building a custom Web Server listener to send events to 

• This is provided to enable a Redfish subscription, this feature is only supported using Redfish 

• To enable a WS Event subscription, the only option is WS-MAN 

Purpose of Email Alerts 

• It provides real time alerting 

• No need of any monitoring software 

• Provides visibility to new issues 

Email Sender 

• Reliant on Common Settings in the Network Settings by Default 

• If no iDRAC DNS name is populated in the network settings:   Email is sent as idrac-svctag@[ip_address]  

• If the iDRAC DNS name is populated, but DNS domain name is blank:   Email is sent as DNSRacName@[ip_address]  

• If the iDRAC DNS name is populated and DNS domain name is populated:   Email is sent as DNSRacName@DNSDomainName  

• If the iDRAC DNS name is populated, and DNS domain name is set to DHCP:   Email is sent as DNSRacName@DNSDomainName 

• On firmware 4.00.00.00 and newer this is configurable 

Configuration 

• Alerts Enabled 

• Event filters configured for Email 

• SMTP Server settings 

• SMTP Address to send to 

• DNS if using FQDN of mail server 

• Recommended: Common Settings 

The only Error will be the following.

• Error Message: RAC0225 

• This means that it was unable to connect to the mail server connector either due to incorrect configuration in the iDRAC or on the receiving connector of the mail server. Additional cause can be due to timeout. 

Troubleshooting Workflow 

• Rule Out DNS 

• If it used to work prior to 4.00.00.00, run racadm set iDRAC.RemoteHosts.ConnectionEncryption None 

• If one iDRAC does not work, copy configuration from a working iDRAC 

• Check SMTP configuration in the iDRAC 

• Ensure iDRAC can ping the mail server 

• Try with and without Authentication 

• Try making the iDRAC Mail Sender a valid mailbox for third-party mailboxes or scenarios where anonymous sending may be disabled 

• Check Mail server logs 

O365 Workaround 

• O365 will not allow mail to be sent from an invalid mailbox 

• Ensure that the sender has an existing O365 email address