Reference Guide

Synopsis
racadm eventfilters <eventfilters command type>
racadm eventfilters get -c <alert category>
racadm eventfilters set -c <alert category> -a <action> -n <notifications>
racadm eventfilters set -c <alert category> -a <action> -r <recurrence>
racadm eventfilters test -i <Message ID to test>
NOTE: The general format of an alert category:
idrac.alert.category.[subcategory].[severity]
where, category is mandatory, but subcategory and severity are optional. A severity cannot precede
a subcategory.
Valid Category values are:
• All
• System
• Storage
• Updates
• Audit
• Config
• Worknotes
Definitions of the values are:
• System Health — System Health category represents all the alerts that are related to hardware within the
system chassis. Examples include temperature errors, voltage errors, and device errors.
• Storage Health — Storage Health category represents alerts that are related to the storage subsystem.
Examples include, controller errors, physical disk errors, and virtual disk errors.
• Updates — Update category represents alerts that are generated when firmware/drivers are upgraded or
downgraded..
NOTE:
This doesn’t represent firmware inventory.
• Audit — Audit category represents the audit log. Examples include, user login/logout information, password
authentication failures, session info, and power states.
• Configuration — Configuration category represents alerts that are related to hardware, firmware and software
configuration changes. Examples include, PCI-e card added/removed, RAID configuration changed, iDRAC
license changed.
• Work notes — Work notes represents an entry in the Lifecycle log. You can add a work note to the Lifecycle
Log to record comments for your reference. You can enter comments such as scheduled downtime or changes
made by administrators who work in different shifts for the later reference.
NOTE: idrac.all.all is not a valid sub category.
Valid Severity values are:
• Critical
• Warning
• Info
Valid examples of alert queries are:
• idrac.alert.all
• idrac.alert.audit
• idrac.alert.audit.lic
• idrac.alert.audit.warning
• idrac.alert.audit.lic.critical
This command does not support proxy parameters. To perform the operation with http and https, the proxy
parameters has to be configured in the lifecyclecontroller.lcattributes. Once these proxy parameters are configured,
they become the part of default configuration. They have to be removed to ignore the proxy parameters.
The valid proxy parameters :
• UserProxyUserName
• UserProxyPassword
• UserProxyServer
• UserProxyPort
• UserProxyType
52
RACADM Subcommand Details