CLI Guide

Example
• racadm deploy -m server-1 -s 192.168.0.20 255.255.255.0 192.168.0.1
The server was deployed successfully.
The deploy command generates an error when used on the extension slot of a multi-slot server.
• racadm deploy -m server-2 192.168.0.11 255.255.255.0 192.168.0.1
ERROR: Server in slot 9 is an extension of the server in slot 1.
• racadm deploy -m server-1 -u root -p <default root user password> -
s -6 ::/64 :: 10
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.
26 RACADM Subcommand Details