CLI Guide

eventlters
Table 15. Details of eventlters
Description
Gets, sets, and displays the list of event lter settings.
To use this subcommand with the get option, you must have the CMC Login User privilege.
Synopsis
• racadm eventlters <eventlters command type>
• racadm eventlters get -c <alert descriptor>
• racadm eventlters set -c <alert descriptor>-n <notications>
NOTE: The general format of an alert descriptor:
cmc.alert.category.[subcategory].[severity]
where, category is mandatory, but subcategory and severity are optional. A severity cannot
precede a subcategory.
Valid category values are:
• System
• Cong
• Updates
• Audit
Valid severity values are:
• Critical
• Warning
• Informational
Valid examples of alert descriptors are:
• cmc.alert.all
• cmc.alert.audit
• cmc.alert.audit.lic
• cmc.alert.audit.warning
• cmc.alert.audit.lic.critical
Input
• get — Displays the list of event lter settings.
• set — Congures the actions and notications for a given event lter conguration.
• -c — Alert descriptor of the specic event lter.
• -n — The notication to be sent when the event occurs. Valid values are all, snmp, ipmi, email, or
none. You can append multiple notications separated by a comma. You cannot enter the values
all or none with other notications.
NOTE: If both event generation interval and notications are congured and there is an
error while conguring the notications, the event generation interval is not set. The valid
values are from 0–365. 0 disables the event generation.
Example
• Display all available event lter congurations:
racadm eventfilters get -c cmc.alert.all
• Display eventlter congurations for a specic category. For example, audit:
racadm eventfilters get -c cmc.alert.audit
RACADM Subcommand Details 27