Users Guide

b. Congure using severity as a parameter. For example, all informational events in storage category are assigned powero as
action, and email and SNMP as notications: racadm eventfilters set -c cmc.alert.storage.info -n
email,snmp
c. Congure using subcategory as a parameter. For example, all congurations under the licensing subcategory in the audit
category are assigned powero as action and all notications are enabled: racadm eventfilters set -c
cmc.alert.audit.lic -n all
d. Congure using subcategory and severity as parameters. For example, all Information events under the licensing
subcategory in the audit category are assigned powero as action and all notications are disabled:
racadm
eventfilters set -c cmc.alert.audit.lic.info -n none
4. Enable traps alerts:
racadm config -g cfgTraps -o cfgTrapsEnable 1 -i <index>
where <index> is a value between 1–4. CMC uses the index number to distinguish up to four congurable destinations for
traps alerts. Destinations may be specied as appropriately formatted numeric addresses (IPv6 or IPv4), or Fully-Qualied
Domain Names (FQDNs).
5. Specify a destination IP address to receive the traps alert:
racadm config -g cfgTraps -o cfgTrapsAlertDestIPAddr <IP address> -i <index>
where <IP address> is a valid destination, and <index> is the index value specied in step 4.
6. Specify the community name:
racadm config -g cfgTraps -o cfgTrapsCommunityName <community name> -i <index>
where <community name> is the SNMP community to which the chassis belongs, and <index> is the index value
specied in steps 4 and 5.
You can congure up to four destinations to receive traps alerts. To add more destinations, do the tasks in steps 2–6.
NOTE: The commands in steps 2–6 overwrites any existing settings congured for the index specied (1–4). To
determine whether an index has previously-congured values, type: racadm getconfig -g cfgTraps -i
<index>
. If the index is congured, values appear for the cfgTrapsAlertDestIPAddr and cfgTrapsCommunityName
objects.
7. To test an event trap for an alert destination, type:
racadm testtrap -i <index>
where <index> is a value between 1–4 representing the alert destination you want to test.
If you are not sure about the index number, run the following command:
racadm getconfig -g cfgTraps -i <index>
Conguring Email Alert Settings
When CMC detects a chassis event, such as an environmental warning or a component failure, it can be congured to send an email
alert to one or more email addresses.
Congure the SMTP email server to accept relayed emails from the CMC IP address, a feature which is normally turned o in most
mail servers due to security concerns. For instructions to congure in a secure manner, see the documentation that was provided
with the SMTP server.
NOTE: If your mail server is Microsoft Exchange Server 2007, make sure that iDRAC domain name is congured for the
mail server to receive the email alerts from iDRAC.
NOTE: Email alerts support both IPv4 and IPv6 addresses. The DRAC DNS Domain Name must be specied when using
IPv6.
If your network has an SMTP server that releases and renews IP address leases periodically, and the addresses are dierent, then
there is a duration when this property setting does not work due to change in the specied SMTP server IP address. In such cases,
use the DNS name.
110