Setup Guide

Server Configuration Profiles: User’s Guide
55 Server Configuration Profiles: Reference Guide | 456
racadm get -t xml -f export.xml -u user -p password -l //ip/share/ --includeCustomTelemetry
or
racadm get -t json -f export.json -u user -p password -l //ip/share/ --includeCustomTelemetry
NOTE: The ‘Include Custom Telemetry’ option can be combined with any other optional parameters.
This flag will add a new XML or JSON element to the template that is outside of the legacy schema. As a
result, the schema has been updated in iDRAC9 4.40.00.00 to accommodate this new feature. Templates
generated with this optional flag are not backwards compatible with older versions of iDRAC.
The custom Metric Report Definitions can be located at the end of the template under the
CustomComponents element in XML templates.
<SystemConfiguration>
<Component FQDD="iDRAC.Embedded.1">
<Attribute Name="Telemetry.1#EnableTelemetry">Enabled</Attribute>
</Component>
<CustomComponents>
<CustomMetricReportDefinitions>
…
</CustomMetricReportDefinitions>
</CustomComponents>
</SystemConfiguration>
Likewise, the CustomComponents block can be located towards the end of a JSON template.
],
"CustomComponents": {
"CustomMetricReportDefinitions": [
{
"@odata.type": "#MetricReportDefinition.v1_3_0.MetricReportDefinition",
Importing Telemetry custom Metric Report Definitions requires that the Datacenter license is installed on the
iDRAC and the Telemetry feature is enabled. The Telemetry feature can be enabled, configured, and applied
to custom Metric Report Definitions in a single SCP Import operation.
16.3 Troubleshooting
Below are examples of possible error scenarios when configuring Telemetry and custom Metric Report
Definitions.
16.3.1 Missing License
If the Datacenter license is missing, then the configuration results will show a SYS319 message ID for
CustomComponents.
SYS319 - The operation cannot be completed because either the required license is missing or expired.
racadm>>lclog viewconfigresult -j JID_034847857859
SeqNumber = 8049