Users Guide
The IP alert destinations are congured.
Conguring SNMP Trap Alert Destinations Using RACADM
To congure IP alert destination using RACADM:
1 Open a serial/Telnet/SSH text console to CMC and log in.
NOTE: Only one lter mask may be set for both SNMP and email alerting. If you have already selected the lter mask, do
not perform task 2, and go to step 3.
2 Enable alert generation:
racadm config -g cfgAlerting -o cfgAlertingEnable 1
3 Specify the events lters by running the racadm eventfilters set command.
a To clear all the available alert settings, run the following command: racadm eventfilters set -c cmc.alert.all -n
none
b Congure using severity as a parameter. For example, all informational events in storage category are assigned powero as
action, and email and SNMP as notications:
racadm eventfilters set -c cmc.alert.storage.info -n
email,snmp
c Congure using subcategory as a parameter. For example, all congurations under the licensing subcategory in the audit
category are assigned powero as action and all notications are enabled: racadm eventfilters set -c
cmc.alert.audit.lic -n all
d Congure 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 notications 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 congurable destinations for traps
alerts. Destinations may be specied as appropriately formatted numeric addresses (IPv6 or IPv4), or Fully-Qualied 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 specied 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 specied in
steps 4 and 5.
You can congure 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 congured for the index specied (1–4). To determine
whether an index has previously-congured values, type: racadm getconfig -g cfgTraps -i <index>. If the index
is congured, 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>
Conguring
CMC To Send Alerts 125