7914appCLI1208.fm
Draft Document for Review March 28, 2011 12:24 pm
546
IBM System Storage DS3500: Introduction and Implementation Guide
out-band@nile.rivers.local
All in-band storage subsystems
in-band@nile.rivers.local
[ALERT SETTINGS - SPECIFIC DEVICES]
Storage arrays:
DS3524 ds3524-a.rivers.local ds3524-b.rivers.local
<None>
DS3512 ds3512-a.rivers.local ds35120-b.rivers.local
<None>
DS3524i colorado.rivers.local
host@nile.rivers.local
DS3512i colorado.rivers.local
host@nile.rivers.local
SMcli completed successfully.
amazon:~ # SMcli -x email:ds3524@nile.rivers.local -n DS3524
SMcli completed successfully.
amazon:~ # SMcli -x email:in-band@nile.rivers.local -r host_sa
SMcli completed successfully.
amazon:~ # SMcli -x email:out-band@nile.rivers.local -r direct_sa
SMcli completed successfully.
amazon:~ # SMcli -x email:host@nile.rivers.local -h colorado.rivers.local
SMcli completed successfully.
amazon:~ # SMcli -x email:global@nile.rivers.local
SMcli completed successfully.
amazon:~ #
17.6.4 SNMP alert recipients
SNMP alert recipients are handled very similarly to e-mail alert recipients, but the trap
parameter is used instead of the e-mail parameter. To specify the recipient, use an SNMP
community string followed by the SNMP trap receiver systems IP address or host name.
Example 17-12 shows how to configure SNMP trap recipients for a single DS3524 system,
in-band and out-of-band managed DS3500 systems, and a global trap recipient.
Example 17-12 SMcli - SNMP alert recipient
amazon:~ # SMcli -a trap:ds3524,nile.rivers.local -n ds3524
SMcli completed successfully.
amazon:~ # SMcli -a trap:in-band,nile.rivers.local -r host_sa
SMcli completed successfully.
Summary of Contents for DS3500
Page 2: ......
Page 5: ...iii Draft Document for Review March 28 2011 12 24 pm 7914edno fm ...
Page 789: ......