This section is a complement to the generic Redfish® Event Service section. It contains some specificities of its implementation in HPE iLO 5 and HPE iLO 6 management controllers.
Information concerning iLO events is also present in the iLO Telemetry section.
HPE iLO 5 implements a version of the Redfish Event Service older than version 1.3. As such, events are based on the EventTypes property, not on the RegistryPrefixes property.
However, the generic flow for subscribing, receiving, and interpreting events is the same as the newer versions of the standard. Refer to the Redfish® Event Service section for more information.
The following example creates an event subscription in an HPE iLO 5 based server. As the Alert event type is part of the body request, the event listener will receive Alert Event Log messages asynchronously.
POST /redfish/v1/EventService/Subscriptions/
Refer to the Telemetry Service for examples explaining how to receive periodical metric report events.
HPE iLO 6 implements a version of the Redfish Event Service that is newer than version 1.3. As such, events are based on the RegistryPrefixes property described in the Redfish Event Service section. Refer to this generic section for the numerous standard examples.
Refer to the Telemetry Service for example, explaining how to to receive periodical metric reports.
You can create Syslog subscriptions under /redfish/v1/EventService/Subscriptions/ using Syslog subscription type and SyslogTLS or SyslogUDP protocols. HPE iLO sends iLO logs over a secure TCP connection to the subscribed entity. The setup must have an authenticated TCP session between the Syslog server and the Syslog client. The packets must be encrypted and sent over a TCP session. The Syslog server (receiving entity) decrypts the payload and renders the logs to HPE iLO (Syslog client).
The Syslog Subscription feature is available from HPE iLO 6 version 1.68.
SubscriptionTypeandProtocolproperties.NoteIf you do not add the above properties to the Payload, HPE iLO considers those subscriptions as Redfish event subscriptions.
Import Certificate Authority (CA) certificate. HPE iLO uses the CA certificate to authenticate the remote syslog server (destination). To import a CA certificate in HPE iLO, perform a
POSToperation like in the following example or use the iLO restcertificate import --ca_certcommand:POST /redfish/v1/eventservice/actions/oem/Hpe/Hpeeventservice.importCAcertificate/You can use the methods presented in this section to format the CA certificate properly.
If you do not add the SubscriptionType property to the Payload, HPE iLO doesn't consider the certificate for the syslog subscriptions.
POST /redfish/v1/eventservice/subscriptions/In the payload if you do not provide a SubscriptionType or if you set it with any value other than the Syslog, HPE iLO does not consider the payload for the Syslog subscriptions.
The following example lists the members of the Event Service collection, containing both Redfish events, with an integer ID, and Syslog subscriptions noted as SyslogID. The following example retrieves the properties of a Syslog subscription, introduced in the HPE iLO 6 version 1.68. It includes the SyslogFilters[] array with the LogFacilities and LowestSeverity properties.
GET /redfish/v1/eventservice/subscriptionsGET /redfish/v1/eventservice/subscriptions/syslogID/PATCH /redfish/v1/eventservice/subscriptions/syslogID/You cannot perform PATCH operation on the SubscriptionType property.
The following example retrieves the members of the imported CA certificates, including the CA certificate used for the Syslog subscription. The last example retrieves the properties of a specific member. For more information on certificates, refer to the HPE Security Service.
GET /redfish/v1/eventservice/CAcertificates/GET /redfish/v1/eventservice/CAcertificates/cacertId