Associating Events And Trapsinks; Defining Views - HP IBRIX X9720 Administrator's Manual

StoreAll software supports multiple trapsinks; you can define any number of trapsinks of any SNMP
version, but you can define only one trapsink per host, regardless of the version.
At a minimum, trapsink configuration requires a destination host and SNMP version. All other
parameters are optional and many assume the default value if no value is specified.
The format for creating a v1/v2 trapsink is:
ibrix_snmptrap -c -h HOSTNAME -v {1|2} [-p PORT] [-m COMMUNITY] [-s {on|off}]
If a port is not specified, the command defaults to port 162. If a community is not specified, the
command defaults to the community name public. The -s option toggles agent trap transmission
on and off. The default is on. For example, to create a v2 trapsink with a new community name,
enter:
ibrix_snmptrap -c -h lab13-116 -v 2 -m private
For a v3 trapsink, additional options define security settings. USERNAME is a v3 user defined on
the trapsink host and is required. The security level associated with the trap message depends on
which passwords are specified, the authentication password, both the authentication and privacy
passwords, or no passwords. The CONTEXT_NAME is required if the trap receiver has defined
subsets of managed objects. The format is:
ibrix_snmptrap -c -h HOSTNAME -v 3 [-p PORT] -n USERNAME [-j {MD5|SHA}]
[-k AUTHORIZATION_PASSWORD] [-y {DES|AES}] [-z PRIVACY_PASSWORD]
[-x CONTEXT_NAME] [-s {on|off}]
The following command creates a v3 trapsink with a named user and specifies the passwords to
be applied to the default algorithms. If specified, passwords must contain at least eight characters.
ibrix_snmptrap -c -h lab13-114 -v 3 -n trapsender -k auth-passwd -z priv-passwd

Associating events and trapsinks

Associating events with trapsinks is similar to associating events with email recipients, except that
you specify the host name or IP address of the trapsink instead of an email address.
Use the ibrix_event command to associate SNMP events with trapsinks. The format is:
ibrix_event -c -y SNMP [-e ALERT|INFO|EVENTLIST]
-m TRAPSINK
For example, to associate all Alert events and two Info events with a trapsink at IP address
192.168.2.32, enter:
ibrix_event -c -y SNMP -e ALERT,server.registered,
filesystem.created -m 192.168.2.32
Use the ibrix_event -d command to dissociate events and trapsinks:
ibrix_event -d -y SNMP [-e ALERT|INFO|EVENTLIST] -m TRAPSINK

Defining views

A MIB view is a collection of paired OID subtrees and associated bitmasks that identify which
subidentifiers are significant to the view's definition. Using the bitmasks, individual OID subtrees
can be included in or excluded from the view.
An instance of a managed object belongs to a view if:
The OID of the instance has at least as many sub-identifiers as the OID subtree in the view.
Each sub-identifier in the instance and the subtree match when the bitmask of the corresponding
sub-identifier is nonzero.
The Fusion Manager automatically creates the excludeAll view that blocks access to all OIDs.
This view cannot be deleted; it is the default read and write view if one is not specified for a group
with the ibrix_snmpgroup command. The catch-all OID and mask are:
OID = .1
Mask = .1
Using SNMP notifications 61