Dissociating Events And Email Addresses; Using Snmp Notifications - HP IBRIX X9720 Administrator's Manual

1. Select the applicable email address in the Current destination email addresses box.
2. Click Select to copy the email address to the Update events for addresses box.
3. To add more email addresses, repeat steps 1 and 2. Multiple entries are comma-separated.
4. Select the applicable events. You can select any combination of events: all Alert, Warning,
or Info events; all events of one type plus a subset of another type; or a subset of all types.
5. Click OK when finished.
To remove an event from an email address:
You cannot delete an email address directly from this dialog box. However, you can remove events
from an email address:
1. Select the applicable email address in the Current destination email addresses box.
2. Click Select to copy the email address to the Update events for addresses box.
3. Ensure that there are no events selected for this email address.
4. Click OK. Because no events are associated with the email address, the email address is
deleted.
To add events for a new email address:
1. Enter the new email address in the Update events for addresses box.
2. Select the applicable events.
3. Click OK when finished.
To manage events using the CLI, use the ibrix_event command. See the HP StoreAll OS CLI
Reference Guide for more information.

Dissociating events and email addresses

To remove the association between events and email addresses, use the following command:
ibrix_event -d [-e ALERT|WARN|INFO|EVENTLIST] -m EMAILLIST
For example, to dissociate event notifications for admin@hp.com:
ibrix_event -d -m admin@hp.com
To turn off all Alert notifications for admin@hp.com:
ibrix_event -d -e ALERT -m admin@hp.com
To turn off the server.registered and filesystem.created notifications for
admin1@hp.com and admin2@hp.com:
ibrix_event -d -e server.registered,filesystem.created -m admin1@hp.com,admin2@hp.com

Using SNMP notifications

StoreAll software supports SNMP (Simple Network Management Protocol) V1, V2, and V3.
Whereas SNMPV2 security was enforced by use of community password strings, V3 introduces
the USM and VACM. Discussion of these models is beyond the scope of this document. Refer to
RFCs 3414 and 3415 at
In the SNMPV3 environment, every message contains a user name. The function of the USM
is to authenticate users and ensure message privacy through message encryption and
decryption. Both authentication and privacy, and their passwords, are optional and will use
default settings where security is less of a concern.
With users validated, the VACM determines which managed objects these users are allowed
to access. The VACM includes an access scheme to control user access to managed objects;
context matching to define which objects can be accessed; and MIB views, defined by subsets
of IOD subtree and associated bitmask entries, which define what a particular user can access
in the MIB.
http://www.ietf.org for more information. Note the following:
Using SNMP notifications 59