API Guide

SSL certificates of iDRAC
iDRAC includes a web server that uses the industry-standard SSL security protocol to transfer encrypted data over a network.
Built upon asymmetric encryption technology, SSL is widely accepted for providing authenticated and encrypted communication
between clients and servers to prevent eavesdropping across a network.
By default, the iDRAC web server has a Dell self-signed SSL digital certificate. Redfish service reuses this certificate installed
on the iDRAC web server. You can replace the default SSL certificate with a certificate signed by a well-known Certificate
Authority (CA). You can replace SSL certificates using the iDRAC interfaces such as web interface, RACADM, or WSMan.
For more information on managing SSL certificates of iDRAC, see the latest iDRAC User’s Guide available at Dell.com/
idracmanuals.
Eventing
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:
● iDRAC.RedfishEventing.DeliveryRetryAttempts
● iDRAC.RedfishEventing.DeliveryRetryIntervalInSeconds
Event delivery retry settings in RACADM
iDRAC.RedfishEventing.DeliveryRetryAttempts (Read or Write)
Description
Specifies the number of retry attempts made for Redfish event delivery
Legal values
Value ranges from 0 to 5
Default value
3
Write privilege
Configure iDRAC
iDRAC.RedfishEventing.DeliveryRetryIntervalInSeconds (Read or Write)
Description
Specifies the intervals (in seconds) of retry attempts made for Redfish event delivery
Legal values
Value ranges from 5 to 60
Default value
30
Write privilege
14
Redfish-based systems management