The Redfish service generates asynchronous notifications
(events) that are defined by Redfish subscription for the eventing
service. These events are sent to an event destination by using HTTP
POST method. Events are generated when some significant change or
error condition typically of time critical nature occurs. When an
event occurs on the service, it notifies the clients. Redfish service
must be enabled and iDRAC must be configured to create event subscriptions
and to gain read-only privilege for viewing event subscriptions.
The iDRAC implementation of a Redfish service supports
only HTTPS notifications. In certain situations, iDRAC may not be
able to verify certificates sent by a peer. To handle such situations,
iDRAC can be configured to skip certificate verification by using
the attribute iDRAC.RedfishEventing.IgnoreCertificateErrors. This attribute can be configured to True or False (Default) using
RACADM or the WS-MAN interface. Set this attribute to True if certificate
validation is not required.
Redfish service provides Lifecycle and Alert events.
Lifecycle events may occur when resources are created, modified, or
destroyed. Alert events occur when a resource needs to indicate a
significant event. Alert events may be either directly or indirectly pertaining
to the resource. Examples of these kinds of event are a chassis
being opened, button being pressed, cable being unplugged, or threshold being exceeded. iDRAC supports up to 20 event subscriptions.
NOTE In this release,
iDRAC supports only Alert event notifications.
If an event delivery fails, the event service
of iDRAC retries delivering the failed event. The number of retries
and delivery intervals can be configured using the following attributes: