Manualshelf

Users Guide

ManualsBrandsDell ManualsAlienwareOEMR R240
231232233234235236237238239240
Table Of Contents
● ReportTriggers
NOTE: Enable iDRAC Alerts and Redfish events for the specific hardware for which you need telemetry reports.
4. Redfish client makes subscription request to the Redfish EventService on iDRAC.
5. iDRAC generates and pushes the metric report or log/event data to the subscribed client when the predefined trigger conditions are
met.
Feature Constraints:
1. For security reasons, iDRAC supports only HTTPS-based communication to the client.
2. For stability reasons, iDRAC supports up to eight subscriptions.
3. Deletion of subscriptions is supported through Redfish interface only, even for the manual deletion by the Admin.
Behavior of Telemetry feature:
● iDRAC generates and pushes (HTTP POST) the Metric Report or log/event data to all the subscribed clients to the destination
specified in the subscription when the predefined trigger conditions are met. The clients receive new data only upon successful
subscription creation.
● The metric data includes the timestamp in ISO format, UTC time (ends in 'Z'), at the time of data collection from source.
● Clients can terminate a subscription by sending an HTTP DELETE message to the URI of the subscription resource through the
Redfish interface.
● If the subscription is deleted either by iDRAC or the client, then iDRAC does not send (HTTP POST) reports. If the number of delivery
errors exceeds predefined thresholds, then iDRAC may delete a subscription.
● If a user has Admin privilege, they can delete the subscriptions but only through Redfish interface.
● Client is notified about the termination of a subscription by iDRAC by sending 'Subscription terminated' event as the last message.
● Subscriptions are persistent and can remain even after iDRAC restarts. But, they can be deleted either by performing racresetcfg
or LCwipe operations.
● User interfaces like RACADM, Redfish, SCP, and iDRAC display the current status of the client subscriptions.
Identifier
GUID-B7EA71B5-C93B-4C87-B317-8C78F5FB8C35
Version 6
Status In translation
Serial Data Capture
iDRAC allows you to capture console redirection serial for later retrieval with the use of Serial Data Capture feature. This feature requires
iDRAC Datacenter license.
The purpose of Serial Data Capture feature is to capture the system serial data and store it so that the customer can later retrieve it for
debugging purpose.
You can enable or disable a serial data capture using RACADM, Redfish, iDRAC interfaces. When this attribute is enabled, iDRAC will
capture serial traffic received on Host Serial Device2 irrespective of serial Mux mode settings.
To enable / disable Serial Data Capture using iDRAC GUI, go to ［Maintainance］ > ［Diagnostics］ > ［Serial Data Logs］ page, and check
the box to enable or disable.
メモ:
● This attribute is persistent over iDRAC reboot.
● Firmware reset to default will disable this feature.
● While Serial Data capture is enabled, the buffer keeps getting appended with recent data. If user disables Serial capture and
enables it again, iDRAC starts appending from last update.
The System serial data capture starts when user enables the serial data capture flag from any of the interfaces. If serial data capture is
enabled after the system has booted, you have to reboot the system, so BIOS can see the new setting (console redirection Enabled
requested by iDRAC) to get the serial data. iDRAC will start the data capture continuously and stores to the shared memory with limit of
512 KB. This buffer will be circular.
メモ:
● For this feature to be functional, one must have Login privilege and System control privilege.
● This feature requires iDARC Datacenter license.
ネットワークデバイスのインベントリ、監視、および設定 237