To turn off all Alert notifications for [email protected]:
<installdirectory>/bin/ibrix_event -d -e ALERT -m [email protected]
To turn off the
server.registered
and
filesystem.created
notifications for
[email protected] and [email protected]:
<installdirectory>/bin/ibrix_event -d -e server.registered,filesystem.created
-m [email protected],[email protected]
Testing email addresses
To test an email address with a test message, notifications must be turned on. If the address is
valid, the command signals success and sends an email containing the settings to the recipient. If
the address is not valid, the command returns an
address failed
exception.
<installdirectory>/bin/ibrix_event -u -n EMAILADDRESS
Viewing email notification settings
The
ibrix_event
command provides comprehensive information about email settings and
configured notifications.
<installdirectory>/bin/ibrix_event -L
Sample output follows:
Email Notification : Enabled
SMTP Server : mail.hp.com
From : [email protected]
Reply To : [email protected]
EVENT LEVEL TYPE DESTINATION
------------------------------------- ----- ----- -----------
asyncrep.completed ALERT EMAIL [email protected]
asyncrep.failed ALERT EMAIL [email protected]
Setting up SNMP notifications
X9000 Software supports SNMP (Simple Network Management Protocol) V1, V2, and V3.
NOTE:
Users of software versions earlier than 4.3 should be aware that the single
ibrix_snmp
command has been replaced by two commands,
ibrix_snmpagent
and
ibrix_snmptrap
.
If you have scripts that include
ibrix_snmp
, be sure to edit them to include the correct commands.
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
http://www.ietf.org
for more information. Note the following:
•
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.
Steps for setting up SNMP include:
•
Agent configuration (all SNMP versions)
•
Trapsink configuration (all SNMP versions)
36
Configuring cluster event notification
