FAQ

Overview of Redfish Eventing for iDRAC alerts
7 Manage iDRAC alerts by using the Redfish Eventing feature in YX3X and later PowerEdge servers
• SNMP traps—iDRAC alerts are configured to generate SNMP traps.
• Redfish alerts—All iDRAC alerts that can currently generate SNMP traps can also be configured to
generate Redfish event. Redfish events are supported for a larger spectrum of system events. In
combination with Redfish Lifecycle events and Telemetry, a complete monitoring solution can be built.
• SNMP traps—SNMP clients require the latest MIB to be imported to decipher the traps.
• Redfish alerts—Redfish event are in human readable format and do not have such a restriction.
• SNMP traps—SNMP is preferred by older SNMP based clients.
• Redfish alerts—Modern REST or Redfish clients such as OpenStack Ironic can easily consume Redfish
events.
• SNMP traps—The iDRAC SNMP implementation currently supports only GET and TRAP operations. SET
operations are not supported.
• Redfish alerts—The Redfish stack supports GET, PATCH, POST, DELETE, and PUT operations.
• SNMP traps—SNMPv2 or SNMPv3 can be used to encrypt packets and send traps securely.
• Redfish alerts—Redfish events use HTTPs to send events securely.
• SNMP traps—SNMP supports only the push type.
• Redfish alerts—Redfish supports push type and ServerSentEvents. SSE uses single HTTPS GET
Connection operation to subscribe and receive the alert events. This connection exists until either the
client or server closes it.
1.2 Prerequisites
Redfish alert events can be subscribed by following event subscription as defined by DMTF redfish
specification with no additional iDRAC licensing requirement from iDRAC8 2.30.30.30 and later versions.