API Guide

By default, the iDRAC web server has a Dell self-signed SSL digital certicate. Redsh service reuses this certicate installed on the iDRAC
web server. You can replace the default SSL certicate with a certicate signed by a well-known Certicate Authority (CA). You can
replace SSL certicates using the iDRAC interfaces such as web interface, RACADM, or WSMan. For more information on managing SSL
certicates of iDRAC, see the latest iDRAC User’s Guide available at Dell.com/idracmanuals.
Eventing
The Redsh service generates asynchronous notications (events) that are dened by Redsh subscription for the eventing service. These
events are sent to an event destination by using HTTP POST method. Events are generated when some signicant change or error
condition typically of time critical nature occurs. When an event occurs on the service, it noties the clients. Redsh service must be
enabled and iDRAC must be congured to create event subscriptions and to gain read-only privilege for viewing event subscriptions.
The iDRAC implementation of a Redsh service supports only HTTPS notications. In certain situations, iDRAC may not be able to verify
certicates sent by a peer. To handle such situations, iDRAC can be congured to skip certicate verication by using the attribute
iDRAC.RedfishEventing.IgnoreCertificateErrors. This attribute can be congured to True or False (Default) using
RACADM or the WS-MAN interface. Set this attribute to True if certicate validation is not required.
Redsh service provides Lifecycle and Alert events. Lifecycle events may occur when resources are created, modied, or destroyed. Alert
events occur when a resource needs to indicate a signicant 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 notications.
If an event delivery fails, the event service of iDRAC retries delivering the failed event. The number of retries and delivery intervals can be
congured using the following attributes:
• iDRAC.RedfishEventing.DeliveryRetryAttempts
• iDRAC.RedfishEventing.DeliveryRetryIntervalInSeconds
Event delivery retry settings in RACADM
iDRAC.RedshEventing.DeliveryRetryAttempts (Read or Write)
Description
Species the number of retry attempts made for Redsh event delivery
Legal values Value ranges from 0 to 5
Default value 3
Write privilege Congure iDRAC
iDRAC.RedshEventing.DeliveryRetryIntervalInSeconds (Read or Write)
Description
Species the intervals (in seconds) of retry attempts made for Redsh event delivery
Legal values Value ranges from 5 to 60
Default value 30
Write privilege Congure iDRAC
Eventing operations
The Redsh event service provides the following URIs:
Redsh-based
systems management 13